Process ended with network broken errors
ABeMie reported Genero 4GL application errors -25580 (system error 110, network) and -404 against Informix 12.10.FC6WE on RHEL 8, occurring on production but not staging. Dennis Melnikov suggested tracing with onmode -I -25580; David Williams thought unclosed connections likely and warned against the trace in production. The poster asked about TCP or session limits; no cause was found.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hi Support
We received a complaint from users claim that their application process ended with network broken / failure while through out monitoring there is no network intermittance.
Here few errors inside the application logs :
Program error at 'lib_gen.4gl', line number 3124.
SQL statement error number -25580.
System error occurred in network function.
SYSTEM error number 110.
ISAM error: end or beginning of the file.
Date: 23/07/2024 Time: 16:45:03Program error at 'lib_prgctrl.4gl', line number 1071.
SQL statement error number -25580.
System error occurred in network function.
SYSTEM error number 110.
ISAM error: end or beginning of the file.
Date: 23/07/2024 Time: 16:45:03Program error at 'lib_gen.4gl', line number 3819.
*** An error occurred in the error handler ***
Date: 23/07/2024 Time: 16:45:03
Program error at 'lib_gen.4gl', line number 3819.
SQL statement error number -404.
The cursor or statement is not available.
SYSTEM error number 110.
We are running our application which was developed on FourJS Genero. We did simulate either via browse or through desktop client, both sometimes will hit same error.
Our application on RHEL 8.0 with IBM Informix CSDK 4.10.FC14 While DB using IBM Informix Dynamic Server 12.10.FC6WE.
Seek expert advise what usually cause this
------------------------------
ABeMie
------------------------------
ABeMie,
Try to trace the error with `onmode -I -25580`.
------------------------------
Sincerely,
Dennis
------------------------------
Hi, This probably means application programs are terminating without closing the database connections. Otherwise I could mean network connectivity issues but the first is more likely. Regards, David. ------------------------------ David Williams ------------------------------
Hi, I would not go that, in this kind of environment that could generate a lot of hung sessions and impact the instance. Regards, David. ------------------------------ David Williams ------------------------------
Hi
What could be the behaviour by run
`onmode -I 25580`
in production db server. ?
Following are what our application support have simulated:
With the same application program version and from same app server, he ran with 2 scenario :
Using TCP A connected to Staging DB server. He not hitting the network broken errors.
Using TCP B connected to Production DB server. This time he hit the network broken errors.
For broken scenario i counldn't see any lines can be relate inside Informix DB online log. Could it be related to limit on TCP connection or session memory limit etc.
The configuration in production was cluster between one db node at DC and one db node at DR. The cluster information (using onstat -g dri and onstat -g cluster) shown no issue and most uptodate send and receive. Hope can get some other tips to narrow down the issue
------------------------------
ABeMie
------------------------------