As Java not running - PI 7.3

[Former Member]

Hi,

When we are applyiing the NW 7.3 SP05, JSPM SP has been deployed and restarted the JSPM. Once restarted, it was showing the status restarting as Java. At last, it fetches the error " As java not

running". when I check dev_server0, it fetches the below

Resources:

/data/sap/PD1/DVEBMGS00/j2ee/cluster/bin/ext/webservices_lib/lib/private/sap.com_tcje_{webservices_lib}impl.jar

-

---

at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:278)

at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:247)

at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:367)

... 21 more

*FATAL: Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [tc_lmnzdm~crrsrv] failed to start

]*Heap

par new generation reserved 349184K, committed 349184K, used 309758K [0x00002aaabf170000, 0x00002aaad4670000, 0x00002aaad4670000)

eden space 285696K, 97% used [0x00002aaabf170000, 0x00002aaad02d7720, 0x00002aaad0870000)

from space 31744K, 93% used [0x00002aaad2770000, 0x00002aaad4488260, 0x00002aaad4670000)

to space 31744K, 0% used [0x00002aaad0870000, 0x00002aaad0870000, 0x00002aaad2770000)

concurrent mark-sweep generation reserved 2272256K, committed 2272256K, used 836K [0x00002aaad4670000, 0x00002aab5f170000, 0x00002aab5f170000)

concurrent-mark-sweep perm gen reserved 1048576K, committed 1048576K, used 65835K [0x00002aab5f170000, 0x00002aab9f170000, 0x00002aab9f170000)

Please help me to resolve the issue.

Regards

Shobana

[marksmyth · Accepted solution]

Hello

This is the PI forum (which deals with PI technical issues only). This query would be best placed in the Netweaver Administrator forum. We will forward this thread to the Netweaver Administrator forum and you should get a better response there.

Regards

Moderator.

[Former Member]

Hallo,

Please refer to this note

Note 1713021 - Core service [tc~lm~nzdm~crrsrv] failed to start

usually the problem is caused by sapstartsrv for the instance is stopped/not running

To solve the connectivity issue, check the host file for entries which prevent the AS Java from communicating with the SAP Service "sapstartsrv". Adapt the host file so that localhost is reachable via IPv4 (127.0.0.1) and restart service "sapstartsrv".

In addition check if sapcontrol is working for the instance which does not start:

sapcontrol -nr [instance number]  -function GetProcessList

In our case this solve the issue.

Regards,

Paul

[Former Member]

Hi,

The Issue has been resolved by reinstallaing the PI 7.3.

Regards

Shobana

[Former Member]

Hi

Check the Heap memory, set in the config tool, and increase that accordingly. Refer to SAP Note 723909, for more details.

Its purely memory issue, because of which your JAVA stacking is not comming up.

Thanks!!

Rajesh

[Former Member]

Hi Rajesh,

Thanks for you reply. I tried to change the Heap and Perm accordingly but still faces the same error. I herewith attached the dev_dispatcher for your reference

LOG => State changed from 0 (Initial) to 2 (Starting framework).

F [Thr 1084852544] *** LOG state real time: 1.314 CPU time: 0.480 sys, 1.720 usr

F [Thr 1084852544] *** LOG total real time: 1.314 CPU time: 0.480 sys, 1.720 usr

F [Thr 1084852544]

J [GC 20246K->14827K(27200K), 0.0161140 secs]

J [Full GC 14827K->10681K(35840K), 0.0189690 secs]

J [GC 22969K->15773K(48000K), 0.0441630 secs]

J

J Wed Feb 29 07:35:07 2012

J [GC 33757K->15011K(48384K), 0.0295920 secs]

J [GC 32995K->14910K(59456K), 0.0123500 secs]

J [GC 44670K->15427K(59776K), 0.0119180 secs]

J

J Wed Feb 29 07:35:08 2012

J [GC 45187K->14911K(69376K), 0.0025120 secs]

J [GC 54783K->15787K(70144K), 0.0033030 secs]

J [GC 55659K->16792K(80064K), 0.0114070 secs]

F

F [Thr 1084852544] Wed Feb 29 07:35:17 2012

F [Thr 1084852544] *** LOG => State changed from 2 (Starting framework) to 3 (Running).

F [Thr 1084852544] *** LOG state real time: 11.521 CPU time: 0.480 sys, 4.280 usr

F [Thr 1084852544] *** LOG total real time: 12.835 CPU time: 0.960 sys, 6.000 usr

F [Thr 1084852544]

J

J Wed Feb 29 07:35:18 2012

J [GC 67864K->20186K(81216K), 0.0197470 secs]

F

F [Thr 1084852544] Wed Feb 29 07:35:22 2012

F [Thr 1084852544] *** LOG => State changed from 3 (Running) to 5 (Stopping).

F [Thr 1084852544] *** LOG state real time: 4.297 CPU time: 0.110 sys, 2.750 usr

F [Thr 1084852544] *** LOG total real time: 17.133 CPU time: 1.070 sys, 8.750 usr

F [Thr 1084852544]

F

F [Thr 1085905216] Wed Feb 29 07:35:22 2012

F [Thr 1085905216] *** LOG => SfCJavaVm: exit hook is called. (rc = 0)

F

F [Thr 47674139790976] Wed Feb 29 07:35:22 2012

F [Thr 47674139790976] *** LOG => exiting (exitcode 0, retcode 0).

M [Thr 47674139790976] CCMS: CCMS Monitoring Cleanup finished successfully.

Intially, it's starting and running. After some time, it goes stopping state.

Regards

shobana

[Former Member]

Hi Shobana,

Can you check, the log /usr/sap/<SID>/D*/j2ee/cluster/server0/log/application.0.log and other defaultTrace.x.trc files ?

From the above log, I understand that, because of insufficient memory, the processes are killed. From the same note, which I have mentioned, try to set other parameters too, like garbage collector etc. Also, if you 2 java instances, like server0 and server1, for time being, start only 1 and disable the other and see.

Try to increase the heap memory further, based on the available memory. From 2 GB to 3 - 4 GB and see.

Hope this helps to fix.

Regds,

Rajesh

[Former Member]

Hi Rajesh,

I had increased the Heap Size from 3072 to 3584 and also incresed the Perm Gen from 1536 to 1792 but still faces the same error.

I herewith pasted the Application _log for your reference.

#BC-INS#tc_SLutility#C00093F3A9A000610000010E00005C09#2108750000000002##com.sap.sl.util.jarsl.impl.JarSL#J2EE_ADMIN#30##171FC42A05CC1000A227C31BCD6842D0#171fc42a05cc1000a227c31bcd6842d0#171fc42a05cc1000a227c31bcd6842d0#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

stack trace:#

#2.0 #2012 02 27 10:27:38:711#+0200#Fatal#/Applications/SL/UTIL#

#BC-INS#tc_SLutility#C00093F3A9A000670000011000005C09#2108750000000002##com.sap.sl.util.jarsl.impl.JarSL#J2EE_ADMIN#32##5CC5BE9A05F310009D3CAF4371A37F0C#5cc5be9a05f310009d3caf4371a37f0c#5cc5be9a05f310009d3caf4371a37f0c#0#Thread[RMI/IIOP Worker [4],5,Dedicated_Application_Thread]#Plain##

Exc=java.io.EOFException: Unexpected end of ZLIB input stream#

#2.0 #2012 02 27 10:27:38:711#+0200#Error#/Applications/SL/UTIL#

#BC-INS#tc_SLutility#C00093F3A9A000670000011200005C09#2108750000000002##com.sap.sl.util.jarsl.impl.JarSL#J2EE_ADMIN#32##5CC5BE9A05F310009D3CAF4371A37F0C#5cc5be9a05f310009d3caf4371a37f0c#5cc5be9a05f310009d3caf4371a37f0c#0#Thread[RMI/IIOP Worker [4],5,Dedicated_Application_Thread]#Plain##

stack trace:#

#2.0 #2012 02 27 10:45:11:978#+0200#Info#/Applications/ExchangeInfrastructure#

#BC-XI-IBD#com.sap.xi.util.misc#C00093F3A9A000830000000100005C09#2108750000000270#sap.com/com.sap.xi.repository#com.sap.aii.ib.core.applcomp.ApplicationComponent#J2EE_GUEST#0##5B4415D1611F11E1BD13000000202D4E#5b4415d1611f11e1bd13000000202d4e#5b4415d1611f11e1bd13000000202d4e#0#Application [28]#Plain##

Shutdown of XI Application "REPOSITORY" finished.#

#2.0 #2012 02 27 10:45:12:875#+0200#Info#/Applications/Common/Archiving/Initialization Service#

#BC-ILM-ACJ#sap.com/tc_archtechinitservice#C00093F3A9A000840000000000005C09#2108750000001299#sap.com/tc_archtechxmldasinitservice#com.sap.archtech.initservice#RUNAS_yynklq#0##5B4415D1611F11E1BD13000000202D4E#5b4415d1611f11e1bd13000000202d4e#5b4415d1611f11e1bd13000000202d4e#0#Application [31]#Plain##

XMLDAS MBean Unregistration: SAP_ITSAMXMLDataArchivingServer MBean was unregistered successfully.#

#2.0 #2012 02 27 10:45:13:082#+0200#Info#/Applications/ExchangeInfrastructure#

#BC-XI-IBD#com.sap.xi.util.misc#C00093F3A9A000850000000100005C09#2108750000001475#sap.com/com.sap.xi.directory#com.sap.aii.ib.core.applcomp.ApplicationComponent#J2EE_GUEST#0##5B4415D1611F11E1BD13000000202D4E#5b4415d1611f11e1bd13000000202d4e#5b4415d1611f11e1bd13000000202d4e#0#Application [24]#Plain##

Shutdown of XI Application "DIRECTORY" finished.#

#2.0 #2012 02 27 10:45:15:193#+0200#Info#/Applications/DI/SDIC#

com.sap.DI.sdic.050004#BC-CTS-SDIC#tc_disdic_{srv#C00093F3A9A000880000000000005C09#2108750000002828##com.sap.di.sdic.srv.java.SDICServiceFrame#####5b4415d1611f11e1bd13000000202d4e##0#Service Stopper [tc}di_sdicsrv]#Plain##

Successfully stopped the SDIC service#

#2.0 #2012 02 27 10:45:15:279#+0200#Warning#/Applications/ExchangeInfrastructure/Security#

#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C00093F3A9A000890000000000005C09#2108750000001709##com.sap.aii.security.ServiceThread.ServiceThread.run()#J2EE_GUEST#0###ab39d6be611111e18de8005056ab629d##0#Application [38]#Plain##

InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.#

#2.0 #2012 02 27 10:45:15:280#+0200#Error#com.sap.aii.af.service.trex.TrexScheduler#

#BC-XI-CON-AFW#com.sap.aii.af.lib#C00093F3A9A0008A0000000100005C09#2108750000001714##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#J2EE_GUEST#0###ab39d6be611111e18de8005056ab629d##0#Application [40]#Plain##

InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0 #2012 02 27 10:45:18:204#+0200#Info#/Applications/ChangeRecording#

com.sap.CTS.cr_.005009#BC-CTS-TMS-PLS#tc_dicr_{service#C00093F3A9A0008D0000000000005C09#2108750000003455##com.sap.tc.di.cr.crService.startup.ChangeRecordingStartup#####5b4415d1611f11e1bd13000000202d4e##0#Service Stopper [tc}di_crservice]#Plain##

Shutting down change recording -> deregistration of internal services, application callbacks and listeners#

#2.0 #2012 02 27 10:50:36:322#+0200#Fatal#/Applications/NZDM#

#BC-UPG-OCS-ZDM#tc_lmnzdm_{crrsrv#C00093F3A9A000090000000100001298#2108750000000867##com.sap.tc.lm.nzdm.crr.srv.core.NZDMServiceFrame#####141ed5e6612011e1c429005056ab629d##0#Service Runner [tc}lm_nzdmcrrsrv]#Plain##

NZDM service startup failed!#

#2.0 #2012 02 27 10:51:47:210#+0200#Fatal#/Applications/NZDM#

#BC-UPG-OCS-ZDM#tc_lmnzdm_{crrsrv#C00093F3A9A0000C00000000000039ED#2108750000000874##com.sap.tc.lm.nzdm.crr.srv.core.NZDMServiceFrame#####7cadad93629711e1ba52005056ab629d##0#Service Runner [tc}lm_nzdmcrrsrv]#Plain##

NZDM service startup failed!#

Default Trace :

com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.<init>(SAPServiceDelegate.java:140)

at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createDelegate(CTSProvider.java:179)

at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createServiceDelegate(CTSProvider.java:160)

at javax.xml.ws.Service.<init>(Service.java:56)

at com.sap.tc.lm.nzdm.crr.srv.util.sapControlWS.SAPControl.<init>(SAPControl.java:27)

at com.sap.tc.lm.nzdm.crr.srv.util.sapControlWS.NZDMSAPControl.<init>(NZDMSAPControl.java:91)

at com.sap.tc.lm.nzdm.crr.srv.util.sapControlWS.NZDMSAPControl.init(NZDMSAPControl.java:120)

at com.sap.tc.lm.nzdm.crr.srv.core.NZDMServiceFrame.start(NZDMServiceFrame.java:71)

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)

at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)

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

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

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

Caused by: java.lang.ClassNotFoundException: com.sap.engine.services.webservices.espbase.configuration.PropertyType

-

---

Loader Info -

---

ClassLoader name: [library:webservices_lib]

Loader hash code: 7c6159c4

Living status: alive

Direct parent loaders:

[system:Frame]

[library:mail]

[library:jaxr_api]

[interface:webservices]

[interface:tc_secdestinations~interface]

[library:javax_persistenceapi]

[library:jws_api]

[library:tc_blbase_webservices_lib]

[library:ejb_api]

[interface:tc_jesca~spi]

[interface:appcontext]

Resources:

/data/sap/PD1/DVEBMGS00/j2ee/cluster/bin/ext/webservices_lib/lib/private/sap.com_tcje_{webservices_lib}impl.jar

-

---

at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:278)

at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:247)

at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:367)

... 21 more

#

#2.0 #2012 02 29 07:37:44:087#+0200#Fatal#com.sap.engine.core.Framework#

com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C00093F3A9A0000C00000006000039ED#2108750000000874##com.sap.engine.core.Framework#####7cadad93629711e1ba52005056ab629d##0#Service Runner [tc_lmnzdm~crrsrv]#Plain##

Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [tc_lmnzdm~crrsrv] failed to start]#

Regards

Shobana

[Former Member]

Hi

If you search for this servicein default trace file of server0 you will find the cause why it is not starting. You can check the

cause or attch this with message. Oterwise java server restart will also help here.

Regards,

Vipin

[Former Member]

Hi Shobana,

From the above log,

ED#2108750000000874##com.sap.engine.core.Framework#####7cadad93629711e1ba52005056ab629d##0#Service Runner [tc_lmnzdm~crrsrv]#Plain##

Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [tc_lmnzdm~crrsrv] failed to start]#

I understand that, Framework application couldn;t start. Can you try to start the same manually, in Configtool [server0 > Deploy > webdynpro> search for tc_lmnzdm~crrsrv ]

and see, what error message it throws.

Try to upgrade the kernel, to the latest version, available.

Regds,

Rajesh