RE: XML File is not loading

      Dear All,

      In our BI system when we try to test a service under SICF the page we are requesting cannot load on the web browser. We have activated all related services and still the service test fail with error “Internet Explorer cannot display the webpage”. Please advice me on this and it will be great if you can provide a log from where we can find a relevant error for this issue.

      Thanks all.

      Edited by: shanakac on Jan 26, 2012 8:33 AM

      I found below exception in log file “/usr/sap/BPJ/JC00/j2ee/cluster/dispatcher/log”

      #1.#001125E7D7FA001200000001000761540004B6CBA3796331#1326885644100#com.sap.engine.services.httpserver.dispatcher##com.sap.engine.services.httpserver.dispatcher#######OrderedChannel for http service##0#0#Error##Plain###Connection [4352] is NOT removed! To see all opened connections on the server nodes change logging severity to DEBUG.#

      #1.#001125E7D7FA001900000002000840D20004B6E16736F0E1#1326979122344#com.sap.engine.services.jmx.MBeanServerInvoker##com.sap.engine.services.jmx.MBeanServerInvoker#######SAPEngine_System_Thread[impl:6]_29##0#0#Warning#1#/System/Server#Java###JMX connector exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 314 | src: cluster target-node: 3223200 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=3223200,SAP_J2EECluster=”” null null null ]

      [EXCEPTION]

      #1#com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to de-serialize request parameters, message [ JMX request (java) v1.0 len: 314 | src: cluster target-node: 3223200 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=3223200,SAP_J2EECluster=”” null null null ] at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:537) at com.sap.engine.services.jmx.RequestMessage.getParams(RequestMessage.java:586) at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:90) at com.sap.engine.services.jmx.JmxServiceConnectorServer.receiveWait(JmxServiceConnectorServer.java:172) at com.sap.engine.core.service630.context.cluster.message.MessageListenerWrapper.process(MessageListenerWrapper.java:81) at com.sap.engine.core.cluster.impl6.ms.MSListenerThread.run(MSListenerThread.java:47) at com.sap.engine.frame.core.thread.Task.run(Task.java:64) at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:82) at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:154) Caused by: javax.management.InstanceNotFoundException: MBean with name com.sap.default:name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=3223200,SAP_J2EECluster=BPJ not found in repository at com.sap.pj.jmx.server.MBeanServerImpl.getClassLoaderFor(MBeanServerImpl.java:1408) at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getClassLoaderFor(MBeanServerWrapperInterceptor.java:455) at com.sap.engine.services.jmx.CompletionInterceptor.getClassLoaderFor(CompletionInterceptor.java:576) at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getClassLoaderFor(BasicMBeanServerInterceptor.java:438) at com.sap.jmx.provider.ProviderInterceptor.getClassLoaderFor(ProviderInterceptor.java:330) at com.sap.engine.services.jmx.RedirectInterceptor.getClassLoaderFor(RedirectInterceptor.java:501) at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getClassLoaderFor(MBeanServerInterceptorChain.java:443) at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:531) … 8 more # #1.#001125E7D7FA001100000001000840D20004B6E1FF0498AA#1326981669230#com.sap.engine.services.httpserver.dispatcher##com.sap.engine.services.httpserver.dispatcher#######SAPEngine_System_Thread[impl:6]_26##0#0#Error##Plain###Setting socket properties failed. java.net.SocketException: The specified option is invalid at the specified socket level or the socket has been shut down at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:292) at java.net.Socket.setTcpNoDelay(Socket.java:805) at com.sap.engine.services.httpserver.dispatcher.Processor.initialize(Processor.java:189) at com.sap.engine.core.manipulator.TCPRunnableConnection.init(TCPRunnableConnection.java:375) at com.sap.engine.core.manipulator.TCPRunnableConnection.run(TCPRunnableConnection.java:564) at com.sap.engine.frame.core.thread.Task.run(Task.java:64) at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:82) at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:154) # #1.#001125E7D7FA000200000002000831120004B6E22EB131A1#1326982469046#com.sap.engine.services.jmx.MBeanServerInvoker##com.sap.engine.services.jmx.MBeanServerInvoker#######SAPEngine_System_Thread[impl:6]_15##0#0#Warning#1#/System/Server#Java###JMX connector exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 314 | src: cluster target-node: 3223200 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=3223200,SAP_J2EECluster=”” null null null ] [EXCEPTION] #1#com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to de-serialize request parameters, message [ JMX request (java) v1.0 len: 314 | src: cluster target-node: 3223200 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=3223200,SAP_J2EECluster=”” null null null ]

      at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:537)

      at com.sap.engine.services.jmx.RequestMessage.getParams(RequestMessage.java:586)

      at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:90)

      at com.sap.engine.services.jmx.JmxServiceConnectorServer.receiveWait(JmxServiceConnectorServer.java:172)

      at com.sap.engine.core.service630.context.cluster.message.MessageListenerWrapper.process(MessageListenerWrapper.java:81)

      at com.sap.engine.core.cluster.impl6.ms.MSListenerThread.run(MSListenerThread.java:47)

      at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

      at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:82)

      at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:154)

      Caused by: javax.management.InstanceNotFoundException: MBean with name com.sap.default:name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=3223200,SAP_J2EECluster=BPJ not found in repository

      at com.sap.pj.jmx.server.MBeanServerImpl.getClassLoaderFor(MBeanServerImpl.java:1408)

      at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getClassLoaderFor(MBeanServerWrapperInterceptor.java:455)

      at com.sap.engine.services.jmx.CompletionInterceptor.getClassLoaderFor(CompletionInterceptor.java:576)

      at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getClassLoaderFor(BasicMBeanServerInterceptor.java:438)

      at com.sap.jmx.provider.ProviderInterceptor.getClassLoaderFor(ProviderInterceptor.java:330)

      at com.sap.engine.services.jmx.RedirectInterceptor.getClassLoaderFor(RedirectInterceptor.java:501)

      at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getClassLoaderFor(MBeanServerInterceptorChain.java:443)

      at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:531)

      … 8 more

      #

      #1.#001125E7D7FA001600000001000831120004B6EE19CB4700#1327033658066#com.sap.engine.services.httpserver.dispatcher##com.sap.engine.services.httpserver.dispatcher#######OrderedChannel for http service##0#0#Error##Plain###Connection [4352] is NOT removed! To see all opened connections on the server nodes change logging severity to DEBUG.#

      #1.#001125E7D7FA001600000002000831120004B6EE19D31C48#1327033658580#com.sap.engine.services.httpserver.dispatcher##com.sap.engine.services.httpserver.dispatcher#######OrderedChannel for http service##0#0#Error##Plain###Connection [4864] is NOT removed! To see all opened connections on the server nodes change logging severity to DEBUG.#

      #1.#001125E7D7FA001B00000000000831120004B6EF15C451FE#1327037885469#com.sap.engine.services.httpserver.dispatcher##com.sap.engine.services.httpserver.dispatcher#######OrderedChannel for http service##0#0#Error##Plain###Connection [27136] is NOT removed! To see all opened connections on the server nodes change logging severity to DEBUG.#

      #1.#001125E7D7FA0003000000020006F1200004B76934781E80#1327562386550#com.sap.engine.services.jmx.MBeanServerInvoker##com.sap.engine.services.jmx.MBeanServerInvoker#######SAPEngine_System_Thread[impl:6]_10##0#0#Warning#1#/System/Server#Java###JMX connector exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 314 | src: cluster target-node: 3223200 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=3223200,SAP_J2EECluster=”” null null null ]

      [EXCEPTION]

      #1#com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to de-serialize request parameters, message [ JMX request (java) v1.0 len: 314 | src: cluster target-node: 3223200 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=3223200,SAP_J2EECluster=”” null null null ]

      at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:537)

      at com.sap.engine.services.jmx.RequestMessage.getParams(RequestMessage.java:586)

      at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:90)

      at com.sap.engine.services.jmx.JmxServiceConnectorServer.receiveWait(JmxServiceConnectorServer.java:172)

      at com.sap.engine.core.service630.context.cluster.message.MessageListenerWrapper.process(MessageListenerWrapper.java:81)

      at com.sap.engine.core.cluster.impl6.ms.MSListenerThread.run(MSListenerThread.java:47)

      at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

      at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:82)

      at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:154)

      Caused by: javax.management.InstanceNotFoundException: MBean with name com.sap.default:name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=3223200,SAP_J2EECluster=BPJ not found in repository

      at com.sap.pj.jmx.server.MBeanServerImpl.getClassLoaderFor(MBeanServerImpl.java:1408)

      at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getClassLoaderFor(MBeanServerWrapperInterceptor.java:455)

      at com.sap.engine.services.jmx.CompletionInterceptor.getClassLoaderFor(CompletionInterceptor.java:576)

      at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getClassLoaderFor(BasicMBeanServerInterceptor.java:438)

      at com.sap.jmx.provider.ProviderInterceptor.getClassLoaderFor(ProviderInterceptor.java:330)

      at com.sap.engine.services.jmx.RedirectInterceptor.getClassLoaderFor(RedirectInterceptor.java:501)

      at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getClassLoaderFor(MBeanServerInterceptorChain.java:443)

      at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:531)

      … 8 more

      #

      Edited by: shanakac on Jan 26, 2012 8:33 AM

      This issue is resolved as our network team has mapped the wrong IP to the hostname we are using to access this SAP service.   Thanks.

      User Rating: Be the first one !
      larsks Vice Professor Asked on November 2, 2016 in bi solution-architecture.
      Add Comment
      1 Answers

        This issue is resolved as our network team has mapped the wrong IP to the hostname we are using to access this SAP service.

         

        Thanks.

        Add Comment

        Your Answer

        By posting your answer, you agree to the privacy policy and terms of service.