Skip to Content
author's profile photo Former Member
Former Member

During SSM installation urgente please

Hi all,

during SSM 4.0 sr3 installation, I have the following error in dev_server0 file......

SDM and dispatcher service are running but server 0 It does'n start.............

  • ERROR => The Java VM terminated with a non-zero exit code.

  • Please see SAP Note 943602 , section 'J2EE Engine exit codes'

  • for additional information and trouble shooting.

last rows of std_server0.out are the following:

"VM Thread" prio=5 tid=0x00000001015060f0 nid=0x7 runnable

"VM Periodic Task Thread" prio=10 tid=0x0000000101515400 nid=0xf runnable

"Suspend Checker Thread" prio=10 tid=0x000000010150edf0 nid=0xa runnable

Service com.sap.security.core.ume.service > hard reference to service dbpool.

Service http > hard reference to interface log.

Service cafruntimeconnectivityimpl > service cafruntimeconnectivityimpl start method invoked.

Service tclmctcconfsservice_sda > hard reference to service deploy.

Service CUL > hard reference to interface container.

Service tc.monitoring.logviewer > hard reference to service jmx.

Service tcdisdic~srv > hard reference to service com.sap.security.core.ume.service.

Service apptracing > hard reference to service deploy.

Service com.adobe~XMLFormService > hard reference to service naming.

Service shell > hard reference to interface security.

Service tcsecwssecservice > hard reference to service tcsecsecurestorageservice.

Service servlet_jsp > hard reference to service naming.

Service iiop > hard reference to service ts.

Service com.adobe~FontManagerService > hard reference to service iiop.

Service bimmrdeployer > hard reference to interface container.

Service classload > hard reference to service security.

Service com.adobe~DocumentServicesLicenseSupportService > hard reference to service naming.

Service log_configurator > service log_configurator start method invoked.

Service com.adobe~DocumentServicesBinaries2 > hard reference to service naming.

Service configuration > hard reference to interface log.

Service basicadmin > hard reference to service jmx.

Service dbpool > hard reference to service connector.

Service appclient > hard reference to service naming.

[Framework -> criticalShutdown] 10 core services have timed out [naming; connector; adminadapter; security; jmx; deploy; com.sap.sec

urity.core.ume.service; log_configurator; basicadmin; dbpool].

Feb 8, 2008 11:57:13 AM com.sap.engine.core.Framework [Thread[Thread-1,5,main]] Fatal: Critical shutdown was invoked. Re

ason is: 10 core services have timed out [naming; connector; adminadapter; security; jmx; deploy; com.sap.security.core.ume.service;

log_configurator; basicadmin; dbpool].

I checked the right sdk version, and It is ok....I don't know what I should do....

Can someone help me?

thanks in advanced

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Feb 08, 2008 at 04:03 PM

    Check in server0 the section above the one you posted, that is just the last exit of the jlaunch.

    Also check jcontrol* and dev_bootstrap*

    Markus

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.