Skip to Content

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

Troubles after upgrade to EHP5

Hallo, fiends.

Not so far I install with EHPi EHP5 on my test system. After that I get error on JAVA:

 Application error occured during processing java.lang.NoSuchMethodError:com/sap/security/core/util/imp/LogonUtils. getOriginalURLFromCookie(Ljavax/servlet/ http/HttpServletRequest;)Ljava/lang/String 

I found solution for this problem - it is note 1577330. By this note I download a few patches:

rowstartpatch name          SAPJTECHS06P
rowstartpatch level         7

rowstartpatch name          SAPJEECOR06P
rowstartpatch level         9

Then I try install this patches by JSPM java process server0 can't start I saw.

In dev_server0:

[Thr 30] JHVM_RegisterNatives: com.sap.bc.krn.perf.PerfTimes
[Thr 30] JHVM_RegisterNatives: com.sap.bc.proj.jstartup.JStartupFramework
[Thr 30] JLaunchISetClusterId: set cluster id 8419150
[Thr 30] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 30] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]

[Thr 19] Mon May 23 22:51:44 2011
[Thr 19] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 19] **********************************************************************
[Thr 19] *** ERROR => The Java VM terminated with a non-zero exit code.
[Thr 19] *** Please see SAP Note 943602 , section 'J2EE Engine exit codes'
[Thr 19] *** for additional information and trouble shooting.
[Thr 19] **********************************************************************
[Thr 19] SigISetIgnoreAction : SIG_IGN for signal SIGCHLD
[Thr 19] JLaunchCloseProgram: good bye (exitcode = -11113) 

In the std_server0.out:

node name   : server0
pid         : 19968
system name : DV2
system nr.  : 00
started at  : Mon May 23 22:51:36 2011

[Thr 01] MtxInit: 10001 0 2

SAP J2EE Engine Version 7.02   PatchLevel 107037. is starting...

Loading: LogManager ... 610 ms. 
Loading: PoolManager ... 2 ms. 
Loading: ApplicationThreadManager ... 66 ms. 
Loading: ThreadManager ... 25 ms. 
Loading: IpVerificationManager ... 12 ms. 
Loading: ClassLoaderManager ... 12 ms. 
Loading: ClusterManager ... 160 ms. 
Loading: LockingManager ... 69 ms. 
Loading: ConfigurationManager ... 1891 ms. 
Loading: LicensingManager ... 151 ms. 
Loading: CacheManager ... 95 ms. 
Loading: ServiceManager ... 

Loading services.:
[Framework -> criticalShutdown] 10 core services not loaded: [connector; userstore; adminadapter; security; jmx; deploy; com.sap.security.core.ume.service; jmx_notification; basicadmin; dbpool]. Please check default trace files for details.
May 23, 2011 10:51:44...            com.sap.engine.core.Framework [Thread[Thread-1,5,main]] Fatal: Critical shutdown was invoked. Reason is: 10 core services not loaded: [connector; userstore; adminadapter; security; jmx; deploy; com.sap.security.core.ume.service; jmx_notification; basicadmin; dbpool]. Please check default trace files for details. 

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