The AS Java's Java Messaging Service implementation has a star like topology with a single server node in the system acting as the central JMS server, handling all requests for JMS resources that come from the other servers in the system. The server node that acquires the $service.jms_provider global enqueue lock becomes the central JMS node and is referred to as the JMS lock owner. The lock is acquired by a server during system startup and the lock owner changes whenever there is a system restart or the current lock owner crashes/restarts. Determining which server currently has the lock or where possible, which server had the lock at the time of the incident, is a first step in the analysis of JMS issues.
- Release Independent
- SAP NetWeaver
JMS lock, JMS lock owner, Determine JMS lock owner , KBA , BC-JAS-JMS , Messaging , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.