Services running in time out and portal stays in starting application

Question

Hi Group,
when starting the portal (sp12 on windows) the status is running into "starting applications" and don't change to running.
In the server logfile I found:
Timed out services:
Service ssl.
Service tc.monitoring.logviewer.
Service keystore.
Service shell.
Service prtbridge.
Service webdynpro.
Service com.sap.security.core.ume.service.
Service pmi.
Service tcsecsaml~service.
Service sld.
Service com.sap.portal.prt.sapj2ee.
Service jms_provider.
Service basicadmin.
Service classload.
Service adminadapter.
Service telnet.
Service servlet_jsp.
Service ejb.
Service dsr.
Service monitor.
Service tcsecdestinations~service.
Service tcsecsecurestorage~service.
Service security.
Service applocking.
Service com.sap.portal.pcd.gl.
Service jmx.
Service DQE.
Service tceCATTPingservice.
Service rfcengine.
================================================================================
Full thread dump Java HotSpot(TM) Server VM (1.4.2_09-b05 mixed mode):
"Thread-12" daemon prio=10 tid=0x055bc2f8 nid=0xff0 in Object.wait() [7f4f000..7f4fd94]
     at java.lang.Object.wait(Native Method)
     - waiting on <0x11ad9298> (a java.util.TaskQueue)
     at java.util.TimerThread.mainLoop(Timer.java:429)
     - locked <0x11ad9298> (a java.util.TaskQueue)
     at java.util.TimerThread.run(Timer.java:382)
"ConnectionSetCleaner Thread (UNMANAGED)." prio=10 tid=0x0433ccf8 nid=0x1c8 in Object.wait() [7f0f000..7f0fd94]
     at java.lang.Object.wait(Native Method)
     - waiting on <0x17810060> (a com.sap.engine.services.connector.jca.ConnectionHashSet$ConnectionSetCleaner)
     at com.sap.engine.services.connector.jca.ConnectionHashSet$ConnectionSetCleaner.run(ConnectionHashSet.java:636)
     - locked <0x17810060> (a com.sap.engine.services.connector.jca.ConnectionHashSet$ConnectionSetCleaner)
"SAPEngine_System_Thread[impl:5]_73" prio=5 tid=0x044f95d0 nid=0xdc in Object.wait() [6ecf000..6ecfd94]
     at java.lang.Object.wait(Native Method)
     - waiting on <0x17810118> (a com.sap.engine.lib.util.WaitQueue)
     at java.lang.Object.wait(Object.java:429)
     at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
     - locked <0x17810118> (a com.sap.engine.lib.util.WaitQueue)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:121)
"SAPEngine_System_Thread[impl:5]_72" prio=5 tid=0x05825c58 nid=0xbc0 in Object.wait() [6e7f000..6e7fd94]
     at java.lang.Object.wait(Native Method)
     - waiting on <0x17810118> (a com.sap.engine.lib.util.WaitQueue)
     at java.lang.Object.wait(Object.java:429)
     at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
     - locked <0x17810118> (a com.sap.engine.lib.util.WaitQueue)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:121)
"SAPEngine_System_Thread[impl:5]_71" prio=5 tid=0x047e74f8 nid=0xc6c in Object.wait() [6e3f000..6e3fd94]
     at java.lang.Object.wait(Native Method)
     - waiting on <0x17810118> (a com.sap.engine.lib.util.WaitQueue)
     at java.lang.Object.wait(Object.java:429)
     at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
     - locked <0x17810118> (a com.sap.engine.lib.util.WaitQueue)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:121)
what went wrong?
Kind regards,
Mike

Answer 1

Did you ever find an answer? I'm having the exact same error on Solaris.