aspose file tools*
The moose likes Websphere and the fly likes Issues in Migrating from Websphere 5.1 to 6.1 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Issues in Migrating from Websphere 5.1 to 6.1" Watch "Issues in Migrating from Websphere 5.1 to 6.1" New topic
Author

Issues in Migrating from Websphere 5.1 to 6.1

Ridhav Mahajan
Greenhorn

Joined: Oct 23, 2008
Posts: 11
I am facing an issue after migrating from websphere 5.1 .We have a layered architecture and one EJB layer calls another EJB layer.
We have RAD 6 where we have deployed our EJB applications to 5.1 test environment to which we hit through Junits.
And these EJB's for further processing calls other EJB's which are deployed on some remote server which has now been upgraded to WAS 6.
Now my test case can succesfully lookup the EJB deployed on local test server , but these further cant lookup the EJB deployed on WAS 6.1.

(EJBHome Failure: Unable to obtain Home reference for ...)
WsnInitCtxFac W NMSV0602E: Naming Service unavailable. A communications error occurred


After this, I deployed our EJB's to WAS 6.1 server and and then hit through Junit and it was working fine. I could get the EJB deployed on our Was6.1 which further succesfully hit the other EJB's.

So Can this be the case that the context lookup properties are different or some other issue as because of time , we cant move to RAD 7 right now which has embedded WAS 6.1.

Can this be the case that EJB deployed on one server cant hit the other server's EJB or this is because of difference of JDK version?

Please suggest

Ridhav
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18669
    
    8

I don't know the answer to your question, but if your two theories are (1) configuration problem (2) doesn't work in Java 5, then I can say that (2) is not the problem.
Bhaskar Ramaraju
Greenhorn

Joined: May 23, 2008
Posts: 2
May be useful
http://www-01.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q1=NMSV0602E&uid=swg21287083&loc=en_US&cs=utf-8&lang=en
Ridhav Mahajan
Greenhorn

Joined: Oct 23, 2008
Posts: 11
@Paul
Thanks for the reply, even i think so, as i checked further, this issue seems to be coming because of the naming service running at some other port in Websphere 6.1 than in 5.1 test environment, But still cud'nt solve it.

Ridhav Mahajan
Greenhorn

Joined: Oct 23, 2008
Posts: 11

Thanks for the link, I will check these tommorow
Ridhav Mahajan
Greenhorn

Joined: Oct 23, 2008
Posts: 11
Not able to do as i have checked the bootstrap port config and its correct.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Issues in Migrating from Websphere 5.1 to 6.1