Re: 1000 messages left in the queue

Sounds like your producer is doing a transactional lock on the write, like it is waiting for a session.commit() on it. What is the structure (environment) of your producer?

Ok... these are the instance variables & imports of mention...
import com.sun.messaging.jms.Session;
import javax.jms.*;
import javax.naming.NamingException;
import java.io.IOException;
import java.io.Serializable;
import java.util.Enumeration;
private Queue queue;
private QueueSender sender;
private QueueReceiver receiver;
private QueueConnection connection;
private QueueSession session;

Similar Messages

  • QueueBrowser doesn't work when messages are in the queue

    We are attempting to list off the messages in a JMQ 2.0 queue while our application is running. The code currently creates a new Connection & Session and then a new QueueBrowser on each queue. Following that, we get an Enumeration of the messages in the queue and print them out.
    When no messages are in the queue, this approach works fine and prints out all the relevent information. However, when a message is in the queue, the QueueBrowser just hangs. I've tried on transacted and non transacted QueueSessions and the same thing happens.
    Is this known behavior and is it possible to work around it?
    Thanks,
    Mike

    Try restarting the Mac with the ethernet cable plugged in and with a live device attached ('live device' = another Mac, a modem, a printer, or a hub/switch/router, which has been powered on).

  • Messages stuck in the queue... how do I make them to be processed again?

    Hi,
    I'm new to SAP PI and kinda confused with queues.
    I have file -> bpm -> file scenario and there was an error in mapping within bpm process.
    When I went to qRFC Monitor (smq2), I see that in XBQO$PE_WS90000002 queue,
    there's an error, 'Permanent error in BPE inbound processing'... which is expected.
    Now, I run the interface scenario again several times but they don't get processed
    but stuck in the same queue. At this stage, I didn't know what to do...
    I thought by deleting the error message, other messages will be processed...
    I deleted the error message but the other messages are still in the queue...
    I have two questoins.
    1. What is the best way to handle an error in the queue... can I just delete it? or is there a better way to handle an error in the queue?
    2. After deleting the queue, what should I do to make the other messages to be processed again...
    Thank you.
    -Won

    Hi Won,
    There are programs for restarting the LUW entries:
    programs
    · RSARFCRD: tRFC Monitor (transaction SM58)
    · RSARFCSE: Restart an LUW (background job)
    · RSARFCEX: Restart tRFC LUWs (background job)
    · RSQOWKEX: Restart QOUT qRFC LUWs
    · RSQIWKEX: Restart QIN qRFC LUWs
    · RSARFCSE: Delete an LUW (background job)
    · RSARFCER: Delete various LUWs
    Also, check the url:
    http://help.sap.com/saphelp_nw04/helpdata/en/25/bcfa40badbf46fe10000000a1550b0/content.htm
    Hope this helps.
    Regards,
    Sushama

  • Message processing in the queue for long time

    Hello All,
    We are executing a file to Idoc scenario. The mapping is very complex.
    The file to be processed is of size 125kb size. Which generates around 450 Idocs.
    The file is picked by the adapter engine in hardly a minute.
    But I see the message taking 6 hours to process in the Queue.
    (SMQ2)
    Is there a way I can improve and speed up the Queue processing.

    Hi,
    >message taking 6 hours to process in the Queue.
    It should not happen,
    Check whether all the Queue are Registered.
    /people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/59e837d3-0201-0010-c096-dc1869733413
    Regards
    Agasthuri Doss

  • Messages waiting in the queue for long time.

    Hi Experts,
    We are having some Production issue - messages were waiting in the queue for long time and we found the errors in defaultTrace.12.trc file -
    Please help how to solve this issue its production and we need to move forward and solve this issue asap.
    XI AF API call failed. Module exception: (No information available). Cause Ex
    ception: 'JDBC Adapter configuration not initialized: null'.
    Thrown:
    com.sap.aii.af.service.api.AFException: XI AF API call failed. Module exception: (No information available). Cause Exception: 'JDBC Adapter configuration not
    initialized: null'.
            at com.sap.aii.af.service.api.AdapterAccess.sendMsg(AdapterAccess.java:214)
            at com.sap.aii.af.service.api.AdapterAccess.call(AdapterAccess.java:99)
            at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.process(AdapterProxyLocal.java:87)
            at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.call(SystemAccessorInternal.java:47)
            at com.sap.aii.mapping.lookup.SystemAccessor.call(SystemAccessor.java:115)
            at com.sony.pi.sp.StoredProceduresHandler.runScalarStoredProcedure(StoredProceduresHandler.java:86)
            at com.sap.xi.tf._MyPage_Invoice_SAP_to_Loyalty_MM_.invokePROC_CUSTOMER_DEDUP$(_MyPage_Invoice_SAP_to_Loyalty_MM_.java:1272)
            at sun.reflect.GeneratedMethodAccessor384.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:324)
            at com.sap.aii.mappingtool.tf3.rt.C2CFunctionWrapper.cacheContext(C2CFunctionWrapper.java:91)
            at com.sap.aii.mappingtool.tf3.rt.C2CFunctionWrapper.gotoNextContext(C2CFunctionWrapper.java:44)
            at com.sap.aii.mappingtool.tf3.rt.Q2QFunctionWrapper.cacheQueue(Q2QFunctionWrapper.java:86)
            at com.sap.aii.mappingtool.tf3.rt.Q2QFunctionWrapper.gotoNextContext(Q2QFunctionWrapper.java:41)
            at com.sap.aii.mappingtool.tf3.rt.Q2QFunctionWrapper.cacheQueue(Q2QFunctionWrapper.java:74)
            at com.sap.aii.mappingtool.tf3.rt.Q2QFunctionWrapper.gotoNextContext(Q2QFunctionWrapper.java:41)
            at com.sap.aii.mappingtool.flib3.CollapseContexts.gotoNextValue(CollapseContexts.java:52)
            at com.sap.aii.mappingtool.flib3.CollapseContexts.gotoNextContext(CollapseContexts.java:37)
            at com.sap.aii.mappingtool.tf3.rt.AResIterator.gotoNextContext(AResIterator.java:37)
            at com.sap.aii.mappingtool.tf3.rt.FunctionWrapper.gotoNextContext(FunctionWrapper.java:37)
            at com.sap.aii.mappingtool.flib3.IfWithoutElse.gotoNextContext(IfWithoutElse.java:58)
            at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:266)
            at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:326)
            at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:326)
            at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:415)
            at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:142)
            at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:118)
            at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64)
            at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92)
            at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90)
            at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95)
            at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68)

    Hi All,
    CPACache refresh worked for one day and the same problem repeated again next day, but need to have parmanent fix and should know the root cause of the problem so that the problem can not be repeated again.
    Is there any solution other than  CPACache refresh and JDBC adapter stop and start to fix the issue.
    And also found some entries in SM12 lock entry list during the same schedule time when the messages was triggered and remains for long time. Let me know whether we can delete those locks ?
    user PIAFUSER
    Lock mode E
    and table SXMSPMAST
    with lock argument ......
    Any suggestions and tips help us alot in fixing this issue.
    Thanks in advance
    Gary.

  • JMS has messages pending in the queue

    Hi, I created a JMS queue to hold some messages, then two message driven bean each take a message from the queue and use JavaMail API 1.2 to send an email out. But somehow, after a while, say, a couple of weeks, there will be about 20 messages pending the queue causing the queue hanging forever. Does anybody know what cause this JMS queue pending? Or is there anything wrong with this design? Thank you very much.

    No, Acknowledgement is sending successfully, no excpeption is raising, in finally it is got acknowledged.
    here is code block,
    public void sendObject(Serializable message) throws JMSException
    try {
    HelperMethods.logDebugMessage("begin sendObject " + System.currentTimeMillis(),
    this.getClass().getName(), "sendObject");
    ObjectMessage objectMessage = getQueueSession().createObjectMessage();
    objectMessage.clearBody();
    objectMessage.setObject(message);
    getQueueSender().send(objectMessage);
    HelperMethods.logDebugMessage("sent sendObject " +System.currentTimeMillis(),
    this.getClass().getName(), "sendObject");
    getQueueSession().commit();
    catch (Exception e) {
    HelperMethods.logDebugMessage("Exception" + e.getMessage(),
    this.getClass().getName(), "sendObject");
    throw new JMSException(e.getMessage());
    public void onMessage(Message message) {
    ObjectMessage objectMessage = (ObjectMessage) message;
    AttachmentFileUtil attachUtil = new AttachmentFileUtil();
    try {
    HelperMethods.logDebugMessage("received write sendObject msg " +
    System.currentTimeMillis(),
    this.getClass().getName(), "onMessage");
    if (message instanceof ObjectMessage) {
    HelperMethods.logDebugMessage("about to process write sendObject msg " +
    System.currentTimeMillis(),
    this.getClass().getName(), "onMessage");
    AttachmentInfoBean attachment = (AttachmentInfoBean)
    objectMessage.getObject();
    HelperMethods.logDebugMessage("processed the write sendObject msg " +
    System.currentTimeMillis(),
    this.getClass().getName(), "onMessage");
    HelperMethods.logDebugMessage("writing the sendObject msg to disk " +
    System.currentTimeMillis(),
    this.getClass().getName(), "onMessage");
    // Here we are calling attachment bean, which uploads the file into file server
         attachUtil.writeContents(attachment);
         HelperMethods.logDebugMessage("After writing the sendObject msg to disk ",
                                                           this.getClass().getName(), "onMessage");
              HelperMethods.logDebugMessage("After Commiting Session " +
                        System.currentTimeMillis(),
                        this.getClass().getName(), "onMessage");
    HelperMethods.logDebugMessage(
    "finished writing the sendObject msg to disk " +
    System.currentTimeMillis(), this.getClass().getName(), "onMessage");
    else {
    HelperMethods.logDebugMessage(
    "oops! no ObjectMessage was received" +
    message.getClass(), this.getClass().getName(), "onMessage");
    throw new NowException("not an ObjectMessage was received" +
    message.getClass());
    catch (Exception ex) {
    ex.printStackTrace();
    HelperMethods.logDebugMessage("Exception" + ex.getMessage(),
    this.getClass().getName(), "onMessage");
    finally {
    try {
    HelperMethods.logDebugMessage("acknowledging the message",
    this.getClass().getName(), "onMessage");
    objectMessage.acknowledge();
    catch (JMSException ex) {
    ex.printStackTrace();
    HelperMethods.logDebugMessage("JMSException" + ex.getMessage(),
    this.getClass().getName(), "onMessage");
    This is my production problem, please suggest me ASAP.
    Regards,
    Murthy Patnaik

  • Need to raise an Alert for huge Volume of messages struck in the queue

    Dear All,
    I have a query which is mentioned below.
    The Partners send huge number of volume of messages at a time to PI Server and due to this reason,the messages are getting struck up in the inbound/outbound queue.Everytime the user manually check for the struck up messages and reprocess it.
    Example: One Partner sends  50,000 number of ORDERS at a time.
    Now an alert needs to be raised for those messages which  got struck up ( i.e. messages on hold and "not failed") in the queue.
    Please share your inputs /suggestion.
    Warm Regards
    B.Dheepa

    Hi,
    Else you can implement the Logic in this blog
    XI :  How to Re-Process failed XI Messages Automatically
    You can Schedule the Strandard Reports to release  automatically the Strucked messages in Queues
    Regards
    Seshagiri

  • Acknowledging individual message, leaving others in the queue

    Hi,
    I am trying to find a way to acknowledge some messages while leaving others on the queue but when I do call m.acknowledge() on the message I want to ack all the messages previously received are removed from the queue. I have read the doc and it seems to me like what I want to do is not possible, hence my post :/
    The scenario is:
    1. I have 2 messages on a queue
    2. I receive message 1 and decide to keep it on the queue
    3. I receive message 2, process it and acknowledge it
    4. Both messages have been removed from the queue
    Do you know how I could achieve the following behaviour:
    1. I have 2 messages on a queue
    2. I receive message 1 and decide to keep it on the queue
    3. I receive message 2, process it and acknowledge it
    4. Only message 1 is left on the queue
    Thanks a lot,
    Mickael

    The behavior you are seeing is expected by JMS specification for javax.jms.Message.acknowledge().
    Have you looked at MQ's com.sun.messaging.jms.Message.acknowledgeThisMessage() ?

  • Backing Up and Restoring the Message Store v.s. the queue

    Hello,
    We are running iPlanet 5.2 Messaging Server and need to migrate to another (duplicate) 5.2 Messaging Server. We have all the software installed and the LDAP user accounts created. Now we just need to move the existing mail from one server to the other.
    I found the Backing Up and Restoring the Message Store section in the Admin Guide says to back up and restore your data, Messaging Server provides the imsbackup and imsrestore utilities.
    However I am wondering about the Queue?
    Under <instance>/imta/queue
    What is the difference between the Message Store
    and the Queue? Can I just backup and restore the Queue using tar or cpio?
    Thanks in advance for any advice.
    Regards,
    Tim

    Hello,
    We are running iPlanet 5.2 Messaging Server and need
    to migrate to another (duplicate) 5.2 Messaging
    Server. We have all the software installed and the
    LDAP user accounts created. Now we just need to move
    the existing mail from one server to the other.
    I found the Backing Up and Restoring the Message
    Store section in the Admin Guide says to back up and
    restore your data, Messaging Server provides the
    imsbackup and imsrestore utilities.
    However I am wondering about the Queue?
    Under <instance>/imta/queue
    What is the difference between the Message Store
    and the Queue? The Message Store is where messages get delivered to, so you can read them.'
    The queue is where messages are temporarily stored, pending delivery to wherever they go.
    You can use tar, cpio, or what have you for the queue. Stop the server first. . .
    You then just restore the files to the new server. No need to restart or anything like that. Just dump the files in, and run
    imsimta cache -sync
    to tell the MTA to re-read the queue.
    Can I just backup and restore the
    Queue using tar or cpio?
    Thanks in advance for any advice.
    Regards,
    Tim

  • MQ Adapter does not clear the rejected message from the queue

    Hi All,
    I'm using a MQ Adapter to fetch the message from the queue without any Backout queue configured. However, whenever there is any bad structured message found in the queue, MQ adapter rejects the message and moves the message to the rejmsg folder but does not clear it off the queue, as a result of which it keeps retrying the same hence, filling the logs and the physical memory. Somehow we do not have any backout queue configured so I can move the message to blackout queue. I have tried configuring the jca retry properties and global jca retry as well but to no avail.
    - Is it not the default behaviour of MQ Adapter to remove the rejected message from the queue irrespective of Backout queue is configured or not? The same behaviour working well with the JMS and File Adapter though.
    - Is there any way I can make MQ Adapter delete the message from that queue once it is rejected?
    Regards,
    Neeraj Sehgal

    Hi Jayson,
    Check this URL which answers a problem with com.sap.engine.boot.loader.ResourceMultiParentClassLoader problem:
    http://209.85.175.132/search?q=cache:RnFZ9viwuKkJ:https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.sap.sdn.folder.sdn!2fcom.sap.sdn.folder.application!2fcom.sap.sdn.folder.roles!2fcom.sap.sdn.folder.navigationroles!2fcom.sap.sdn.role.anonymous!2fcom.sap.sdn.tln.workset.forums!2fforumtest!2fcom.sap.sdn.app.iview.forumthread%3FQuickLink%3Dthread%26tstart%3D45%26threadID%3D1020700+com.sap.engine.boot.loader.ResourceMultiParentClassLoader&hl=en&ct=clnk&cd=3&gl=in&client=firefox-a
    Please check that the JDK compliance level is at 5.0
    Window->Preferences->Java->Compiler->Compiler compliance level set this to 5.0
    Set the installed JRE to the one you have mentioned JDK 5.0 update 16
    Window->Preferences->Java->Installed JRE's->
    Click on the add button to select the path of your JDK.
    once completed click on the check box next to it.
    regards,
    AKD

  • What is the consequence if I delete the BDoc Messages from the Queue?

    Hi,
    What is the consequence if I delete the BDoc Message (SMW01) from the queue with any state (e.g. intermediate)?
    Regards,
    Alex.

    Hi Alex.
    I had a similar issue with Bdoc. We have had a lot of errors comming through as our CRM & ECC syste were out of sync.
    You need to look into the exact error message before you delete a Bdoc. I would suggest that you do not delete any Bdoc message unless you are sure of the error is and it is fixed.
    Hope this helps
    Mohammed.
    Edited by: Mohammed Faisal on Jun 2, 2010 4:43 PM

  • 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)> <&lt;?xml version="1.0" encoding="UTF-8"?&gt;
    &lt;mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"&gt;&lt;mes:Header&gt;&lt;mes:JMSTimestamp&gt;1259114392542&lt;/mes:JMSTimestamp&gt;&lt;mes:Properties/&gt;&lt;/mes:Header&gt;&lt;/mes:WLJMSMessage&gt;> <>
    ####<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)> <&lt;?xml version="1.0" encoding="UTF-8"?&gt;
    &lt;mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"&gt;&lt;mes:Header&gt;&lt;mes:JMSTimestamp&gt;1259114393181&lt;/mes:JMSTimestamp&gt;&lt;mes:Properties/&gt;&lt;/mes:Header&gt;&lt;/mes:WLJMSMessage&gt;> <>
    ####<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)> <&lt;?xml version="1.0" encoding="UTF-8"?&gt;
    &lt;mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"&gt;&lt;mes:Header&gt;&lt;mes:JMSTimestamp&gt;1259114400626&lt;/mes:JMSTimestamp&gt;&lt;mes:Properties/&gt;&lt;/mes:Header&gt;&lt;/mes:WLJMSMessage&gt;> <>
    ####<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)> <&lt;?xml version="1.0" encoding="UTF-8"?&gt;
    &lt;mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"&gt;&lt;mes:Header&gt;&lt;mes:JMSTimestamp&gt;1259114393125&lt;/mes:JMSTimestamp&gt;&lt;mes:Properties/&gt;&lt;/mes:Header&gt;&lt;/mes:WLJMSMessage&gt;> <>
    ####<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)> <&lt;?xml version="1.0" encoding="UTF-8"?&gt;
    &lt;mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"&gt;&lt;mes:Header&gt;&lt;mes:JMSTimestamp&gt;1259114393128&lt;/mes:JMSTimestamp&gt;&lt;mes:Properties/&gt;&lt;/mes:Header&gt;&lt;/mes:WLJMSMessage&gt;> <>
    ####<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)> <&lt;?xml version="1.0" encoding="UTF-8"?&gt;
    &lt;mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"&gt;&lt;mes:Header&gt;&lt;mes:JMSTimestamp&gt;1259114393123&lt;/mes:JMSTimestamp&gt;&lt;mes:Properties/&gt;&lt;/mes:Header&gt;&lt;/mes:WLJMSMessage&gt;> <>
    ####<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)> <&lt;?xml version="1.0" encoding="UTF-8"?&gt;
    &lt;mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"&gt;&lt;mes:Header&gt;&lt;mes:JMSTimestamp&gt;1259114400005&lt;/mes:JMSTimestamp&gt;&lt;mes:Properties/&gt;&lt;/mes:Header&gt;&lt;/mes:WLJMSMessage&gt;> <>
    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)> <&lt;?xml version="1.0" encoding="UTF-8"?&gt;
    &lt;mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"&gt;&lt;mes:Header&gt;&lt;mes:JMSTimestamp&gt;1259114400029&lt;/mes:JMSTimestamp&gt;&lt;mes:Properties/&gt;&lt;/mes:Header&gt;&lt;/mes:WLJMSMessage&gt;> <>
    ####<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)> <&lt;?xml version="1.0" encoding="UTF-8"?&gt;
    &lt;mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"&gt;&lt;mes:Header&gt;&lt;mes:JMSTimestamp&gt;1259114400258&lt;/mes:JMSTimestamp&gt;&lt;mes:Properties/&gt;&lt;/mes:Header&gt;&lt;/mes:WLJMSMessage&gt;> <>
    ####<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)> <&lt;?xml version="1.0" encoding="UTF-8"?&gt;
    &lt;mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"&gt;&lt;mes:Header&gt;&lt;mes:JMSTimestamp&gt;1259114400032&lt;/mes:JMSTimestamp&gt;&lt;mes:Properties/&gt;&lt;/mes:Header&gt;&lt;/mes:WLJMSMessage&gt;> <>
    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)> <&lt;?xml version="1.0" encoding="UTF-8"?&gt;
    &lt;mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"&gt;&lt;mes:Header&gt;&lt;mes:JMSTimestamp&gt;1259114400324&lt;/mes:JMSTimestamp&gt;&lt;mes:Properties/&gt;&lt;/mes:Header&gt;&lt;/mes:WLJMSMessage&gt;> <>
    ####<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)> <&lt;?xml version="1.0" encoding="UTF-8"?&gt;
    &lt;mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"&gt;&lt;mes:Header&gt;&lt;mes:JMSTimestamp&gt;1259114400535&lt;/mes:JMSTimestamp&gt;&lt;mes:Properties/&gt;&lt;/mes:Header&gt;&lt;/mes:WLJMSMessage&gt;> <>
    ####<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)> <&lt;?xml version="1.0" encoding="UTF-8"?&gt;
    &lt;mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"&gt;&lt;mes:Header&gt;&lt;mes:JMSTimestamp&gt;1259114400432&lt;/mes:JMSTimestamp&gt;&lt;mes:Properties/&gt;&lt;/mes:Header&gt;&lt;/mes:WLJMSMessage&gt;> <>
    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

  • TNEF Issue - Winmail.dat or messages stuck in submission queue

    Hi guys, 
    I've looked around the forums and have found people that have had submission queue issues when they set TNEF to $null or $false, and have found that the unified answer is to set TNEF to $true.
    I also see folks having issues with recipients in remote domains receiving winmail.dat files in some instances (with a .pdf or .xls file attached) if TNEF is set to $true.
    I have both issues. If I set TNEF to $true, I encounter the winmail.dat file problem. If I set TNEF to $false or $null, I encounter the submission queue issue (submission queue states "A transient storage failure occured", and users get a queue
    expiration bounce). Neither of these states are acceptable. I cannot have messages stuck in the queue only to be expired, and I cannot have recipients in remote domains failing to receive attachments in emails. 
    Does anyone have a possible workaround that might resolve this particular situation? It seems that this has been an issue in Exch 2010.
    Current Environment Configuration:
    I am running Exchange 2013 SP1 Standard on both of my CAS/MBX servers, running on Server 2012 R2 patched to the latest updates. I have an inbound spam filter, but mail outbound is not filtered, therefore the spam filter on our side should not play a role.
    I do have not made any changes to the exchange default malware filter either. Other than this issue, mail is flowing correctly and as expected.

    I also see folks having issues with recipients in remote domains receiving winmail.dat files in some instances (with a .pdf or .xls file attached) if TNEF is set to $true.
    Hi,
    According to your description, my understanding is that all the remote domain's recipients would receive winmail.dat files when you send the message to them if TNEF is set to $true, right?
    The Winmail.dat file is used to preserve Rich Text formatting. Outlook uses it when sending a Rich Text-formatted message. During transport, the content of the message may be changed, preventing the receiving client from being able to read the formatting
    instructions. In other cases, the receiving client does not use or recognize the winmail.dat file.
    I recommend that you refer to the following article to solve the issue:
    http://support.microsoft.com/kb/278061
    Method 1: Change the default message format
    The sender can change the format of the email messages that they send by using the following steps:  
    On the Tools menu, click Options, and then click
    Mail Format.
    In Compose in this message format, click to select Plain Text, and then click
    OK.
    NOTE: To send to certain recipients that use RTF format and others recipients that use plain text format, the sender must set the option for the recipient in either the Personal Address Book or the recipient's contact record.
    Method 2: Modify the recipient's entry in the Personal Address Book
    The sender can use the following steps to remove the RTF format from the recipient attribute in the Personal Address Book:  
    On the Tools menu, click Address Book.
    In Show Names From, click the Personal Address Book.
    Select the addressee that you want to set as plain text, and then click
    Properties on the File menu.
    In the SMTP-General tab, click to clear the Always send to this recipient in Microsoft Exchange rich text format check box, and then click
    OK.
    Method 3: Change the specific contact format
    The sender can use the following steps to set plain text in the recipient's contact record:  
    Open the recipient's record in the Contacts folder.
    Double-click the recipient's e-mail address.
    In the E-Mail Properties dialog box, click Send Plain Text only under
    Internet Format.
    Method 4: Set the Outlook Rich Text Format Internet e-mail setting
    In Outlook 2003 and Outlook 2007, click Options on the Tools menu.
    Click the Mail Format tab.
    Click Internet Format.
    Under Outlook Rich Text options, click either Convert to HTML format or
    Convert to Plain Text format.
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support
    Niko,
    The Winmail.dat issue is only part of the problem, as described in my original post. For these messages (which it's a different set of messages every time, and it's becoming impossible for me to track them all down), if I set exchange or outlook to encode
    the message in Rich Text, the message gets encoded and sent to the recipient. Some of our recipients will reject the message because it is rich text, others receive a winmail.dat file.
    However, if I set exchange to not encode messages (TNEF= $false or $null), the message becomes stuck in the submission queue and eventually times out with an error resembling "Storage Transient Failure". 

  • Document on the queues

    Hi
    we have recently installed the SAP 7.0.. just been wondering like if any one document on how to set up the queues and what are main points we need to be considered while configuring the queues..
    SV

    1)  clear the queues in SMQ2,first try to activate them,if that doesn't work them delete them
    2)You may need to re-register your queues.
    Follow SXMB_ADM -> Manage Queues -> Deregister Queues
    Afterwards, re-register the queues and activate from the same screen
    3)Only use SMQ1 (outbound queues) and SMQ2 (inbound queues) if re-registering doesn't fix it. You will need to give the queues sometime to get activated so be patient.
    4)From SXMB_MONI go to Queue ID of the message, a click here shall take you to qRFC monitor.
    if the messages are stuck, you should see an entry indicating number of messages stuck in the queue.
    a double click on the entry shall take you to detailed list.
    if the messages are stuck because of any error (other than queue not registered etc for e.g. a message failure) then the first message shall show you that.
    if indeed you find a message stuck in the queue then the way is to delete the stuck message (DONT DO THIS IN PRODUCTION SERVER without being sure of what does this mean for that particular process !!) and unlock the queue from previous screen.
    5)Go to smq2 and execute F8. Then it should come as Nothing was Selected.
    If any queues are present then open a queue.if the status is SYS ERROR check the entries,right click on the status text and give save LUW.This brings queue to READY. .
    GoTo-> Qin Scheduler: check for the scheduler status to be inactive->Edit-> Activate Scheduler: status frm inactive to starting to wait.Now the queue will be RUNNING.U can see the entries in the queue moving.
    Now go to SMQ3, right click on the queue and give Restore LUW.
    6)this basically means tht message is waiting in the queue.
    in sxmb_moni go to queue Id column and double click on the entry .It will take u to SMQ2.Check the status of the queue
    If its SYSFAIL or STOP then double click on it and try to correct the error.After correcting the error send the message again.Also check whether the Queeu is Registred in transaction SMQR.
    7)Select your queue form the sxmb_moni, you will reacht he QRFC monitor.
    Here you will see some lock figures on the , Select on the 'Unlock Queues'. Activate your queues once again.
    This is if your data is correct and queue is stuck. You should only delete the queue if it has errored out due to incorrect data and you need to urgenetly process the rest of the data in the queue.
    If you drill down one step more than selct the error message and on the menu select edit-->Save LUW.

  • Why the queue is locked in SMQ2?

    Sometimes,I find the queue would be locked in SMQ2 ,so i have to release the locked queue so that it can keep on working normally.
    I'd like to know what reason can cause the queue locked ?Once the queue is locked,how to get the notificaion?
    thanks in advance.
    Regards,
    brand

    Hi
    queues are locked when the load to the processor is hight..and the second task is in queue while first one is processing at that time..secodn process will be locked after some time..extent
    1)  clear the queues in SMQ2,first try to activate them,if that doesn't work them delete them
    2)You may need to re-register your queues.
    Follow SXMB_ADM -> Manage Queues -> Deregister Queues
    Afterwards, re-register the queues and activate from the same screen
    3)Only use SMQ1 (outbound queues) and SMQ2 (inbound queues) if re-registering doesn't fix it. You will need to give the queues sometime to get activated so be patient.
    4)From SXMB_MONI go to Queue ID of the message, a click here shall take you to qRFC monitor.
    if the messages are stuck, you should see an entry indicating number of messages stuck in the queue.
    a double click on the entry shall take you to detailed list.
    if the messages are stuck because of any error (other than queue not registered etc for e.g. a message failure) then the first message shall show you that.
    if indeed you find a message stuck in the queue then the way is to delete the stuck message (DONT DO THIS IN PRODUCTION SERVER without being sure of what does this mean for that particular process !!) and unlock the queue from previous screen.
    5)Go to smq2 and execute F8. Then it should come as Nothing was Selected.
    If any queues are present then open a queue.if the status is SYS ERROR check the entries,right click on the status text and give save LUW.This brings queue to READY. .
    GoTo-> Qin Scheduler: check for the scheduler status to be inactive->Edit-> Activate Scheduler: status frm inactive to starting to wait.Now the queue will be RUNNING.U can see the entries in the queue moving.
    Now go to SMQ3, right click on the queue and give Restore LUW.
    6)this basically means tht message is waiting in the queue.
    in sxmb_moni go to queue Id column and double click on the entry .It will take u to SMQ2.Check the status of the queue
    If its SYSFAIL or STOP then double click on it and try to correct the error.After correcting the error send the message again.Also check whether the Queeu is Registred in transaction SMQR.
    7)Select your queue form the sxmb_moni, you will reacht he QRFC monitor.
    Here you will see some lock figures on the , Select on the 'Unlock Queues'. Activate your queues once again.
    This is if your data is correct and queue is stuck. You should only delete the queue if it has errored out due to incorrect data and you need to urgenetly process the rest of the data in the queue.
    If you drill down one step more than selct the error message and on the menu select edit-->Save LUW.

Maybe you are looking for