Error -25587 using a shared memory connection.
Snorri Bergmann got error -25587 (network receive failed) in heavy Genero 4GL jobs over a shared memory connection, with nothing in online.log. Marcus Haarmann, Andreas Legner, Paul Watson and Vicente Salvador Cubedo suggested checking onmode -z, session limits and QUERY_TIMEOUT; none applied. Salomi Gaddam suggested server-side resource exhaustion. Unresolved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hello everyone.
I was trying to run some heavy Genero 4GL jobs on the DB server via a shared memory connection.
Some ran fine but other jobs crashed almost immedately (while in a cursor loop) with error
$ finderr -25587-25587 Network receive failed.
A system call has failed. Perform a DISCONNECT and then check the
status of the server. See the system administrator for assistance.
What does this mean when using a shmem connection?
It looks like the application was disconnected?
Thx in advance,
-S
------------------------------
Snorri Bergmann
------------------------------
Anything in online.log ? MARCUS HAARMANN
No, nothing in online.log. ------------------------------ Snorri Bergmann ------------------------------
Weird, and 25587 apparently being a rare error.
Any signs of sessions having been terminated (onmode -z, maybe induced by some server side config - session limit)?
------------------------------
Andreas Legner
Informix Dev
HCL Software
------------------------------
Can you onmode -I 25587 ?
Cheers
Paul
Paul Watson
Oninit LLC
+1-913-387-7529
www.oninit.com
Oninit® is a registered trademark of Oninit LLC
Thanks Andreas.
No, there are no signs of onmode -z and there are no session limits whatsoever.
I am now running one job locally via onsoctcp. It seems much faster than from a different client machine.
Will I see major performance benefits with shared mem compared to that?
------------------------------
Snorri Bergmann
------------------------------
Just in case, check if you've defined QUERY_TIMEOUT environment session option. This can close sessions automativaly. QUERY_TIMEOUT session environment option Ibm remove preview QUERY_TIMEOUT session environment option Use the QUERY_TIMEOUT environment option of the SET ENVIRONMENT statement to limit the amount of clock time a query may take before being interrupted internally. View this on Ibm > ------------------------------ Vicente Salvador Cubedo Software Architect DEISTER, S.A. Barcelona +34 932063298 ------------------------------
Thanks Vicente. No, this parameter is not set at all. Regs, -S ------------------------------ Snorri Bergmann ------------------------------
No "mode" needs to be turned ON This is NOT a connectivity setting issue It's almost certainly: Server-side resource exhaustion or session termination during heavy processing ------------------------------ Salomi Gaddam ------------------------------