[Info-ingres] E_SC0220_SESSION_ERROR_MAX
Karl and Betty Schendel
schendel at kbcomputer.com
Tue Aug 1 16:32:19 UTC 2017
Alas:
scb->scb_sscb.sscb_noerrors++;
if (scb->scb_sscb.sscb_noerrors > 1)
{
sc0e_put(E_SC0220_SESSION_ERROR_MAX, (DB_ERROR *)NULL, 0, 1,
....
Not very sophisticated, I'm afraid.
> On Aug 1, 2017, at 6:51 AM, Roy Hann <specially at processed.almost.meat> wrote:
>
> I've been waiting about a month for a server to SIGSEGV so I could get a
> core dump for it. But yesterday it decided to E_SC0220_SESSION_ERROR_MAX
> instead.
>
> That seems to have been graceful enough to avoid the core dump but not
> graceful enough to write anything helpful in the detailed DBMS log file
> designated by II_DMBS_LOG.
>
> Is the session error max a configurable limit? I really don't want the
> server to just stop. A massive explosion with lots of interesting
> shrapnel would be preferable.
>
> Roy
> _______________________________________________
> Info-ingres mailing list
> Info-ingres at lists.planetingres.org
> http://lists.planetingres.org/mailman/listinfo/info-ingres
More information about the Info-ingres
mailing list