It's not a secret anymore!
The moose likes Websphere and the fly likes Help WAS 5.1 Wrong Context Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Help WAS 5.1 Wrong Context " Watch "Help WAS 5.1 Wrong Context " New topic

Help WAS 5.1 Wrong Context

Sybil Santos-Burgan

Joined: Jan 30, 2004
Posts: 15
Help Please!!!
I have 3 servers created in WAS
1. default server1
2. serverQA
3. serverPROD
I have an duplicate copies of an ear file attached to each, serverQA and serverPROD When I run this the lookups are looking in server1 rather than the serverQA or serverProd that it is attached to. The ear file is not on server1 So I get this error:

[4/1/04 12:10:18:880 CST] 45da68a0 SystemErr R javax.naming.NameNotFoundException: Context: testserver-jeff/nodes/testserver-jeff/servers/server1, name: org/inccrra/ned/ejb/service/SecUserEJBService: First component in name SecUserEJBService not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL
Where I can I change so the Context Context: testserver-jeff/nodes/testserver-jeff/servers/server1 is to the right server?
Help Please!!!
Thanks in Advance!
Jeanne Boyarsky
author & internet detective

Joined: May 26, 2003
Posts: 33102

Is your ejb using explicit port numbers?

[OCA 8 book] [Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Sybil Santos-Burgan

Joined: Jan 30, 2004
Posts: 15

Thanks, I figured out what my problem was.
I didn't specify the bootstrap address used by my new server for my PROVIDER_URL. If you don't specify it goes to the default port 2089 which happen to be pointing to another server. This link helped me realize my problem.
I agree. Here's the link:
subject: Help WAS 5.1 Wrong Context
jQuery in Action, 3rd edition