Advanced Technical Sales
WebSphere Application Server for z/OS
|Abstract: If any transactional batch job is running in a WebSphere Compute Grid Endpoint Server and the endpoint server is stopped, many trace messages may be written until the jobs end. The Stop will complete successfully, but you will see over 20 trace messages per second in the Endpoint server's control region SYSPRINT log during this period.|
The Endpoint Controller is waiting for the job to complete before it can continue with Stop processing. During this time, the Controller loops, checking for outstanding requests and writes ORB_Registry trace records until the Compute Grid job completes.
Resolving the Problem:
- Do not Stop an Endpoint server while jobs are running in it.
- The "GAPAgent" MBean "quiesceEndpoint" method could be called to quiesce the Endpoint Server. This code be implemented by writing code using the WAS admin client.
Sample Trace Messages:
Trace: 2013/07/02 09:13:49.177 02 t=8BF718 c=UNK key=S2 tag= (0400502E)
Description: No active Transactions
Function: BBO_BOA::context_disassociation(MVS::GTID *)
About to post BBO_BOA::deactivate_impl: no active transactions
Trace: 2013/07/02 09:13:49.178 02 t=8BFE88 c=UNK key=S2 tag= (0400502F)
Description: transactions_active no GTID_Rows
from filename: ./bbgoboai.cpp
at line: 6212
No Active Transactions in the GTID Hash Table:
Trace: 2013/07/02 09:13:49.178 02 t=8BFE88 c=UNK key=S2 tag= (0403402E)
ORB_Request Target Operation : data_address=1598b7fe, data_length=12
- WebSphere Application Server Version 188.8.131.52 on z/OS
- WebSphere Extended Deployment Compute Grid Version 184.108.40.206 on z/OS
IBM System z Family
IBM System z Software
WebSphere Extended Deployment, Compute Grid, WebSphere Batch, WCG, V.220.127.116.11, z/OS, stop server, quiesce, endpoint, server
|Is this your first visit to Techdocs (the Technical Sales Library)?