Yes, I've seen it several times. There is one more issue with my project, the scenario is:
- web service deployed on server1 got a request (HTTP);
- the service makes a remote EJB call deployed on server2;
- on the server2 something goes wrong, lost of connection with DB for instance;
- remote EJB throws an exception;
- for some reason WS thread calling remote EJB does not see the exception response; it waits for answer until CORBA timeout occurs (30 minutes by default!)
- during this 30 minutes all HTTP threads can be exhausted and GF stops processing new incoming requests;
I'm going to make CORBA timeout smaller using JVM option:
-Dcom.sun.corba.ee.transport.ORBWaitForResponseTimeout=60000
Do you know why it occurs?
Thanks, Denis.
[Message sent by forum member 'sdv0967']
http://forums.java.net/jive/thread.jspa?messageID=397880