Messages struck in Queue

Hi ,
I am doing a IDoc to JDBC scenarios ,the number of IDoc hitting XI is huges.Most of them pass XI successfully and create records in XI.But some of them get stuck in Queue.I can see them in SMQ2.When I check them they are struck there with the error "SQL error in the database when accessing a table".I when through other thread with the same error.It was suggested to increase the tablespace.My question is which tablespace to increase ,is it the DB tablespace or the XI tablespace?I am using SQL Server as the DB.I was told that there is no tablespace concept in SQL Server.So,does it mean that I need to increase the table space of XI ,if so how to do that?
Thanks,
Venu

hi,
Kindly check this [http://help.sap.com/saphelp_nw04/helpdata/en/c4/3a71c8505211d189550000e829fbbd/content.htm]

Similar Messages

BPM scenario,message struck in queue.

Hi folks,
I am doing a Simple file to file BPM scenario(NO TRANSFORMATION)...
My scenario executed properly,but in moni i receive a green flag, after i looked it in
LUW -->Display Process, I can see the steps as
Receive1--initialize-send1-UNDEFINEDWork flow completed.
I think there is a problem after send.... can u plz tell me what may be the reason.
Or Am i doing in creating a IP,..... if so can u give me a simple file to file scenario,with detailed steps

Yes i have checked everything,
Status code of IP is 0 in sxi_cache-->IP
and interfaces are assigned properly at right places......
Still the message gt struck in queue...
I have a doubt,that why The Unsefined step is coming after send1....
RECEIVE1>INITIALIZE>SEND1>UNDEFINED-STEP>COMPLETED

Client proxy message strucked in ECC queues

Hi All,
I am working on Proxy interface. My interface is like below
ECC 6----
>PI (7.1) -
>File
I had done the entire configuration in ECC and PI for proxy activation. While testing the interface in ECC system messages processed successfully, but the message strucked in queues (SMQ2) in ECC system. If run the queue manually the message processed successfully to the PI.
Can you please tell any more configurations required?
Regards,
Ramesh

Hi,
The queue used for Proxy call is not registerd in ECC system. You need to register the queue to process successfully.
you will get the name of Queue from SMQ2 t-code and register it with t-code SMQR.
Thanks
Swarup
Edited by: Swarup Sawant on Aug 24, 2009 8:03 AM

Screen output without connection to user, Message struck at inbound queue

Chaps,
I executed inbound proxy form PI 7.0, the message was struck in the inbound queue of ECC 6.0,
with status text "Screen output without connection to user" then when I apply execute LUW then it is converted to
"ThiSend:bad tm type /connection closed (no data)".
when i test the same message from 'SPROXY' t.code, inbound proxy class was working fine.
I came to know that when we call an ABAP program in side a proxy then it will throw same error what I got by checking the below url
Message struck at inbound que in server proxy
But in my proxy. I am just putting the data into z table and on some condition I am calling some other BAPI call.
Here my doubt is calling the SUBMIT for other ABAP program is same as calling the BAPI call?
because in the above thread clearly saying that don't use the other ABAP program in proxies. is the same case for calling the BAPI call into the proxy?
In proxy, the logic is I am just simply reading the data from IS(integration server, PI7.0 SP 18) to ECC 6.0(SP14) if the row is not there the data is reading into table. If row is already there then it is stuck up in SMQ2 (inbound queue) of the ECC
am I missing any basic things? please guide.

But in my proxy. I am just putting the data into z table and on some condition I am calling some other BAPI call.
Here my doubt is calling the SUBMIT for other ABAP program is same as calling the BAPI call?
I too believe ..
because in the above thread clearly saying that don't use the other ABAP program in proxies. is the same case for calling the BAPI call into the proxy?
It is saying not suggestable...!!!! BAPI calls work perfectly !1
In proxy, the logic is I am just simply reading the data from IS(integration server, PI7.0 SP 18) to ECC 6.0(SP14) if the row is not there the data is reading into table. If row is already there then it is stuck up in SMQ2 (inbound queue) of the ECC
am I missing any basic things? please guide.
Seems so,
Lets try below things..
1. Plz check the user is having auth to run the executable program in ECC.
2. It seems that you are not using the proxy structures in a correct way..and check the calling program also..!!
Edited by: Santosh Rawat on Jul 30, 2009 1:12 PM

Inbound Messages are struck in Queue.-Production environment of client box.

Dear All,
We have scheduled a Job(RSQIWKEX) to process messages in Inbound Queue. we are facing probem after restarting the XI server that the messages are struck in Queue and scheduled job also not getting executed. Even manually also not able to process the messages.
Could anyone help as how to proceed or what could be the cause of this problem.
Regards,
Siva

What is the error message?

Message Got Struck in Queue ----Repeatedly happening

Hi Frnds,
I am working on one scenarios File to IDOC, when i am sending messages to IDOC some messages got struck in Queue, when i am resending the messages manually then its processing.
why thi issues happends repeatedly, how to avoind this issue.
Regards,
Raj

Hi
Call the Integration Server and call transaction SMQR in the sender and receiver Integration Engine in the corresponding system client.
Check the status of the scheduler and the status of the XBQ* and XBT* queues:
u25CF     Inbound qQueues
XBTI* (ExactlyOnce)
XBQI* (ExactlyOnceInOrder)
u25CF     Outbound queues
XBTO* (ExactlyOnce)
XBQO* (ExactlyOnceInOrder)
u25CF     Acknowledgment queues
XBTB* (ExactlyOnce)
XBQB* (ExactlyOnceInOrder)
u25CF     Large message queue
XBTL* (ExactlyOnce)
If the scheduler has the status Waiting, it is waiting for free work processes. This is why delays occur when XML messages are processed.
If not all necessary queues are registered, you can search for queues with the name prefix above using transaction SMQ2. Use transaction SXMB_ADM to register the queues in this case.
Check queue configuration
For a complete analysis, make sure that the queues of the integration server are registered. To do this start the transaction for the Integration Engine administration (SXMB_ADM) and select the function manage queues.

SXMB_MONI message fail causing Queue struck at SMQ2

Hi All,
If mapping error occured in SXMB_MONI, corresponding entry will be struck up in SMQ2 and saying that SYSFAIL.
When i drill down this into further, it is saying that Mapping error.
Because of this all messages coming later also getting strucked in this queue.
Why is this happening and what to do for not to get struck further messages
Regards

Hi Hetal,
>>Create a job which will restart message after some time if it is stuck because of connection problem or something, then queue will be clear.
It's because of Mapping problem, even though we schedule a job to restart, it won't resolve. again it comes into same error.
@Prateej:
>>Could you check the QoS for the following entry in SXMB_MONI? Is it EOIO ?
QOS is Exactly Once
@Madu:
>>This is the standard behavior of PI. When some message will fail in Integration Engine(either because of Receiver not found or mapping error),some of remaining message(not all messages) which will come in the same queue of failed message will stuck.
You can not predict which messages will stuck and which messages will not stuck.
YES, you are right.
>>If you are having some important interface, which you want to divert the messages in other queue. You apply exactly once in order in sender channel for other interfaces so that these messages will not stuck in SMQ2.
For me all are Important Interfaces only. I can't prioritize
I think the better solution is Monitor failed messages in MONI every day and if it is failed because of Mapping error means, we can delete that entry from SMQ2.because for mapping related errors we don't require that message to restart again.
so that nothing will be queued after wards.
Regards

Messages in Buffered queue not beeing applied

Hi All,
Im running a streams environment. The receiving server crashed and was restarted. The apply process was restarted and the buffer was flooded with messages. Flow control initiatied on the sending database. The apply process doesn't show errors, but there are 5001 messages in the queue that arn't beeing applied. I' ve tried restarting the apply process and increased the number of parallel apply processes. Purging the queue doesn't seem like a good idea since the I will loose data. What can I do?
btw The messages in de queue seem to be in defered state. I dont know if this is of any importance...
Another thing that struck me as odd was the following:
Coordinator Low Watermark: 11063412548
Reader Oldest SCN: 11063412382
I would assume the Oldest SCN would be equal or higher that the Coordinator low watermark because messages are first beeing read, then coordinated then applied right?
and while I' m at it: it is no longer possible to disable the queue from Grid Control. If I try to, what happens is, that the status becomes disabled (red downward arrow) but the state remains:"DEQUEUEING MESSAGES"
kind regards,
Erik
Edited by: erikros on Apr 28, 2010 2:47 PM
Edited by: erikros on Apr 28, 2010 3:05 PM
Edited by: erikros on Apr 28, 2010 3:08 PM

Query 1
APPLY_NAME : P_APP1
Latency in Seconds : 29139
Message Creation : 2010-04-27 14:48
Apply Time : 2010-04-27 22:54
APPLIED_MESSAGE_NUMBER : 11063412548
Query 2
CAPTURE_NAME : P_CAP1
STATE : PAUSED FOR FLOW CONTROL
CAPTURE_TIME : 2010-04-29 07:41
CAPTURE_MESSAGE_NUMBER : 11063460122
CAPTURE_MESSAGE_CREATE_TIME : 2010-04-27 14:55
ENQUEUE_TIME : 2010-04-29 07:41
ENQUEUE_MESSAGE_NUMBER : 11063460122
ENQUEUE_MESSAGE_CREATE_TIME : 2010-04-27 14:55
AVAILABLE_MESSAGE_NUMBER : 11076534248
The second query had some fields in it that weren't supported by my version of Oracle 10.2. I replaced them with some others....
Edited by: erikros on Apr 29, 2010 8:24 AM

Message struck at inbound que in server proxy

Sub :Message struck in SMQ2 with status text"ThiSend:bad tm type" .
HI,
I executed inbound proxy form PI 7.0, the message was struck in the inbound queue of ECC 6.0,
with status text "ThiSend:bad tm type /connection closed (no data)".
when i test the same message from 'SPROXY' t.code, inbound proxy class was working fine.
I came to know the message scheduled due to function
module sxms_async_exec
and raising an exception as ThiSend:bad tm type/
connection closed (no data)
please provide the details like when this function
module throw an exception as connection closed(no data).
inside inbound proxy,
could you please suggest us, what should be avoided inside the proxy
method.
warm regards
mahesh.

Hi Chaitanya,
                   previouly, i have the same problem.
                   At that time, we are using 'submit' command inside proxy method i.e i ABAP program.
                     because of that, the message was struck in the inbound que.
                   'submit' is not suggestable inside proxy method.
                   so, pls check your ABAP Program.
warm regards
mahesh.

Message struck in adapter engine with status Hold

Hi,
In intergaration engine all messages are processed, I have checked SMQ1, SMQ2 (no message is struck in queue)
where as messages struck in adapter engine with status Hold, I have checked this in RWB. How to resolve this?
Regards,
Krishna

Hello,
Below is some information on how to resolve this type of issue:
1 - In the RWB, expand the tray for "Configure Table Columns" - by clicking on a square at the right end of this heading.
2 - Check the checkboxes for "Serialization Context" and "Sequence Number". These should then appear in the table columns as well.
3 - Add the Serialization Context to the Extended Filter Criteria. Search the messages in status HOLD based on this new additional criteria.
4 - Sort the messages in ascending order based on the Sequence no.
5 - Check the predecessor message of the first message in status "HOLD"
Based on the following status for this predecessor messages, the actions that can be taken for the HOLD messages are:
a - Predecessor is in Failed State/System Error : Cancel/Resend the
first message in status HOLD after this. Then the remaining messages
can be cancelled/resent.
b - Predecessor is in DLVD state(delivered state) : First Holding
message can be resent/cancelled followed by the others.
c - Predecessor is in NDLV(Non-Delivered Status) : Check why the
predecessor message failed and correct the reason for the failure.
Then resend the predecessor message and then cancel/resend the
remaining HOLD messages. Alternatively, you can directly try
resending this NDLV predecessor message and see if it goes. If it
goes, then the remaining HOLD messages can be resent/cancelled.
Another option could be to cancel this NDLV predecessor message so
that it goes to FAILED state and then cancel/resend remaining HOLD
messages.
Regards,
Sarah

Messages strucking in Receiver ECC

Hi,
I have a scenario i.e. non-SAP to PI to SAP ECC. In that, in PI we are getting Successful flags on every monitoring, but data is not inserting in ECC tables, due to Queues strucked in ECC (smq2) and we can see those messages with status scheduled in SXMB_MONI tcode in ECC system. Means messages are strucked in Queue. Some times In production environment it is giving very critical issue. Here I have a doubt. Between PI and ECC only one Queue is available or multiple? If one message struked in Queue remaining all the messages also be strucking. If only one queue is avail between PI and ECC, Is there any other way to increase number of Queues to overcome this problem.
Thanks & Regards,
Srihari.

Hi Srihari ,
Every R/3 system will have the concept of queue.
If the messages are passed successfully from PI and are stuck up in ECC means there might be some data issue with the first failed message in queue. you can save that message using save LUW and then thus releasing rest of messages from queue.
even if you increase number of queues on ECC , queue stuck still can be a issue. Only way is to remove problamatic message from queue and clear the queue. lateron you can investigate on error message .
Regards,
Sheetal

Unable to receive notifications of new messages arriving on queue

I was wondering whether any AQ experts out there could help me....
I have an Oracle AQ queue and a .net service which listens and dequeues messages from the queue. The .net service is written (using ODP.net) to execute a poll of the queue upon startup (in order to process anything on the queue initially), and thereafter to hook into the relevant ODP.net event (happens to be OracleAQQueue.MessageAvailable) such that anything that subsequently arrives on the queue gets dequeued.
Now, before you tell me to head off to the odp.net forum, I will add very quickly that we have this code in both DEV and TEST environments and it works fine. The queue happens to be a multiple-consumer queue, so the service subscribes as a particular consumer and everything hangs together. My problem is that we promoted all this code to LIVE a couple of days ago and although we are able to dequeue messages no problem we are no longer receiving MessageAvailable notifications.
Now, I come from a .net background and am 100% sure that the .net code on our Live servers is the same as the code on our Test servers, save for the connection string. So I believe that the problem is more database- or queue-config-related than software-related.
I do not have a high degree of Oracle knowledge in this area but what I can say is that when we start our .NET service, it is happily able to do the initial poll of the queue and to dequeue any messages. So this says to me that, fundamentally, we're not far off. i.e. it isn't anything really dumb like the queue doesn't exist in the live environment! It is purely that the MessageAvailable event never fires.
I guess my question is fairly open, then. Given what I have said, can anyone think of reasons why this could happen?
Things I have already thought of include:
- different versions of ODP drivers. Not so, I supervised their installation myself on each environment.
- firewall on the Live database blocking comms? I mean, presumably there is some tcp/udp comms going on underneath the MessageAvailable subscription. I don't believe this to be the case but if anyone knows where I can find out in more details how this works I'd be grateful, if only because it would allow me to ask more specific questions of the DBAs/Server admins
- my initial hunch was that it was something with the consumer not being set up fully (the .net code uses the consumer name to register both to dequeue messages and to subscribe to MessageAvailable notifications). Not I am told that this is not the case and that the consumer has been set up properly, but I'm still a little suspicious.
Anyway, any help would be gratefully received.
Pete

Hi Pete,
Together we may be able to work this out ... I have a good level of knowledge on the database side of AQ but know nothing about ODPAQ :)
Have you seen the following documentation section? Could there be some restrictions on the production host on the ports?
Oracle Data Provider for .NET opens a port to listen for notifications. HA events, load balancing, and database change notification features also share the same port. This port can be configured centrally by setting the database notification port in an application or Web configuration file. The following example code specifies a port number of 1200:
<configuration>
<oracle.dataaccess.client>
<settings>
<add name="DbNotificationPort" value="1200"/>
</settings>
</oracle.dataaccess.client>
</configuration>
If the configuration file does not exist or the db notification port is not specified, then ODP.NET uses a valid and random port number. The configuration file may also request for a random port number by specifying a db notification port value of -1.
The notification listener, which runs in the same application domain as ODP.NET, uses the specified port number to listen to notifications from the database. A notification listener gets created when the application registers with OracleAQQueue.MessageAvailable event. One notification listener can listen to all notification types. Only one notification listener is created for each application domain.
Thanks
Paul

How to set up the maximum number of messages on a queue programmatically

Hi,
I am using IMQ 3.5 to implement a message layer for one of my projects. I created a "Job Status Queue", which receives job status report from a java application every minute. But I just want to keep the most current status report instead of all the job running history. How can I restrict the maximum number of messages to 1 programmatically?
Any suggestion or help will be appreciated.
Xiaoyun Tang

You can't limit the destination size programmatically, but you can do it administratively and associate a behavior to occur when the limit is reached. In your case it sounds like you want a queue, 1 message deep, and to discard the oldest message when the queue is full. When you create the physical queue on the broker you can specify these attributes (you can also update them on an existing queue). For example:
imqcmd create dst -t q -n StatusQ -o maxNumMsgs=1 -o limitBehavior=REMOVE_OLDESTFor more information see Chapter 6 of the Message Queue Administration Guide. In particular the "Managing Destinations" section:
http://docs.sun.com/app/docs/coll/MessageQueue_35_SP1
Joe

How do i find the number of messages in a queue

Sorry if this is too trivial, but i haven't been able to figure out how to determine the number of messages in a queue. business case being that i can only have 3 messages in the send queue, so i need to stop sending if there are 3 outstanding messages still in the send queue.
Can someone point the way?
Thanks,
Nilesh

Hi,
To get the depth using JMS you must create a QueueBrowse and browse the entire queue. Its generally horribly inefficient if you want to do it with any regularity.
In Hermes I have had to write plugins that open separate connections to providers using their non-JMS APIs or JMX and get that kind of information that way.
Look at the getDepth() method in this JBoss plugin for an example that uses JMX:
http://cvs.sourceforge.net/viewcvs.py/hermesjms/Hermes4/src/java/hermes/ext/jbossmq/JBossMQAdmin.java?view=markup
And here is one for WebSphereMQ that uses one of its many APIs..
http://cvs.sourceforge.net/viewcvs.py/hermesjms/Hermes4/src/java/hermes/ext/mq/MQSeriesAdmin.java?view=markup
Colin.
http://hermesjms.com

Error while trying to pick message from weblogic queue

Hi,
We are getting the following error while trying to connect to pick up a message from weblogic queue.
We are suing oracle soa suite 10.1.3.1 and weblogic 8.1
the bad part is that, this error is not documented anywhere and couldn't get much help on this.
Would appreciate any suggestions / pointers on this.
Let me know if any further information is required.
invoke failed
org.collaxa.thirdparty.apache.wsif.WSIFException: file:/E:/product/10.1.3.1/OracleAS_4/bpel/domains/default/tmp/.bpel_OTOCBPELProcess_1.0_78fcf080ec2bd7495aebfb5373e76116.tmp/readmsg.wsdl [ Consume_Message_ptt::Consume_Message(opaque) ] - WSIF JCA Execute of operation 'Consume_Message' failed due to: ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
; nested exception is:
ORABPEL-12115
ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
---------------------------------------------------

Hi!
I am facing a similar issue, does someone have an idea ?
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>null</code>
</part><part name="detail"><detail>null</detail>
</part><part name="summary"><summary>file:/opt/oracle/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_TestReceiveMessage_BPEL_1.0_e00fd88d454889b871183d0d92dc9f7d.tmp/plReceiveMessage.wsdl [ Consume_Message_ptt::Consume_Message(TestPushMessage_BPELProcessRequest) ] - WSIF JCA Execute of operation 'Consume_Message' failed due to: ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
; nested exception is:
ORABPEL-12115
ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
Please examine the log file to determine the problem.
</summary>
</part></remoteFault>
Thanks,
romain.

Messages struck in Queue

Similar Messages

Maybe you are looking for