Cheers, Martijn,
Twitter.
Andr�s Irmer wrote:Same problem here... Any solution?
I was experiencing this problem, and after running an ethernet trace found that my WebSphere server was responding with a redirect to itself using it's host name, which was not resolvable from the client.
Once I added the hostname into the <windows>\system32\drivers\etc\hosts file, it worked just fine.
So check to make sure the name ( not ip) that your host thinks it is can be resolved by anybody trying to lookup jndi resources on it.
Sibi Joseph wrote:hi
DID anyine get a solution. i am facing the same problem with WAS 7.0.0.7 running on a redhat enterprise linux 5.5
please share
thanks and Regards
sibi
Andr�s Irmer wrote:Same problem here... Any solution?
Sibi Joseph wrote:hi Saw the following post
http://www.ecmplace.com/viewtopic.php?f=39&t=9906&start=0
I was experiencing this problem, and after running an ethernet trace found that my WebSphere server was responding with a redirect to itself using it's host name, which was not resolvable from the client.
Once I added the hostname into the <windows>\system32\drivers\etc\hosts file, it worked just fine.
So check to make sure the name ( not ip) that your host thinks it is can be resolved by anybody trying to lookup jndi resources on it.
Sibi Joseph wrote:hi
DID anyine get a solution. i am facing the same problem with WAS 7.0.0.7 running on a redhat enterprise linux 5.5
please share
thanks and Regards
sibi
Andr�s Irmer wrote:Same problem here... Any solution?
Askar Akhmerov wrote:try to check port number.
as long as I understand 2810 is a port number of some node(on my installation it's the port number of the app server which was created along with installation). Make sure you have deployed your EjB on that node.
2809 - default port
2811, 2812, and so on are the port numbers of the AppSrv's that you have created on your own.
You should look for the correct port number in you admin console.
-Dcom.ibm.CORBA.Debug=true -Dcom.ibm.CORBA.CommTrace=true -Dcom.ibm.CORBA.Debug.Output= client.log
Sibi Joseph wrote:hi Saw the following post
http://www.ecmplace.com/viewtopic.php?f=39&t=9906&start=0
I was experiencing this problem, and after running an ethernet trace found that my WebSphere server was responding with a redirect to itself using it's host name, which was not resolvable from the client.
Once I added the hostname into the <windows>\system32\drivers\etc\hosts file, it worked just fine.
So check to make sure the name ( not ip) that your host thinks it is can be resolved by anybody trying to lookup jndi resources on it.
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. - Rich Cook