Messages stuck in Java Queues

[Former Member]

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!

[Former Member]

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.

[Former Member]

Ok,

really, really strange... I had already found that some problems at sap world are solved with actions that at the first moment does not seems to make sense

cheers!

roberti

[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

[Former Member]

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)

[Former Member]

I am not sure of the relevance, but in SM21 every minute we get the following:

Details Page 2 Line 9 System Log: Local Analysis of gbrdoxlx110 1

Time Type Nr Clt User TCode Grp N Text

09:01:12 BTC 012 000 SAPSYS D0 1 Transaction Canceled BT 510 ( )

Transaction Canceled BT 510 ( )

Details

Recording at local and central time........................ 23.01.2008 09:01:12

Task...... Process User...... Terminal Session TCode Program Cl Problem cl Package

20245 Background Processor No. 012 SAPSYS 1 RSBTCRTE K SAP Web AS Problem SDYN

Module nam Loc T100................ Parameters

BT 510

Documentation for system log message D0 1 :

The transaction has been terminated. This may be caused by a

termination message from the application (MESSAGE Axxx) or by an

error detected by the SAP System due to which it makes no sense to

proceed with the transaction. The actual reason for the termination

is indicated by the T100 message and the parameters.

Technical details

File Offset RecFm System log type Grp N variable message data

72 210780 n Transaction Termination D0 1 BT 510

[Former Member]

We have opened an OSS note with SAP on this!

Clearly there must be a way of clearing messages in the status "to be delivered".

I will update the note as I hear back!

[Former Member]

I am still baffled... No news from SAP!

Here is the Audit Log regarding the Messages from the MessagingSystem/Monitor...

Time Stamp Status Description

2008-01-24 00:48:07 Success Message successfully received by messaging system. Profile: XI URL: http://vxipci:55000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER

2008-01-24 00:48:07 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.

2008-01-24 00:48:07 Success Message successfully put into the queue.

[Former Member]

Hi Barry,

So, it seems to be working, as the message now is on the queue.

We have another issue with SOAP_http://sap.com/xi/XI/SystemRecv. We have 10 threads for this queue, but still it seems to be a bottleneck, and messages are stopping on the queue about 20 per minute. In 10 minutes, 200 messages enqueued and growing...

What is really strange is that we have two nodes in a cluster. This issue only happens in the second node... in the first node messages does not stay on that queue, and the parameters about maxthreads are same on both nodes. Here are the status found on MessageMonitor

Queue Name isStarted QueueSize ThreadCount (working) MaxThreads

• Node 1

SOAP_http://sap.com/xi/XI/SystemCall true 0 10 (10) 20

SOAP_http://sap.com/xi/XI/SystemRecv true 0 0 (0) 10

SOAP_http://sap.com/xi/XI/SystemRqst true 0 0 (0) 20

SOAP_http://sap.com/xi/XI/SystemSend true 0 0 (0) 10

• Node 2

SOAP_http://sap.com/xi/XI/SystemCall true 0 0 (0) 20

SOAP_http://sap.com/xi/XI/SystemRecv true 138 10 (10) 10

SOAP_http://sap.com/xi/XI/SystemRqst true 0 0 (0) 20

SOAP_http://sap.com/xi/XI/SystemSend true 0 0 (0) 10

SystemRecv QueueSize on node 2 is on 138 because every 10 minutes we are performing a CPACache Refresh (then, queue size come back to 0). I don't know why it happens, nor if it is a correct action. And don't know why only this queue has this problem...

regards.

roberti

[Former Member]

Thanks for your input Roberti.

The issue seems similar, but when we run the CPACacheRefresh, nothing happens...

Our queues look like this...

File_http://sap.com/xi/XI/SystemCall true 0 0 (0) 5

File_http://sap.com/xi/XI/SystemRecv false 124 0 (0) 5

File_http://sap.com/xi/XI/SystemRqst false 0 0 (0) 5

File_http://sap.com/xi/XI/SystemSend true 0 0 (0) 5

SOAP_http://sap.com/xi/XI/SystemCall true 0 0 (0) 5

SOAP_http://sap.com/xi/XI/SystemRecv false 143 0 (0) 5

SOAP_http://sap.com/xi/XI/SystemRqst false 0 0 (0) 5

SOAP_http://sap.com/xi/XI/SystemSend true 0 0 (0) 5

As you can see - they are in set as "False" in the isStarted Column...

We need to work out how to activate/switch this on... It was working perfectly for two months before the Java Engine collapsed!

[Former Member]

Ok,

I think you don't have a high workload on this server, otherwise you should have this queue growing fast...

The destination of those messages is an Abap Proxy or any RFC? As just a hint, check if the rfc connection for the destination is ok. Also check the rfc INTEGRATION_DIRECTORY_HMI.

If this is not the case, please, let us now what are the destinations of those file and soap interfaces.

regards.

roberti

[Former Member]

Hi Roberti

We are the Phase one of the XI go live.. ironing out the problems...

The workload on the server will grow considerably over the coming months... Only if we can resolve this issue

The response I get back from the INTEGRATION_DIRECTORY_HMI is:

HTTP/1.1 200 OK

Set-Cookie: saplb_*=(vxipci_XIP_50)508033150; path=/

Set-Cookie: JSESSIONID=(vxipci_XIP_50)ID1951913750DB01753214971266888557End; path=/; domain=.eu.xerox.net

Content-Type: text/html

Content-Length: 192

connection: close

server: SAP J2EE Engine/7.00

date: Thu, 24 Jan 2008 11:47:56 GMT

<html>

<head><title>HMI Servlet - worker external client</title></head>

<body><p>

Worker "external client" of servlet "com.sap.aii.ib.web.hmi.HmiServlet #1" is reachable!<p>

<p></body></html>

The weird thing is Idocs are running fine. The ABAP Proxies post to XI, run through the BPMs successfully, but when it comes to the SOAP/File Adapter, the files are not posted to the destination. Both the SOAP url and the FTP file site are both up and running.

I tried reactivating the adapters in the Integration Directory and stopping and starting the same in the RWB... but to no avail!

SAP have suggested increasing the MaxThreadCount parameter in the Visual Administrator, which we have done, but are awaiting to bounce the J2EE stack...

I don't expect this to make much of a difference though!

[Former Member]

Ok,

It seems to be ok, the return can be http 200 or http 500.

The Soap and File are destinations, ok.

The messages are with status "delivering" on rwb... really, increasing the number of threads will not solve this...

I don't have access to visual admin (only basis team can access it here). I thought it could be something wrong with destination (but you already checked it)... so, the only thing can be done is to find in visual admin somewhere about system properties, conection parameters searching for something wrong there... here are our parameters if you would like to find something (sorry for the size of message)...

AFW.Call.maxConsumers 10

AFW.Recv.maxConsumers 5

AFW.Rqst.maxConsumers 10

AFW.Send.maxConsumers 5

BC_http://sap.com/xi/XI/System.Call.maxConsumers 20

BC_http://sap.com/xi/XI/System.Recv.maxConsumers 10

BC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20

BC_http://sap.com/xi/XI/System.Send.maxConsumers 10

BcAdapter.Call.maxConsumers 10

BcAdapter.Recv.maxConsumers 5

BcAdapter.Rqst.maxConsumers 10

BcAdapter.Send.maxConsumers 5

CIDXAdapter.Call.maxConsumers 10

CIDXAdapter.Recv.maxConsumers 5

CIDXAdapter.Rqst.maxConsumers 10

CIDXAdapter.Send.maxConsumers 5

CIDX_http://sap.com/xi/XI/System.Call.maxConsumers 20

CIDX_http://sap.com/xi/XI/System.Recv.maxConsumers 10

CIDX_http://sap.com/xi/XI/System.Rqst.maxConsumers 20

CIDX_http://sap.com/xi/XI/System.Send.maxConsumers 10

EOIO.lockTimeout 5

File_http://sap.com/xi/XI/System.Call.maxConsumers 20

File_http://sap.com/xi/XI/System.Recv.maxConsumers 10

File_http://sap.com/xi/XI/System.Rqst.maxConsumers 20

File_http://sap.com/xi/XI/System.Send.maxConsumers 10

JDBC_http://sap.com/xi/XI/System.Call.maxConsumers 20

JDBC_http://sap.com/xi/XI/System.Recv.maxConsumers 10

JDBC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20

JDBC_http://sap.com/xi/XI/System.Send.maxConsumers 10

JMS_http://sap.com/xi/XI/System.Call.maxConsumers 20

JMS_http://sap.com/xi/XI/System.Recv.maxConsumers 10

JMS_http://sap.com/xi/XI/System.Rqst.maxConsumers 20

JMS_http://sap.com/xi/XI/System.Send.maxConsumers 10

JPR.Call.maxConsumers 10

JPR.Recv.maxConsumers 5

JPR.Rqst.maxConsumers 10

JPR.Send.maxConsumers 5

MPA.Call.maxConsumers 10

MPA.Recv.maxConsumers 5

MPA.Rqst.maxConsumers 10

MPA.Send.maxConsumers 5

Mail_http://sap.com/xi/XI/System.Call.maxConsumers 20

Mail_http://sap.com/xi/XI/System.Recv.maxConsumers 10

Mail_http://sap.com/xi/XI/System.Rqst.maxConsumers 20

Mail_http://sap.com/xi/XI/System.Send.maxConsumers 10

Marketplace_http://sap.com/xi/XI/System.Call.maxConsumers 20

Marketplace_http://sap.com/xi/XI/System.Recv.maxConsumers 10

Marketplace_http://sap.com/xi/XI/System.Rqst.maxConsumers 20

Marketplace_http://sap.com/xi/XI/System.Send.maxConsumers 10

RFC_http://sap.com/xi/XI/System.Call.maxConsumers 20

RFC_http://sap.com/xi/XI/System.Recv.maxConsumers 10

RFC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20

RFC_http://sap.com/xi/XI/System.Send.maxConsumers 10

RNIF11Adapter.Call.maxConsumers 20

RNIF11Adapter.Recv.maxConsumers 10

RNIF11Adapter.Rqst.maxConsumers 20

RNIF11Adapter.Send.maxConsumers 10

RNIF11_http://sap.com/xi/XI/System.Call.maxConsumers 20

RNIF11_http://sap.com/xi/XI/System.Recv.maxConsumers 10

RNIF11_http://sap.com/xi/XI/System.Rqst.maxConsumers 20

RNIF11_http://sap.com/xi/XI/System.Send.maxConsumers 10

RNIFAdapter.Call.maxConsumers 10

RNIFAdapter.Recv.maxConsumers 5

RNIFAdapter.Rqst.maxConsumers 10

RNIFAdapter.Send.maxConsumers 5

RNIF_http://sap.com/xi/XI/System.Call.maxConsumers 20

RNIF_http://sap.com/xi/XI/System.Recv.maxConsumers 10

RNIF_http://sap.com/xi/XI/System.Rqst.maxConsumers 20

RNIF_http://sap.com/xi/XI/System.Send.maxConsumers 10

SOAP_http://sap.com/xi/XI/System.Call.maxConsumers 20

SOAP_http://sap.com/xi/XI/System.Recv.maxConsumers 10

SOAP_http://sap.com/xi/XI/System.Rqst.maxConsumers 20

SOAP_http://sap.com/xi/XI/System.Send.maxConsumers 10

bulkCommit.threshold 100

cluster.timeout 60000

connection.0.ackListener null

connection.0.exceptionListener localejbs/AFWListener

connection.0.jms.messageSelector null

connection.0.jms.profile null

connection.0.jms.provider null

connection.0.jms.queue null

connection.0.messageListener localejbs/AFWListener

connection.0.name AFW

connection.0.pollAttempts 60

connection.0.pollInterval 60000

connection.1.ackListener localejbs/MarketPlaceAdapterListener

connection.1.exceptionListener localejbs/MarketPlaceAdapterListener

connection.1.jms.messageSelector null

connection.1.jms.profile null

connection.1.jms.provider null

connection.1.jms.queue null

connection.1.messageListener localejbs/MarketPlaceAdapterListener

connection.1.name MPA

connection.1.pollAttempts 60

connection.1.pollInterval 60000

connection.2.ackListener null

connection.2.exceptionListener localejbs/JPR

connection.2.jms.messageSelector null

connection.2.jms.profile null

connection.2.jms.provider null

connection.2.jms.queue null

connection.2.messageListener localejbs/JPR

connection.2.name JPR

connection.2.pollAttempts 60

connection.2.pollInterval 60000

connection.3.ackListener null

connection.3.exceptionListener localejbs/RNIFMessageListener

connection.3.jms.messageSelector null

connection.3.jms.profile null

connection.3.jms.provider null

connection.3.jms.queue null

connection.3.messageListener localejbs/RNIFMessageListener

connection.3.name RNIFAdapter

connection.3.pollAttempts 60

connection.3.pollInterval 60000

connection.4.ackListener null

connection.4.exceptionListener localejbs/CIDXMessageListener

connection.4.jms.messageSelector null

connection.4.jms.profile null

connection.4.jms.provider null

connection.4.jms.queue null

connection.4.messageListener localejbs/CIDXMessageListener

connection.4.name CIDXAdapter

connection.4.pollAttempts 60

connection.4.pollInterval 60000

connection.5.ackListener localejbs/BcAdapterListener

connection.5.exceptionListener localejbs/BcAdapterListener

connection.5.jms.messageSelector null

connection.5.jms.profile null

connection.5.jms.provider null

connection.5.jms.queue null

connection.5.messageListener localejbs/BcAdapterListener

connection.5.name BcAdapter

connection.5.pollAttempts 60

connection.5.pollInterval 60000

connection.6.ackListener null

connection.6.exceptionListener localejbs/TestListener

connection.6.jms.messageSelector null

connection.6.jms.profile null

connection.6.jms.provider null

connection.6.jms.queue null

connection.6.messageListener localejbs/TestListener

connection.6.name test

connection.6.pollAttempts 60

connection.6.pollInterval 60000

connection.7.ackListener null

connection.7.exceptionListener localejbs/RNIF11MessageListener

connection.7.jms.messageSelector null

connection.7.jms.profile null

connection.7.jms.provider null

connection.7.jms.queue null

connection.7.messageListener localejbs/RNIF11MessageListener

connection.7.name RNIF11Adapter

connection.7.pollAttempts 60

connection.7.pollInterval 60000

connections (name=AFW, messageListener=localejbs/AFWListener, exceptionListener=localejbs/AFWListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=MPA, messageListener=localejbs/MarketPlaceAdapterListener, exceptionListener=localejbs/MarketPlaceAdapterListener, ackListener=localejbs/MarketPlaceAdapterListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=JPR, messageListener=localejbs/JPR, exceptionListener=localejbs/JPR, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=RNIFAdapter, messageListener=localejbs/RNIFMessageListener, exceptionListener=localejbs/RNIFMessageListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=CIDXAdapter, messageListener=localejbs/CIDXMessageListener, exceptionListener=localejbs/CIDXMessageListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=BcAdapter, messageListener=localejbs/BcAdapterListener, exceptionListener=localejbs/BcAdapterListener, ackListener=localejbs/BcAdapterListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=test, messageListener=localejbs/TestListener, exceptionListener=localejbs/TestListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=10, Recv.maxConsumers=10, Call.maxConsumers=20, Rqst.maxConsumers=20)(name=RNIF11Adapter, messageListener=localejbs/RNIF11MessageListener, exceptionListener=localejbs/RNIF11MessageListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=10, Recv.maxConsumers=10, Call.maxConsumers=20, Rqst.maxConsumers=20)

debug HTTP

failover.reassignOnNodeLoss true

initial.delay 0

jdbc.autoConfigure false

jdbc.datasource jdbc/SAP/BC_XI_AF_MSG

jdbc.dbProductName ORACLE

jdbc.substituteEmptyString true

jdbc.supportsOpenSQL true

jdbc.supportsScrollableResultSet false

jms.0.dmq SonicMQ.deadMessage

jms.0.messageLengthKey message_length

jms.0.password ********

jms.0.provider

jms.0.url

jms.0.username

monitoring.displayDefault fromParty, toParty, status, timesFailedRetries, sentRecvTime

persistMessageRemover.checkInterval 1440

proxy.password ********

proxy.user

reassignCheck.waitTime 30

ssl.httpsHandler iaik.protocol.https.Handler

ssl.securityProvider iaik.security.provider.IAIK

ssl.serverNameCheck false

ssl.trustedCACerts.viewName TrustedCAs

startup.delay 0

syncMessageRemover.checkInterval 60

syncMessageRemover.messageCount 1000

syncMessageRemover.removeBody true

system.deafaultMaxConsumersPerQueue 10

system.failNonDelivered false

system.message.lazyRead true

system.node 23654950

system.queueConsumerThreadPoolSize 0

system.statusLog System,Send,Recv,Call,Rqst

system.transactionManager ts

test.Call.maxConsumers 20

test.Recv.maxConsumers 10

test.Rqst.maxConsumers 20

test.Send.maxConsumers 10

throughputStatistics enabled

regards

roberti

[Former Member]

How do we increase the threads for the following:

JDBC_http://sap.com/xi/XI/System.Call.maxConsumers 20

JDBC_http://sap.com/xi/XI/System.Recv.maxConsumers 10

JDBC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20

JDBC_http://sap.com/xi/XI/System.Send.maxConsumers 10

Regards,

XIer

[aashish_sinha]

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

[former_member214364]

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

[Former Member]

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?

[Former Member]

Hi Barry,

Is it EOIO messages? There is a possibility that some messages failed to deliver which why the queue is stuck.

Try resending/canceling the failed message in queue using RWB or

http://hostname:port/MessagingSystem/monitor/sequenceMonitor.jsp

-Pinkle

[ranjit_deshmukh]

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