Netweaver Portal Log Configuration & Viewing (Part 2)
Welcome to part two of my weblog about Netweaver Portal Log Configuration & Viewing.
If you missed part one – Log Configuration – Netweaver Portal Log Configuration & Viewing (Part 1).
Welcome to part two of my weblog about Netweaver Portal Log Configuration & Viewing.
If you missed part one – Log Configuration – Netweaver Portal Log Configuration & Viewing (Part 1).
com.sapmarkets.bam.util.BAMRuntimeException
at com.sapmarkets.bam.jmx.connector.rmi.AbstractConnectorClient.invoke(AbstractConnectorClient.java:113)
at $Proxy3.invoke(Unknown Source)
at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.invokeMBeanMethod(AbstractLogDepot.java:163)
at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.invokeFacadeMethod(AbstractLogDepot.java:206)
at com.sapmarkets.bam.application.LogQuery.getLogRecords(LogQuery.java:43)
at com.sapmarkets.bam.application.LogQuery.getLatest(LogQuery.java:61)
at com.sapmarkets.bam.application.SingleServerBrowser.getLatest(SingleServerBrowser.java:56)
at com.sapmarkets.bam.application.logbuffer.LogRecordTransporter.getLatest(LogRecordTransporter.java:52)
at com.sapmarkets.bam.application.logbuffer.LogRecordTransporterLatestToOldest.getTopResults(LogRecordTransporterLatestToOldest.java:19)
at com.sapmarkets.bam.application.logbuffer.LogRecordTransporter.getTop(LogRecordTransporter.java:145)
at com.sapmarkets.bam.application.logbuffer.LogBufferModel$1.getInitialResults(LogBufferModel.java:233)
at com.sapmarkets.bam.application.logbuffer.event.LBMCommand.execute(LBMCommand.java:89)
at com.sapmarkets.bam.application.logbuffer.event.LBMCommandConsumer.run(LBMCommandConsumer.java:49)
at java.lang.Thread.run(Thread.java:534)
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:107)
... 13 more
Caused by: com.sapmarkets.bam.util.BAMRuntimeException
at com.sapmarkets.bam.jmx.connector.rmi.AbstractConnectorClient$1.call(AbstractConnectorClient.java:93)
at com.sapmarkets.bam.util.FutureResult$1.run(FutureResult.java:47)
at com.sapmarkets.bam.util.ConnectorClientPooledExecutor$WorkerThread.run(ConnectorClientPooledExecutor.java:83)
Caused by: java.lang.reflect.InvocationTargetException
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:324)
at com.sapmarkets.bam.jmx.connector.AbstractLVServer.invoke(AbstractLVServer.java:149)
at sun.reflect.GeneratedMethodAccessor3878.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:161)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
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:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.engine.services.jmx.exception.MBeanServerClusterException: Exception during invocation of remote MBeanServer method, target node: 1979751
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:816)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
... 18 more
Caused by: com.sap.engine.services.jmx.exception.JmxConnectorException: Sending message synchronously failed, target node 1979751, message [ JMX request (java) v1.0 len: 498 | src: cluster target-node: 1979751 req: invoke params-number: 4 params-bytes: 0 | :name=LogControllerFacade,j2eeType=LogControllerFacadeMBean,SAP_J2EEClusterNode=1979751,SAP_J2EECluster="" getLatest [Ljava.lang.Object;@52f64d [Ljava.lang.String;@15f7364 ]
at com.sap.engine.services.jmx.MBeanServerConnectionImpl.invokeMbsInternal(MBeanServerConnectionImpl.java:677)
at com.sap.engine.services.jmx.MBeanServerConnectionImpl.invoke(MBeanServerConnectionImpl.java:464)
at com.sap.engine.services.jmx.MBeanServerConnectionSecurityWrapper.invoke(MBeanServerConnectionSecurityWrapper.java:217)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:813)
... 19 more
Caused by: com.sap.engine.frame.cluster.message.ResponseTimedOutException: Participant 1,979,751 did not return a response in the specified timeout of 100,000 ms.
at com.sap.engine.core.cluster.impl6.lazy.AnswerObject.getResult(AnswerObject.java:88)
at com.sap.engine.core.cluster.impl6.lazy.LazyConnection.sendRequest(LazyConnection.java:223)
at com.sap.engine.core.cluster.impl6.lazy.LazyConnectorImpl.sendRequest(LazyConnectorImpl.java:171)
at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendRequest(ClusterManagerImpl.java:2260)
at com.sap.engine.core.service630.context.cluster.message.MessageContextImpl.sendAndWaitForAnswer(MessageContextImpl.java:93)
at com.sap.engine.services.jmx.JmxFrame.sendAndWaitForAnswer(JmxFrame.java:735)
at com.sap.engine.services.jmx.JmxServiceConnectorServerInvoker.invokeMbs(JmxServiceConnectorServerInvoker.java:47)
at com.sap.engine.services.jmx.MBeanServerConnectionImpl.invokeMbsInternal(MBeanServerConnectionImpl.java:671)
... 22 more
I don't think this is the right place to present stack traces 😉
Sorry, I haven't seen this error before, looks you have kind of connection problems. All configuration tasks should be described in the blog.
Does your integrated logviewer work? (the one in the visual admintool)
If yes, please double check the configuration of your standalone log viewer with the corresponding chapter in the Logviewer_Userguide.pdf, which can be found in the logviewer directory.
Regards, Karsten
>Developers usually dont have admin password!!!
Yes. Check the PDF doc for instructions on setting up a service, and connect to it using "standalone" rather than "J2EE" mode.