JMS Service

[Former Member]

Greetings,

We are noticing that a JMS method named, “MessageConsumer.receive()” runs every thirty seconds across all WAS instances; is there a way of disabling this service, if so please share.

[Former Member]

Peter,

We are using Mercury's diagnostic tool and looking at server requests. The graphs show that all of the servers have a MessageConsumer.receive() request that runs continuously at a 30s latency.

We're trying to figure out what that means. The only usage of JMS in our applicaiton is by MDX when getting data from BW, and all that is done through the BISDK.

[Former Member]

**********Contd*************

No explicit JMS destinations for our application have been created; we just have the sap.com ones:

sap.com/com.sap.ip.me.insttool

sap.com/com.sap.security.core.admin

sap.com/tc_mobileadmin~ea

sap.com/tc_TechSrvXML_DAS

Any help figuring out what is causing this in our monitor would be appreciated.

[Former Member]

Hi Travis,

the most brutal approach would be to start deleting them one by one and check at what time the calls would stop.

Then you can recreate them again from VA

Alternative approach would be to put on debug level the logging of the JMS (Visual Administrator, Log configurator, location com.sap.jms)

Then check in the server log files what is the application that is constantly openening new receiver.

The trace file is located at something like :

C:\usr\sap\J2E\JC00\j2ee\cluster\server0\log

You should see traces like

#XXX#...#Entering...receive

where the XXX would be the application name that is causing the load. You can stop it or undeploy it.

Btw, isn't your tool capable of showing what is the invocation stack of the call ?

HTH

Peter

[Former Member]

Peter,

I will give this a try and get back with you. Yes, the profiler gives this information as well and available for free download:

http://www.mercury.com/us/promotions/diagnostics-profiler.html

[Former Member]

Hi Travis,

Well, if you have the invocation stacktrace, you may post it in the SDN. Perhaps I or somebody else with more experience and JMS knowledge can tell what application is doing this periodic calling and why.

HTH

Peter

[Former Member]

Hello,

I work with Travis. Our profiler doesn't go below the MessageConsumer.receive() call and we can't determine who is trying to receive the message

[Former Member]

Hi Eric,

well, you could enable the log files of the engine to debug.

Visual Administrator - log configurator, location com.sap.jms

then you will be able to see in details all the JMS activities. You will see also the message data being transferred, perhaps that can give you a hint.

The log file would be located to

:\usr\sap\<sid>\<id>\j2ee\cluster\server0\log

In the debug statements the log files should have the application name in the format #MyApplicationThatIsCausingTroubles#

HTH

Peter

[Former Member]

Hello Peter,

Here is a sample session from the log. I don't know what I'm looking at so it doesn't mean much to me. Do you see anything abnormal?

#1#=================================== Session ====================================

ID: 7225

Type: QueueSession

ConnectionID: 8531746375073816

AcknowledgeMode: AUTO_ACKNOWLEDGE

================================================================================

#

#1.5#0003BACE7B0D0075000003410000072F0004197EA4F0E65F#1153931630667#com.sap.jms.client.Connection#sap.com/irj#com.sap.jms.client.Connection#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Exiting...createSession() connection id = [], transacted = [], acknowledge mode = [], session type = [], session id = []#5#8531746375073816#false#1#0#7225# #1.5#0003BACE7B0D0075000003420000072F0004197EA4F0E72A#1153931630667#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Entering...createProducer() - session id = []#1#7225#

#1.5#0003BACE7B0D0075000003430000072F0004197EA4F0E7D4#1153931630667#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###destination is queue with name = []#1#JMS_POLLING_QUEUE# #1.5#0003BACE7B0D0075000003440000072F0004197EA4F0E89E#1153931630667#com.sap.jms.server.ServerClientAdapter#sap.com/irj#com.sap.jms.server.ServerClientAdapter#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path#1#/Applications/JMS#Plain###send requestId = -2147455082 type = ProducerCreateRequest# #1.5#0003BACE7B0D00540000003D0000072F0004197EA4F0E989#1153931630668#com.sap.jms.server.routingcontainer.RoutingContainer#sap.com/irj#com.sap.jms.server.routingcontainer.RoutingContainer#Guest#2####84e9bc801cc411dbae750003bace7b0d#SAPEngine_Application_Thread[impl:3]_35##0#0#Debug##Java###receiveFromDispatcher()...Going to receive from cluster node with id = []#1#1986452#

#1.5#0003BACE7B0D00540000003E0000072F0004197EA4F0EA7D#1153931630668#com.sap.jms.server.service.impl.RegistryServiceImpl#sap.com/irj#com.sap.jms.server.service.impl.RegistryServiceImpl#Guest#2####84e9bc801cc411dbae750003bace7b0d#SAPEngine_Application_Thread[impl:3]_35##0#0#Debug#1#/System/Server#Java###Requesting destination with name and encoded name #2#JMS_POLLING_QUEUE#JMS_POLLING_QUEUE# #1.5#0003BACE7B0D00540000003F0000072F0004197EA4F0EBF0#1153931630668#com.sap.jms.server.routingcontainer.RoutingContainer#sap.com/irj#com.sap.jms.server.routingcontainer.RoutingContainer#Guest#2####84e9bc801cc411dbae750003bace7b0d#SAPEngine_Application_Thread[impl:3]_35##0#0#Debug##Java###sendToDestinationContainerSynchronously()...Going to receive from cluster node with id = []#1#1986452#

#1.5#0003BACE7B0D0054000000400000072F0004197EA4F0ECBA#1153931630668#com.sap.jms.server.service.impl.RegistryServiceImpl#sap.com/irj#com.sap.jms.server.service.impl.RegistryServiceImpl#Guest#2####84e9bc801cc411dbae750003bace7b0d#SAPEngine_Application_Thread[impl:3]_35##0#0#Debug#1#/System/Server#Java###Requesting destination with name and encoded name #2#JMS_POLLING_QUEUE#JMS_POLLING_QUEUE# #1.5#0003BACE7B0D0054000000410000072F0004197EA4F0EDA8#1153931630669#com.sap.jms.server.routingcontainer.RoutingContainer#sap.com/irj#com.sap.jms.server.routingcontainer.RoutingContainer#Guest#2####84e9bc801cc411dbae750003bace7b0d#SAPEngine_Application_Thread[impl:3]_35##0#0#Debug##Java###sendToDispatcher()...Going to send to connection with id = [], cluster node id = [], packet request id = []#3#24#1986452#-2147455082# #1.5#0003BACE7B0D0075000003450000072F0004197EA4F0EEAA#1153931630669#com.sap.jms.server.ServerClientAdapter#sap.com/irj#com.sap.jms.server.ServerClientAdapter#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path#1#/Applications/JMS#Plain###currentWaitID = -2147455082 response requestId = -2147455082 type = ProducerCreateResponse# #1.5#0003BACE7B0D0075000003460000072F0004197EA4F0F015#1153931630669#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#/Applications/JMS#Java###JMS producer successfully created: #1#=============================== MessageProducer ================================ ID: 8531746375081030 Type: QueueSender Destination: JMS_POLLING_QUEUE SessionID: 7225 IsClosed: NO MessagePriority: 4 MessageIDEnabled: true MessageTimestampEnabled: true MessageTimeToLive: 0 ================================================================================ # #1.5#0003BACE7B0D0075000003480000072F0004197EA4F0F2DD#1153931630670#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Exiting...createProducer() - Normal exit! session id = []#1#7225# #1.5#0003BACE7B0D0075000003490000072F0004197EA4F0F3CD#1153931630670#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Entering...close() - session id = []#1#7225# #1.5#0003BACE7B0D00750000034A0000072F0004197EA4F0F483#1153931630670#com.sap.jms.client.Connection#sap.com/irj#com.sap.jms.client.Connection#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Entering...stopDeliveryToSession(int) - connection id = [], session id = []#2#8531746375073816#7225#

#1.5#0003BACE7B0D00750000034B0000072F0004197EA4F0F551#1153931630671#com.sap.jms.server.ServerClientAdapter#sap.com/irj#com.sap.jms.server.ServerClientAdapter#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path#1#/Applications/JMS#Plain###send requestId = -2147455081 type = SessionStopRequest#

#1.5#0003BACE7B0D0054000000420000072F0004197EA4F0F638#1153931630671#com.sap.jms.server.routingcontainer.RoutingContainer#sap.com/irj#com.sap.jms.server.routingcontainer.RoutingContainer#Guest#2####84e9bc801cc411dbae750003bace7b0d#SAPEngine_Application_Thread[impl:3]_35##0#0#Debug##Java###receiveFromDispatcher()...Going to receive from cluster node with id = []#1#1986452# #1.5#0003BACE7B0D0054000000430000072F0004197EA4F0F725#1153931630671#com.sap.jms.server.routingcontainer.RoutingContainer#sap.com/irj#com.sap.jms.server.routingcontainer.RoutingContainer#Guest#2####84e9bc801cc411dbae750003bace7b0d#SAPEngine_Application_Thread[impl:3]_35##0#0#Debug##Java###sendToDispatcher()...Going to send to connection with id = [], cluster node id = [], packet request id = []#3#24#1986452#-2147455081# #1.5#0003BACE7B0D00750000034C0000072F0004197EA4F0F870#1153931630671#com.sap.jms.server.ServerClientAdapter#sap.com/irj#com.sap.jms.server.ServerClientAdapter#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path#1#/Applications/JMS#Plain###currentWaitID = -2147455081 response requestId = -2147455081 type = SessionStopResponse# #1.5#0003BACE7B0D00750000034D0000072F0004197EA4F0F94A#1153931630672#com.sap.jms.client.Connection#sap.com/irj#com.sap.jms.client.Connection#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Exiting...stopDeliveryToSession(int) - connection id = [], session id = []#2#8531746375073816#7225#

#1.5#0003BACE7B0D00750000034E0000072F0004197EA4F0F9FD#1153931630672#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Entering...stopDelivery() - session id = []#1#7225# #1.5#0003BACE7B0D00750000034F0000072F0004197EA4F0FAA9#1153931630672#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Listeners size = [], session id = []#2#0#7225# #1.5#0003BACE7B0D0075000003500000072F0004197EA4F0FB5B#1153931630672#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Entering...stopDeliveryToReceivers() - session id = []#1#7225# #1.5#0003BACE7B0D0075000003510000072F0004197EA4F0FC05#1153931630672#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Exiting...stopDeliveryToReceivers() - Normal exit! session id = []#1#7225# #1.5#0003BACE7B0D0075000003520000072F0004197EA4F0FCB0#1153931630673#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Exiting...stopDelivery() - session id = []#1#7225# #1.5#0003BACE7B0D0075000003530000072F0004197EA4F0FD5E#1153931630673#com.sap.jms.client.Connection#sap.com/irj#com.sap.jms.client.Connection#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Entering...closeSession() with session id = [], connection id = []#2#7225#8531746375073816#

#1.5#0003BACE7B0D0075000003540000072F0004197EA4F0FF0F#1153931630673#com.sap.jms.server.ServerClientAdapter#sap.com/irj#com.sap.jms.server.ServerClientAdapter#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path#1#/Applications/JMS#Plain###send requestId = -2147455080 type = SessionCloseRequest#

#1.5#0003BACE7B0D0054000000440000072F0004197EA4F0FFF0#1153931630673#com.sap.jms.server.routingcontainer.RoutingContainer#sap.com/irj#com.sap.jms.server.routingcontainer.RoutingContainer#Guest#2####84e9bc801cc411dbae750003bace7b0d#SAPEngine_Application_Thread[impl:3]_35##0#0#Debug##Java###receiveFromDispatcher()...Going to receive from cluster node with id = []#1#1986452# #1.5#0003BACE7B0D0054000000450000072F0004197EA4F100DE#1153931630674#com.sap.jms.server.routingcontainer.RoutingContainer#sap.com/irj#com.sap.jms.server.routingcontainer.RoutingContainer#Guest#2####84e9bc801cc411dbae750003bace7b0d#SAPEngine_Application_Thread[impl:3]_35##0#0#Debug##Java###sendToDestinationContainerSynchronously()...Going to receive from cluster node with id = []#1#1986452#

#1.5#0003BACE7B0D0054000000460000072F0004197EA4F101CB#1153931630674#com.sap.jms.server.routingcontainer.RoutingContainer#sap.com/irj#com.sap.jms.server.routingcontainer.RoutingContainer#Guest#2####84e9bc801cc411dbae750003bace7b0d#SAPEngine_Application_Thread[impl:3]_35##0#0#Debug##Java###sendToDispatcher()...Going to send to connection with id = [], cluster node id = [], packet request id = []#3#24#1986452#-2147455080# #1.5#0003BACE7B0D0075000003550000072F0004197EA4F102B8#1153931630674#com.sap.jms.server.ServerClientAdapter#sap.com/irj#com.sap.jms.server.ServerClientAdapter#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path#1#/Applications/JMS#Plain###currentWaitID = -2147455080 response requestId = -2147455080 type = SessionCloseResponse# #1.5#0003BACE7B0D0075000003560000072F0004197EA4F10389#1153931630674#com.sap.jms.client.Connection#sap.com/irj#com.sap.jms.client.Connection#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Exiting...closeSession() with session id = [], connection id = []#2#7225#8531746375073816# #1.5#0003BACE7B0D0075000003570000072F0004197EA4F1044E#1153931630674#com.sap.jms.client.MessageProducer#sap.com/irj#com.sap.jms.client.MessageProducer#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Entering...close() - producer id [], session id = []#2#8531746375081030#7225#

#1.5#0003BACE7B0D0075000003580000072F0004197EA4F1050B#1153931630675#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Entering...closeProducer() - producer id = [], session id = []#2#8531746375081030#7225# #1.5#0003BACE7B0D0075000003590000072F0004197EA4F105C0#1153931630675#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Exiting...closeProducer() - Normal exit! consumer id = [], session id = []#2#8531746375081030#7225# #1.5#0003BACE7B0D00750000035A0000072F0004197EA4F106F2#1153931630675#com.sap.jms.client.MessageProducer#sap.com/irj#com.sap.jms.client.MessageProducer#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#/Applications/JMS#Java###JMS producer closed: #1#=============================== MessageProducer ================================ ID: 8531746375081030 Type: QueueSender Destination: JMS_POLLING_QUEUE SessionID: 7225 IsClosed: YES MessagePriority: 4 MessageIDEnabled: true MessageTimestampEnabled: true MessageTimeToLive: 0 ================================================================================ # #1.5#0003BACE7B0D00750000035C0000072F0004197EA4F109CA#1153931630676#com.sap.jms.client.MessageProducer#sap.com/irj#com.sap.jms.client.MessageProducer#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Exiting...close() - w/o helper producers; producer id [], session id = []#2#8531746375081030#7225#

#1.5#0003BACE7B0D00750000035D0000072F0004197EA4F10AB1#1153931630676#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#/Applications/JMS#Java###JMS session closed:

#1#=================================== Session ==================================== ID: 7225 Type: QueueSession ConnectionID: 8531746375073816 AcknowledgeMode: AUTO_ACKNOWLEDGE ================================================================================ # #1.5#0003BACE7B0D00750000035F0000072F0004197EA4F10CD8#1153931630677#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Exiting...close() - session id = []#1#7225#

#1.5#0003BACE7B0D0076000000230000072F0004197EA4FA25E9#1153931631273#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####081233e01cc411dbc5560003bace7b0d#Thread[RTCBaseService,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Plain###There is no message to provide.#

#1.5#0003BACE7B0D0076000000240000072F0004197EA4FA26CA#1153931631273#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####081233e01cc411dbc5560003bace7b0d#Thread[RTCBaseService,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Exiting...provideMessage() - consumer id = [], session id = []#2#8531746375073868#65# #1.5#0003BACE7B0D0076000000250000072F0004197EA4FA2795#1153931631273#com.sap.jms.client.MessageConsumer#sap.com/irj#com.sap.jms.client.MessageConsumer#Guest#2####081233e01cc411dbc5560003bace7b0d#Thread[RTCBaseService,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Exiting...receive(timeout), timeout = [], consumer id = [], session id = [], message id = []#4#30000#8531746375073868#65#<null># #1.5#0003BACE7B0D0076000000260000072F0004197EA4FA28AF#1153931631274#com.sap.jms.client.MessageConsumer#sap.com/irj#com.sap.jms.client.MessageConsumer#Guest#2####081233e01cc411dbc5560003bace7b0d#Thread[RTCBaseService,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Entering...receive(timeout), timeout = [], consumer id = [], session id = []#3#30000#8531746375073868#65# #1.5#0003BACE7B0D0076000000270000072F0004197EA4FA2974#1153931631274#com.sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Session#Guest#2####081233e01cc411dbc5560003bace7b0d#Thread[RTCBaseService,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Entering...provideMessage() - consumer id = [], session id = [], timeout = [], blockedWait = []#4#8531746375073868#65#30000#false# #1.5#0003BACE7B0D00120000001D0000072F0004197EA4FD2238#1153931631469#com.sap.jms.server.routingcontainer.RoutingContainer##com.sap.jms.server.routingcontainer.RoutingContainer######16ce58601c1e11dbc3a50003bace7b0d#SAPEngine_System_Thread[impl:5]_56##0#0#Debug##Java###receiveFromRemoteSessionContainerSynchronously()...Going to receive from cluster node with id = []#1#1986452# #1.5#0003BACE7B0D00120000001E0000072F0004197EA4FD2333#1153931631469#com.sap.jms.server.service.impl.RegistryServiceImpl##com.sap.jms.server.service.impl.RegistryServiceImpl######16ce58601c1e11dbc3a50003bace7b0d#SAPEngine_System_Thread[impl:5]_56##0#0#Debug#1#/System/Server#Java###Requesting destination with name and encoded name #2#JMS_POLLING_QUEUE#JMS_POLLING_QUEUE# #1.5#0003BACE7B0D003A0000001A0000072F0004197EA4FD3A96#1153931631475#com.sap.jms.server.routingcontainer.RoutingContainer##com.sap.jms.server.routingcontainer.RoutingContainer####usorlu86_SPD_1986452#Guest#7dc560e01cb411dbc7b10003bace7b0d#SAPEngine_System_Thread[impl:5]_50##0#0#Debug##Java###receiveFromRemoteSessionContainerSynchronously()...Going to receive from cluster node with id = []#1#1986452# #1.5#0003BACE7B0D001F000000080000072F0004197EA57081F7#1153931639030#com.sap.jms.server.routingcontainer.RoutingContainer##com.sap.jms.server.routingcontainer.RoutingContainer####usorlu86_SPD_1986452#Guest#2143f5201c1e11dbbc990003bace7b0d#SAPEngine_System_Thread[impl:5]_46##0#0#Debug##Java###receiveFromRemoteSessionContainerSynchronously()...Going to receive from cluster node with id = []#1#1986452# #1.5#0003BACE7B0D001F000000090000072F0004197EA57082EE#1153931639030#com.sap.jms.server.service.impl.RegistryServiceImpl##com.sap.jms.server.service.impl.RegistryServiceImpl####usorlu86_SPD_1986452#Guest#2143f5201c1e11dbbc990003bace7b0d#SAPEngine_System_Thread[impl:5]_46##0#0#Debug#1#/System/Server#Java###Requesting destination with name and encoded name #2#JMS_POLLING_QUEUE#JMS_POLLING_QUEUE# #1.5#0003BACE7B0D003B000000030000072F0004197EA5709D0B#1153931639037#com.sap.jms.server.routingcontainer.RoutingContainer##com.sap.jms.server.routingcontainer.RoutingContainer######3db98de01cc411db892d0003bace7b0d#SAPEngine_System_Thread[impl:5]_71##0#0#Debug##Java###receiveFromRemoteSessionContainerSynchronously()...Going to receive from cluster node with id = []#1#1986452# #1.5#0003BACE7B0D0075000003600000072F0004197EA589BAE3#1153931640683#com.sap.jms.client.Connection#sap.com/irj#com.sap.jms.client.Connection#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Java###Entering...createSession() connection id = [], transacted = [], acknowledge mode = [], session type = []#4#8531746375073816#false#1#0#

#1.5#0003BACE7B0D0075000003610000072F0004197EA589BC52#1153931640683#com.sap.jms.server.ServerClientAdapter#sap.com/irj#com.sap.jms.server.ServerClientAdapter#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path#1#/Applications/JMS#Plain###send requestId = -2147455079 type = SessionCreateRequest#

#1.5#0003BACE7B0D004F0000006F0000072F0004197EA589BF32#1153931640684#com.sap.jms.server.routingcontainer.RoutingContainer#sap.com/irj#com.sap.jms.server.routingcontainer.RoutingContainer#Guest#2####8ae2aac01cc411dba53c0003bace7b0d#SAPEngine_Application_Thread[impl:3]_34##0#0#Debug##Java###receiveFromDispatcher()...Going to receive from cluster node with id = []#1#1986452# #1.5#0003BACE7B0D004F000000700000072F0004197EA589C720#1153931640686#com.sap.jms.server.routingcontainer.RoutingContainer#sap.com/irj#com.sap.jms.server.routingcontainer.RoutingContainer#Guest#2####8ae2aac01cc411dba53c0003bace7b0d#SAPEngine_Application_Thread[impl:3]_34##0#0#Debug##Java###sendToDispatcher()...Going to send to connection with id = [], cluster node id = [], packet request id = []#3#24#1986452#-2147455079#

#1.5#0003BACE7B0D0075000003620000072F0004197EA589C84C#1153931640686#com.sap.jms.server.ServerClientAdapter#sap.com/irj#com.sap.jms.server.ServerClientAdapter#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path#1#/Applications/JMS#Plain###currentWaitID = -2147455079 response requestId = -2147455079 type = SessionCreateResponse#

#1.5#0003BACE7B0D0075000003630000072F0004197EA589C996#1153931640686#com.sap.jms.client.Connection#sap.com/irj#com.sap.jms.client.Connection#Guest#2####fb7bda001cc311dba9bb0003bace7b0d#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#/Applications/JMS#Java###JMS session created:

[Former Member]

Hi Eric,

Here is the interesting part and who is using the receive() from the extract you have pasted.

The thread that is doing it is called :

RTCBaseService,5,SAPEngine_Application_Thread[impl:3]_Group

while the application is

sap.com/irj

(that is the SAP Netweaver portal)

As far as I know RTC is a portal component, that is offering many nice features, like for example instant messaging between users logged in the portal. Check this SDN link (it will open PDF file) for more information:

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7b4d2557-0601-0010-4a85-9208abb77635">Collaboration Tools</a>

Obviously from your posts it seems it is using JMS for its internal work and is performing periodically a call to receive().

Alas, I am not that familiar with it, but I think there should be a way to configure this timeout.

I would suggest searching its documentation or perhaps opening a support ticket to SAP asking how it can be configured and why it is doing periodically JMS calls.

HTH

Peter

[Former Member]

Thanks for the help! I'll check out the documentation on the RTC.

[Former Member]

For more information you may also try posting in the forums under Enterprise Portal. Here are more general Web AS server questions.

[Former Member]

Hello Travis,

If you disable the whole JMS that will mean that all applications that use MDB-s or JMS will becomes disabled as well.

Unfortunately as far as I know, that will include some of the default applications that comes with the server (For example the web admin for user administration).

It might make more sense, not to disable the whole JMS, but just this application that is causing problems and such periodic JMS usage. You may even try to undeploy it.

Here is a link about starting applications, you may use it, just instead of "start" you may want to click on the "remove" button

<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/e034417f222004e10000000a155106/content.htm">Using VA and applications</a>

Btw, I am just curious - how did you find that a method from the server is being invoked ?

Best Regards

Peter

[Former Member]

Hi,

Here is the link on JMS Messaging which also covers its features and administration:

http://help.sap.com/saphelp_nw04/helpdata/en/a3/63af1bbf09469fa1615c05f0daff6f/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/90/57849e5e3e45d784afc4e3bfa8136f/frameset.htm

Hope you will find the solution in the administration of JMS.

Regards,

Srinivasan T

<b>Helpful answer=>points</b>