Salesforce

PASOE instance can't be stopped in the production environment with TCMAN STOP command

« Go Back

Information

 
TitlePASOE instance can't be stopped in the production environment with TCMAN STOP command
URL Namepasoe-instance-can-t-be-stopped-in-the-production-environment-with-tcman-stop-command
Article Number000197275
EnvironmentProduct: OpenEdge
Version: 11.7 to 11.7.8, 12 to 12.2.2
OS: LINUX / UNIX
Other: PASOE
Question/Problem Description
PASOE instance can't be stopped in the production environment with TCMAN STOP command
PASMAN STOP agents not shutting down and the hung worker threads

When the command "pasman stop -I " is issued the agent processes don't stop 
  • In the OE Manager / OEE shows the PASOE instance is indicated as being down.
  • process listing shows all MSAgent processes still running and they only respond to KILL -9 
Steps to Reproduce
Clarifying Information

tcman/pasman stop :

  • The stop is received by the session manager
  • The session manager stops taking requests
  • The session manager asks the agent(s) to stop
  • The session manager waits for agent(s) to complete all requests
  • When all agents are done, they exit
  • Then the tomcat process ends
Error Message
Defect NumberOCTA-29002
Enhancement Number
Cause
PASOE agent fails to shutdown due to a worker thread hung on a read or write to the Session Manager, or if it the worker thread hangs due to a recursive Signal condition on AIX platforms specifically:
  • The shutdown process will hang forever, waiting for ABL Sessions that are bound to their client to run their disconnect procedure as the worker thread is blocked or ABL Sessions waiting for the worker threads to complete.
  • As a consequence, those hung agent worker threads never disconnect from their database and if the database is connected via shared memory, the shutdown process never gets to the point where the resource manager can be told to disconnect from the database.
When an ABL Session is deliberately destroyed while waiting on a read/write, the Session Manager and the Agent become out of sync in their count of how many ABL Sessions are available to be used. The Session Manager does not send new requests to the Agent because a new ABL Session is not prestarted to comply with the minAvailableAblSessions setting after the Session is terminated.
Resolution
Fixed version(s): OpenEdge 12.3, OpenEdge 12.4, OpenEdge 12.2.3, OpenEdge 11.7.9
Workaround
Before stopping the PASOE instance, terminate MSA's : How to stop a PASOE agent with OEJMX?

Then should agents remain, terminate the _mproapsv process with OS SIGKILL kill -9

Once all MSA's have been stopped, the PAS instance itself can be stopped TCMAN / PASMAN stop

    Notes
    Keyword Phrase
    Last Modified Date10/25/2023 1:41 PM

    Powered by