This content has been marked as final. Show 14 replies
Please don't revive old threads just to ask someone if the problem is fixed. If you want to ask a question the correct way to do it is to start a new thread as you have here.
java.rmi.ConnectIOException: error during JRMP connection establishmentWhat's the rest of the stack trace?
Here is the rest of the stack trace:
java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
at [class that calls Naming.lookup()].<init>([class that calls Naming.lookup()].java:52)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
... 11 more
The Registry is frozen, or something else is running on that port that isn't responding.
Do I need additional configuration for that in my Websphere?
It doesn't look like it, as long as you have the correct port configured. 1099.
I am running my Websphere and right now, my application server is on. However, no one is listening on port 1099. Isn't Websphere using another port? I have looked into it and no settings for RMI port were given.
I have only seen this two (hopefully related) ports:
BOOTSTRAP_ADDRESS = 2811
ORB_LISTENER_ADDRESS = 10000 (I have set this one)
I am using 2811, instead of 1099. And the exception above is the result I am getting. I also tried 10000, and same results.
1099 is the port the RMI Registry should be running on, and that's the port that should be named in the Naming.lookup() call. Or omitted.
So it means, the RMI Registry of my Websphere is not running? since no one is listening in port 1099??
It has nothing to do with Websphere configuration except for wherever your WS app gets the Naming.lookup() string from.
I am talking about the Registry you are running. It is using 1099 unless you changed it. Whatever it is using must agree with the Naming.lookup() call. My question is, is what is running on whatever that port is on whatever host the Registry is running on really a Registry? If it is, it's stuck. If it isn't, find and fix that problem.
Ok. I will try to do that.
I think I may have assumed that Websphere has packaged its own RMI Registry, that whenever Websphere startup, RMI registry will also start up.
It is still nothing to do with WebSphere, assuming this statement of yours is still correct:
2. All servers will be on my local machine, so is the RMI Registry.That is the RMI Registry I am talking about. Is it running on the same port that the code is looking for in Naming.lookup()? Clearly something is, or you would have got a ConnectException instead of a read timeout, so either the Registry is frozen or it isn't a Registry and is misbehaving badly when it receives a Registry request. I suspect it's frozen myself, these things do seem to happen somehow. How long had it been up when this happened?
I am just new to it, I have encountered this error only yesterday.
Do Websphere has its own RMI Registry? Not the one included in the java package, but the one included in WEBSPHERE itself?
Do Websphere has its own RMI Registry? Not the one included in the java package, but the one included in WEBSPHERE itself?I don't know why you're even asking this question. You are running the RMI Registry on your own host with your own RMI servers. Websphere and anything else accesses that via Naming.lookup().
Websphere's Registry, and whether it even has one, is completely irrelevant to this problem. I seem to have said that about five times already.
FYI the answer is that, like most J2EE containers, Websphere uses RMI/IIOP, which doesn't use the RMI Registry at all, it uses the CORBA COS Naming service.