JDBC Queue Blocked

Hi there.
There is problem that's been bugging me.
We use XI 7.0. and all of patchs have been up-to-date.
Queue Hanging in the Adapter engine(JDBC) occasionally happen.
Like below,
In 2009-01-14 13:21:59, Receiver JDBC adapter successfully processed.
But Next step took approximately 10 min ( 13:31:07 ).
In that time, Work process in PI was idle and Only this Interface processed
I really don't know why this waiting situation in a queue occurs.
Truely appreciate your help.
Regards,
Miru.
============================== Symptoms =================================
2009-01-14 13:21:59 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2009-01-14 13:31:07 Success JDBC adapter receiver channel PCCM_JDBC_Receiver_Temp:
processing started; party , service SKEC_CCMS_PRD_PCCM
Edited by: Tae-Woo Kim on Jan 14, 2009 7:18 AM
Edited by: Tae-Woo Kim on Jan 14, 2009 7:26 AM

Hi, Dharamveer
Thanks for the answer.
My case is similar with Henrique's reply.
But In my case, we don't have any EOIO scinarios( only use EO and BE )
and there were not error in the queue at that time.
Problem is taking so much time to process message that is blocked with status "Delivering in AE queue.
SP Level is 17 ( Both ABAP and J2EE)
Regards,
Miru.

Similar Messages

Message Queue Blocking / MSGMNI Setting

Hi All,
Firstly, many thanks to all that can assists. I am currently getting Message Queue
Blocking messages in my ULOG files in my Tuxedo Application. (Tux ver 7.1 in Unix).
I am not sure what is causing this, but started to look into the Tux Config (UBB.MP)
and System message queue setting. Detailed as follows:
1)
Listed below is the system message queue setting:
set msgsys:msginfo_msgmni=2000
set msgsys:msginfo_msgmax=128000
set msgsys:msginfo_msgmnb=100000
set msgsys:msginfo_msgssz=256
set msgsys:msginfo_msgseg=25088
set msgsys:msginfo_msgtql=1550
set msgsys:msginfo_msgmap=1000
According to the BEA site, the MSGMNI is determined by this formula:
MSGMNI = MAXACCESSERS + 7 + (no. of servers with REPLYQ) + (no. MSSQ sets) - (no.
of servers with MSSQ sets)
The following is my current Tux. Config (UBB.MP) is set as :
- MAXACCESSERS = 2300
- Each servers (4 types in total) has its own REPLYQ and RQADDR.
- The same type of servers are set the same across 4 application servers.
Hence, my MSGMNI should be a minimum 2339 (ie. MSGMNI = 2300 + 16 + 16 - 0 = 2339).
But my current MSGMNI is 2000.
Would this contribute to my Message Queue Blocking?
Is my understanding correct and is this something I should change to avoid Message
Queue Blocking? Any helps and advice is much appreciated.

Malcolm,
Your information and explanations behind these error messages are very useful.
It allow me to further understand Tuxedo internal processing and at the same time
give me a chance to start analysing these fields.
I am reluctant to ask further questions at the mean time. I will use your suggestions
as a starting point.
I will certainly keep you posted of the outcome when I have made the changes in
my UBB config and machine parameters.
Many thanks with your help/explanations Malcolm. It helps alot!
Cheers.
David.
"Malcolm Freeman" <[email protected]> wrote:
>
Hi David,
The MSGTQL reference you give (Solution S-00488) refers to the BEA MessageQ
product
and is not relevant to Tuxedo.
The error messages indicate that the queue buildup is probably due to
a restartable
server failing. What happens is this:
When a restartable server fails its IPC queue remains in place and continues
to
receive messages (which will be processed when the server restarts).
Depending
on the time taken to restart, the queue could become full and unable
to receive
any more messages, and this is probably why you got the message CMDTUX_CAT:1380
indicating that the BRIDGE process was unable to put a message on the
server's
queue.
A server is only restarted when the BBL does a SANITYSCAN check. If,
for example,
your SANITYSCAN interval is 300 seconds and your server fails immediately
after
the previous scan, then there will be a delay of almost 5 minutes before
the failure
is detected and the server restarted - plenty of time for the queue to
fill up.
There are a few things you could do:
The key thing would be to find out why the server is failing, and fix
the problem.
If this is not possible immediately, consider some of the other ideas
below.
Have several servers form an MSSQ to service this queue; then if one
fails the
others will continue processing the messages while the failed server
restarts
(this assumes, of course, that your application does not require the
messages
to be processed in strict order through the server).
Reduce the SANITYSCAN interval (but don't make it too small). This would
reduce
the average time taken to restart the server.
Increase the size of the IPC queue (MSGMNB) so that it can hold more
messages.
I'm not sure why you got a LIBTUX_CAT:1485 message, but this could be
due to a
BRIDGE failure as a result of the congestion.
The NETLOAD parameter would reduce the number of messages going to the
remote
machine, but only if the local machine offers the same service. If the
remote
machine is the only source of the service then NETLOAD will have no effect.
I
recommend you do a search of this newsgroup for postings on "load balancing"
there's some good stuff which will explain how load balancing works.
Depending how things go, it might not be a bad idea to open a case with
BEA Support
and ask for guidance (remember to submit your ubbconfig (or preferably
do a tmunloadcf)
together with the complete ULOGs from both the master and the slave machine).
Hope this helps some.
Regards,
Malcolm.
"Dave" <[email protected]> wrote:
Hi Malcolm,
Thank you for your reply. Interesting point you have made about theMSGTQL
value.
Based on your suggestion I went hunting around the BEA site and found
the following
snipplet:
"- The MSGTQL parameter must be set to a value greater than or
equal to the MSGMNI setting."
(http://support.bea.com/application?namespace=askbea&origin=ask_bea_answer.jsp&event=link.view_answer_page_solution&answerpage=solution&page=msq/S-00488.htm)
If the above point is valid, then my MSGTQL is definitely way too low.
IF this
be the case, would you know of a method to work out what my MSGTQL bytes
value
should be?
Additionally, I have looked at other parameters which I could tune,and
would
adding a NETLOAD parameter in the *MACHINES section will reduce remote
servers
call? Which potentially, maybe reduce message queue blocking?
FYI:
The error messages I am seeing in my ULOG file are:
"LIBTUX_CAT: 1477 : ERROR .SysServerDied
LIBTUX_CAT: 1476 : ERROR: .SysServerRestarting"
Which then leads to message queue blocking
"CMDTUX_CAT: 1380 : ERROR: Message queue blocking prevented delivery,
Qaddr=..."
and potentially "LIBTUX_CAT: 1485 .SysNetworkDropped."
Many Thanks. Hope to hear from you (Malcolm) or other parties out there
that can
assists.
Thanks.
David

Message Queue Blocking/MSGMNI Confirmations

Hi All,
Firstly, many thanks to all that can assists. I am currently getting Message Queue
Blocking messages in my ULOG files in my Tuxedo Application. (Tux ver 7.1 in Unix).
I am not sure what is causing this, but started to look into the Tux Config (UBB.MP)
and System message queue setting. Detailed as follows:
1)
Listed below is the system message queue setting:
set msgsys:msginfo_msgmni=2000
set msgsys:msginfo_msgmax=128000
set msgsys:msginfo_msgmnb=100000
set msgsys:msginfo_msgssz=256
set msgsys:msginfo_msgseg=25088
set msgsys:msginfo_msgtql=1550
set msgsys:msginfo_msgmap=1000
According to the BEA site, the MSGMNI is determined by this formula:
MSGMNI = MAXACCESSERS + 7 + (no. of servers with REPLYQ) + (no. MSSQ sets) - (no.
of servers with MSSQ sets)
The following is my current Tux. Config (UBB.MP) is set as :
- MAXACCESSERS = 2300
- Each servers (4 types in total) has its own REPLYQ and RQADDR.
- The same type of servers are set the same across 4 application servers.
Hence, my MSGMNI should be a minimum 2339 (ie. MSGMNI = 2300 + 16 + 16 - 0 = 2339).
But my current MSGMNI is 2000.
Would this contribute to my Message Queue Blocking?
Is my understanding correct and is this something I should change to avoid Message
Queue Blocking? Any helps and advice is much appreciated.

Hi All,
Firstly, many thanks to all that can assists. I am currently getting Message Queue
Blocking messages in my ULOG files in my Tuxedo Application. (Tux ver 7.1 in Unix).
I am not sure what is causing this, but started to look into the Tux Config (UBB.MP)
and System message queue setting. Detailed as follows:
1)
Listed below is the system message queue setting:
set msgsys:msginfo_msgmni=2000
set msgsys:msginfo_msgmax=128000
set msgsys:msginfo_msgmnb=100000
set msgsys:msginfo_msgssz=256
set msgsys:msginfo_msgseg=25088
set msgsys:msginfo_msgtql=1550
set msgsys:msginfo_msgmap=1000
According to the BEA site, the MSGMNI is determined by this formula:
MSGMNI = MAXACCESSERS + 7 + (no. of servers with REPLYQ) + (no. MSSQ sets) - (no.
of servers with MSSQ sets)
The following is my current Tux. Config (UBB.MP) is set as :
- MAXACCESSERS = 2300
- Each servers (4 types in total) has its own REPLYQ and RQADDR.
- The same type of servers are set the same across 4 application servers.
Hence, my MSGMNI should be a minimum 2339 (ie. MSGMNI = 2300 + 16 + 16 - 0 = 2339).
But my current MSGMNI is 2000.
Would this contribute to my Message Queue Blocking?
Is my understanding correct and is this something I should change to avoid Message
Queue Blocking? Any helps and advice is much appreciated.

CMDTUX_CAT:1380: ERROR: Message queue blocking prevented delivery

Today, I changed a Tuxedo application (server) to the product systems(One master and two slaves). Only a small changes in code. But after a period of running, there are many errors in ULOG:
CMDTUX_CAT:1380: ERROR: Message queue blocking prevented delivery, Qaddr = 583902
And then, the server is died. After restart the server, this will happen again later.
I don't know why this happens? Thx.

Hi Bill,
This is happening because the BRIDGE process received a message from the network and was unable to place the message on the intended IPC queue. This could be because the server handling that message is backed up, or the system IPC resource settings are too low. Please check the recommended actions in:
http://download.oracle.com/docs/cd/E18050_01/tuxedo/docs11gr1/messages/cdtux/cdtux013.html
Regards,
Todd Little
Oracle Tuxedo Chief Architect

.SysMachineMsgq: message queue blocking

Hi,
I am getting the following error message:
064222.hostname!TMSYSEVT.14351.3071440608.0: WARN: .SysMachineMsgq: hostname message queue blocking
Is there anyway to pinpoint exactly which application and or which service is causing the blocking?
Thank you,
Ivan

Ivan,
You can look in the userlog for a "LIBTUX_CAT:672 ERROR: Message operation
failed because the message queue or the system is full" message. That will
tell you the process in which the msgsnd() failed, although it will not tell
you the specific queue that was full. If the queue full condition is not
something transient, you can use the "ipcs -q -a" command to examine the
number of bytes currently on each queue on the machine.
If you need to automate the process of searching the ULOG, the T_ULOG class
in TM_MIB(5) can be used.
The event message for the SysMachineMsgq event deliberatly contains very few
details, since the process where msgsnd() failed uses a message to inform
the event server of the failure and if a message queue is full, then there
might be a problem with sending a large message to the TMSYSEVT server.
(There is a check to prevent looping if the message send to TMSYSEVT fails.)
Ed
<Ivan Novick> wrote in message news:[email protected]..
Hi,
I am getting the following error message:
064222.hostname!TMSYSEVT.14351.3071440608.0: WARN: .SysMachineMsgq:
hostname message queue blocking
Is there anyway to pinpoint exactly which application and or which service
is causing the blocking?
Thank you,
Ivan

Query regarding Queue block

Hi Experts,
The BASIS team has configured the CCMS alert for XBTI* and XBTO* queues in development system.
Hence we need to test the same.
Possibilities tried:
1. Huge payload
2. Stop and start of BPE this blocks the XBQ which is not needed as of now
3. Deregistering the specific queues. The queus is set to ready state until we register the same. Once registered the queue block is cleared. Hence this option is not helpful.
Kindly let us know the various ways to block the queues in PI.
Thanks
Suganya.

Hi,
If you have any interfaces using EOIO queues then try failing the same at mapping level and check...
Another option is try failing the interface at mapping level by sending some invalid data for normal interfaces (EO) only and check...but in this case runtime may not block the queues all the times only few times and few circumstances it will block the queues...
HTH
Rajesh

Outbound queue blocked in CFM2

Hello folks,
I am trying to activate the integration model in CFM2 and I am getting message
"Outbound queue blocked"
Function/Q/SAPAPO/CIF_PROD_INBOUND
Text: NOSENDS
When I try to manually send the data in the queue in SMQ1 in the r/3, system asks me login to the SCM system and even though I give proper login, queue fails with the error message "Password logon no longer possible - too many failed attempts".But there is no issue with the login credentials.
Can you please helpme out here.
Thanks,
Vikram

Hi
Although you may be entering the correct user and password, the user may now be locked. You need to check if the RFC user is locked and if so unlock then try again.
Regards
Ian

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

Queue blocked at the receiver side

Gurus,
I have worked on one scenario i.e file to RFC.My sender is MDM and receiver is BW.Data is easily passing through PI but it's in scheduled status at the BW side.For 500 records,its passing successfully and we can see the output at the BW reports but when we are passing 10K records,its coming in scheduled status i mean the messagae flag is in Green color(sceduled status).I have checked in the Tx SMQR also.Some queues are blocked but its status shows "Running".I can not see any error also.
Can anyone please suggest some way out.
Warm Regards
Veeru

Hi Veeru,
Please try this one
I think there is some issue with the Idoc at R/3 side , R/3 may not release the confirmation idoc to bw server, you or some one from Basis team can manually u2018Processu2019 these idocs at R/3 system then bw loads will process further.
User BD87 t-code and select the yellow request, drill down to end and right click on that and select process option. It will then release Idocs.
Check SM58 : check if the IDocs are stucked up on the t-rfc queue. If so, you can right click and choose Execute LUW to release them.
Please me know if this is doesn't work for you
Cheers
Sukhi

Queues block because of mapping Exception

Hi guys,
I have a scenario in PI 7.0 that makes use of BPM and creates and posts 3 Idocs that are posted to R/3 subsequently. However, when mapping fails in first step of BPM because of an exception, then all subsequent entries in the same queue, are blocked inside the queue.
Do you have any idea how this could be avoided.
My preference would be to have the mapping failing in XI and from SXMB_MONI_BPE to be able to restart all failed BPM's and have all subsequent BPM's successfully executed even if the first one fails.
--Evaggelos

check if this blog helps:
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
for restarting bpm check : SXMB_MONI_BPE->Restart Process After Error
Edited by: Prabhu S on Jan 8, 2008 7:42 AM

Jdbc connection blocks when run from jar

The following code establishes a connection EXCEPT when run from within a jar file:
String jdbcDriverName = "oracle.jdbc.driver.OracleDriver";
String dbConnectionURL = "jdbc:oracle:thin:@192.168.2.7:1521:PRISM";
String userName = "mdo";
String password = "mdpass";
// Load the JDBC driver and create a connection to the database
Class.forName( jdbcDriverName );
OracleDataSource dataSource = new OracleDataSource();
dataSource.setURL( dbConnectionURL );
dataSource.setUser( userName );
dataSource.setPassword( password );
connection = dataSource.getConnection();
When run from a jar file, the application does not execute beyond the line:
connection = dataSource.getConnection();
No exceptions are thrown, it just appears that getConnection never returns.
Do I need to do anything different to execute this code from within a jar file?
Thanks in advance,
Phil
<><

When building the JAR file, I inadvertently included files from two Oracle JDBC driver versions (1.2 and 1.4). I was building a single jar file with all files in it.
I am guessing same named files existed in both driver JARs and caused "confussion" when combined into the single JAR.
Still, I would have expected an exception to be thrown or a null connection to be returned instead if the thread just blocking.
Thanks for all replies,
Phil
<><

SMQ2 - Queue blocked EVENT??

Hi there,
I am working on an SAP XI system and was wondering if anyone knows of a way to catch some sort of EVENT when a queue in SMQ2 gets "blocked"? I have looked for a Business Object but now luck......I know I can possible schedule a background job to "poll" the ARFCASTATE table I think? I think the table is something like that.....
I have also tried to find a user exit / BADI / enhancement spot that I may be able to trigger my own event from.....but no luck yet.....
Any ideas on how this could be done? I want to trigger a workflow when a queue gets blocked......
Thanks for the help
Lynton

You can write your program using this FM QRFC_LOG_CHECK which will check the queue log. Trigger the event using FM SAP_WAPI_CREATE_EVENT or if you want to just to notify someone, the simple Use FM SO_NEW_DOCUMENT_SEND_API1,if there a specific queue log found. Schedule this report on a periodic basis.

SMQ1 & SMQ2 Alerts: Please help set up Queue blocking alterts

Hi ALL
We have been experiencing problems with Queue Failures / Blocked Queue in PROS.
However, we do NOT get this notification as part of Alerts we have set up in ALRTCATDEF.
Can you please, help us with any links on documentation on how to set up SMQ1 & SMQ2 alerts.So, that we get notified via whenever a queue is blocked.
Your help is greatly appreciated!!
Regards,
Patrick

Hi ,
For runtime errors , you can trigger an alert.
I don't think so, it is possible to trigger an alert when message is stuck in Queue, but if you get any error either system error or application error then you can trigger an alert.
For more-
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
If you have got any errors like communication errors because of Queue error, then you can think of configuring CCMS alerts.(i.e alerts for Components)
/people/aravindh.prasanna/blog/2005/12/23/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part--1
also see:
http://help.sap.com/saphelp_nw04s/helpdata/en/b1/ca6c3c32ac8754e10000000a114084/frameset.htm
Re: Event Queue related- events not geting delivered
Regards

Queue Blocking and File picked Partially Problem ?

Hi All,
The File which is placed in FTP server having more 50000 to 65000 rows .
when XI picks the File the Partial Data is processed.
In SXMB_MONI if we check the message we are able to see some rows not full Data which was in file.
it's also blocking the Large message QUEUE -XBTM0000
while processing.
In QUEUE monitoring(SMQ2) the STATUS message is "Connnection CLosed No DATA" .
what could the reason here and also we are not able see any error related information(If it is having error) in SXMB_MONI.
it's urgent because of Production issue.
Regards
Nandan

Hi Indira,
In our scenario the Modification Check is set 5000 .
To resolve this problem what should i must do ?
Whether to decrease the present value or increase the present set value.
what will be the timing parameter Actually in Additional Parameter Tab?( SECONDS or MILLI SECONDS)

Inbound Queue blocked: Parallel and alternative sequences are not supported

Hi,
Just now, I checked the Inbound Queue in SCM system through SMQ2 and found which was blocked by error message "Parallel and alternative sequences are not supported". Could you please tell me what does it mean? How to fix it?
Thanks,
Quanyin Su

Hi Quanyin Su,
Parallel and Alternative sequences are used in routing.
I believe you are trying to CIF PPM/PDS from ECC to APO and you are getting this queue stuck at inbound of APO.
Both the alternative and parallel sequences are supported in APO.
Alternative sequence is used as alternative modes in APO.
I can think of this as a master data issue.
At least one of your work center used in either of the sequences is not available in APO or is not APO relevant.
Could you please check your master data such as all the work centers used and make sure your parallel and alternative sequences are consistent.
Once you made sure that master is available in ECC, you can CIF it to APO by using CURTO_CREATE transaction in ECC.
Please see below link for Routing and its usage in APO:
http://help.sap.com/saphelp_apo/helpdata/en/99/ed3a981d0f11d5b3fc0050dadf0791/content.htm
You also need to activate a BADI in order to sent alternative sequences to APO.
Below thread has all the details regarding this.
Re: /SAPAPO/CURTO 103 : Mode .. is not assigned to an activity
Regards,
Abhay Kapase
Edited by: AbhayKapase on Aug 5, 2011 2:24 PM

JDBC Queue Blocked

Similar Messages

Maybe you are looking for