on 11-22-2013 3:51 PM
Hi,
We installed NW 7.3 in HP UX, suddenly Java Stack stopped responding.
Server is Running in JCMON
Server trace log showing :
please suggest....
#BC-JAS-ADM-MON#sap.com/com.sap.engine.heartbeat#C00010B829870039000000E8000060FA#5556250000000001##com.sap.engine.monitor.impl.VMAggregatedStatesMonitors####2440709D537D11E3B9C700306EF3DEF1#2440709d537d11e3b9c700306ef3def1#2440709d537d11e3b9c700306ef3def1#0#Timeout Service Synchronous Queue Processor#Plain##
Exception while retrieving system problems monitors.
[EXCEPTION]
com.sap.mona.api.NodeNotExistingException: com.sap.mona.api.JMonAPIException: can not find [\\Kernel\\SAPJVM\\SystemProblemReporting\\GC Work Time Ratio] under TID <SUMM>:I09 :SAPLicense:5:1:499:-1
at com.sap.mona.api.JMonException.create(JMonException.java:109)
at com.sap.mona.api.NodeFactory.getMonitoringNode(NodeFactory.java:145)
at com.sap.engine.monitor.impl.VMAggregatedStatesMonitors.evaluateGCMonitor(VMAggregatedStatesMonitors.java:146)
at com.sap.engine.monitor.impl.VMAggregatedStatesMonitors.getSystemProblems(VMAggregatedStatesMonitors.java:88)
at sun.reflect.GeneratedMethodAccessor436.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)
at com.sun.jmx.mbeanserver.PerInterface.getAttribute(PerInterface.java:65)
at com.sun.jmx.mbeanserver.MBeanSupport.getAttribute(MBeanSupport.java:216)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:666)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:638)
at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:662)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:423)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:231)
at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:161)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:235)
at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:559)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:161)
at com.sap.engine.services.monitor.mbeans.Monitor.getMBeanResult(Monitor.java:268)
at com.sap.engine.services.monitor.mbeans.IntegerMonitor.collectMonitoringData(IntegerMonitor.java:167)
at com.sap.engine.services.monitor.mbeans.IntegerMonitor.collectAndStoreMonitoringData(IntegerMonitor.java:71)
at com.sap.engine.services.monitor.mbeans.Monitor.handleNotification(Monitor.java:134)
at com.sap.engine.services.monitor.common.StandardMBeanWrapper.handleNotification(StandardMBeanWrapper.java:77)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerInterceptor.java:1732)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:257)
at javax.management.NotificationBroadcasterSupport$SendNotifJob.run(NotificationBroadcasterSupport.java:322)
at javax.management.NotificationBroadcasterSupport$1.execute(NotificationBroadcasterSupport.java:307)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:229)
at com.sap.engine.services.jmx.timer.j2ee.Timer.sendTimerNotification(Timer.java:431)
at com.sap.engine.services.jmx.timer.j2ee.TimerNotificationEntry.timeout(TimerNotificationEntry.java:69)
at com.sap.engine.services.timeout.TimeoutNode.synchronousRun(TimeoutNode.java:123)
at com.sap.engine.services.timeout.TimeoutManagerImpl.singleThreadRun(TimeoutManagerImpl.java:707)
at com.sap.engine.services.timeout.TimeoutManagerRunner.run(TimeoutManagerRunner.java:18)
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)
#
#2.#2013 11 22 21:39:32:838#+0530#Error#com.sap.engine.monitor.impl.VMAggregatedStatesMonitors#
#BC-JAS-ADM-MON#sap.com/com.sap.engine.heartbeat#C00010B829870039000000E9000060FA#5556250000000001##com.sap.engine.monitor.impl.VMAggregatedStatesMonitors####2440709D537D11E3B9C700306EF3DEF1#2440709d537d11e3b9c700306ef3def1#2440709d537d11e3b9c700306ef3def1#0#Timeout Service Synchronous Queue Processor#Plain##
Error while retrieving aggregated data for GC problem reporting monitors
[EXCEPTION]
com.sap.mona.api.NodeNotExistingException: com.sap.mona.api.JMonAPIException: can not find [\\Kernel\\SAPJVM\\GCProblemReporting\\Java Heap Memory Shortages] under TID <SUMM>:I09 :SAPLicense:5:1:499:-1
at com.sap.mona.api.JMonException.create(JMonException.java:109)
at com.sap.mona.api.NodeFactory.getMonitoringNode(NodeFactory.java:145)
at com.sap.engine.monitor.impl.VMAggregatedStatesMonitors.evaluateGCMonitor(VMAggregatedStatesMonitors.java:146)
at com.sap.engine.monitor.impl.VMAggregatedStatesMonitors.getGCProblems(VMAggregatedStatesMonitors.java:70)
at sun.reflect.GeneratedMethodAccessor448.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)
at com.sun.jmx.mbeanserver.PerInterface.getAttribute(PerInterface.java:65)
at com.sun.jmx.mbeanserver.MBeanSupport.getAttribute(MBeanSupport.java:216)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:666)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:638)
at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:662)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:423)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:231)
at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:161)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:235)
at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:559)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:161)
at com.sap.engine.services.monitor.mbeans.Monitor.getMBeanResult(Monitor.java:268)
at com.sap.engine.services.monitor.mbeans.IntegerMonitor.collectMonitoringData(IntegerMonitor.java:167)
at com.sap.engine.services.monitor.mbeans.IntegerMonitor.collectAndStoreMonitoringData(IntegerMonitor.java:71)
at com.sap.engine.services.monitor.mbeans.Monitor.handleNotification(Monitor.java:134)
at com.sap.engine.services.monitor.common.StandardMBeanWrapper.handleNotification(StandardMBeanWrapper.java:77)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerInterceptor.java:1732)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:257)
at javax.management.NotificationBroadcasterSupport$SendNotifJob.run(NotificationBroadcasterSupport.java:322)
at javax.management.NotificationBroadcasterSupport$1.execute(NotificationBroadcasterSupport.java:307)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:229)
at com.sap.engine.services.jmx.timer.j2ee.Timer.sendTimerNotification(Timer.java:431)
at com.sap.engine.services.jmx.timer.j2ee.TimerNotificationEntry.timeout(TimerNotificationEntry.java:69)
at com.sap.engine.services.timeout.TimeoutNode.synchronousRun(TimeoutNode.java:123)
at com.sap.engine.services.timeout.TimeoutManagerImpl.singleThreadRun(TimeoutManagerImpl.java:707)
at com.sap.engine.services.timeout.TimeoutManagerRunner.run(TimeoutManagerRunner.java:18)
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)
500 Internal Server Error | ||
SAP NetWeaver Application Server 7.20 / AS Java 7.30 | ||
Error: Application error occurred during the request processing.
Troubleshooting Guide https://sdn.sap.com/irj/sdn/wiki?path=/display/JSTSG/Home
Details: |
|
Hi Reddy,
Open the Config tool , and increase the Heap Memory.
Also you need to check the four other parameter in java parameter of the instance
Can you please paste the content or screenshot of window.
You have not define the java parameter properly so GC is not able to get the appropriate memory for it execution.
Also check the license as suggested.
With Regards
Ashutosh Chaturvedi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Reddy ,
pls check below links may get more information regarding the java stack
http://sapbasisanswers.blogspot.com/2013/02/nw-73-apply-sap-java-license-steps.html
Regards
Nayeem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
These are generic messages. Exaction info can be found in the std_server.out in /usr/sap/SID/J*/work.
Please post that log.
was the system up for 30 min and then the issue happened. then its license issue.(Server node still running then this cant be the cause of it.)
Have you changed the ume. If yes the ume user has the correct permission.(Server node still running then this cant be the cause of it.)
Please provide more info that what changes were done before you found this issue.
Thanks
Rishi Abrol
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please check your heap memory parameters alongwith below link to check the proceess for identifying the GC problem:
http://help.sap.com/saphelp_nw73/helpdata/en/c2/8f3f1e35624dd2852ed932895ddb98/content.htm
Thanks,
Manish Singh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Reddy,
Can you check if there are any heap dumps created ?
Mudasir.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
Please provide the dev_server0 and st_server0 log flles.
Also have you installed the license after the installation ?
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.