You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Neo Wang <wa...@hotmail.com> on 2009/09/07 09:08:15 UTC
How to send one message to a topic in MDB?
Environment: JBoss 5.1GA, Active MQ 5.2 embeded broker configuration
I want to send a message to a topic when receiving one message in a MDB, but
it can't be successful all the time, any one can help me? I have struggled
in it about 2 weeks.
It is my sample code:
package com.trading.platform.ejb;
import javax.ejb.MessageDrivenBean;
import javax.ejb.MessageDrivenContext;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.Queue;
import javax.jms.QueueConnectionFactory;
import javax.jms.TextMessage;
import javax.jms.Topic;
import javax.jms.TopicConnection;
import javax.jms.TopicConnectionFactory;
import javax.jms.TopicPublisher;
import javax.jms.TopicSession;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import com.trading.platform.context.ServerContext;
import com.trading.platform.exception.InvokeException;
import com.trading.platform.exception.SystemException;
import com.trading.platform.handler.MessageHandler;
import com.trading.platform.log.ILogger;
import com.trading.platform.log.Logger;
public class OrderResponseMDB implements MessageDrivenBean, MessageListener{
private ILogger logger = Logger.getLogger(this.getClass());
private MessageDrivenContext messageDrivenContext;
private volatile TopicConnectionFactory topicConnnectionFactory;
private volatile Topic topic;
private void getInitialContext(){
try {
Context context = new InitialContext();
topicConnnectionFactory =
(TopicConnectionFactory)context.lookup("java:comp/env/jms/TopicConnectionFactory");
//topic = (Topic)context.lookup("java:comp/env/jms/OrderBroadcastTopic");
if(logger.isDebugEnabled()) logger.debug("Platform:Publisher Topic
Session connnection is created..." );
} catch (NamingException e) {
if(logger.isErrorEnabled()) logger.error("NamingExcetion:" + e);
throw new SystemException("System Error", e);
}
}
public void onMessage(Message inMessage) {
TopicConnection topicConn = null;
try {
if (inMessage instanceof TextMessage) {
TextMessage txtmsg = (TextMessage)inMessage;
System.out.println("MESSAGE BEAN3: Message received:
index="+txtmsg.getText());
topicConn =
topicConnnectionFactory.createTopicConnection();
topicConn.start();
TopicSession topicSession = topicConn.createTopicSession(false,
TopicSession.AUTO_ACKNOWLEDGE);
topic = topicSession.createTopic("topic.orderbroadcast");
TopicPublisher publisher = topicSession.createPublisher(topic);
TextMessage newMsg = topicSession.createTextMessage("11111");
publisher.send(newMsg);
//publisher.close();
//topicSession.close();
topicConn.close();
} else {
System.out.println("WRONG MESSAGE TYPE received: " +
inMessage.getClass().getName());
}
} catch (Throwable t) {
System.out.println("error...");
t.printStackTrace();
messageDrivenContext.setRollbackOnly();
try {
if (topicConn != null) topicConn.close();
System.out.println("MESSAGE BEAN: Rollback:
index="+((TextMessage)inMessage).getText());
} catch (Exception e) {
System.out.println("MESSAGE BEAN: Unable to get index
property because:"+e.getMessage());
e.printStackTrace();
}
throw new RuntimeException(t.getMessage());
}
}
public void ejbCreate(){
System.out.println("ConnectionFactory created...");
getInitialContext();
}
public void ejbRemove(){
}
public void setMessageDrivenContext(MessageDrivenContext
messageDrivenContext){
this.messageDrivenContext = messageDrivenContext;
}
}
The following is the exception information:
14:59:09,601 WARN [Service] Async error occurred:
javax.transaction.xa.XAException: Transaction
'XID:131075:312d613061383764343a313862333a34616134616561303a3662:613061383764343a313862333a34616134616561303a3663'
has not been started.
javax.transaction.xa.XAException: Transaction
'XID:131075:312d613061383764343a313862333a34616134616561303a3662:613061383764343a313862333a34616134616561303a3663'
has not been started.
at
org.apache.activemq.broker.TransactionBroker.getTransaction(TransactionBroker.java:266)
at
org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:208)
at org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:126)
at
org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:95)
at
org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:133)
at
org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:455)
at
org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:639)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:308)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:182)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:210)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:203)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:185)
at java.lang.Thread.run(Thread.java:595)
14:59:09,614 WARN [ActiveMQManagedConnection] Connection failed:
javax.jms.JMSException: Transaction
'XID:131075:312d613061383764343a313862333a34616134616561303a3662:613061383764343a313862333a34616134616561303a3663'
has not been started.
14:59:09,615 WARN [TxConnectionManager] Connection error occured:
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@18936ae[state=NORMAL
mc=org.apache.activemq.ra.ActiveMQManagedConnection@1365339 handles=0
lastUse=1252306749595 permit=false trackByTx=false
mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@191c3ce
context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@ce1472
xaResource=org.apache.activemq.ra.ActiveMQManagedConnection$1@164e48d
txSync=null]
javax.jms.JMSException: Transaction
'XID:131075:312d613061383764343a313862333a34616134616561303a3662:613061383764343a313862333a34616134616561303a3663'
has not been started.
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
at
org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1784)
at
org.apache.activemq.ActiveMQConnection$2$1.run(ActiveMQConnection.java:1705)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.transaction.xa.XAException: Transaction
'XID:131075:312d613061383764343a313862333a34616134616561303a3662:613061383764343a313862333a34616134616561303a3663'
has not been started.
at
org.apache.activemq.broker.TransactionBroker.getTransaction(TransactionBroker.java:266)
at
org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:208)
at org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:126)
at
org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:95)
at
org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:133)
at
org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:455)
at
org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:639)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:308)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:182)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:210)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:203)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:185)
... 1 more
--
View this message in context: http://www.nabble.com/How-to-send-one-message-to-a-topic-in-MDB--tp25325925p25325925.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: How to send one message to a topic in MDB?
Posted by Mick Knutson <mk...@baselogic.com>.
I might be able to help a little.
Here is a blog I am working on that has a Message Driven POJO through
Spring.
http://www.baselogic.com/blog/java/testing-activemq-virtualtopics-using-camel-and-junit
I have a unit test that starts an embedded AMQ broker, then starts a jms
listener for the MDP:
<jms:listener-container client-id="jmsContainer1"
transaction-manager="transactionManager">
<jms:listener id="jmsListener1"
destination="Consumer.1.VirtualTopic.Table.1"
ref="testClient1"
method="onMessage" />
</jms:listener-container>
Then I use Mocks to test I get the messages delivered.
Because as i look at your stack, it seems that the broker might not be
started, and/or your MDB has not successfully connected to your destination.
Maybe Spring can be an easier route?
---
Thank You…
Mick Knutson, President
BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring & Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233
Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---
On Mon, Sep 7, 2009 at 12:08 AM, Neo Wang <wa...@hotmail.com> wrote:
>
> Environment: JBoss 5.1GA, Active MQ 5.2 embeded broker configuration
>
> I want to send a message to a topic when receiving one message in a MDB,
> but
> it can't be successful all the time, any one can help me? I have struggled
> in it about 2 weeks.
>
> It is my sample code:
>
> package com.trading.platform.ejb;
>
> import javax.ejb.MessageDrivenBean;
> import javax.ejb.MessageDrivenContext;
> import javax.jms.Message;
> import javax.jms.MessageListener;
> import javax.jms.Queue;
> import javax.jms.QueueConnectionFactory;
> import javax.jms.TextMessage;
> import javax.jms.Topic;
> import javax.jms.TopicConnection;
> import javax.jms.TopicConnectionFactory;
> import javax.jms.TopicPublisher;
> import javax.jms.TopicSession;
> import javax.naming.Context;
> import javax.naming.InitialContext;
> import javax.naming.NamingException;
>
> import com.trading.platform.context.ServerContext;
> import com.trading.platform.exception.InvokeException;
> import com.trading.platform.exception.SystemException;
> import com.trading.platform.handler.MessageHandler;
> import com.trading.platform.log.ILogger;
> import com.trading.platform.log.Logger;
>
> public class OrderResponseMDB implements MessageDrivenBean,
> MessageListener{
> private ILogger logger = Logger.getLogger(this.getClass());
> private MessageDrivenContext messageDrivenContext;
>
> private volatile TopicConnectionFactory topicConnnectionFactory;
> private volatile Topic topic;
>
> private void getInitialContext(){
> try {
> Context context = new InitialContext();
> topicConnnectionFactory =
>
> (TopicConnectionFactory)context.lookup("java:comp/env/jms/TopicConnectionFactory");
> //topic =
> (Topic)context.lookup("java:comp/env/jms/OrderBroadcastTopic");
> if(logger.isDebugEnabled())
> logger.debug("Platform:Publisher Topic
> Session connnection is created..." );
> } catch (NamingException e) {
> if(logger.isErrorEnabled())
> logger.error("NamingExcetion:" + e);
> throw new SystemException("System Error", e);
> }
> }
>
> public void onMessage(Message inMessage) {
>
> TopicConnection topicConn = null;
> try {
> if (inMessage instanceof TextMessage) {
> TextMessage txtmsg = (TextMessage)inMessage;
>
> System.out.println("MESSAGE BEAN3: Message received:
> index="+txtmsg.getText());
> topicConn =
> topicConnnectionFactory.createTopicConnection();
> topicConn.start();
> TopicSession topicSession =
> topicConn.createTopicSession(false,
> TopicSession.AUTO_ACKNOWLEDGE);
> topic =
> topicSession.createTopic("topic.orderbroadcast");
>
> TopicPublisher publisher =
> topicSession.createPublisher(topic);
> TextMessage newMsg =
> topicSession.createTextMessage("11111");
> publisher.send(newMsg);
>
> //publisher.close();
> //topicSession.close();
> topicConn.close();
> } else {
> System.out.println("WRONG MESSAGE TYPE received: " +
> inMessage.getClass().getName());
> }
> } catch (Throwable t) {
> System.out.println("error...");
> t.printStackTrace();
> messageDrivenContext.setRollbackOnly();
>
> try {
> if (topicConn != null) topicConn.close();
> System.out.println("MESSAGE BEAN: Rollback:
> index="+((TextMessage)inMessage).getText());
> } catch (Exception e) {
> System.out.println("MESSAGE BEAN: Unable to get
> index
> property because:"+e.getMessage());
> e.printStackTrace();
>
> }
> throw new RuntimeException(t.getMessage());
> }
> }
>
>
> public void ejbCreate(){
> System.out.println("ConnectionFactory created...");
> getInitialContext();
> }
>
> public void ejbRemove(){
>
> }
>
> public void setMessageDrivenContext(MessageDrivenContext
> messageDrivenContext){
> this.messageDrivenContext = messageDrivenContext;
> }
> }
>
> The following is the exception information:
>
> 14:59:09,601 WARN [Service] Async error occurred:
> javax.transaction.xa.XAException: Transaction
>
> 'XID:131075:312d613061383764343a313862333a34616134616561303a3662:613061383764343a313862333a34616134616561303a3663'
> has not been started.
> javax.transaction.xa.XAException: Transaction
>
> 'XID:131075:312d613061383764343a313862333a34616134616561303a3662:613061383764343a313862333a34616134616561303a3663'
> has not been started.
> at
>
> org.apache.activemq.broker.TransactionBroker.getTransaction(TransactionBroker.java:266)
> at
>
> org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:208)
> at
> org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:126)
> at
>
> org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:95)
> at
>
> org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:133)
> at
>
> org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:455)
> at
> org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:639)
> at
>
> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:308)
> at
>
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:182)
> at
>
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
> at
>
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
> at
>
> org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:210)
> at
>
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
> at
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:203)
> at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:185)
> at java.lang.Thread.run(Thread.java:595)
> 14:59:09,614 WARN [ActiveMQManagedConnection] Connection failed:
> javax.jms.JMSException: Transaction
>
> 'XID:131075:312d613061383764343a313862333a34616134616561303a3662:613061383764343a313862333a34616134616561303a3663'
> has not been started.
> 14:59:09,615 WARN [TxConnectionManager] Connection error occured:
>
> org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@18936ae
> [state=NORMAL
> mc=org.apache.activemq.ra.ActiveMQManagedConnection@1365339 handles=0
> lastUse=1252306749595 permit=false trackByTx=false
>
> mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@191c3ce
>
> context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@ce1472
> xaResource=org.apache.activemq.ra.ActiveMQManagedConnection$1@164e48d
> txSync=null]
> javax.jms.JMSException: Transaction
>
> 'XID:131075:312d613061383764343a313862333a34616134616561303a3662:613061383764343a313862333a34616134616561303a3663'
> has not been started.
> at
>
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
> at
>
> org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1784)
> at
>
> org.apache.activemq.ActiveMQConnection$2$1.run(ActiveMQConnection.java:1705)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: javax.transaction.xa.XAException: Transaction
>
> 'XID:131075:312d613061383764343a313862333a34616134616561303a3662:613061383764343a313862333a34616134616561303a3663'
> has not been started.
> at
>
> org.apache.activemq.broker.TransactionBroker.getTransaction(TransactionBroker.java:266)
> at
>
> org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:208)
> at
> org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:126)
> at
>
> org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:95)
> at
>
> org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:133)
> at
>
> org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:455)
> at
> org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:639)
> at
>
> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:308)
> at
>
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:182)
> at
>
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
> at
>
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
> at
>
> org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:210)
> at
>
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
> at
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:203)
> at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:185)
> ... 1 more
>
>
>
> --
> View this message in context:
> http://www.nabble.com/How-to-send-one-message-to-a-topic-in-MDB--tp25325925p25325925.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
Re: How to send one message to a topic in MDB?
Posted by Gary Tully <ga...@gmail.com>.
can you validate your usage with the current 5.3-SNAPSHOT, we will be
generating a release candidate from there over the next few days and it
would be good to get completion on this.
2009/9/9 Gary Tully <ga...@gmail.com>
> think that should be resolved, the broker sees a single XA identifier and
> jboss sees a single XAResource. So long as the completion occurs on only one
> of the threads (as it should) it will work.
>
> 2009/9/9 andrewsomesyoung <ay...@digitalreefinc.com>
>
>
>>
>> Gary Tully wrote:
>> >
>> > Andy, I think you are experiencing
>> > https://issues.apache.org/activemq/browse/AMQ-2346 which was recently
>> > resolved on trunk. The ended transaction map allows joined contexts to
>> > share
>> > the outcome of a transaction,
>> >
>>
>> Gary, not knowing the details behind
>> https://issues.apache.org/activemq/browse/AMQ-2346, it's not as obvious
>> to
>> me that this is the same issue. The problem I am seeing seems pretty
>> straightforward: the JBoss transaction code is sending multiple start
>> messages to the ActiveMQ XAResource, passing a flag of TMJOIN on the
>> second
>> one, as it seems the JTA specification says to do. This behaviour works as
>> designed. The ActiveMQ XAResource delegates the start to its
>> TransactionContext, which very clearly can not handle TMJOIN or TMRESUME
>> flags. (They're commented out in a TODO). The result is both start
>> messages
>> are sent over the wire to the ActiveMQ broker, which passes them on to two
>> separate threads. If the timing is right, the first thread removes the
>> transaction from the TransactionBroker and then the second thread tries to
>> access it resulting in the "XA Transaction ... has not been started"
>> error.
>>
>> If this has been fixed in trunk, then I am excited to hear it.
>>
>> Andy
>> --
>> View this message in context:
>> http://www.nabble.com/How-to-send-one-message-to-a-topic-in-MDB--tp25325925p25364792.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> http://blog.garytully.com
>
> Open Source Integration
> http://fusesource.com
>
--
http://blog.garytully.com
Open Source Integration
http://fusesource.com
Re: How to send one message to a topic in MDB?
Posted by Gary Tully <ga...@gmail.com>.
think that should be resolved, the broker sees a single XA identifier and
jboss sees a single XAResource. So long as the completion occurs on only one
of the threads (as it should) it will work.
2009/9/9 andrewsomesyoung <ay...@digitalreefinc.com>
>
>
> Gary Tully wrote:
> >
> > Andy, I think you are experiencing
> > https://issues.apache.org/activemq/browse/AMQ-2346 which was recently
> > resolved on trunk. The ended transaction map allows joined contexts to
> > share
> > the outcome of a transaction,
> >
>
> Gary, not knowing the details behind
> https://issues.apache.org/activemq/browse/AMQ-2346, it's not as obvious to
> me that this is the same issue. The problem I am seeing seems pretty
> straightforward: the JBoss transaction code is sending multiple start
> messages to the ActiveMQ XAResource, passing a flag of TMJOIN on the second
> one, as it seems the JTA specification says to do. This behaviour works as
> designed. The ActiveMQ XAResource delegates the start to its
> TransactionContext, which very clearly can not handle TMJOIN or TMRESUME
> flags. (They're commented out in a TODO). The result is both start messages
> are sent over the wire to the ActiveMQ broker, which passes them on to two
> separate threads. If the timing is right, the first thread removes the
> transaction from the TransactionBroker and then the second thread tries to
> access it resulting in the "XA Transaction ... has not been started" error.
>
> If this has been fixed in trunk, then I am excited to hear it.
>
> Andy
> --
> View this message in context:
> http://www.nabble.com/How-to-send-one-message-to-a-topic-in-MDB--tp25325925p25364792.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
--
http://blog.garytully.com
Open Source Integration
http://fusesource.com
Re: How to send one message to a topic in MDB?
Posted by andrewsomesyoung <ay...@digitalreefinc.com>.
Gary Tully wrote:
>
> Andy, I think you are experiencing
> https://issues.apache.org/activemq/browse/AMQ-2346 which was recently
> resolved on trunk. The ended transaction map allows joined contexts to
> share
> the outcome of a transaction,
>
Gary, not knowing the details behind
https://issues.apache.org/activemq/browse/AMQ-2346, it's not as obvious to
me that this is the same issue. The problem I am seeing seems pretty
straightforward: the JBoss transaction code is sending multiple start
messages to the ActiveMQ XAResource, passing a flag of TMJOIN on the second
one, as it seems the JTA specification says to do. This behaviour works as
designed. The ActiveMQ XAResource delegates the start to its
TransactionContext, which very clearly can not handle TMJOIN or TMRESUME
flags. (They're commented out in a TODO). The result is both start messages
are sent over the wire to the ActiveMQ broker, which passes them on to two
separate threads. If the timing is right, the first thread removes the
transaction from the TransactionBroker and then the second thread tries to
access it resulting in the "XA Transaction ... has not been started" error.
If this has been fixed in trunk, then I am excited to hear it.
Andy
--
View this message in context: http://www.nabble.com/How-to-send-one-message-to-a-topic-in-MDB--tp25325925p25364792.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: How to send one message to a topic in MDB?
Posted by Gary Tully <ga...@gmail.com>.
Andy, I think you are experiencing
https://issues.apache.org/activemq/browse/AMQ-2346 which was recently
resolved on trunk. The ended transaction map allows joined contexts to share
the outcome of a transaction,
2009/9/8 andrewsomesyoung <ay...@digitalreefinc.com>
>
> Neo,
>
> I believe I am struggling with the same problem. From what I have learned
> so
> far, it appears that the JBoss TransactionManager sends two "start"
> messages
> to ActiveMQ: the first when the transaction is started upon receiving the
> first message in the MDB, and the second when the outgoing connection is
> created. What I have seen is that the ActiveMQ broker spawns two threads to
> handle these messages, effectively treating them like separate
> transactions.
> Often the first thread will remove the transaction before the second thread
> sends. When that happens the second thread throws an exception because it
> can't find the transaction. Upon further inspection of the JBoss code, it
> looks like JBoss correctly identifies the fact that it has already started
> a
> transaction with the broker and signals that by including the TMJOIN flag
> when starting the resource the second time. Looking at the code for
> org.apache.activemq.TransactionContext, its pretty obvious ActiveMQ doesn't
> handle this TMJOIN flag at all.
>
> I am still looking for a solution myself but I hope this sheds some light
> on
> your problem and inspires someone who knows more about what is supposed to
> happen to chime in.
>
> Andy
>
>
> --
> View this message in context:
> http://www.nabble.com/How-to-send-one-message-to-a-topic-in-MDB--tp25325925p25355114.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
--
http://blog.garytully.com
Open Source Integration
http://fusesource.com
Re: How to send one message to a topic in MDB?
Posted by Neo Wang <wa...@hotmail.com>.
Thanks a lot for your information. I have found the solution to resolve the
problem, you can try to change the value of "UseInboundSession" to "true"
from "false" in ra.xml, then you will find it is OK. But the disadvantage of
this solution is you cannot use this configuration outside of MDB, otherwise
the exception will be thrown. Hope it helps to you.
andrewsomesyoung wrote:
>
> Neo,
>
> I believe I am struggling with the same problem. From what I have learned
> so far, it appears that the JBoss TransactionManager sends two "start"
> messages to ActiveMQ: the first when the transaction is started upon
> receiving the first message in the MDB, and the second when the outgoing
> connection is created. What I have seen is that the ActiveMQ broker spawns
> two threads to handle these messages, effectively treating them like
> separate transactions. Often the first thread will remove the transaction
> before the second thread sends. When that happens the second thread throws
> an exception because it can't find the transaction. Upon further
> inspection of the JBoss code, it looks like JBoss correctly identifies the
> fact that it has already started a transaction with the broker and signals
> that by including the TMJOIN flag when starting the resource the second
> time. Looking at the code for org.apache.activemq.TransactionContext, its
> pretty obvious ActiveMQ doesn't handle this TMJOIN flag at all.
>
> I am still looking for a solution myself but I hope this sheds some light
> on your problem and inspires someone who knows more about what is supposed
> to happen to chime in.
>
> Andy
>
>
>
--
View this message in context: http://www.nabble.com/How-to-send-one-message-to-a-topic-in-MDB--tp25325925p25357582.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: How to send one message to a topic in MDB?
Posted by andrewsomesyoung <ay...@digitalreefinc.com>.
Neo,
I believe I am struggling with the same problem. From what I have learned so
far, it appears that the JBoss TransactionManager sends two "start" messages
to ActiveMQ: the first when the transaction is started upon receiving the
first message in the MDB, and the second when the outgoing connection is
created. What I have seen is that the ActiveMQ broker spawns two threads to
handle these messages, effectively treating them like separate transactions.
Often the first thread will remove the transaction before the second thread
sends. When that happens the second thread throws an exception because it
can't find the transaction. Upon further inspection of the JBoss code, it
looks like JBoss correctly identifies the fact that it has already started a
transaction with the broker and signals that by including the TMJOIN flag
when starting the resource the second time. Looking at the code for
org.apache.activemq.TransactionContext, its pretty obvious ActiveMQ doesn't
handle this TMJOIN flag at all.
I am still looking for a solution myself but I hope this sheds some light on
your problem and inspires someone who knows more about what is supposed to
happen to chime in.
Andy
--
View this message in context: http://www.nabble.com/How-to-send-one-message-to-a-topic-in-MDB--tp25325925p25355114.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.