Skip to Content
avatar image
Former Member

Messages stuck in Java Queues

I am running PI7.0 SP10 on a MCOD system running ECC6.0 and EP.

We had an issue last week on our Production system where the Java Stack went down, and when the system came back up, we cleared the issues in SMQ1, SMQ2 and SM58 and now we have over two hundred messages stuck in the java queues.

There is nothing locked in SM13, in sxmb_moni all the messgaes are successfully processed... In the RWB the status of the messages are "To be delivered".

I have tried reactivating the adapters but this has not worked.

The queues can be seen in the http://host.fqdn:5<SYSNO>00/MessagingSystem/monitor/systemStatus.jsp

specifically : File_http://sap.com/xi/XI/SystemRecv

and

SOAP_http://sap.com/xi/XI/SystemRecv

where the "isStarted" is set to false, where all the others are true...

How can I go about starting these and processing the backlog of messages??

I have searched OSS, SDN and SAPFans but had not luck!

I have subsequently done a full cache refresh and CPACache refresh but this has not helped.

There are no locked users (XI/PI users) holding this up!

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • avatar image
    Former Member
    Jan 23, 2008 at 09:58 AM

    Thanks for all your input.

    That OSS Note is not relevant for PI7.0 - SP10.

    Drilling into the messaging System I get this error...

    There was an error processing your request.

    com.sap.aii.af.ra.ms.impl.app.AdminException: Failed to read the message details remotely from cluster node 0. Reason: Could not execute cluster event, due to: Participant 0 is not available.

    With the following stack trace:

    com.sap.aii.af.ra.ms.impl.app.AdminException: Could not execute cluster event, due to: Participant 0 is not available.

    at com.sap.aii.af.ra.ms.runtime.j2ee.sapengine.SAPJ2EEClusterController.sendClusterEvent(SAPJ2EEClusterController.java:1107)

    at com.sap.aii.af.ra.ms.runtime.j2ee.sapengine.SAPJ2EEClusterController.getMessageBean(SAPJ2EEClusterController.java:686)

    at com.sap.aii.af.ra.ms.app.MonitorBeanImpl.getMessageBean(MonitorBeanImpl.java:236)

    at com.sap.aii.af.ra.ms.app.MonitorRIObjectImpl0_0.getMessageBean(MonitorRIObjectImpl0_0.java:326)

    at com.sap.aii.af.ra.ms.app.MonitorRI_Stub.getMessageBean(MonitorRI_Stub.java:805)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

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

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

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

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

    at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)

    at $Proxy127.getMessageBean(Unknown Source)

    at jsp_monitor21194013825531._jspService(jsp_monitor21194013825531.java:132)

    at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)

    at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)

    at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)

    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)

    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)

    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

    at java.security.AccessController.doPrivileged(AccessController.java:207)

    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 25, 2008 at 09:59 AM

    The MaxThreadCount parameter was raised from 150 to 300, and we bounced the J2EE Engine.

    To increase the parameter, please follow the instructions below:

    1. In the left frame choose Server -> Services -> Configuration Adapter

    2. In the tab Display Configuration (right frame) choose Switch between

    view and edit mode to activate the edit mode.

    3. Choose cluster_data -> server -> cfg -> kernel -> Propertysheet

    ApplicationThreadManager

    4. Choose Show the detail of the selected node

    5. The parameter MaxThreadCount should be set to 300/350.

    6. You will then need to restart the J2ee

    This has cleared the items and life is back to normal!

    Thanks for your valuable input Roberti.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Java + SAP = strange things going on!

      All done and cleared! My job here is finished!

      Again, thanks for your input!

      I've given you a few points 😊

  • avatar image
    Former Member
    Jan 22, 2008 at 02:14 PM

    has anyone come across this before?

    I found an almost relevant OSS Note but that related to XI3.0 and not our version!

    Does anyone have any suggestions?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Barry,

      Did you see if the queues are locked or not?

      And yes normally resending of the message in Moni will help

      and can you please post the SAP note that you found for XI 3.0?

      actually I also faced this problem in our system, but after some efforts from basis team(some memorey resizing) it was solved.

      I suggest to take some back up of all those messages as I can see it is the Prod system, and in any case you dont want to loose ur data.

      Ranjit

  • avatar image
    Former Member
    Jan 22, 2008 at 11:56 PM

    Hi Barry,

    Have you tried resending(Select message in Adapter engine in RWB and click on resend button) messages from RWB?

    if you haven't done this, try now and lets know the result.

    Cheers,

    Jag

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 23, 2008 at 07:04 AM

    Hi Barry,

    it may be possible that MS Queue was using the java keyword volatile , which is incorrectly implemented for many JVM's. i don't know if you gone through with this SAP NOte 893981 or not but please check it. Also you can look into SAP Note 816022. 😊

    regards

    Aashish Sinha

    Add comment
    10|10000 characters needed characters exceeded