Connection recv error in jolt connection

Question

Hi,
We have Java GUI client connecting to the Tuxedo server thru Jolt.
When we try to do some operation that connects to server after the GUI is idle for a about an hour we get Jolt error "Connection recv error" , sometimes we also get the error "Connection send error".
Wanted to know what causes this error, we are connecting the GUI in RETAINED mode option.
I could not get much in edocs on this, please let me know anyone encountered such problem and what really causes to throw this error.
I have pasted the error below:
bea.jolt.TransactionException: Connection recv error\nbea.jolt.SessionException: Connection recv error\nbea.jolt.JoltException: [6] NwHdlr.recv(): Network Error\njava.net.SocketException: Connection reset
     at bea.jolt.JoltTransaction.begin(JoltTransaction.java:337)
     at bea.jolt.JoltRemoteService.call(JoltRemoteService.java:278)
     at bea.jolt.JoltRemoteService.call(JoltRemoteService.java:257)
Thanks
gowardhan

Answer 1

Hi Gowardhan,
My comments are in line.
Wayne
Gowardhan Reddy wrote:
Hi Wayne,
Thanks for your reply.
The disconnect seems to be happening due to network problem.
Can you please help us understand the difference between a connection recv and connection send error? When we get a recv error does that mean a message was sucessfully sent to the server and the error was in receiving the response? [Wayne] I assume you use "call" method of JoltRemoteService class. This
method encapsulates send and recv action in a try{} block. So whether
send or recv throw exceptions depends on when the connection
disconnected. I guess most exceptions were regarding send. When a recv
error happens, I think the message was sent successfully except some
rare situation, that is message transmission seems OK for client, but at
that time the network disconnected.
We tried with ANY option and the problem doesnt seem to happen when we connect with -j ANY option. We have a range of 50 ports reserved for Jolt connection and network maybe dropping the idle connections.
What is difference in using -T option with ANY or just the RETAINED option, as it looks using ANY option without -T specified is same as RETAINED option. Will the server be able to push/connect to GUI in case of ANY option after the timeout value is reached?[Wayne] I think -T option will override the RETAINED option. That is to
say even you give a retained mode for connection, -T may also disconnect
the clients in a specified idle time. But if the client is closed due to
inactive timeout, JSH should have some message in ULOG like "... timed
out due to inactivity".
There is no error logged in ULOG.
Thanks
Gowardhan