on 10-30-2006 9:14 AM
Hello,
perhaps someone here has an idea? After a developer had problems with his developer studio and initiated a restart of the J2EE Engine, it doesn't come up again. It's a 640 Engine with SP17 on Windows/MSSQL.
In the MMC everything is green, but the dev_server0 says:
===========================================================
[Thr 2060] Mon Oct 30 09:59:58 2006
[Thr 2060] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 2060] JLaunchISetClusterId: set cluster id 6417950
[Thr 2060] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 2060] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 5472] Mon Oct 30 10:00:35 2006
[Thr 5472] JLaunchIExitJava: exit hook is called (rc=-11113)
[Thr 5472] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 940893 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
**********************************************************************
[Thr 5472] JLaunchCloseProgram: good bye (exitcode=-11113)
===========================================================
And the std_server0.out:
===========================================================
Loading services.:
Service runtimeinfo started. (63 ms).
Service cross started. (188 ms).
Service file started. (188 ms).
Service memory started. (187 ms).
Service trex.service started. (282 ms).
Service timeout started. (312 ms).
Service userstore started. (188 ms).
Service jmx_notification started. (141 ms).
Service p4 started. (375 ms).
Service classpath_resolver started. (47 ms).
Desired survivor size 37748736 bytes, new threshold 31 (max 31)
- age 1: 7349400 bytes, 7349400 total
Service log_configurator started. (10109 ms).
Service locking started. (0 ms).
Service naming started. (625 ms).
Service http started. (672 ms).
Service failover started. (156 ms).
Service appclient started. (188 ms).
Service javamail started. (360 ms).
Service ts started. (312 ms).
Service jmsconnector started. (359 ms).
Service licensing started. (63 ms).
Service connector started. (688 ms).
Service iiop started. (609 ms).
Service webservices started. (1562 ms).
service deploy ================= ERROR =================
Core service deploy failed. J2EE Engine cannot be started.
java.lang.NullPointerException
at java.util.Arrays$ArrayList.<init>(Arrays.java:2342)
at java.util.Arrays.asList(Arrays.java:2328)
at com.sap.engine.services.deploy.server.DeployServiceImpl.isWebdynproOnly(DeployServiceImpl.java:490)
at com.sap.engine.services.deploy.server.DeployServiceImpl.initializeApplications(DeployServiceImpl.java:463)
at com.sap.engine.services.deploy.server.DeployServiceFrame.start(DeployServiceFrame.java:93)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
java.lang.NullPointerException
at java.util.Arrays$ArrayList.<init>(Arrays.java:2342)
at java.util.Arrays.asList(Arrays.java:2328)
at com.sap.engine.services.deploy.server.DeployServiceImpl.isWebdynproOnly(DeployServiceImpl.java:490)
at com.sap.engine.services.deploy.server.DeployServiceImpl.initializeApplications(DeployServiceImpl.java:463)
at com.sap.engine.services.deploy.server.DeployServiceFrame.start(DeployServiceFrame.java:93)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
[Framework -> criticalShutdown] Core service deploy failed. J2EE Engine cannot be started.
Oct 30, 2006 10:00:35... com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_66] Fatal: Critical shutdown was invoked. Reason is: Core service deploy failed. J2EE Engine cannot be started.
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
===========================================================
The dispatcher seems on the basis of it's logfiles ok and running.
Anyone?
Best regards,
Kai
Problem solved: A developed Webdynpro was deleted in the DTR, but somehow it was stuck in the database. After a restore of the database the Engine came up with all services and is running fine now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.