Its taken me a while to get back to this test and try your recommendations. I
agree that the test code was not conserving resources the way it was written,
but I did not give thought to the fact that the session and publisher was being
created in a transaction and the publish was created in
I see the transaction rolling back:
anonymous wrote :
| 2004-12-17 17:21:01,465 TRACE [org.jboss.tm.TransactionImpl] rollback():
Entered, tx=TransactionImpl
| :XidImpl[FormatId=257, GlobalId=BLITZ/22, BranchQual=, localId=22]
status=STATUS
| _MARKED_ROLLBACK
|
I don't see any
Sorry fot the omission on org.jboss.mq. The following trace appears to have the
mq trace messages from the time the session bean publishes the message, thru
when the client begins to receive it.
thanks,
| 2004-12-20 14:07:42,660 TRACE [org.jboss.mq.SpyMessageProducer] Sending
message
anonymous wrote :
| 2004-12-20 14:07:42,660 TRACE [org.jboss.mq.SpyXAResourceManager] No Xid,
sending message to server
| ID:2-11035696626603
|
It's not enlisted in the transaction.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3859339#3859339
Reply
And of course the answer is obvious:
anonymous wrote :
| //from ejbCreate()
| ConnectionFactory cFactory = (ConnectionFactory)
| jndi.lookup(java:comp/env/jms/myConnectionFactory);
| Connection connection = cFactory.createConnection();
| session_ =
Show the trace logging so we can see what is happening.
org.jboss.ejb.plugins.TxInterceptorCMT or
org.jboss.resource
org.jboss.tm
would also be useful so we can see the transaction demarcation
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3859079#3859079
Reply
I want to make sure I'm doing what you intend to get you the information you've
requested.
* show trace logging. I'm assuming that means go into conf/log4j.xml and add
the following lines:
| category name=org.jboss.ejb.plugins.TxInterceptorCMT
|priority value=DEBUG/
| /category
|
TRACE is what is required. See the examples in READ THIS FIRST.
Also make sure you are not filtering the level on the appender.
I won't need your DEBUG logging.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3859115#3859115
Reply to the post :
This looks to be more of what you were after. This is the result of the session
EJB throwing EJBException after publishing the JMS message. ...
thanks for taking a look at it.
| 2004-12-17 17:21:01,465 TRACE
[org.jboss.resource.connectionmanager.CachedConnectionManager] popped object:
From what I have come to know true means use internal transactions, which
would require one to use manual calls to commit()/rollback() on the session.
false either means none at all (similar to JDBC autocommit=false) when no
JTA is active or part of the JTA when using an XAConnection factory.
I thought if it was transacted, you have to use true when creating
QueueSession:
session_ = connection.createSession(true, 0);
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3857403#3857403
Reply to the post :
I changed my session to transacted=true (and the printed debug stated this was
the case). However, it worked the same as the transacted=false case.
According to what I've read and experienced with WebLogic JMS, transacted=true
means to use JMS internal transactions (thus use commit()/rollback()
12 matches
Mail list logo
