JMS Message Acknowledgement

Hi,
In my application I am using a Pub/Subscribe mode for JMS. I am using a durable subscriber. In the Subscriber side, I am opening a non-transacted TopicSession with Acknowledgement mode CLIENT_ACKNOWLEDGEMENT.
I have a Message listener which processes the message.
In my Message listener, I want to achieve the following...
Process the message, if processing succeeds, acknowledge the message. I am not acknowledging messages if the processing fails due to any reason..
Once, all the messages have been consumed, the program exits. While exiting the program, I am calling Message.recover() to put back unacknowledged messages back into the Topic...But I have observed the following problem...Say I receive the messages in the following order Message1, Message2, Message3.
Now if i don't acknowledge the Message3, and acknowledge the Message1 and 2...and the program exits...Then when the subscriber starts again, Message3 is still there in the Topic as it was not acknowledged...This is all goo...
Where is creates a problem is, say if I don't acknowledge the Message1 and acknowledge Message2 and 3 and the program exits...Now when the program exits, Message1 which was not acknowledged it also not present in the Topic...So acknowledging a message basically works like acknowledging all messages received prior to the particular message?? Is there a way to get around this problems? When I consume the messages in the Listener, can I put the messages that I don't want to acknowledge in a group or something like that? What I want to achieve is any message that is unacknowledged should be redelivered...How to achive that?
Thanks
surajit

As you assert, when you acknowledge Message2, you are also acknowledging all messages not previously acknowledged on the given session (I.E. Message1). That is, per the JMS Specification, how message acknowledgement works. There is no workaround as this is how it is designed.

Similar Messages

Interface Message acknowledge() method acknowledges this and all previous messages received.

Hi,
          I use a JDBC datastore to hold messages in a queue. When I receive a message
          off the queue, there is a flag that says True or False. If True, I want to
          put the message back onto the queue without acknowledge. If False, I want
          to acknowledge. My session instantiation looks like this:
          qsession = qcon.createQueueSession(false,Session.CLIENT_ACKNOWLEDGE);
          Currently, I receive messages by correlation ID in order to filter messages
          based on the flag. First, I receive all messages with False. Those messages
          I will acknowledge. Then, I receive messages with True. This group of
          messages will not be acknowldeged. Instead, I use qsession.recover. The
          messages are put back on the same queue after forwarding them to another
          process. The process will return success or failure. If failure, the
          process will call again, and I'll resend the group of messages I just
          recovered.
          What I would like to have happen is to do this procedure in one loop, not
          two. Instead, I would rather get all messages, and check if True or False.
          If True, I would want to skip acknowledgement. If False, I would want to
          acknowledge. The problem is, the JMS Message.acknowledge method will
          acknowledge all the messages it received before.
          In BEA WebLogic, is there an ability to acknowledge a particular message,
          rather than all previous messages? If it is not possible, is the reason
          because the acknowledge underneath is actually like a database commit? Is
          there any other way to process these two types of messages given that I may
          need to keep one type around in case resending is necessary?
          Regards,
          Scott Lynch


          Scott Lynch wrote:
          > Hi,
          >
          > I use a JDBC datastore to hold messages in a queue. When I receive a message
          > off the queue, there is a flag that says True or False. If True, I want to
          > put the message back onto the queue without acknowledge. If False, I want
          > to acknowledge. My session instantiation looks like this:
          >
          >
          >
          > qsession = qcon.createQueueSession(false,Session.CLIENT_ACKNOWLEDGE);
          >
          >
          >
          > Currently, I receive messages by correlation ID in order to filter messages
          > based on the flag. First, I receive all messages with False. Those messages
          > I will acknowledge. Then, I receive messages with True. This group of
          > messages will not be acknowldeged. Instead, I use qsession.recover. The
          > messages are put back on the same queue after forwarding them to another
          > process. The process will return success or failure. If failure, the
          > process will call again, and I'll resend the group of messages I just
          > recovered.
          >
          > What I would like to have happen is to do this procedure in one loop, not
          > two. Instead, I would rather get all messages, and check if True or False.
          > If True, I would want to skip acknowledgement. If False, I would want to
          > acknowledge. The problem is, the JMS Message.acknowledge method will
          > acknowledge all the messages it received before.
          >
          >
          >
          > In BEA WebLogic, is there an ability to acknowledge a particular message,
          > rather than all previous messages?
          The is a FAQ. And no, BEA does not provide an "acknowledge-one"
          extension. It does provide an "acknowledge-previous" extension, via a
          connection factory configurable, but this won't help in your case.
          One common solution is to use a pool of multiple sessions (one per
          current message).
          > If it is not possible, is the reason
          > because the acknowledge underneath is actually like a database commit?
          No. BEA JMS is just following the JMS spec here.
          > Is
          > there any other way to process these two types of messages given that I may
          > need to keep one type around in case resending is necessary?
          Use multiple sessions.
          >
          >
          >
          > Regards,
          >
          > Scott Lynch
          >
          >
          >
          >

Problem JMS-c api for message Acknowledgement

Hi,
          I am working in a project that uses bea-JMS C api for
          Communictions.In my project i am using topic messaging for message reciving and sending..Here i am using durablesubscriber for receiving and client Acknowledgement to Acknowledge the message.
          In receiving function I store the message in another JmsMessage for Client-Acknowledgement.
          Here comes one problem that, while i Acknowledge on the receive function each and every message Acknowledge correctly.But while i Acknowledge that message from some other function it return -1 as , that it cannot Acknowledge.The other function is working in another thread.
          Wheather the seprate thread will make the problem for confirmation.

Similar to JDBC connections, JMS sessions and their related child producers and consumers are not thread-safe (with the one exception of the session.close() method).
          For example, without added application level locking, its not safe to acknowledge a message from one thread while another thread receives or produces a message. This has special implications for asynchronous consumers, as once the asynchronous consumer is created, access to the session and objects is limited to code within the "onMessage()" and "onException()" callbacks.
          This behavior is detailed in the JMS specification.
          Tom

How to acknowledge JMS messages manually in BPEL

How to acknowledge JMS messages manually in BPEL?
Thanks!

If Oracle BPEL/SOA Dev team is watching this form then please add this feature as all the major vendors support this.

Message Acknowledgement in a Message Driven Bean

Does the message acknowledgement in a Message driven bean take place after the transaction commits? Will the message be available to be consumed by another instance of the MDB in case the transaction was rolled back? I am using WLS 7.0 as my app server and SonicMQ as JMS provider.
 Thx.
 Ajanta.


Yes, ack's are delayed until the transaction commits.
 Yes, the message will be available if the transaction is rolled back.
 "Ajanta Dey" <[email protected]> wrote in message
 news:3ea616e0$[email protected]..
 > Does the message acknowledgement in a Message driven bean take place after
 the transaction commits? Will the message be available to be consumed by
 another instance of the MDB in case the transaction was rolled back? I am
 using WLS 7.0 as my app server and SonicMQ as JMS provider.
 >
 > Thx.
 > Ajanta.

JMS Message Queue - stuck in

I am on SOA SUITE 11.1.17
I have a jms queue set up and am able to successfully send messages to it using the SOA JMS Adapter. I am able to succesfully listen to a queue using a JMS adapter in a different project.
However, here when I try to "listen" to the queue using a java program, the message is "received" in my java program and processed as it should be. The java program is running in a while loop, so it stays running.
On the queue, when the java program reads it, the message is moved to the "Messages Pending" column. When I kill the java program, the message is returned to the "Messages Current"
Would anyone have any ideas about this? We have an existing java based program isn't properly "closing" the message.
I tried:
1. placing msg.acknowledge() in the code, since the documentation states that messages that are in "Messages Pending" have been read, but not acknowledged or committed -- but this does nothing.
2. Setting the expiration on the message to 1, but that is a hack. I would rather fix the problem than use a hack.
Anyone have any ideas what is wrong?
Thank you,
Stuart
import java.io.IOException;
import java.io.InputStreamReader;
import javax.jms.Connection;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageConsumer;
import javax.jms.MessageListener;
import javax.jms.Session;
import javax.jms.TextMessage;
public class JMSListenAndRespond extends JMSQueueHandler implements MessageListener {
private Session jmsSession = null;
private MessageConsumer jmsMessageConsumer = null;
private Connection jmsConnection = null;
int counter = 1 ;
public static void main(String[] args) throws Exception {
    InputStreamReader commandBuffer = null;
    char command = '\0';
      // first listen for any messages
      JmsDataObject q = new JmsDataObject();
      q.setJmsCF("jms/TestConnectionFactory");
      q.setJmsQueue("jms/TestJMSQueue");
      q.setServerPwd("welcome1");
      q.setServerLogin("weblogic");
      q.setUrl("t3://localhost:7101");
      q.setJmsMsg("na -- we are listinging...");
    JMSListenAndRespond lis = new JMSListenAndRespond();
     lis.consumeMessage(q);
    System.out.println("(type q to exit at any time...)\n");
    try {
      // Now just loop, waiting for messages until user types 'q' to quit
      commandBuffer = new InputStreamReader(System.in);
    while (!(command == 'q')) {
       try {
          command = (char)commandBuffer.read();
          System.out.println("Command: "+command);
          lis.stopListening();
        } catch (IOException e) {
          System.err.println("I/O Exception: ");
          e.printStackTrace();
       } //while
    } finally {
            lis.stopListening();
      lis.stopListening();
   public void stopListening() {
    try {
      if (jmsMessageConsumer != null) {
        jmsMessageConsumer.close();
      if (jmsSession != null) {
        jmsSession.close();
      if (jmsConnection != null) {
        jmsConnection.close();
    } catch (JMSException e) {
      System.err.println("Couldn't properly close all resources.\n");
      e.printStackTrace();
private void prepareToConsumeMessage() {
    // create JMS connection, session, consumer and register listener - then start session
        try {
      // create connection
      jmsConnection = getJmsConnectionFactory().createConnection();
      // create session
      jmsSession =   jmsConnection.createSession(false, javax.jms.Session.AUTO_ACKNOWLEDGE);
      jmsMessageConsumer = jmsSession.createConsumer(getJmsDestination());
      // register a message listener (onMessage)
      jmsMessageConsumer.setMessageListener(this);
      // initiate connection - make sure to register your listener first or you might lose messages
      jmsConnection.start();
      System.out.println("\n...listening for message!\n");
    } catch (JMSException e) {
      System.err.println("Problem initializing JMS session");
      e.printStackTrace();
      System.exit(-1);
     * onMessage
     * The callback function invoked upon message reception
public void onMessage(Message msg) {
    try {
      String msgText;
      if (msg instanceof TextMessage) {
        msgText = ((TextMessage)msg).getText();
        // this method expects a CSV string with the following makeup:
        // firstName,lastName,gender,birthdate,address,city,zipcode,state,insurancePolicyId
        String messageId = msg.getJMSMessageID();
      // code to process goes here.....
      } else {
        // if message is not a TextMessage, attempt a conversion to string
        System.out.println("\n** NEW MESSAGE (" + msg.getClass().getName() +
                           "):\n" +
            msg.toString());
    } catch (JMSException e) {
      e.printStackTrace();
public void consumeMessage(JmsDataObject q ) {
    initializeJndiProperties(q);
    initializeJNDIandCF(q.getJmsQueue());
    prepareToConsumeMessage();
import java.util.Properties;
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.Destination;
import javax.naming.InitialContext;
import javax.naming.NamingException;
public abstract class JMSQueueHandler {
protected void initializeJNDIandCF(String destinationQueueName) {
    // initialize JNDI context and lookup connection factory and destination
    try {
      // Initialize JNDI context
      jndiContext = new InitialContext(jndiProperties);
    } catch (NamingException e) {
      e.printStackTrace();
    try {
      // lookup JMS connection factory in JNDI
      jmsConnectionFactory =
          (ConnectionFactory)jndiContext.lookup(jndiProperties.getProperty("factory.name"));
      // lookup JMS destination in JNDI
      jmsDestination = (Destination)jndiContext.lookup(destinationQueueName);
    } catch (NamingException e) {
      System.err.println("Problem during the JNDI lookup\n");
      e.printStackTrace();
      System.exit(-1);
public void initializeJndiProperties(JmsDataObject qdo ) {
    // set JNDI properties
    jndiProperties.put("java.naming.factory.initial","weblogic.jndi.WLInitialContextFactory");
    jndiProperties.put("java.naming.provider.url", qdo.getUrl() );
   // jndiProperties.put("java.naming.security.principal", NAMING_PRINCIPAL);
    jndiProperties.put("java.naming.security.principal", qdo.getServerLogin() ) ;
    // jndiProperties.put("java.naming.security.credentials", NAMING_CREDENTIAL);
    jndiProperties.put("java.naming.security.credentials", qdo.getServerPwd() );
    //jndiProperties.put("factory.name", JMS_CONNECTION_FACTORY);
    jndiProperties.put("factory.name", qdo.getJmsCF() );
//protected static final String NAMING_PROVIDER_URL = "t3://localhost:7101";
//protected static final String NAMING_PRINCIPAL = "weblogic";
// protected static final String NAMING_CREDENTIAL = "welcome1";
// protected static final String JMS_CONNECTION_FACTORY = "jms/patientsJmsCF";
// protected static final String JMS_CONNECTION_FACTORY = "jms/TestConnectionFactory";
ConnectionFactory jmsConnectionFactory = null;
Destination jmsDestination = null;
InitialContext jndiContext = null;
Properties jndiProperties = new Properties();
public void setJmsConnectionFactory(ConnectionFactory jmsConnectionFactory) {
    this.jmsConnectionFactory = jmsConnectionFactory;
public ConnectionFactory getJmsConnectionFactory() {
    return jmsConnectionFactory;
public void setJmsDestination(Destination jmsDestination) {
    this.jmsDestination = jmsDestination;
public Destination getJmsDestination() {
    return jmsDestination;

Thanks for the reply. There are no errors what so ever regarding MDB issues. Not in the weblogic / console logging, nor in the logging of the component itself.
The MDB itself is setup to have 16 concurrent beans per component deployment. The component is clustered over 4 server instances. So there are quite some concurrent MDBs running. However since the messages get stuck for weeks eventhough the component only has bursts of messages to process, one would think that the the stuck messages would be processed whenever the component has some spare time (which it has a lot between the bursts).
Therefor i doubt it has anything to do with too little MDBs running. But frankly I have no idea what's wrong.

Weblogic Message Bridge Producing Duplicate JMS Messages

We have a message bridge that we use to integrate with TIBCO. The message bridge is deployed on a WL cluster. We see duplicate JMS messages produced by the bridge when it is deployed on the cluster. We don't see this behavior when only one ManagedServer in the cluster is active,.
TIBCO version: 4.4.3 V5
WLS: 10.3.3 with patch for bug BUG8732539 (BQC6)
java -version
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Oracle JRockit(R) (build R28.0.0-679-130297-1.6.0_17-20100312-2121-linux-x86_64, compiled mode)
We are also seeing a lot of exceptions related to
<May 27, 2011 4:11:57 PM PDT> <Warning> <Connector> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">
However the bridge is active. We are monitoring the message-out count on TIBCO and we observed that we see duplicates whenever there a message is re-delivered. We opened a case with Oracle support and they suggested patch 10258751 which didn't help. The next suggestion was a patch for "Bug 11852771 - [WLS10.3.2]MISSING AND DUPLICATE IN JMS QUEUE MESSAGE MONITORING" but I don't think it will help since our JMS consumers are getting duplicate messages and this is not just a UI issue.
Here is the message behavior when we send a single message:
Timelines
11:34:17 --> Message sent to TIBCO EMS queue
11:34:17 --> WL MS3 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
11:34:17 --> WL MS1 says it got the message and committed the transaction
11:34:17 --> Message is visible in the JMS queue in the admin console
11:34:17 --> TIBCO EMS has still not received an ACK from WL for the message
11:34:31 --> TIBCO EMS resends the same JMS message to WL
11:34:31 --> WL MS2 says it got the message and committed the transaction
11:34:31 --> WL MS1 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
11:34:31 --> Message is visible in the JMS queue in the admin console (At this point there are two messages in the JMS queue)
11:34:31 --> TIBCO EMS has still not received an ACK from WL for the message
11:34:54 --> TIBCO EMS resends the same JMS message to WL
11:34:31 --> WL MS4 says it got the message and committed the transaction
11:34:31 --> WL MS2 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
11:34:31 --> Message is visible in the JMS queue in the admin console (At this point there are three messages in the JMS queue)
11:34:31 --> TIBCO EMS receives an ACK from WL for the message
MS04
####<May 27, 2011 11:34:54 AM PDT> <Debug> <MessagingBridgeRuntime> <> <MS04> <[ACTIVE] ExecuteThread: '109' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-6A59E8FE76C4FC4CA149> <> <1306521294611> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
JMS Message Class: TextMessage
JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: Queue[SourceQueue1]
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: true
JMSReplyTo: null
JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
JMSType: null
Transaction Id: BEA1-6A59E8FE76C4FC4CA149
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:54 AM PDT> <Debug> <MessagingBridgeRuntime> <MS04> <MS04> <[ACTIVE] ExecuteThread: '109' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-6A59E8FE76C4FC4CA149> <> <1306521294611> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
JMS Message Class: TextMessage
Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
New JMS MessageID: ID:<193654.1306521294611.0>
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
MS03
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257342> <BEA-000000> <Bridge MessageBridge1 Successfully got connection to the target destination>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1: both source and target adapters support XA = true>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 supportsMDBTX = false supportsXA = true async = true>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 WorkMode = Exactly-once>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntimeVerbose> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 Entering processMessages() ------ >
####<May 27, 2011 11:34:17 AM PDT> <Error> <MessagingBridge> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-3AA29116A4CA622834EA> <> <1306521257343> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: javax.resource.ResourceException: Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = 'eis/jms/WLSConnectionFactoryJNDIXA', javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'eis/jms/WLSConnectionFactoryJNDIXA' is unavailable
at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:948)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:634)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1227)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:200)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'eis/jms/WLSConnectionFactoryJNDIXA' is unavailable
at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:948)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:634)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1227)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
... 8 more
).>
####<May 27, 2011 11:34:17 AM PDT> <Warning> <MessagingBridge> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257344> <BEA-200026> <Bridge "MessageBridge1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: MessagingBridgeException: Messaging bridge operation failed
.)>
MS02
####<May 27, 2011 11:34:31 AM PDT> <Debug> <MessagingBridgeRuntime> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-679AF074F381152F047C> <> <1306521271386> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
JMS Message Class: TextMessage
JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: Queue[SourceQueue1]
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: true
JMSReplyTo: null
JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
JMSType: null
Transaction Id: BEA1-679AF074F381152F047C
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:31 AM PDT> <Debug> <MessagingBridgeRuntime> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-679AF074F381152F047C> <> <1306521271392> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
JMS Message Class: TextMessage
Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
New JMS MessageID: ID:<196075.1306521271386.0>
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:54 AM PDT> <Error> <MessagingBridge> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521294610> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: weblogic.transaction.RollbackException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1871)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:330)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:225)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:293)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1534)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
... 2 more
).>
####<May 27, 2011 11:34:54 AM PDT> <Warning> <MessagingBridge> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521294610> <BEA-200026> <Bridge "MessageBridge1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: MessagingBridgeException: Messaging bridge operation failed
MS01
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-72BC818FE2BB8C2655C6> <> <1306521257536> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
JMS Message Class: TextMessage
JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: Queue[SourceQueue1]
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: false
JMSReplyTo: null
JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
JMSType: null
Transaction Id: BEA1-72BC818FE2BB8C2655C6
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-72BC818FE2BB8C2655C6> <> <1306521257542> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
JMS Message Class: TextMessage
Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
New JMS MessageID: ID:<195581.1306521257536.0>
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:31 AM PDT> <Error> <MessagingBridge> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521271384> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: weblogic.transaction.RollbackException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1871)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:330)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:224)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:293)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1534)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
... 1 more
).>
####<May 27, 2011 11:34:31 AM PDT> <Warning> <MessagingBridge> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521271384> <BEA-200026> <Bridge "MessageBridge1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: MessagingBridgeException: Messaging bridge operation failed
.)>

@Tom, thanks for your hints and sorry for my delayed response. Here are my answers to your queries…
-- Does messaging work, without any exceptions, when only one bridge is active?
It works fine when only one node of the cluster is active. -- I'm not familiar with Tibco monitoring, but I suspect that the "message-out count on TIBCO" stat doesn't always imply that there's a duplicate message. It could mean that an initial message delivery attempt failed, it's transaction rolled back, and the message was redelivered. Redelivery after a failure is normal - the original delivered message, if one actually made it onto a WebLogic queue, should be discarded by WebLogic when its failed transaction eventually rolls back (before its ever handed to a consumer application).
You are absolutely right. The mismatch in count was due to redelivery attempts. We could see that as soon as we turned on trace in TIBCO-- The posted stack traces look like they may be JVM stdout/stderr scrapes, which are often automatically truncated, for example, see the "... 8 more" listed at the bottom of one of the stack traces below. There might be more information in the full stack trace for the "Resource manager is unavailable" exception. Full traces are logged in each WebLogic Server's log files.
I tried redirecting the output and even set "stdout Stack Trace Depth:" to -1 but I am not albe to see the complete trace.-- The setTransactionTimeout NullPointerException error message looks like it is collateral damage from the original reported "Resource manager is unavailable" exception that's thrown earlier during the enlistResource() step. If you are truly getting duplicates, then I think this is a clue that the bridge is somehow (stupidly) trying to proceed with forwarding the message despite the fact that there's no current transaction on the thread... 
I have a case open with Oracle support and we have extensive debugging turned on. Here is what the engineer came back with. There is an issue with XA transactions in JCA adapter when it talks to third party providers like TIBCO. Since the resource names are not unique across the cluster, a XA transaction is started on multiple nodes in the cluster for the same message. All transactions abort but the message is persisted and TIBCO redelivers the message since the connection is severed when the transaction aborts. We were able to reproduce this scenario at will with our setup and Oracle was able to reproduce the issue too.  -- Can you check the state of the message on the WebLogic Q? The fact that a message is shown on the WL console doesn't necessarily mean that the state of the message is visible (it could be waiting for the transaction to commit - something that apparently never happens). On the console: Services -> Messaging -> JMS Modules -> [module name] -> [destination name]. 
Our consumer was getting duplicate messages. This confirms that the console was not giving us incorrect information. The console showed that 2/3/4 messages were in "current" state when we expected only one message. -- Make sure that the bridge's Tibco destination is a Tibco queue not a Tibco topic (it's happened). 
Yeah we made sure it was a Queue. -- Can you post your bridge and destination stanzas from your config.xml?  
Will try to do this shortly but have to strip out lot of information. -- I vaguely recall that there was a problem with untyped connection factories in Tibco at one point (not sure). You might want to try changing the Tibco configuration to spin-up "XA Queue Connection Factory" instead of just an "XA Connection Factory" (plus modify the bridge configuration accordingly). 
We tried this but it didn't eliminate this issue. One thing we did notice however was that the number of rollbacks were greatly reduced. 
Here is the workaround that Oracle is suggesting: Create pinned destinations and assign it to a distributed queue. This will keep the transactions local and hence eliminate the duplicate transactions and rollback. We tried it and it eliminated the dups issue. However I discovered another bug during my testing. Our cluster messaging mode is "Unicast" and message forwarding from zero consumer queues to queues with consumers fails. We have four/five nodes in the cluster and two consumer threads. I observed that the zero consumer queues always forward to one queue in the cluster that has consumers. The forwarding stalls when I bring down the node that has consumers. Again, we were able to reproduce this issue at will and Oracle has acknowledged that it is a bug. They've reported that Unicast fails without any warning whereas Multicast fails with a warning in the log. We have observed this message forwarding stalling even with UDQs.
I have another case open for an issue where our message bridges that transfer messages from TIBCO to WLS stalls after sometime. The status is shown as active but it is not doing anything. The server instance shows stuck threads trying to roll back a message. TIBCO logs indicate that it is receiving a request to rollback a transaction but it is not finding the transaction to rollback. The only way to recover from this condition is to restart the cluster. I am fairly confident that he root case for this issue is again the XA transaction issue. I changed our UDQ to pinned destination in one environment and we are no longer seeing dups or bridge stalling there. Hopefully Oracle can resolve the message forwarding issue.Thanks again….

JMS messages sometimes not received by Flex client

We have a problem that Flex client is sometimes not able to
receive JMS messages from a JBoss JMS Queue. Most of the time it
works, but if users logout/login using the same account frequently
or you restart JBoss 4.0.4 during their session then it might
happen. Then it doesn't work at all even if you wait. Client is
able to send messages when this problem occurs, which can then be
intercepted by other clients but cannot receive any messages from
himself or from the others. JBoss 4.0.4 is running in cluster mode.
Could it be that there is an old frozen session which is receiving
the messages meant for the new client?(consumer selector is unique
to each user, but if a user logs in twice, the same selector is
used) If I run 2 instances of my JMS test consumer using the same
selector then the consumer which registered later receives the
messages and if it quits, then the older consumer starts receving
them. This doesn't occur in Flex.
Flex is running on Tomcat 5.5.17.
Our messaging-config.xml is
<?xml version="1.0" encoding="UTF-8"?>
<service id="message-service"
class="flex.messaging.services.MessageService"
messageTypes="flex.messaging.messages.AsyncMessage">
<adapters>
<adapter-definition id="actionscript"
class="flex.messaging.services.messaging.adapters.ActionScriptAdapter"
default="true" />
<adapter-definition id="jms"
class="flex.messaging.services.messaging.adapters.JMSAdapter"/>
</adapters>
<destination id="JMSQueueB">
<properties>
<network>
<session-timeout>10</session-timeout>
</network>
<jms>
<initial-context-environment>
<property>
<name>java.naming.factory.url.pkgs</name>
<value>org.jboss.naming:org.jnp.interfaces</value>
</property>
<property>
<name>Context.PROVIDER_URL</name>
<value>jnp://x.x.x.x:1100,jnp://x.x.x.y:1100</value>
</property>
<property>
<name>Context.INITIAL_CONTEXT_FACTORY</name>
<value>org.jnp.interfaces.NamingContextFactory</value>
</property>
</initial-context-environment>
<destination-type>Queue</destination-type>
<message-type>javax.jms.TextMessage</message-type>
<connection-factory>ConnectionFactory</connection-factory>
<destination-jndi-name>queue/B</destination-jndi-name>
<destination-name>B</destination-name>
<delivery-mode>PERSISTENT</delivery-mode>
<message-priority>DEFAULT_PRIORITY</message-priority>
<acknowledge-mode>AUTO_ACKNOWLEDGE</acknowledge-mode>
<transacted-sessions>false</transacted-sessions>
</jms>
</properties>
<channels>
<channel ref="my-rtmp"/>
<channel ref="my-secure-amf"/>
</channels>
<adapter ref="jms"/>
</destination>
</service>
Part of our actionscript code:
pmConsumer = new Consumer();
pmConsumer.destination = "JMSQueueB";
pmConsumer.selector = "some jms selector ....";
pmConsumer.addEventListener(MessageEvent.MESSAGE,
presenceMessageHandler);
pmConsumer.addEventListener(MessageFaultEvent.FAULT,
faultHandler);
pmConsumer.addEventListener(ChannelFaultEvent.FAULT,
channelFaultHandler);
pmConsumer.subscribe();
Also Flex seems to be handing channel switching incorrectly,
if rtmp port is firewalled, it won't use amf properly even though
it was given 2 channels in configuration file and JMS messaging
doesn't work. We have to alter the channel set during runtime.
Flex also doesn't automatically switch to other JMS server if
one goes down. Is this a feature or a bug? We have to reset
producer and consumer in order for this to work.

Hi,
It was in earlier version of the OS that you could turn Bonjour On and Off.
If this can be done in Leopard and Snow Leopard I have not found it yet. (But I don't look that often and nor for very long)
This Forum may help with that
I would also try a PRAM reset. (on Both computers)
Shut down the computer.
Restart it holding down APPLE(or ⌘)ALT+PR Keys until you have heard three Start Up Bongs.
7:18 PM Tuesday; December 8, 2009
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

JMS message persistance

Hi
I have an interface receiving SMS from a SMSC. This message is dumped into a JMS queue where a MDB receives and processes this.
This MDB relies on a DB connection writing a lot of information away and execute some PL/SQL.
Question is: When the DB is not available, ie the JDBC connection fails, how do I "re-send" this or save it to process it later when the DB is up again.
Is there any method available that will "auto re-submit" the JMS message if I don't acknowledge it?
The currentfunctionlaity works well except for this problem.
Tks
Andre

Isaac -- If you need high reliability or transactional behaviors you really need to be using Oracle JMS. In general we recommend using Oracle JMS for now becasue OC4J JMS is still not JMS 1.0.2 compliant. We are working on that for a future release.
Thanks -- Jeff

Valid JMS Message status

Hello All,
I have two WLS domains. One WLS 10.3.X, another is WLS 8.1.X
Each domain have one queue each (e.g. 10.3.X => Q1 & 8.1.X => Q2) and the 10.3.X domain have been configured with a MessageBridge to deliver the messages from Q1 to Q2
Each domain have ConnectionFactories XA enabled and the Bridge adapter is also set to "eis.jms.WLSConnectionFactoryJNDIXA"
Now the Bridge is showing active, but if we put a test message in Q1, it is taking long to be delivered to Q2. There is no error in the logs (Debug Flgs have also been enabled).
Sometimes it is also not being delivered at all.
During this, the status of the message in the Q1 is showing "receive transaction".
So can anyone tell me :
1> what are the valid status of any message in wls jms queues and what are the meaning of them.
2> what is the lifecycle of a message.
Thanks in advance

http://docs.oracle.com/cd/E24329_01/apirefs.1211/e24391/weblogic/jms/extensions/JMSMessageInfo.html#JMSMessageInfo(long,%20int,%20java.lang.String,%20long,%20java.lang.String,%20weblogic.jms.extensions.WLMessage,%20java.lang.String,%20boolean)
"visible - The message is visible on the destination and may be consumed.
send - The message is pending because it is associated with an in progress send operation.
receive - The message is pending because it has been received by a consumer but not yet acknowledged.
transaction - The message is associated with a transactional “send” or “receive” operation that is in progress.
ordered - The message belongs to a Unit-of-Order (UOO).
delayed - The message is pending because it has a scheduled delivery time or is otherwise delayed.
expired - The message has expired and is no longer available for consumption.
redelivery-count-exceeded - The message has exceeded the redelivery count set for the destination and is no longer available for consumption.
paused - The message is pending because of a destination pause operation .
sequenced - The message that is part of a SAF sequence.
unit-of-work-component - The message is part of an Unit-of-Work (UOW).
deleted - The message is marked for deletion."
You can enable message life cycle logging
- http://docs.oracle.com/cd/E24329_01/web.1211/e24385/troubleshoot.htm#i1128815
"The message life cycle is an external view of the events that a JMS message traverses through once it has been accepted by the JMS server, either through the JMS APIs or the JMS Message Management APIs. Message life cycle logging provides an administrator with easy access to information about the existence and status of JMS messages from the JMS server viewpoint. In particular, each message log contains information about basic life cycle events such as message production, consumption, and removal."
There is also a WLST script provided here (Re: Example using of getMessage(s) with JMS error queues? for browsing messages on a given destination.

Need suggestion on implementing JMS message error recovery

Hi,
Our application has a JMS topic where we publish application events. Now, there can be scenarios where the consumers cannot process the message due to some infrastructure issues and would error out. We need a way so that those messages can be reprocessed again later. we are thinking of the following design for JMS message error recovery
1. Use a persistent TOPIC (this would ensure guaranteed delivery)
2. Configure a error destination on JMS topic e.g a jms queue
3. Have an error handling MDB listening to the Error destination. An error handling MDB would dequeue the errored messages from error destination and persist it to a Data base "error" table..
4. Provide a mechanism to republish those messages to topic (e.g a scheduler or admin ui or a command line utility) .. The messages would deleted from database "error" table and published to topic again....
A. Are there any issues with the above design which we need to handle?
B. Are there any additional steps required in a Cluster environment with a distributed topic and distribute error destination? (our error mdb will have one-copy-per-application setting)
B. From a performance angle, Is it OK to use persistent TOPIC ? Or will it better to persist the message to the db table and then publish it as a non persistent message ... ? (But i guess the performance should be more or less the same in both of these approaches)
C. Are there any other recommended design patterns for error recovery of JMS messages
Please advise.
Regards,
Arif

Thanks Tom !
We may not be able to go with the approach of delaying/pausing redelivery of the messsage because
1. Pausing entire MDB approach: Our MDB application consumes messages generated by different producers and our MDB needs to continue processing the messages even if messages corresponding to one producer is erroring out
2. Redelivery delay : This would only delay the retry of an errored message. But there would still be a problem if the message fails during all retries (i.e redelivery limit count). We don't want to lose this message. In our case, It is possible that a particular message cannot be processed due to unavailability of a third party system for hours or may be a day.
Basically, i am looking on approaches for a robust and performant error recovery/retry framework for our application (refer details in my first post on this thread) while fully making use of all features provided by middleware (WLS). Please advise.
Regards,
Arif

Lost (and found) JMS - messages

 Using WLS 6.1 and have experienced that JMS messages has not been delivered to
 its consumer correctly. We are interested in any suggestions to what has happend,
 what can be done to avoid the problem in the future, or perhaps how we can find
 out more about the problem.
 We have a message driven bean A which sends messages to the queue Q, of which
 the message driven bean B is the only consumer.
 What we recently have experienced is that some of the messages delivered by A
 to Q never are delivered to B. But the messages seems to be persisted correctly,
 because after a restart they reappear!
 Following is a more detailed description of the scenario:
 1. A message is sendt with DeliveryMode=PERSISTENT and TimeToLive=0. QueueSender.send
 is invoked and returns normally.
 2. The consumers never gets the message (B.onMessage i never invoked with this
 message).
 3. Point 1-2 is repeated for 13 different messages over a period when ~100 similar
 messages are delivered normally.
 4. The server is then restarted.
 5. In the starup log it is indicated that 44 records are found in the JMSStore.
 6. When the server restarts, the "lost" messages gets delivered to B.
 After the server restart we have not experienced the problem again.
 Logs does not show anything unusual about the previous restart.
 Other details:
 There is always exatly 1 instance of A running, and 5-20 instances of B. A implements
 and uses a pool of javax.jms.XAQueueSession instances, which shares a single instance
 of javax.jms.XAQueueConnection. The aknowledge-mode for B is "Auto-aknowledge".
 We're using Weblogic Server 6.1.3.0 / Red Hat Linux 7.3.
 Any help on this problem is appreciated!


 I believe we've seen just the behaviour you describe on 6.1 SP2, but only on a
 multi-cpu box (Solaris), and only under load. We can't reproduce the problem reliably,
 and get no error messages/warnings anywhere, so very little to send to customer
 support; by the time we notice this, the problem's long passed, so a thread dump's
 of no use.
 We're going to try and see how SP5 (which has loads of JMS fixes) pans out.
 But if you find anything out, could you post here?
 simon.
 "Harald Stendal" <[email protected]> wrote:
 >
 >Using WLS 6.1 and have experienced that JMS messages has not been delivered
 >to
 >its consumer correctly. We are interested in any suggestions to what
 >has happend,
 >what can be done to avoid the problem in the future, or perhaps how we
 >can find
 >out more about the problem.
 >
 >We have a message driven bean A which sends messages to the queue Q,
 >of which
 >the message driven bean B is the only consumer.
 >What we recently have experienced is that some of the messages delivered
 >by A
 >to Q never are delivered to B. But the messages seems to be persisted
 >correctly,
 >because after a restart they reappear!
 >
 >Following is a more detailed description of the scenario:
 >
 >1. A message is sendt with DeliveryMode=PERSISTENT and TimeToLive=0.
 >QueueSender.send
 >is invoked and returns normally.
 >2. The consumers never gets the message (B.onMessage i never invoked
 >with this
 >message).
 >3. Point 1-2 is repeated for 13 different messages over a period when
 >~100 similar
 >messages are delivered normally.
 >4. The server is then restarted.
 >5. In the starup log it is indicated that 44 records are found in the
 >JMSStore.
 >6. When the server restarts, the "lost" messages gets delivered to B.
 >
 >After the server restart we have not experienced the problem again.
 >
 >Logs does not show anything unusual about the previous restart.
 >
 >Other details:
 >There is always exatly 1 instance of A running, and 5-20 instances of
 >B. A implements
 >and uses a pool of javax.jms.XAQueueSession instances, which shares a
 >single instance
 >of javax.jms.XAQueueConnection. The aknowledge-mode for B is "Auto-aknowledge".
 >
 >We're using Weblogic Server 6.1.3.0 / Red Hat Linux 7.3.
 >
 >Any help on this problem is appreciated!
 >

Problem in sending JMS message on remote OC4J

I have two OC4J standalone (10.1.3.0.0 build 041119.0001.2385)
The containers work on Windows2000 in different machines connected by the LAN.
The First container has deployed application from example http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-jca-intro/doc/how-to-jca-intro.html
The second container has j2ee application (Servlet) that sending JMS messages in the queue of the first container.
Code Servlet in second OC4J:
package mypackage2;
import javax.servlet. *;
import javax.servlet.http. *;
import java.io. PrintWriter;
import java.io. IOException;
import javax.jms. *;
import javax.naming. *;
import java.util. *;
public class Servlet1 extends HttpServlet
private static final String CONTENT_TYPE = "text/html;charset=windows-1251";
public void init (ServletConfig config) throws ServletException
super.init (config);
String QUEUE_NAME = "OracleASjms/MyQueue1";
String QUEUE_CONNECTION_FACTORY = "OracleASjms/MyQCF";
public void doGet (HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException
response.setContentType (CONTENT_TYPE);
PrintWriter out = response.getWriter ();
out.println (" < html > ");
out.println (" < head > < title > Servlet1 < /title > < /head > ");
out.println (" < body > ");
try
Hashtable env = new Hashtable ();
env.put (Context. INITIAL_CONTEXT_FACTORY, "oracle.j2ee.rmi.RMIInitialContextFactory");
env.put (Context. SECURITY_PRINCIPAL, "admin");
env.put (Context. SECURITY_CREDENTIALS, "admin");
env.put (Context. PROVIDER_URL, "ormi://host_OC4J_1:23791/jcamdb");
env.put ("dedicated.rmicontext", "true");
InitialContext ic = new InitialContext (env);
QueueConnectionFactory connectionFactory = (QueueConnectionFactory)ic.lookup (QUEUE_CONNECTION_FACTORY);
QueueConnection connection = connectionFactory.createQueueConnection ();
connection.start ();
QueueSession queueSession =
connection.createQueueSession (false, Session.AUTO_ACKNOWLEDGE);
Queue queue = (Queue) ic.lookup (QUEUE_NAME);
ic.close ();
System.out.println (" Queue: " + queue);
QueueSender sender = queueSession.createSender (queue);
System.out.println (" creating Message: " + queue);
Message message = queueSession.createMessage ();
System.out.println (" Message created ");
message.setJMSType ("theMessage");
message.setLongProperty ("time", System.currentTimeMillis ());
message.setStringProperty ("id", "11111");
message.setStringProperty ("oamount", "55555");
message.setStringProperty ("message", "77777");
message.setStringProperty ("RECIPIENT", "MDB");
System.out.println (" Sending message... ");
sender.send (message);
System.out.println (" Message sent ");
sender.close ();
queueSession.close ();
connection.close ();
catch (Exception e)
System.out.println (" ** TEST FAILED ** Exception: " + e);
out.println (e.toString ());
e.printStackTrace ();
out.println (" The servlet has received a GET. This is the reply. < /html > ");
out.close ();
Error: This code send message in The First container, and should send in the second OC4J !!!!
Please answer :
As configure (what code it is necessary to write) servlet (any J2EE the application in OC4J) to use a path to OC4J JMS (remote OC4J JMS) through the Resource Adapter (using OracleASjms.rar). ???

I have two OC4J standalone (10.1.3.0.0 build 041119.0001.2385)
The containers work on Windows2000 in different machines connected by the LAN.
The First container has deployed application from example http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-jca-intro/doc/how-to-jca-intro.html
The second container has j2ee application (Servlet) that sending JMS messages in the queue of the first container.
Code Servlet in second OC4J:
package mypackage2;
import javax.servlet. *;
import javax.servlet.http. *;
import java.io. PrintWriter;
import java.io. IOException;
import javax.jms. *;
import javax.naming. *;
import java.util. *;
public class Servlet1 extends HttpServlet
private static final String CONTENT_TYPE = "text/html;charset=windows-1251";
public void init (ServletConfig config) throws ServletException
super.init (config);
String QUEUE_NAME = "OracleASjms/MyQueue1";
String QUEUE_CONNECTION_FACTORY = "OracleASjms/MyQCF";
public void doGet (HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException
response.setContentType (CONTENT_TYPE);
PrintWriter out = response.getWriter ();
out.println (" < html > ");
out.println (" < head > < title > Servlet1 < /title > < /head > ");
out.println (" < body > ");
try
Hashtable env = new Hashtable ();
env.put (Context. INITIAL_CONTEXT_FACTORY, "oracle.j2ee.rmi.RMIInitialContextFactory");
env.put (Context. SECURITY_PRINCIPAL, "admin");
env.put (Context. SECURITY_CREDENTIALS, "admin");
env.put (Context. PROVIDER_URL, "ormi://host_OC4J_1:23791/jcamdb");
env.put ("dedicated.rmicontext", "true");
InitialContext ic = new InitialContext (env);
QueueConnectionFactory connectionFactory = (QueueConnectionFactory)ic.lookup (QUEUE_CONNECTION_FACTORY);
QueueConnection connection = connectionFactory.createQueueConnection ();
connection.start ();
QueueSession queueSession =
connection.createQueueSession (false, Session.AUTO_ACKNOWLEDGE);
Queue queue = (Queue) ic.lookup (QUEUE_NAME);
ic.close ();
System.out.println (" Queue: " + queue);
QueueSender sender = queueSession.createSender (queue);
System.out.println (" creating Message: " + queue);
Message message = queueSession.createMessage ();
System.out.println (" Message created ");
message.setJMSType ("theMessage");
message.setLongProperty ("time", System.currentTimeMillis ());
message.setStringProperty ("id", "11111");
message.setStringProperty ("oamount", "55555");
message.setStringProperty ("message", "77777");
message.setStringProperty ("RECIPIENT", "MDB");
System.out.println (" Sending message... ");
sender.send (message);
System.out.println (" Message sent ");
sender.close ();
queueSession.close ();
connection.close ();
catch (Exception e)
System.out.println (" ** TEST FAILED ** Exception: " + e);
out.println (e.toString ());
e.printStackTrace ();
out.println (" The servlet has received a GET. This is the reply. < /html > ");
out.close ();
Error: This code send message in The First container, and should send in the second OC4J !!!!
Please answer :
As configure (what code it is necessary to write) servlet (any J2EE the application in OC4J) to use a path to OC4J JMS (remote OC4J JMS) through the Resource Adapter (using OracleASjms.rar). ???

Specifying additional JMS message attributes in Sender Adapter

Hi,
Iam using sender JMS adapter and I have to use the option " Specify Additional JMS Message Properties" for adding addtionalJMS properties in XI message header.
Once I cselect the option in the below table Iam not able to add new lines to add addtional JMS Message Properties..But In receiver adapter I was able to add the new lines.
Is this option graded in SAP PI 7.3 or relatd to any authorization issue..?
Is anyone faced this issue before.. Please help me out
Thank you

Hi everybody
I'm starting a project where I have to take adptadores JMS and I'm in the same situation kirian, I am need to configure a JMS adapter with version of SAP PI 7.3 and I wonder if anyone can help me or give me manuals leagues where information comes related.
Someone can help me with this information
Regards

How to stop and start MDBs to listen for JMS messages

Hello! This might be more of an architecture question rather than a technical questing, but I post it here, in the lack of a better place...
For several years I have been using Webster and Webster MQ to send messages back and forth to clients. The architecture for the middleware platform has been designed around the functionality of ListenerPorts. Listenerports is a Webster functionality that let you "stop" and start to listen to JMS messages for a given MDB either by admin console, or by JMX.
The arhitecture we used was something like this :
1.Client sends a persistent message to a queue. (order)
2. An MDB pics up the order message, calls a SessionBean that "fronts" the IIOP back end system.
This is quite "out of the box" architecture, but we used the Listenerports to solve a stability problem for our back end system.
The backEnd system was quite unstable, so the EJB threw an exception (typically because of timeout or connection refused) back to the MDB.
The Listenerport was "defined" to handle 3 errors before stopping, so the MDB resent the message twice before the listenerport automatically stopped. The nice thing about this feature was that the client could continue to send orders, and was not bothered when the back end system was down.
When the backEnd system was up and running, we could start the listenerport and it was all back to normal state. We even had a start script that checked the state of the listenerport every 30 minute, and started it automatically if it was stopped, making the admin task of starting the MDB unnecessary..
Now.. Why am I telling this story..
I would like to know how this could be done using "clean" J2EE technologies..That is..Not using any technology that is not portable..
I`m playing with glassfish at home, and it struck me that there is nothing in the J2EE spec that defines the functionality described above ? Am i missing something ?
I Do not want to stop My application because the back end system is down? That is the only way (i know of) that i can "stop" to listen for messages..
I can put all the messages on an error queue when the backbend system is down, but that would lead to more code just to handle the error messages. Maybe the easiest way to solve this is to "move" (programmatically) all messages from the error queue over to the "standard" queue every XX minute, but somehow that sounds "wrong"
Can anyone give me some advice to how this problem situation should be solved ? I`m interested in the solution both from an architectural perspective and from a more technical perspective..
Best regards
Hans-Jacob Melby

Breakpoints, whether normal or conditional, are just meant for debugging of your code. I had the sense from your question that the pausing you want to do is a part of normal operation of your code. I would NOT recommend using a breakpoint for that situation. It would bring up the block diagram showing the breakpoint when it occurs. A user besides the programmer would not know what to do in that case.
Yes, both the inner and outer loops would have shift registers.
Putting a case structure with a small while loop inside the "Pausing Case" is doable. It just depends on what you are doing or waiting for while the program operation is "paused".

JMS Message Acknowledgement

Similar Messages

Maybe you are looking for