Messages getting stuck in SMQ2

Messages get stuck in SMQ2 with the Error msg "SQL error on database occurred when accessing a table".
This is happening on PI system 7.11 SP04 with Max DB version 7.7.06.07.
This typically happens when sending messages from one BPM to another although it has more of a random pattern.
A corresponding dump is also seen in ST22.
The dump details are as below:
Runtime error : DBIF_RSQL_SQL_ERROR
Exception : CX_SY_OPEN_SQL_DB
Database error text : Invalid numeric value for parameter/column (10)
Internal call code : "[RSQL/UPDT/SWFRXIHDR ]"
Any help is highly appreciated in resolving this issue.
Regards,
Murali Narayanan

> The dump details are as below:
> Runtime error : DBIF_RSQL_SQL_ERROR
> Exception : CX_SY_OPEN_SQL_DB
> Database error text : Invalid numeric value for parameter/column (10)
I would update the kernel (plus the database interface library lib_dbsl) to the latest patchlevels and try again. If the error persists I'd upgrade the database to the latest patchlevel. If it still doesn't work I'd open an OSS call (BC-DB-SDB).
Markus

Similar Messages

Message getting stuck in SMQ2 for proxy

Hi All,
I am facing one problem in inbound queue of proxy scenario. Some times messages are in scheduled status. In the trace i can see the following message.
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
if i am deleting the entry from SMQ2 and restarting the message will be success.
what may be the reason. Please help me.
Regards
Pradeep P N

Hi ,
One moreThis is happening in R3 system for proxy scenario. not in XI.
Regards
Pradeep P N

Messages getting stuck in QRFC Queue

Hi,
Today I noticed that a message had gotten stuck with the status "Sheduled for Outbound Processing" (scenario IDOC->XI->File), XI 3.0 SP11.
This in turn had the effect that the whole QRFC queue got stuck, and all following messages got stuck with status "Sheduled".
I had to remove the first message from the queue manually so that XI could start to purge the other messages from the queue.
What could be the reason for the first messages getting stuck with this status ("Sheduled for Outbound Processing")?
The message was very small, just a couple of lines. One thing that comes into mind, is that XI received 4 IDOCS for the same interface, within one second. These 4 messages were assigned to different queues, but one of them got stuck. Could there be problems with XI when several messages arrive on the same interface within a very short time?
Is it possible to use Alerts to detect this kind of problem in the future? As I have understood, Alerts only handle XI "errors", but according to XI, this message did not have an "error status", it just had the status "Sheduled for Outbound processing"..
Thanks for any help,
Hans

Hi,
If the message got struck in Queue, you try to activate the queues in smq2 to reprocess the data instead of deleting it. This is the final solution. But you should able to see a dump in ST22 for this problem.
thanks,
sasi

Message getting stuck in XBQO queue - Time limit exceeded

Hi All,
We have a BPM scenario in our project (on PI 7.0 SP18), where bundle of PEXR2002 Payment IDocs are received as a single flat file. This file is then consumed by the BPM, to split the message into multiple payments using Java Mapping.
However, when we get an IDoc file of size greater than 5 MB (more than 500 IDocs), the message gets stuck in XBQO queue and eventually giving a SYSFAIL with the message "Time limit exceeded". Could you please let us know if you have encountered a similar issue and are aware of a possible solution.
Any pointers to this will be really appreciated.
Thanks & Regards,
ROSIE SASIDHARAN

H Rosie,
1) Goto SXMB_ADM-> Integration Engine Configuration->Parameter EO_MSG_SIZE_LIMIT->possible values 0 - 2,097,151 (KB)
The parameter EO_MSG_SIZE_LIMIT enables serial processing of messages of a particular size. This applies for messages with the quality of service Exactly Once (EO). If the message is larger than the parameter value, the message is processed in a separate queue.
2) Goto SXMB_ADM-> Integration Engine Configuration->Parameter HTTP_TIMEOUT->possible values n Seconds, where n is a whole number.
The parameter Specifies the timeout for HTTP connections (time between two data packages at line level). This value overrides the system profile parameter icm/server_port_n (for example, icm/server_port_0 : PROT=HTTP, PORT=50044, TIMEOUT=900). If you do not set the parameter HTTP_TIMEOUT or if you set the parameter to 0, then the setting for the system profile parameter is used.
See SAP Note 335162 for sysfail issue....
Hope these will help u....
Regds,
Pinangshuk.

Messages getting stuck in tcp_local Channel

Hi All
Version
Sun Java(tm) System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004)
libimta.so 6.1 HotFix 0.01 (built 12:52:04, Jun 24 2004)
SunOS dakota 5.9 Generic_112233-12 sun4u sparc SUNW,Sun-Fire-V440
Background
In the last week we've been experiencing problems with outgoing messages getting stuck in our tcp_local channel. They can stay for up to 4 hours before dequeuing. We plan to install Patch 116568 which is the latest core patch for our version of the Messaging Server.
To date we haven't experienced any DNS problems and have not made any configuration changes.
However I was just wondering if anyone had come across this type of problem before? We're hoping the patch will resolve the issue but would be interested in other alternatives.
Thanks in advance
Paul

You'll have to do more research before I can offer help. . .
It's not unusual for some messages to be retried, and depending on the destination, that may take a while.
Some outside domains are always slow. If you have many messages queued for such outside domains, they can involve the whole server, and cause mails to queue up behind them.
Many installations create a new channel, such as, "tcp_slow", and use rewrite rules to move messages addressed to these domains (aol, hotmail, earthlink, etc.) into this separate channel. You can "tune" that channel differently, and messages there won't block tcp_local.

Messages are stuck in SMQ2

Hi,
Our messages are stuck in SMQ2, and I think this is due to high volume of messages. I have configured the IS to allow the QRF_RESTART_ALLOWED to 1, and scheduled the RSQIWKEX job to run periodically. But, the messages are still stuck in SMQ2.
Does anyone know what are the next steps we should look into to solve this problem?
Any help is greatly appreciated.
Thanks,
Karma

Just try - go to SXMB_ADM->Manage Queues and Deregister all the Queues. Then go to SMQ2 and try to activate all the queues by selecting the each lines and with activate button.
Then re-register the queues in SXMB_ADM and chek it..
Problem may be because of workprocess related. Also check transaction ST22 for if any dump in XI box.
btw what is the scenario ? Is it because of huge message processing ?
Regards,
Moorthy

From time to time, my outgoing mail messages get stuck in the "outbox". I'm having trouble resolving the problem.

From time to time, my outgoing mail messages get stuck in the "outbox". I'm having trouble resolving the problem.

I use Comcast. My computer (Mac Air) also uses my iCloud and Me accounts. The message I get back says they are all offline.

Messages gets stuck up in active state

Hi ,
In our production environment, we are facing strange issues for the past 1 week.
Issue 1:
Messages gets stuck up in active state. In our message tracking mechanism ,the status is successfully sent to destination party. The message should not hold up in active state in first place?
If we restart the Host instance, it is creating duplicate and processing it which is creating misssing ICR issue.
Per day message flow-200 messages
Please suggest ?
Kind Regards,
Giri.a
girishkumar.a

Hi Girish,
I believe OFTP adapter is not native adapter(in box) for BizTalk Server.
So, is there any logging mechanism in OFTP adapter?
Also, can we connect to the FTP server using some other tool like Filezilla etc. If other 3rd party products are also not able to connect to this server then we can say that its not a BizTalk issue.
Thanks,
Prashant
Please mark this post accordingly if it answers your query or is helpful.

Proxy messages are stucked in SMQ2.Can I pass these msgs in separate queue?

Hi Guys,
File >PI>ABAP proxy. (ECC)
Once i pick and process the file, the resultant message is updating the table in ECC through ABAP proxy. These messages are high priority and they should not stuck in the queues in ECC.
The problem is some of the messages of this interface are getting stucked in queues (SMQ2) by colliding with other low priority messages which are failed due to some data issues.
Is there any way I can separate these high priority messages into separate custom queue and process them?
Do I need to this in ECC or PI?
Thanks
Deepthi

Hi,
As Debashis has already said, use message prioritization in PI to handle your requirement.
For SAP NetWeaver PI 7.0, navigate to SAP NetWeaver 7.0  SAP NetWeaver 7.0 Library  SAP NetWeaver Library  SAP NetWeaver by Key Capability  Process Integration by Key Capability  SAP NetWeaver Exchange Infrastructure  Runtime  Integration Engine  Prioritized Message Processing.
For SAP NetWeaver PI 7.1 (including EHP 1), navigate to SAP NetWeaver  SAP NetWeaver PI/Mobile/IdM 7.1  SAP NetWeaver Process Integration 7.1 Including Enhancement Package 1  SAP NetWeaver Process Integration Library  Function-Oriented View  Process Integration  Integration Engine  Prioritized Message Processing.
For more details about message prioritization within the Advanced Adapter Engine, please refer to SAP Help Portal http://help.sap.com, and navigate to SAP NetWeaver  SAP NetWeaver PI/Mobile/IdM 7.1  SAP NetWeaver Process Integration 7.1 Including Enhancement Package 1  SAP NetWeaver Process Integration Library  Function-Oriented View  Process Integration  Process Integration Monitoring  Component Monitoring  Prioritizing the Processing of Messages.

Messages getting scheduled in SAP ECC Box:Messages getting stuck in Inbound

The scenario is -
JDBC Sender-->> SAP PI-->> ECC Server(via ABAP proxy)
The Interface is running properly in SAP PI & then the messages are getting posted to the Inbound queues in SAP ECC Box. Generally it takes few seconds for the messages to get processed, but now all are getting scheduled in the Inbound queues(in different channels as seen in SMQ2)
We re-ran the interfaces again a few times, but all of them kept getting scheduled. Finally, after 2 hours one of the messages got processed. I suppose we won't face any problem now onwards.
Though I can see several suggestions like registering the queues & assigning dedicated queues to the interface, none of the blog suggest the probable cause of the event?
Can this be due to some issue in the server(heavy pressure of data in the server during the period/issue in the queues??)
I found the following links regarding issues like these --
XML file getting stucked in queue in ECC
Message in scheduled state
Thanks

Is the printing issue with one specific printer or across system.
What method you have configured for output device.
There should be any issue if you add spool work process to Application server.
Then you should be able to configure spool server load balancing. (Search on help.sap.com for spool load balancing)

Proxy messages are stucked in SMQ2 as scheduled status

Hi,
I am doing File(FCC) >PI 7.0>ABAP proxy. (ECC) Scenario.
Once i pick and process the file, the resultant message is updating the table in ECC through ABAP proxy. These messages are getting stucked in queues (SMQ2) in ECC. My message is not having much data , it is very less in size.
And there is no messages in Queue.
I register all queues in SMQR in PI and ECC.
Does I need to do any activity in ECC or PI? What could be a problem. Please suggest .
Thanks
Ayub

Hi Venkata,
Thanks for very quick replay.
Are the messages stuck with any error?--> First I can see the Green Color Flag as scheduled status, I open the message I can see there is no error message.Bt when I have look at end of the message in SXMB_MONI at Q.Status , I can see Message Has error
In SMQ2 -->
Cl. Queue Name               Entries    Status   Date 1     Time 1   NxtDate           NxtTim                  Sender ID                        Wait for queue
200 XBTR0009                         1 SYSFAIL 24.02.2012 10:53:34 24.02.2012 10:53:34      R3DEVQA_RDV_01
And when I double click the XBTR009 I can see the below message :
Cl.       User                  Function Module                 Queue Name                Date        Time                       StatusText
200 ALEREMOTE    SXMS_ASYNC_EXEC                 XBTR0009                  24.02.2012 10:53:34 Screen output without connection to user.
This are status of the messages. Please help me.
Regards,
Ahmed

Messages getting stuck in Queue

Hi All,
In my scenario data is coming from database into XI and creating a file in SAP. The messages are getting stuck in the Queue and in message monitoring the status is showing as 'waiting'. Earlier the messages were getting successfully processed but system was running slow for the past two days. Is this because of system speed or some data issue?
For testing pupose I have deleted the old messages from Smq2 and tried but every new message is getting stuck in the queue. Please suggest.
Thanks,
Aparna

Please check the following blog :
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
try cancelling oldest messages, this should unblock queue
Regards,
Jamal

3 Messages getting struck in SMQ2 at same time with difference in seconds

Hi all,
Three EOIO messages with Queue name QBTJ.......................(same Queue id for 3days)
that is day1 QBTJ(message (a) queue id=day2 QBTJ queue id=day3 QBTJ queue id
day1 QBTJ(message (b) queue id=day2 QBTJ queue id=day3 QBTJ queue id
day1 QBTJ(message (c) queue id=day2 QBTJ queue id=day3 QBTJ queue id
.These are getting struck in smq2 at same times (compared the timings 3 days).the time at which these messages are getting struck are same with the difference in seconds.
Other than these 3 different times ,these messages are moving with out strucking in SMQ2.
I have two questions here
1)what could be the reason for only these three messages are getting struck in smq2
2)is there any parameter which could be set in SXMB_ABMIN to unlock the queue automatically with out going to smq2 and manually unlocking.
Please do not send nonrelavent blogs
Thanks,
Srinivasa

Hello,
you can schedule the report RSQIWKEX in your XI system. This report does automatically unlock all queues.
See the blog for more details.
regards,
Björn

Email messages getting stuck in Outbox

I have regular problems with my sent emails getting stuck in my Outbox when using verizon.net mail. The problem only occurs with verizon.net and only on my tablet (Nexus 7), not on my PC. Both are on same wireless network so I don't think it is due to interruption in connection. Is there some adjustment I need to make?

Gmail is a deliberately broken implementation of IMAP that often causes problems with Mail. The problem seems to have gotten worse in Mavericks. Google has no incentive to make Gmail work well with any mail client, because the company makes money by delivering targeted ads via the Web. The Gmail servers analyze your messages to gather information about you and your contacts that Google can then sell to marketers, or to anyone who will pay for it. You agreed to those terms when you registered a Gmail address. The marketers—not Gmail users—are Google's customers and the ones it aims to please.
I suggest either not to use Gmail at all, or to access it through the website as Google intends. You might get better results with another email client. I don't recommend any one in particular.
If you insist on trying to make Gmail work with Mail, the following links may help:
Configuring OS X Mail For Gmail Without Duplicates
Setting up Apple Mail to Rock and Roll with Gmail
Apple Mail and Gmail Part Deux

JMS Messages getting stuck in queues

Hi,
I am facing this peculiar issue with queue messages not getting picked up.
Application Architecture: There is 1 JMS queue ( which resides in WLDomain1 with in a Unix Box) and there are 2 windows boxes having 2 weblogic domains each with 3 instances of MDB deployed on each of the domains. So total of 12 consumers (2 Box * 2 Domain * 3 Instances of MDB) listens to the JMS queue.
Issue: After bringing everything up I am able to see 12 consumer count listening to the queue. But when I run the application which writes total of 13 messages in the queue only 7 of them are getting processed and 6 messages are always getting stuck in the queues. Interestingly this 7 messages are mostly getting processed by consumers with in the same windows box. And the selection of windows box is completely random. To confirm whether both the windows boxes are configured fine I tried to test them individually and it works fine individually, the problem happens only if I bring up both the boxes together.
Another observation is, if I bring down the non working domains, the pending messages start getting processed by the working domains. It gives an impression that the non working domains seem to lock the messages for processing but doesn't actually process it. Only when I bring down the domains it releases this lock.
Below is the JMS Life cycle events I captured from log files :
1. Start domain1 in WIN Box1
####<Nov 24, 2009 7:54:00 PM CST> <> <> <1259114040304> <783400> <> <> <JMSModule!Queue> <ConsumerCreate> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection59.session60.consumer62)> <> <>
####<Nov 24, 2009 7:54:00 PM CST> <> <> <1259114040309> <239900> <> <> <JMSModule!Queue> <ConsumerCreate> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection59.session63.consumer65)> <> <>
####<Nov 24, 2009 7:54:00 PM CST> <> <> <1259114040313> <2100> <> <> <JMSModule!Queue> <ConsumerCreate> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection59.session66.consumer68)> <> <>
2. Start domain2 in WIN Box 1
####<Nov 24, 2009 7:54:55 PM CST> <> <> <1259114095403> <38600> <> <> <JMSModule!Queue> <ConsumerCreate> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection69.session70.consumer72)> <> <>
####<Nov 24, 2009 7:54:55 PM CST> <> <> <1259114095407> <335400> <> <> <JMSModule!Queue> <ConsumerCreate> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection69.session73.consumer75)> <> <>
####<Nov 24, 2009 7:54:55 PM CST> <> <> <1259114095410> <997700> <> <> <JMSModule!Queue> <ConsumerCreate> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection69.session76.consumer78)> <> <>
3. Start domain1 in WIN Box 2
####<Nov 24, 2009 7:56:12 PM CST> <> <> <1259114172061> <316500> <> <> <JMSModule!Queue> <ConsumerCreate> <<anonymous>> <MC:CA(/<IP_BOX2>):OAMI(server.jms.connection79.session80.consumer82)> <> <>
####<Nov 24, 2009 7:56:12 PM CST> <> <> <1259114172066> <324300> <> <> <JMSModule!Queue> <ConsumerCreate> <<anonymous>> <MC:CA(/<IP_BOX2>):OAMI(server.jms.connection79.session83.consumer85)> <> <>
####<Nov 24, 2009 7:56:12 PM CST> <> <> <1259114172072> <757000> <> <> <JMSModule!Queue> <ConsumerCreate> <<anonymous>> <MC:CA(/<IP_BOX2>):OAMI(server.jms.connection79.session86.consumer88)> <> <>
4. Start domain2 in WIN Box 2
####<Nov 24, 2009 7:56:54 PM CST> <> <> <1259114214000> <142800> <> <> <JMSModule!Queue> <ConsumerCreate> <<anonymous>> <MC:CA(/<IP_BOX2>):OAMI(server.jms.connection89.session90.consumer92)> <> <>
####<Nov 24, 2009 7:56:54 PM CST> <> <> <1259114214005> <38200> <> <> <JMSModule!Queue> <ConsumerCreate> <<anonymous>> <MC:CA(/<IP_BOX2>):OAMI(server.jms.connection89.session93.consumer95)> <> <>
####<Nov 24, 2009 7:56:54 PM CST> <> <> <1259114214009> <22400> <> <> <JMSModule!Queue> <ConsumerCreate> <<anonymous>> <MC:CA(/<IP_BOX2>):OAMI(server.jms.connection89.session96.consumer98)> <> <>
At this point console shows 12 consumers listening the queue which is absolutely fine.
5. Run application
--Message Production
This produces 13 messages ( I have not pasted the complete log)
-- Message Consumption ( Only 7 messages are consumed)
####<Nov 24, 2009 8:00:05 PM CST> <> <> <1259114405953> <576400> <ID:<1047832.1259114392542.0>> <> <JMSModule!Queue> <Consumed> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection59.session63.consumer65)> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSTimestamp>1259114392542</mes:JMSTimestamp><mes:Properties/></mes:Header></mes:WLJMSMessage>> <>
####<Nov 24, 2009 8:00:10 PM CST> <> <> <1259114410091> <310100> <ID:<1047832.1259114393181.0>> <> <JMSModule!Queue> <Consumed> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection59.session66.consumer68)> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSTimestamp>1259114393181</mes:JMSTimestamp><mes:Properties/></mes:Header></mes:WLJMSMessage>> <>
####<Nov 24, 2009 8:00:10 PM CST> <> <> <1259114410130> <364600> <ID:<1047832.1259114400626.0>> <> <JMSModule!Queue> <Consumed> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection59.session63.consumer65)> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSTimestamp>1259114400626</mes:JMSTimestamp><mes:Properties/></mes:Header></mes:WLJMSMessage>> <>
####<Nov 24, 2009 8:00:10 PM CST> <> <> <1259114410134> <540700> <ID:<1047832.1259114393125.0>> <> <JMSModule!Queue> <Consumed> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection69.session76.consumer78)> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSTimestamp>1259114393125</mes:JMSTimestamp><mes:Properties/></mes:Header></mes:WLJMSMessage>> <>
####<Nov 24, 2009 8:00:10 PM CST> <> <> <1259114410137> <632400> <ID:<1047832.1259114393128.0>> <> <JMSModule!Queue> <Consumed> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection69.session73.consumer75)> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSTimestamp>1259114393128</mes:JMSTimestamp><mes:Properties/></mes:Header></mes:WLJMSMessage>> <>
####<Nov 24, 2009 8:00:12 PM CST> <> <> <1259114412026> <984200> <ID:<1047832.1259114393123.0>> <> <JMSModule!Queue> <Consumed> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection59.session60.consumer62)> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSTimestamp>1259114393123</mes:JMSTimestamp><mes:Properties/></mes:Header></mes:WLJMSMessage>> <>
####<Nov 24, 2009 8:00:16 PM CST> <> <> <1259114416045> <41800> <ID:<1047832.1259114400005.0>> <> <JMSModule!Queue> <Consumed> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection69.session70.consumer72)> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSTimestamp>1259114400005</mes:JMSTimestamp><mes:Properties/></mes:Header></mes:WLJMSMessage>> <>
6. At this point Admin Consol shows 6 messages pending in the queue
and From consumer numbers it is evident that consumers in WIN Box2 domains have not processed any messages
Now if I stop server in WIN Box2 Domain1, WIN Box1 picks up the messages instantely
####<Nov 24, 2009 8:13:22 PM CST> <> <> <1259115202343> <897600> <> <> <JMSModule!Queue> <ConsumerDestroy> <<anonymous>> <MC:CA(/<IP_BOX2>):OAMI(server.jms.connection79.session80.consumer82)> <> <>
####<Nov 24, 2009 8:13:22 PM CST> <> <> <1259115202346> <421900> <> <> <JMSModule!Queue> <ConsumerDestroy> <<anonymous>> <MC:CA(/<IP_BOX2>):OAMI(server.jms.connection79.session83.consumer85)> <> <>
####<Nov 24, 2009 8:13:22 PM CST> <> <> <1259115202379> <582300> <> <> <JMSModule!Queue> <ConsumerDestroy> <<anonymous>> <MC:CA(/<IP_BOX2>):OAMI(server.jms.connection79.session86.consumer88)> <> <>
####<Nov 24, 2009 8:13:24 PM CST> <> <> <1259115204888> <4600> <ID:<1047832.1259114400029.0>> <> <JMSModule!Queue> <Consumed> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection69.session76.consumer78)> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSTimestamp>1259114400029</mes:JMSTimestamp><mes:Properties/></mes:Header></mes:WLJMSMessage>> <>
####<Nov 24, 2009 8:13:32 PM CST> <> <> <1259115212820> <256700> <ID:<1047832.1259114400258.0>> <> <JMSModule!Queue> <Consumed> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection59.session66.consumer68)> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSTimestamp>1259114400258</mes:JMSTimestamp><mes:Properties/></mes:Header></mes:WLJMSMessage>> <>
####<Nov 24, 2009 8:13:43 PM CST> <> <> <1259115223579> <280600> <ID:<1047832.1259114400032.0>> <> <JMSModule!Queue> <Consumed> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection59.session60.consumer62)> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSTimestamp>1259114400032</mes:JMSTimestamp><mes:Properties/></mes:Header></mes:WLJMSMessage>> <>
7. At this poing Admin Consol shows 3 messages pending in the queue
Now if I stop server in WIN Box2 Domain2, the remaining 3 gets processed
####<Nov 24, 2009 8:16:08 PM CST> <> <> <1259115368998> <193400> <> <> <JMSModule!Queue> <ConsumerDestroy> <<anonymous>> <MC:CA(/<IP_BOX2>):OAMI(server.jms.connection89.session90.consumer92)> <> <>
####<Nov 24, 2009 8:16:08 PM CST> <> <> <1259115369000> <885500> <> <> <JMSModule!Queue> <ConsumerDestroy> <<anonymous>> <MC:CA(/<IP_BOX2>):OAMI(server.jms.connection89.session93.consumer95)> <> <>
####<Nov 24, 2009 8:16:09 PM CST> <> <> <1259115369002> <902500> <> <> <JMSModule!Queue> <ConsumerDestroy> <<anonymous>> <MC:CA(/<IP_BOX2>):OAMI(server.jms.connection89.session96.consumer98)> <> <>
####<Nov 24, 2009 8:16:25 PM CST> <> <> <1259115385151> <123700> <ID:<1047832.1259114400324.0>> <> <JMSModule!Queue> <Consumed> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection69.session70.consumer72)> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSTimestamp>1259114400324</mes:JMSTimestamp><mes:Properties/></mes:Header></mes:WLJMSMessage>> <>
####<Nov 24, 2009 8:16:29 PM CST> <> <> <1259115389660> <836600> <ID:<1047832.1259114400535.0>> <> <JMSModule!Queue> <Consumed> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection59.session63.consumer65)> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSTimestamp>1259114400535</mes:JMSTimestamp><mes:Properties/></mes:Header></mes:WLJMSMessage>> <>
####<Nov 24, 2009 8:16:37 PM CST> <> <> <1259115397823> <610200> <ID:<1047832.1259114400432.0>> <> <JMSModule!Queue> <Consumed> <<anonymous>> <MC:CA(/<IP_BOX1>):OAMI(server.jms.connection69.session73.consumer75)> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSTimestamp>1259114400432</mes:JMSTimestamp><mes:Properties/></mes:Header></mes:WLJMSMessage>> <>
Kindly throw some light on this issue. Also do let me know if you need any more specific details about this.
Thanks,
Abhijeet
Edited by: user5240164 on Nov 25, 2009 11:35 AM
Edited by: user5240164 on Nov 28, 2009 1:21 PM

Hi,
The problem may be conflicting names in your configuration. To ensure proper operation of WL Security, JMS, JTA, and JDBC, make sure that (A) each domain has a unique name, and (B) no two WebLogic servers have the same name (even if in two different domains).
To ensure a more even distribution of messages, either simply send more than a token amount messages (eg, a hundred or so, rather than just 12), or configure a custom connection factory on the domain that hosts the queue, reduce MessagesMaximum on the connection factory to 1, and then modify each MDB to refer to the custom connection factory. The MessagesMaximum setting controls the number of messages that can be pre-pushed (pipelined) to a single asynchronous consumer.
For more information see "Best Practices for JMS Beginners and Advanced Users" in the latest versions of the JMS admin guide, and "JMS Performance & Tuning Check List" in the WebLogic Performance and Tuning guide.
Tom

Messages getting stuck in SMQ2

Similar Messages

Maybe you are looking for