TimeOut Exceeded in Inbound BPE queue

Hi All,
We have been facing an issue in our PI production box which stops the whole BPE inbound queue for one particular BPM.
We have a simple BPM pattern to spilitt messages
Receive Message>Transformation which includes Java mapping>Send step Inside Block with multiline elemnet ( To send n number of messages to target application using HTTP adapter).
We received 5 MB file for this interface and it got failed in BPE inbound queue with error message "Time Limt Exceeded". The IP is using One queue and Buffering possible options. Ideally what happens is message is getting blocked in the BPE inbound queue which stops other messages.
There is always active receive step is available to receive messages from Q.
The corresponding Integration process was not able to pick the message which 5-7MB file size. The BPM is running fine without any issue when file size is smaller.
I have gone through the following documents already.
How To Configure Inbound Processing in ccBPM Part I: DeliveryMode
How to Configure Inbound Processing in ccBPM Part II Queue Assignment
How ToConfigure ccBPM Runtime Part III: Transactional Behavior of an Integration Process.
Could anyone suggest me if i hcan change any default settings which mentioned in above documents? Rightnow i am using "One Queue" and "Buffering possible" options.
Where exactly time limt settings are maintained for BPE inbound queue?
Edited by: Rajesh on Oct 27, 2009 11:47 PM

First thing that I would do is to remove the queue specification in the BPM. This way, it will not block any other messages of the BPM. Then check for any Runtime paramters in SXMB_ADM for increasing the wait time.
VJ

Similar Messages

IO Exception: Lock timeout exceeded for documents , wait time = 60014

Hi,
We are getting an error while uploading any document on portal in KM content area. The full error details as follows
#D27E2001B003002500000D210005D0D20004520E6FF2B6FB#1216121868039#com.sapportals.wcm.repository.service.accessstatistic.AccessStatisticManager#sap.com/irj#com.sapportals.wcm.repository.service.accessstatistic.AccessStatisticManager#BMERRON#71986##<host name>_7664450#BMERRON#3f730c80526211ddb0fcd27e2001b003#SAPEngine_Application_Thread[impl:3]_4##0#0#Error##Plain###error while handling event - com.sapportals.wcm.WcmException: IO Exception: Lock timeout exceeded for <documents>, wait time = 60006
     at com.sapportals.wcm.repository.service.appproperties.PropertiesService.setProperty(PropertiesService.java:984)
     at com.sapportals.wcm.repository.service.appproperties.PropertiesService.setProperty(PropertiesService.java:1203)
     at com.sapportals.wcm.repository.service.appproperties.PropertiesManager.setProperty(PropertiesManager.java:176)
     at com.sapportals.wcm.repository.service.accessstatistic.AccessStatisticManager.updateLastReadDate(AccessStatisticManager.java:177)
     at com.sapportals.wcm.repository.service.accessstatistic.AccessStatisticManager.received(AccessStatisticManager.java:253)
     at com.sapportals.wcm.util.events.ReceiverEntry.doSend(ReceiverEntry.java:223)
     at com.sapportals.wcm.util.events.EventBroker.send(EventBroker.java:86)
     at com.sapportals.wcm.util.events.TransactionalEventBroker.send(TransactionalEventBroker.java:56)
     at com.sapportals.wcm.repository.manager.ResourceEventBroker.send(ResourceEventBroker.java:219)
     at com.sapportals.wcm.repository.manager.AbstractRepositoryManager.sendEvent(AbstractRepositoryManager.java:322)
     at com.sapportals.wcm.repository.RMAdapter.sendEvent(RMAdapter.java:342)
     at com.sapportals.wcm.repository.ResourceImpl.sendEvent(ResourceImpl.java:4206)
     at com.sapportals.wcm.repository.ContentImpl.getInputStream(ContentImpl.java:119)
     at com.sapportals.wcm.repository.ContentImpl.getInputStream(ContentImpl.java:132)
     at com.sapportals.wcm.service.xmlforms.transformation.ResourceDemultiplexer.getContentStream(ResourceDemultiplexer.java:71)
     at com.sapportals.wcm.service.xmlforms.transformation.Transformation.render(Transformation.java:209)
     at com.sapportals.wcm.app.xmlforms.PreviewServlet.sendForm(PreviewServlet.java:165)
     at com.sapportals.wcm.app.xmlforms.PreviewServlet.doGetAction(PreviewServlet.java:130)
     at com.sapportals.wcm.app.xmlforms.XFBaseServlet.doGet(XFBaseServlet.java:241)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sapportals.wcm.app.xmlforms.XFBaseServlet.service(XFBaseServlet.java:134)
     at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:333)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sapportals.portal.prt.core.broker.ServletComponentItem$ServletWrapperComponent.doContent(ServletComponentItem.java:110)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
     at java.security.AccessController.doPrivileged(AccessController.java:242)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     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:175)
     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:215)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Any Help?
Regards,
Sree

Hi sreedhar Gunda,
Check whether the repositories are in active and running mode or not. If they are running fine. then check the authorization is sufficient from BASIS people.
points if useful
Thanks
Suresh

Inbound stuck queues

Hi guys,
There are a few inbound stuck queues in the CRM system with the error SYSFAIL.
When we checked in smw01 the error is"The transaction getting locked by the user"
When we manually activate the queues the queue gets processed out.
But we need to manaully go in every day to reprocess these queues .any idea of automatically reprocessing these stuck queueus.
Thanks,
Krishna

Hi Krishna,
You can reprocess those queues automatically, but again I would suggest the administrator should manually go and reprocess it as SAP standard don't recomment the autoprocess of the Queues/ BDocs, because this may lead to inconsistency.Again in the end decision is ours but SAP would never take responsibility if anything goes wrong as of SAP standard practice is not followed.
Best Regards,
Pratik Patel
<b>Reward with Points!</b>

DBM_EXECUTE command timeout exceeded

Hello All,
When i am excuting any db t-code from my system ,
i am gettting DBM_EXECUTE command timeout exceeded.
I have tried it with different user but facing the same problem.
kindly let me know the sloution for this.
Thanks in advance,
Atul

Hello Atul,
if you don't find a solution in the SAP notes then you should open a customer message.
SAP support will then logon to your system and analyze the problem.
Best regards,
Melanie

Help out for Inbound & Outbound queue

BW Gurus
pl. help me on Inbound & Outbound queue, give details as step by step or any document pl. send it on [email protected]
but i want to understand the through process of it.
assign points if helpful
thanks in advance
charu

http://help.sap.com/saphelp_nw04/helpdata/en/e7/555e3c0f51a830e10000000a114084/content.htm
You can check the tRFCs using tcode SM58 ,and analyze it.
Outbound queue is something which maintains data when it gets posted to R/3. You can check Outbound queue using tcode LBWQ. We generally load the LBWQ data to Delta Queue using JoB Controller.
WE20 is tocode where you maintain Inbound n Outbound parameters. Like which messages to communicate in between Bw & R/3 system.

TimeOut Exceeded in SMQ2- queue Block

Hi all,
I am having an issue with my production PI BOX. Not sure if there is any solution for this.
I have some interfaces in PI which expects huge payload data.Sometime the messages are getting failed in SMQ2 with error message " Time Limit Exceeded ". This is not happening with one particular interface message.Sometime teh queue got blocked for one interface and then the other day with some other interface.
When i tried to resend the same messages by selecting Execute LUW option, all of them have gone through fine. But we cannot do this manually everyday. I just wants to know where exactly the time out parameter has been maintained for pipeline processing.
The messages are getting timed out in receiver grouping pipeline step.
I have gone through the = Michal Blog : 3802 about the time out. But nothing helpful on that.
Could anyone of you help me out here?

Hi
We are using JDBC communication channels for all these interfaces. But messages are failing in SXMB_MONI .ideally it means that messages are still in Integration engine. right?
It doesn't send teh message to adapter engine
If we increase timeout level at adapter level, does it really help? If yes how come? Could you please explian?
Thanks
Rajesh

Time limit exceeded in inbound qRfc

Hi all!
Please I need your help with this timeout issue. I have the following scenario:
FTP --> XI (Java mapping) --> R3 (Idoc)
Where from that Java mapping I do some RFC's to R3 in order to make conversions and validations.
When I test this interface in development environment with a 1Mb flat file, it took 5 minutes to process. However, i did the same test in QA environment, it took pretty much more than 5 minutes and I got this "time limit exceeded" in the qRfc inbound queue (sxmb_moni t-code).
I was told that the hardware beneath development and QA are different but theorically, the later should be faster.
Anyone has any suggestion to resolve this? I will really appreciate it.
Best regards!
Vanesa.

Hi,
have a look on this doc called "HowTou2026 Investigate Timeouts in Synchronous XI/PI Scenario"
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747
You will certainly find your answer.
Regards.
Mickael

Inbound Idocs: Queue Processing (non-stop queue?)

Hi everyone!
I have an issue with a File to Idoc interface. The customer would want the IDocs arriving to R3 to be in the same order they were sent from the legacy. From the File Adapter there isn't any problem using the EOIO QoS, and in the IDoc Receiver Adapter I checked the "Queue Processing".
There is something in the R3 side that the customer doesn't like much and it's about the stop of queue when an IDoc gets in error status: all the subsequent IDocs stay in status 75 ("IDoc received via qRFC").
I can change the status of the wrong IDoc and then release the stopped queue but: Is there a way to process serialized inbound IDocs avoiding the stop of the queue if an error occurs?
I'm using PI 7.0 SP30.
Thank you in advance!

First, this is not serialization, it's the queuing design EOIO... they are not the same.
So, since you activated EOIO in the Sender CC it's normal to have such behave (i.e. 75 status)...
Basically the serialization is not a good fit for these requirements.
Here is one solution:
1- Use dynamic queue name (via UDF) to create more parallelism since I dont think you have to queue all the IDOCs in one single queue.
2- Copy the IDOCs with 75 status to a new IDOCS with 64 (You must have very few)
3- Use RC1_IDOC_SET_STATUS to change the status of the IDOCS from 75 to something 73
4- There is standard report that you have to schedule and restart the queues
5- Reprocess the IDOCs from steps 2
The enemy of EOIO design is the user locks in the target system...
Cheers,
Fouad

Inbound Stuck Queue in the SMQ2

Hi,
One of the Q got stuck in the Inbound of the CRM system.
It is showing the system status as "Running".IT has been in this staus for the past 2 days.
When I try to activate it is giving Message"The queue is registered and therefore cannot be activated"
The Q is giving Dump Error "Exception condition DELETE_ERROR raised
When I chekced the Bdoc SMW01 the BDOC is in "Yellow Status".
How can i process this queue.

Implement SAP note 758677 for this. This exactly deals with your issue.
This Basically speaks about scheduling 'RSQIWKEX' for inbound and 'RSQOWKEX' for outbound queues.
Also, you need to set the parameter 'QRFC_Restart_ALLOWED' to '1' in the transaction 'SXMB_ADM' -> Integration engine. Its in the runtime dropdown menu.
Note : without this parameter being set this will not work.
Thanks,
Karthik
Edited by: Karthik Rangaraju on Oct 1, 2008 2:13 PM

FlexUnit 4.1 RC1 - adl.exe hangs and is not killed when timeout exceeded

I am running AIR based tests using FlexUnit 4.1 RC1.
I have the "timeout" parameter of the FlexUnit Ant task set to 45 minutes (2700000 milliseconds). I expect that if this threshold is exceeded, the runner should be killed and the ant task will exit. I am not seeing this behavior. The adl.exe task continues to run, even though the timeout has been exceeded.
Is this a known issue?
Thanks,
Trevor

Brian,
Thanks!
Ah... OK, I was thinking the timeout was more like the JUnit ant task timeout when running in forked mode, i.e.the entire test run has that amount of time to complete (see http://ant.apache.org/manual/Tasks/junit.html). I know I was making an assumption there, but it seemed logical to me since the Flexunit test runner is essentially a forked process...
So, you are saying that the timeout in the FU 4.1 ant task specifies the time to wait for a connection from the SWF running in the player? I see this stated in the Ant task doc on the wiki now - Doh! You also say that the timeout also applies to each individual test? So, it sounds like the behavior is similar to the JUnit ant task running in "perTest" forkmode.
Out of curiosity, is there any way to specify an overall timeout for the entire test suite run, by chance?
Anyway, I figured out why adl.exe was hanging. Evidently an error occurred in the tests which caused a pop-up window to be spawned, and this halted test execution. When I clicked "Dismiss All", the execution continued. Of course, in a CI environment, there is no one there to click the button to dismiss the pop-up! So this is kind of a show-stopper. Is there any way to configure the player (Flash or AIR) to suppress pop-ups, or at least not to stop execution when they occur?
Thanks,
Trevor

Bug in timeout behavior of wait for queue element

The first time a wait for queue element is executed with an infinite timeout (-1 ms) after previously having waited with a finite timeout, it actually times out after the previously used finite interval, a subsequent wait with an infinite timeout then works correctly. Attached is a test program demonstrating the problem. I have tried this demo on both Mac and Sun (LV 6.1 on Mac, LV 6.1f1 on Sun) and it behaves the same on both.
Attachments:
QueueTest.vi.sit ‏22 KB

I do not have an answer at the moment but I have unsuffited the file so that others can look at the program.
Jeremy Braden
Attachments:
Queue.vi ‏77 KB

Help with status of inbound/outbound queues

Hello SDN XI experts!
I hope one of you can offer some assistance with an XI issue we have, as we currently have no XI resource on site and we're stuck in dire straits!
We have had some problems with our inbound and outbound queues in XI, and a search of the net and SDN hasn't helped yet. Basically, if I go in to transaction SMQ1 or SMQ2, I can see that there are files (or do you call them messages?) are building up in our queues with the status READY. To process these files through XI, I am going in to transaction SMQ1 and SMQ2 periodically, and activating the queue. This sets the status to RUNNING, and the files/messages are processed successfully.
What I'm after is how do I either:
a) set the queues so that they are always in status RUNNING;
b) schedule a job to activate the queues periodically; or
c) is there some other thing I am missing?
Sorry if this is a bit vague, but I have no experience of XI at all. If I haven't provided enough info, please ask some questions. Anything you can do to help would be great as I'm manually doing this ten times a day and it's getting tiresome!

Thanks for all your help guys, it's much appreciated as I have ZERO experience with XI...
I have uploaded a screenshot of SMQR to the web, apologies for the quality, but I only have MS Paint on this desktop:
http://img405.imageshack.us/img405/7202/smqrws8.jpg
Luckily, some files have started to queue up again, so I could take some more screen shots! Here is the view of SMQ2:
http://img166.imageshack.us/img166/7086/smq2mv6.jpg
And then when I double click a queue, you see this screen with the queue in the status READY:
http://img248.imageshack.us/img248/3935/smq22ed6.jpg
Until I go in to SMQ2, double click the queue, highlight it and press activate, the files/messages will just stay in XI. After I press the Activate button on the application toolbar in the third image, the files are processed successfully. i.e. If you go in to SXMB_MONI they have a little chequered flag next to them.
Thanks for all your time guys, points will be awarded if you can help me out!

SMQ2 Inbound Blocked Queues Due to UoM.

Dear Experts,
We sustain a number of materials in ECC with order unit TN (Tonnes) and are really causing issues because as the particular supplier delivers in KG's.
I.e....
•We order 0.100 TN (100kgs) of a Metal Sheet from a supplier
•They deliver us 100.123kgs
•Stock is receipted in EWM as 100.123kgs
•PO in ECC only allows 3 decimal places with Unit of Measure TN, so we can only have the PO as 0.100 TN, not 0.100123 that it should be...
•Receipt of the stock from EWM to ECC is then stuck in a queue because of this issue
•Stock cannot get booked in from EWM to ECC
•Stock cannot be backflushed when consumed in production
We need to raise PO's need in KGs. Contracts have been set up in Tonnes and will not allow us to select KGs as a UOM in the PO.
What best practices do you recommend here please?
ADP.

Hello Andriko,
It is always recommended to have same Unit of Measurement both in ECC and EWM.
Can you try maintaining Conversion in your Material master and try reprocess the queue in ECC.
Regards,
Sathish

Connection timeout exceed

Hi, I need to make a connection via http. I'm using next code:
" StreamConnection streamConnection = null;
InputStream inputStream = null;
StringBuffer b = new StringBuffer();
try {
streamConnection = (StreamConnection) Connector.open(url, Connector.READ_WRITE, true);
inputStream = streamConnection.openInputStream();
int ch;
while ((ch = inputStream.read()) != -1) {
b.append((char) ch);
return b.toString();
But the web page takes too long to show the result because of an application necesary stuff. I don't want to reconnect the URL because of traffic charges. How can I ignore the timeout? or any ideas?

Hi, I need to make a connection via http. I'm using next code:
" StreamConnection streamConnection = null;
InputStream inputStream = null;
StringBuffer b = new StringBuffer();
try {
streamConnection = (StreamConnection) Connector.open(url, Connector.READ_WRITE, true);
inputStream = streamConnection.openInputStream();
int ch;
while ((ch = inputStream.read()) != -1) {
b.append((char) ch);
return b.toString();
But the web page takes too long to show the result because of an application necesary stuff. I don't want to reconnect the URL because of traffic charges. How can I ignore the timeout? or any ideas?

Delay into the inbound qRFC queue

Hi:
I am sending a pack of idocs with an xml message through an idoc channel from XI to R/3.
Can I do a delay between the sending of each idoc?
Thanks

Hi,
It is very simple.
If you use BPM,
See first you need to collect IDocs as you mensioned pack of Idocs,this can
be done by the following way
- first import Idoc into IR,
- export the IDoc structure file WSDL and change max occur as 0..unbounded.
- again import into IR under external def
After this collect Idocs and MM,IM target as unbounded msg.
In BPM Use steps
Receive - receive msgs and maitain loop upto satisfying your business requirement condition
maitain the block with foreach mode and put wait step whatever you want to delay
each mesg od IDoc can be send to target by transformation step which will send each record as IDoc sending to target by send step
Try..
Please let me know you got it clear or not.
Regards
Chilla...

TimeOut Exceeded in Inbound BPE queue

Similar Messages

Maybe you are looking for