Closed NicolaIsotta closed 5 months ago
Looks like the server isn't responding in time. This error is occurring at the socket level.
gio gen 18 14:14:37:077 CET 2024 as400: Statement STMT0001 (1594199808) : Prepared STMT0001, SQL Statement -->[select from OBVAC00F where OBVACCOCOM = 'FREQ']. gio gen 18 14:14:56:287 CET 2024 as400: ConnectionImpl [redacted]:XXX.XXX.XXX.XXX (70807318) : Throwing exception. Original exception: .java.net.SocketTimeoutException: Read timed out at java.base/java.net.SocketInputStream.socketRead0(Native Method)
I find it odd that there is only a 20 second timeout. Is there a setting on your OS that is limiting a read timeout to 20 seconds?
Some additional notes:
Maybe it's a bug at the DB2 level?
Weird, it could be that the job on the "IBM i" is ending. Are you able to find the joblog for the QZDASOINIT job used by the connection? The joblog should show the cause of the job ending and you could contact IBM to resolve the problem.
Closing because of inactivity.
The job log is in the first post. Anyway, I applied some PTFs, I'll test again, maybe it had already been fixed.
It would be nice to see the entire job log. This should be a joblog from a QZDASOINIT job.
Is there an "intelligent" firewall between the client and the server? I've seen cases where a firewall drops connections because it thinks there is some type of network attack taking place. You may want to check with the network administrator to see if the firewall is dropping the connection.
Test code:
Exception stack trace
Toolbox trace output
First message on the job log
Second message on the job log