cancel
Showing results for 
Search instead for 
Did you mean: 

Error during upgrade from 640sp19 to 700sp13

Former Member
0 Kudos

My upgrade stuck at START_J2EE_INITIAL

this is the message extracted from std_dispatcher.out

for thye p4 problem i have follow the Note 609603 - Problems with Multiple NICs and SAP J2EE Engine

but seem still having problem..

The ume server is ECC6 server...

Service classload started. (4 ms).

Dec 26, 2007 2:36:35 PM com.sap.engine.services.ssl [SAPEngine_System_Thread[impl:6]_43] Fatal: Source: com.sap.engine.services.ssl.exception.SSLConfigurationException: Unable to configure active SSL sockets; check log for details; Description: SSL transport supplier not registered; Consequences: SSL transport protocol is not available; Countermeasures:see log for details

Service log_configurator started. (8206 ms).

Service configuration started. (2 ms).

Service jms_provider started. (198 ms).

service basicadmin ================= ERROR =================

Core service basicadmin failed. J2EE Engine cannot be started.

java.lang.NoClassDefFoundError: com/sap/bc/proj/jstartup/JStartupFramework

at com.sap.engine.services.basicadmin.BasicadminServiceFrameImpl.registerInstanceMBeans(BasicadminServiceFrameImpl.java:254)

at com.sap.engine.services.basicadmin.BasicadminServiceFrameImpl.start(BasicadminServiceFrameImpl.java:110)

at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)

at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)

java.lang.NoClassDefFoundError: com/sap/bc/proj/jstartup/JStartupFramework

at com.sap.engine.services.basicadmin.BasicadminServiceFrameImpl.registerInstanceMBeans(BasicadminServiceFrameImpl.java:254)

at com.sap.engine.services.basicadmin.BasicadminServiceFrameImpl.start(BasicadminServiceFrameImpl.java:110)

at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)

at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)

[Framework -> criticalShutdown] Core service basicadmin failed. J2EE Engine cannot be started.

Dec 26, 2007 2:36:40 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:6]_6] Fatal: Critical shutdown was invoked. Reason is: Core service basicadmin failed. J2EE Engine cannot be started.

-


stdout/stderr redirect

-


node name : dispatcher

pid : 635060

system name : WS3

system nr. : 00

started at : Wed Dec 26 14:36:45 2007

JVMST080: verbosegc is enabled

JVMST082: -verbose:gc output will be written to stderr

SAP J2EE Engine Version 7.00 PatchLevel 109044.44 is starting...

Loading: LogManager ... 2198 ms.

Loading: PoolManager ... 4 ms.

Loading: ThreadManager ... 251 ms.

Loading: IpVerificationManager ... 22 ms.

Loading: ConnectionsManipulator ... 29 ms.

Loading: ClassLoaderManager ... 18 ms.

Loading: ClusterManager ... 303 ms.

Loading: PortsManager ... 17 ms.

Loading: LockingManager ... 134 ms.

Loading: ConfigurationManager ... 5242 ms.

Loading: LicensingManager ... 26 ms.

Loading: CacheManager ... 263 ms.

Loading: ServiceManager ...

Loading services.:

Service security started. (26 ms).

Service httptunneling started. (54 ms).

Service sld started. (73 ms).

Service licensing started. (111 ms).

Service jmx_notification started. (35 ms).

Service timeout started. (148 ms).

Service webservices started. (109 ms).

Service memory started. (157 ms).

Service keystore started. (216 ms).

Service iiop started. (181 ms).

Service ssl started. (209 ms).

Service jmx started. (708 ms).

Service shell started. (1158 ms).

service p4 ================= ERROR =================

Core service p4 failed. J2EE Engine cannot be started.

java.lang.NullPointerException

at com.sap.engine.core.cluster.impl6.ms.MSEventListener$LogonInfo.isFQHN(MSEventListener.java:2037)

at com.sap.engine.core.cluster.impl6.ms.MSEventListener$LogonInfo.getLocalHost(MSEventListener.java:1992)

at com.sap.engine.core.cluster.impl6.ms.MSEventListener$LogonInfo.<init>(MSEventListener.java:2094)

at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1369)

at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.putLogonInfo(MSConnectionImpl.java:605)

at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.putLogonInfo(ClusterManagerImpl.java:3165)

at com.sap.engine.core.service630.context.cluster.session.CommunicationSessionContextImpl.putLogonInfo(CommunicationSessionContextImpl.java:143)

at com.sap.engine.services.rmi_p4.dispatcher.P4ServiceFrame.putLogonInfo(P4ServiceFrame.java:426)

at com.sap.engine.services.rmi_p4.dispatcher.P4ServiceFrame.start(P4ServiceFrame.java:100)

at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)

at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)

java.lang.NullPointerException

at com.sap.engine.core.cluster.impl6.ms.MSEventListener$LogonInfo.isFQHN(MSEventListener.java:2037)

at com.sap.engine.core.cluster.impl6.ms.MSEventListener$LogonInfo.getLocalHost(MSEventListener.java:1992)

at com.sap.engine.core.cluster.impl6.ms.MSEventListener$LogonInfo.<init>(MSEventListener.java:2094)

at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1369)

at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.putLogonInfo(MSConnectionImpl.java:605)

at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.putLogonInfo(ClusterManagerImpl.java:3165)

at com.sap.engine.core.service630.context.cluster.session.CommunicationSessionContextImpl.putLogonInfo(CommunicationSessionContextImpl.java:143)

at com.sap.engine.services.rmi_p4.dispatcher.P4ServiceFrame.putLogonInfo(P4ServiceFrame.java:426)

at com.sap.engine.services.rmi_p4.dispatcher.P4ServiceFrame.start(P4ServiceFrame.java:100)

at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)

at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)

[Framework -> criticalShutdown] Core service p4 failed. J2EE Engine cannot be started.

Dec 26, 2007 2:37:03 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:6]_7] Fatal: Critical shutdown was invoked. Reason is: Core service p4 failed. J2EE Engine cannot be started.

Service telnet started. (109 ms).

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

In the Config tool, for the 'Instance ID' open the 'Servers Debug' and uncheck 'Restricted load balance'. Save the changes.

For the Server_ID, open 'debug' tab and check the checkbox for 'Restricted load balance'. Save the changes. When there are more than one server node, ensure that at least one server node has unchecked box. Then, restart the whole cluster.

Hope this helps !

Regards

Srinivasan T

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi thanks for the hints, but the mentioned options is already unchecked in my server

Former Member
0 Kudos

Hi,

Before proceeding with the upgrade, check that the following Java VM setting is configured correctly in your system.

In the configtool->Cluster Data node->Instance_IDxxxxxxx node->Dispatcher_IDxxxxxx node->General tab check the Java parameters.

If there is a "-" missing in front of the -Xmsxxx parameter, add "-". Save change and restart the system.

Hope this helps !

Regards

Srinivasan T

Former Member
0 Kudos

My problem is solved.. its because the script did not copy the new kernel to /sapmnt/SID/exe folder

after copying the kernel from /usr/sap/jupgrade/data/kernel

the j2ee can startup, in addtion im also updating the java to lates SR9 JIT version