cancel
Showing results for 
Search instead for 
Did you mean: 

7.3 PI Installation

Former Member
0 Kudos

Hi guru's

I have installed a PI 7.3 system in our landscape I am able to log in to the ABAP system but I am unable to view the Java System information page I am able to view the java home page but if i click on System Information and give the username password I am getting a dump. I am attaching a part of the default log trace with this message

#2.0 #2011 11 17 01:02:54:979#0-600#Error#com.sap.engine.monitor.impl.VMAggregatedStatesMonitors#

#BC-JAS-ADM-MON#sap.com/com.sap.engine.heartbeat#C0000A0C0C730040000041BA00001D5C#8028250000000001##com.sap.engine.monitor.impl.VMAggregatedStatesMonitors####6A0EBCF80C4F11E1C55400155D0C1715#6a0ebcf80c4f11e1c55400155d0c1715#6a0ebcf80c4f11e1c55400155d0c1715#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>:P73 :SAPLicense:5:1:379:-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.GeneratedMethodAccessor434.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)"

and below is the error Im getting while Im in System Information page

500 Internal error page is getting displayed

Kindly let me know the solution for it

Regards,

Abhishek

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

have you completed Post installation config - CTC wizard ??

Former Member
0 Kudos

Hello,

I have the same Problem with 7.3PI. Starting the CTC Wizard is not possible, because I get the same error when I start NWA:

Error: Application error occurred during the request processing.

Troubleshooting Guide https://sdn.sap.com/irj/sdn/wiki?path=/display/JSTSG/Home

Details:

WebApplicationException log ID is [C000C0A8B22B00520000000100001384].

Trace:

#2.0 #2012 05 21 09:19:09:135#+0200#Error#com.sap.engine.monitor.impl.VMAggregatedStatesMonitors#

#BC-JAS-ADM-MON#sap.com/com.sap.engine.heartbeat#C000C0A8B22B00390000001300001384#3788350000000001##com.sap.engine.monitor.impl.VMAggregatedStatesMonitors####34E5B0D9A31211E1CFBC000C29D697A2#34e5b0d9a31211e1cfbc000c29d697a2#34e5b0d9a31211e1cfbc000c29d697a2#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>:HP3     :SAPLicense:5:1:550:-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.NativeMethodAccessorImpl.invoke0(Native Method)

          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

          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)

Former Member
0 Kudos

Hi,

  Can you share how you were able to solve this issue. I am having same issue with PI 7.3 installaiton where the installer errors during the JAVA component diployement phase.

Thanks,

phanikumar_akella
Participant
0 Kudos

Hi All

I am facing exactly the same issue. Were you able to resolve this issue?