Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Dispatcher running but no server connected

Hi Guys,

I got this error when we installed second instance in one database.

"SAP WebAS Engine is starting or started but not yet operational! If this state does not change within a few minutes, please contact your system administrator. Check the recommendations in SAP Notes: 943498, 764417 Message: Dispatcher running but no server connected!"

At first, dispatcher stopped after I restarted the system. All of the ABAP work process were ended.

I find a solution for the by adding SQLNET.INBOUND_CONNECT_TIMEOUT=120 to the script of sqlnet.ora. I was now able to connect with the ABAP side. But I still got yellow on the disp+work.exe. It indicates that the Dispatcher is Running, Message Server connection ok, Dialog Queue time: 0.00 sec, J2EE some process running.

Unfortunately, J2EE process table is not visible at MMC, and I can't monitor the SDM, server 0 and the dispatcher. I can no longer connect to the SAP Web AS.

Below are the logs.

for server 0 logs:

#1.5#02004C4F4F5000160000000A0000165400045699E94377D8#1221118950343#/System/Server##com.sapmarkets.bam.jmxadapter.CCMSCommandConsumer#######SAPEngine_System_Thread[impl:6]_23##0#0#Info#1#com.sapmarkets.bam.jmxadapter.CCMSCommandConsumer#Plain###New thread spawned for generating the ccmstemplates.#

#1.5#02004C4F4F500016000000330000165400045699E9486171#1221118950671#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:6]_23##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service tc.monitoring.logviewer started. (906 ms).#

#1.5#02004C4F4F500017000000000000165400045699E94867EC#1221118950671#/System/Server##com.sapmarkets.bam.communication.SocketMultiServer#######Thread[Thread-14,10,SAPEngine_System_Thread[impl:6]_Group]##0#0#Info#1#com.sapmarkets.bam.communication.SocketMultiServer#Plain###Opening registration server socket on port: 50009#

#1.5#02004C4F4F500018000000190000165400045699E954B7A4#1221118951468#/System/Server##com.sap.engine.services.monitor.common.installCcmsConnector()#######SAPEngine_System_Thread[impl:6]_28##0#0#Warning#1#com.sap.engine.services.monitor.common#Plain###Monitor service could not establish connection to CCMS.The monitors won't be sent to the CCMS. Could not attach to shared memory (java.lang.UnsatisfiedLinkError: no jmon in java.library.path).#

#1.5#02004C4F4F5000180000001A0000165400045699E9607D8D#1221118952250#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:6]_28##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service monitor started. (2625 ms).#

#1.5#02004C4F4F500000000000160000165400045699E9608067#1221118952250#/System/Server##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.Framework#Plain###ServiceManager started for 17422 ms. #

#1.5#02004C4F4F500000000000170000165400045699E9608184#1221118952250#/System/Server##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.Framework#Plain###Framework started for 24172 ms. #

#1.5#02004C4F4F500000000000180000165400045699E960A702#1221118952265#/System/Server##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.Framework#Plain###

SAP J2EE Engine Version 6.40 PatchLevel 106831.313 is running!

PatchLevel 106831.313 October 26, 2006 18:56 GMT

#

#1.5#02004C4F4F500019000000000000165400045699EB6FD7E9#1221118986812#/System/Server##com.sap.engine.core.thread.impl6.SingleThread.SingleThread.run().Interrupted#######Session Reader for cluster node 9782750##0#0#Warning#1#com.sap.engine.core.thread.impl6.SingleThread#Plain###Thread interrupted while waiting for new task to process. Probably the system is shutting down. null#

#1.5#02004C4F4F50001A000000000000165400045699EB6FD9A7#1221118986812#/System/Server##com.sap.engine.core.locking.AbstractLockingManagerImpl.elementLoss(element)#######SAPEngine_System_Thread[impl:6]_79##0#0#Info#1#com.sap.engine.core.locking.AbstractLockingManagerImpl#Java###The cluster-element was lost. Removing all enque locks related to the lost node.#1#9782750# #1.5#02004C4F4F50001A000000010000165400045699EB6FE421#1221118986812#/System/Server##com.sap.engine.core.locking.AbstractLockingManagerImpl.removeAllLokcsForClusterIdLogException(clusterId)#######SAPEngine_System_Thread[impl:6]_79##0#0#Info#1#com.sap.engine.core.locking.AbstractLockingManagerImpl#Java###All locks for cluster-element removed successfully#1#9782750#

#1.5#02004C4F4F50001B000000000000165400045699ECC6CCDD#1221119009296#/System/Server##com.sap.engine.core.thread.impl6.SingleThread.SingleThread.run().Interrupted#######Session Reader for cluster node 9782750##0#0#Warning#1#com.sap.engine.core.thread.impl6.SingleThread#Plain###Thread interrupted while waiting for new task to process. Probably the system is shutting down. null#

#1.5#02004C4F4F50001C000000000000165400045699ECC6CFBF#1221119009296#/System/Server##com.sap.engine.core.locking.AbstractLockingManagerImpl.elementLoss(element)#######SAPEngine_System_Thread[impl:6]_90##0#0#Info#1#com.sap.engine.core.locking.AbstractLockingManagerImpl#Java###The cluster-element was lost. Removing all enque locks related to the lost node.#1#9782750# #1.5#02004C4F4F50001C000000010000165400045699ECC6E06B#1221119009296#/System/Server##com.sap.engine.core.locking.AbstractLockingManagerImpl.removeAllLokcsForClusterIdLogException(clusterId)#######SAPEngine_System_Thread[impl:6]_90##0#0#Info#1#com.sap.engine.core.locking.AbstractLockingManagerImpl#Java###All locks for cluster-element removed successfully#1#9782750#

#1.5#02004C4F4F50001D000000000000165400045699EE5E8F89#1221119036031#/System/Server##com.sap.engine.core.thread.impl6.SingleThread.SingleThread.run().Interrupted#######Session Reader for cluster node 9782750##0#0#Warning#1#com.sap.engine.core.thread.impl6.SingleThread#Plain###Thread interrupted while waiting for new task to process. Probably the system is shutting down. null#

#1.5#02004C4F4F50001E000000000000165400045699EE5E91A1#1221119036031#/System/Server##com.sap.engine.core.locking.AbstractLockingManagerImpl.elementLoss(element)#######SAPEngine_System_Thread[impl:6]_5##0#0#Info#1#com.sap.engine.core.locking.AbstractLockingManagerImpl#Java###The cluster-element was lost. Removing all enque locks related to the lost node.#1#9782750# #1.5#02004C4F4F50001E000000010000165400045699EE5E9C47#1221119036031#/System/Server##com.sap.engine.core.locking.AbstractLockingManagerImpl.removeAllLokcsForClusterIdLogException(clusterId)#######SAPEngine_System_Thread[impl:6]_5##0#0#Info#1#com.sap.engine.core.locking.AbstractLockingManagerImpl#Java###All locks for cluster-element removed successfully#1#9782750#

#1.5#02004C4F4F50001F000000000000165400045699EFC8F9BD#1221119059781#/System/Server##com.sap.engine.core.thread.impl6.SingleThread.SingleThread.run().Interrupted#######Session Reader for cluster node 9782750##0#0#Warning#1#com.sap.engine.core.thread.impl6.SingleThread#Plain###Thread interrupted while waiting for new task to process. Probably the system is shutting down. null#

#1.5#02004C4F4F500020000000000000165400045699EFC8F9C1#1221119059781#/System/Server##com.sap.engine.core.locking.AbstractLockingManagerImpl.elementLoss(element)#######SAPEngine_System_Thread[impl:6]_51##0#0#Info#1#com.sap.engine.core.locking.AbstractLockingManagerImpl#Java###The cluster-element was lost. Removing all enque locks related to the lost node.#1#9782750#

#1.5#02004C4F4F500020000000010000165400045699EFC908CD#1221119059781#/System/Server##com.sap.engine.core.locking.AbstractLockingManagerImpl.removeAllLokcsForClusterIdLogException(clusterId)#######SAPEngine_System_Thread[impl:6]_51##0#0#Info#1#com.sap.engine

Please help me solve this error. All inputs are highly appreciated.

Thanks.

Former Member

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question