cancel
Showing results for 
Search instead for 
Did you mean: 

Error when trying to use the Log Viewer

Former Member
0 Kudos

Hello experts, today I wanted to examine some logs using the Log Viewer on Visual Administrator. However, when clicking on this service, the Visual Administrator would freeze for a long while and after that, an error message was displayed. I do not remember the exact message, but it was something like "A fatal error occurred. For more information, click on the Details button". After clicking on that button, the following error was displayed:

com.sapmarkets.bam.util.BAMRuntimeException

at com.sapmarkets.bam.jmx.connector.rmi.AbstractConnectorClient.invoke(AbstractConnectorClient.java:110)

at $Proxy31.getAttribute(Unknown Source)

at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.getAttribute(AbstractLogDepot.java:236)

at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.getLogDescriptors(AbstractLogDepot.java:84)

at com.sapmarkets.bam.view.config.RemoteViewConfiguration.initializeViewConfiguration(RemoteViewConfiguration.java:65)

at com.sapmarkets.bam.view.overview.OverviewFacade.populateOverview(OverviewFacade.java:219)

at com.sapmarkets.bam.view.AbstractLogViewerAppplication.populateOverview(AbstractLogViewerAppplication.java:171)

at com.sapmarkets.bam.view.AbstractLogViewerAppplication.initOverview(AbstractLogViewerAppplication.java:652)

at com.sapmarkets.bam.j2ee.services.logviewer.gui.LogViewerRuntimeLogical.setRuntime(LogViewerRuntimeLogical.java:121)

at com.sapmarkets.bam.j2ee.services.logviewer.gui.LogViewerRuntimeLogical.show(LogViewerRuntimeLogical.java:88)

at com.sap.engine.services.adminadapter.gui.node.ServiceNodeView.selectSingleService(ServiceNodeView.java:202)

at com.sap.engine.services.adminadapter.gui.node.ServiceNodeView.selectNode(ServiceNodeView.java:156)

at com.sap.engine.services.adminadapter.gui.AdminManager.selectServiceNode(AdminManager.java:290)

at com.sap.engine.services.adminadapter.gui.AdminManager.selectNode(AdminManager.java:170)

at com.sap.engine.services.adminadapter.gui.AdminManager.valueChanged(AdminManager.java:108)

at javax.swing.JTree.fireValueChanged(JTree.java:2392)

at javax.swing.JTree$TreeSelectionRedirector.valueChanged(JTree.java:2763)

at javax.swing.tree.DefaultTreeSelectionModel.fireValueChanged(DefaultTreeSelectionModel.java:629)

at javax.swing.tree.DefaultTreeSelectionModel.notifyPathChange(DefaultTreeSelectionModel.java:1076)

at javax.swing.tree.DefaultTreeSelectionModel.setSelectionPaths(DefaultTreeSelectionModel.java:287)

at javax.swing.JTree.setSelectionInterval(JTree.java:2041)

at javax.swing.plaf.basic.BasicTreeUI$TreeIncrementAction.actionPerformed(BasicTreeUI.java:3268)

at javax.swing.SwingUtilities.notifyAction(SwingUtilities.java:1530)

at javax.swing.JComponent.processKeyBinding(JComponent.java:2438)

at javax.swing.JComponent.processKeyBindings(JComponent.java:2473)

at javax.swing.JComponent.processKeyEvent(JComponent.java:2401)

at java.awt.Component.processEvent(Component.java:4978)

at java.awt.Container.processEvent(Container.java:1569)

at java.awt.Component.dispatchEventImpl(Component.java:3684)

at java.awt.Container.dispatchEventImpl(Container.java:1627)

at java.awt.Component.dispatchEvent(Component.java:3546)

at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1713)

at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:627)

at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:831)

at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:741)

at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:592)

at java.awt.Component.dispatchEventImpl(Component.java:3575)

at java.awt.Container.dispatchEventImpl(Container.java:1627)

at java.awt.Window.dispatchEventImpl(Window.java:1606)

at java.awt.Component.dispatchEvent(Component.java:3546)

at java.awt.EventQueue.dispatchEvent(EventQueue.java:480)

at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)

at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)

at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)

at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

Caused by: java.lang.reflect.InvocationTargetException

at com.sapmarkets.bam.util.FutureResult.get(FutureResult.java:71)

at com.sapmarkets.bam.jmx.connector.rmi.AbstractConnectorClient.invoke(AbstractConnectorClient.java:104)

... 45 more

Caused by: java.lang.OutOfMemoryError: Java heap space

at javax.management.ObjectName.construct(ObjectName.java:385)

at javax.management.ObjectName.readObject(ObjectName.java:1063)

at sun.reflect.GeneratedMethodAccessor60.invoke(Unknown Source)

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

at java.lang.reflect.Method.invoke(Method.java:324)

at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:838)

at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1736)

at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)

at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)

at java.io.ObjectInputStream.readObject(ObjectInputStream.java:322)

at java.util.ArrayList.readObject(ArrayList.java:559)

at sun.reflect.GeneratedMethodAccessor63.invoke(Unknown Source)

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

at java.lang.reflect.Method.invoke(Method.java:324)

at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:838)

at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1736)

at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)

at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)

at java.io.ObjectInputStream.readObject(ObjectInputStream.java:322)

at java.util.HashMap.readObject(HashMap.java:1015)

at sun.reflect.GeneratedMethodAccessor64.invoke(Unknown Source)

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

at java.lang.reflect.Method.invoke(Method.java:324)

at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:838)

at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1736)

at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)

at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)

at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1835)

at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1759)

at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)

at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)

at java.io.ObjectInputStream.readObject(ObjectInputStream.java:322)

The lines I marked in bold are the ones that caught my attention. What is this error and how can I fix it?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Increase you JVM Heap Size to :

for 32 bit H/W -> 1024M

for 64 bit H/W -> 2048M

-Xms and -Xmx should be of the same value.

Former Member
0 Kudos

Hello, thanks for your answers. I checked the JVM Heap size, we are using a 64 bit HW, and it was already set to 2048M, as well as both parameters Xms and Xmx. I also checked our virtual memory and directory space, the virtual memory looks fine, and the <SID> directory uses 5 GB of space.

If you wish, I can write the configuration found on the Config Tool, where you set the JVM Heap size and other parameters.

Former Member
0 Kudos

Pls check your ..../logviewer-standalone/server/log/console_logs directory in the logviewer, that could be running out of diskspace.

Cleanup the oldest logs if not required, or move them to a different location

Former Member
0 Kudos

Hhhhmm....there's a problem there. That directory does not exist. All I have is ..../logviewer-standalone/server/ and inside that directory there is "cfg" directory which contains only one file. Anyways, I checked the disk space beginning from .../logviewer-standalone and taking in account all subdirectories, and they take up only about 24M of space.

Former Member
0 Kudos

The problem seemed to be caused by a memory leak. Once we installed SP Stack 15, the Log Viewer started working correctly. It does take a little bit to load, but at least it is working.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hai,

Check the /usr/sap/<SID> directory space, Also check the Pagefile and Virtual memory at the OS level.

Incrae the Heap memory in the configtool and restart the system and try to open the Logviewer.

Thanks and Regards,