cancel
Showing results for 
Search instead for 
Did you mean: 

J2EE server restarting continuously

Former Member
0 Kudos

Hey Experts,

We are facing an issue with the J2EE server. It is restarting continuously. It was fine till yesterday night. Suddenly it started to behave like this. This is the extract from the dev_server0 log.

(quote)Fri Aug 14 11:17:25 2009

: 701322K->734631K(873472K), 0.3882712 secs] 810361K->734631K(1004800K), 0.4697989 secs]

46.487: [Full GC 46.487: [Tenured

Fri Aug 14 11:17:26 2009

: 734631K->730050K(873472K), 0.8389036 secs] 734631K->730050K(1004800K), [Perm : 97130K->96498K(262144K)], 0.8389919 secs]

Full thread dump Java HotSpot(TM) 64-Bit Server VM (1.4.2_16-b05 mixed mode):

"Finalizer" daemon prio=9 tid=0x0000000001350500 nid=0x23d8 in Object.wait() [0x000000000630f000..0x000000000630fb80]

at java.lang.Object.wait(Native Method)

- waiting on <0x000000001ab18528> (a java.lang.ref.ReferenceQueue$Lock)

at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)

- locked <0x000000001ab18528> (a java.lang.ref.ReferenceQueue$Lock)

at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)

at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)

"Reference Handler" daemon prio=10 tid=0x000000000134ffe0 nid=0x6d0 in Object.wait() [0x000000000610f000..0x000000000610fb80]

at java.lang.Object.wait(Native Method)

- waiting on <0x000000001ab10610> (a java.lang.ref.Reference$Lock)

at java.lang.Object.wait(Object.java:429)

at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115)

- locked <0x000000001ab10610> (a java.lang.ref.Reference$Lock)

"main" prio=5 tid=0x0000000001350270 nid=0x23cc in Object.wait() [0x000000000225f000..0x000000000225fc68]

at java.lang.Object.wait(Native Method)

- waiting on <0x000000001ab185d0> (a com.sap.engine.boot.StartFrame)

at java.lang.Object.wait(Object.java:429)

at com.sap.engine.boot.StartFrame.work(StartFrame.java:121)

- locked <0x000000001ab185d0> (a com.sap.engine.boot.StartFrame)

at com.sap.engine.boot.Start.main(Start.java:34)

"VM Thread" prio=5 tid=0x00000000013af910 nid=0x23d4 runnable

"VM Periodic Task Thread" prio=10 tid=0x00000000013afb10 nid=0x23f0 waiting on condition

"Suspend Checker Thread" prio=10 tid=0x00000000013afa10 nid=0x23dc runnable

[Thr 9172] JLaunchIExitJava: exit hook is called (rc = 666)

[Thr 9172] **********************************************************************

      • 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.

**********************************************************************

[Thr 9172] JLaunchCloseProgram: good bye (exitcode = 666)

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Problem solved by increasing the MaxPermSize and the MaxThreadCOunt parameters using the configtool.

Regards.

Former Member
0 Kudos

Hi,

This happened to me too.

What i did is i applied the whole SAP Note 723909 based on 32/64bit server. Then the issue resolved.

Please check again all your settings.

Thanks,

Rohan

Former Member
0 Kudos

Did this just start happening or have support packs been applied recently? I've worked on a system with this similar situation and helped stabilize the server by applying the latest kernel and SP's, resolving a slowness issue with the storage subsystem, and applying an OS patch to resolve an issue with system clocks on dual processor AMD systems (this generated negative ping tijmes).

Don't know if that helps but thought I'd share it to demonstrate some areas that you might want to look into.

J. Haynes

Former Member
0 Kudos

HI,

No updates have been performed. It just started recently. We actually locked some users of the previous consultants after which I believe the system started to behave like this. The weird thing is that even though, the users are locked in all the three DEV, QA and PROD systems, the problem is only with the DEV system.

Getting frustrated with this.

Dont know what to do.Also applied the note 63930 for registering the external RFC programs and recreating the RFC destinations is SM59.

Still no luck.

Former Member
0 Kudos

Hi Experts,

After going through the defaultTrace.trc file in logviewer, this is the first error that I could see after starting the server.

CPA Cache not updated with directory data, due to: Couldn't open Directory URL (http://pi-dev:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.pid.pi-dev), due to: HTTP 503: Not Ready

Source Name: com.sap.aii.service.cpa.impl.cache.CacheManager.I checked the RFC destination of INTEGRATION_DIRECTORY_HMI and also checked if PIDIRUSER and PIAFUSER are locked or not. But they are not locked.

After the above error, the errors just build up probably because of the adapter framework not firing up. One of the error is:

Failed to lookup object from JNDI for name localejbs/AFWListener within app level thread. Reason: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at localejbs, the whole lookup name is localejbs/AFWListener.

Source: com.sap.aii.af.ra.ms.runtime.Resources

I also increased the max thread count in the Application Thread Manager to 250 in the Config tool. I kept the heap sizes as posted above.

Any help will be greatly appreciated.

Regards

Edited by: DNSPK on Aug 20, 2009 1:37 AM

debasissahoo
Active Contributor
0 Kudos

Hi,

Check the JVM settings as per SAP Note Note 723909.

After change of the parameters restart the java cluster.

If you still face the issue, follow the java troubleshooting guide. and paste the latest log jvm_server0.out

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e09e4a5e-8280-2a10-ca98-a59dd47d...

Regards,

Debasis

Former Member
0 Kudos

Hey Sahoo,

Thanks for the reply. I checked the note and increased the heap size.

These are the settings I made for both the Instance and the Server ID.

-Xmx2048m

-Xms2048m

-Djco.jarm=1

-XX:PermSize=512m

-XX:MaxPermSize=512m

-XX:NewSize=320m

-XX:MaxNewSize=320m

After the changes, it still restarts by itself.

The jvm_server0.out file is empty.

Regards.

Former Member
0 Kudos

Hey guys,

This is the error message in the dev_jrfc.trc file.

Error file opened at 20090815 211043 Pacific Daylight Time Rel 6.45.15 (2007-12-03) [700.159]

Exception thrown [Sat Aug 15 21:10:43,164]:Exception thrown by application running in JCo Server

java.lang.RuntimeException: Bean LCRBEAN_GET_PROFILE_PARAMETERnot found on host cwe-pi-dev, ProgId =LCRSAPRFC_PID: Object not found in lookup of LCRBEAN_GET_PROFILE_PARAMETER.

at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:138)

at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Please help me out.

Regards.

0 Kudos

Hi,

What is current JDK version installed on machine. Automatic start of Java Server Node happen with old versions of JDK.

Rgds,

Mahesh

Former Member
0 Kudos

Hi,

The JDK version is j2sdk1.4.2_16-x64. We did not even update the JDK.

Regards.