| Gerrit,
The error message is mostly used to log when a pthread_create
request fails. pthread_create appears to have set the error
code to ENOMEM indicating a shortage of memory. This might be
what is happening or it could be misleading and the symptom of
some other problem.
What version and patch level of the gateway are they running on the
system that displays this error. I have seen this message on earlier
revisions of the V2.1 gateway but have not encountered it since
changing the thread package to allocate a pool of reusable threads
at startup rather than creating and deleting them as needed. When the
gateway first opens the log file after startup, it outputs a banner
that will show the version. The latest revision is V2.1C-3, I expect
this error is coming from their production machine and it is still
running something close to the original released version.
Does this occur after running for some time, and when it does happen, how
much virtual memory is being used by the acmsdid process. Does it
appear that the VM usage of the gateway creeps upwards over a period of
days? They might be able to avoid the occurance by increasing some of
the VM system parameters. If it is related to having been running for
some days, it might be avoidable by restarting the gateway every few
days or something depending on how long it runs without problems.
Amongst the parameters that I have had the need to increase are the
following: vm-vpagemax, max-threads-per-user, max-per-proc-stack-size,
maxssiz, maxdsiz
Are they still unable to upgrade ACMS Desktop because they would
also need to disturb the ACMSxp system installation? If so, do they
have an estimate of when they can upgrade? I guess if this can't be
corrected by tuning, then the question is do we really have to rework
the various fixes and maintain a separate release to run against the
original ACMSxp system, or will they upgrade both products to stay
synchronized?
/Tom
|