Hello
[using Sun Java System Application Server 9.1_01 (build local)], Java 6 _ 11
Problem:
Client uses initialContext to lookup a @Remote handle to a stateless session bean.The bean offers three methods. The client unit test calls the three methods in consecutive order, but hangs on the second and third method until network layer throws a timeout exception.
The first call succeeds and returns the expected data. The second call gets to the server but the method is not invoked on the server side. I enabled remote debugging and was able to remote debug the first method, but the second method simply does not get called, the breakpoint in the very first line is never reached.
I tested if the second call is leaving my client maschine by changing the serialVersionUid of one of the classes passed as parameter. That call returned somewhat immediatly stating that the uid did not match. So i can safely assume that the request is reaching the server and "dissapears".
The same goes for the third method.
There is no sensible error message in the log file.
Is there a way to debug the call stack in the glassfish network layer, add an interceptor of some sort, anything?
Regards
[Message sent by forum member 'mark1971' (mark1971)]
http://forums.java.net/jive/thread.jspa?messageID=330025