Hi
I deploy 2 ear files at the same time A.ear and B.ear. Jboss always deploys
B.ear first, but I would like it to start with A.ear instead.
The problem is that B contains some JMS structures, and when there are messages
in the persistent store on startup of jboss, the MDB's fails because they
[EMAIL PROTECTED] wrote :
| * Not using pooled transactional jms resource adapter
Is this not fixed this by using java:/JmsXA as connection factory, as
configured in my earlier post ?
anonymous wrote :
| * Not using said pooled resource as a pool instead allocating resources per
ejb
That seemed to solve my problem about committing automatically.
But I still have a problem with the scenario. In a MDB onMessage method I
change/create some entity beans and send a message. Both changes are committed
successfully on exit of the onMessage method. The message sent then reaches
I have now read this wiki entry
http://wiki.jboss.org/wiki/Wiki.jsp?page=MyJMSReceiverCannotSeeADBUpdateMadeInTheSameTransactionAsASend
and understand that 2 phase commits does not guarantee that when the
transaction is done, all datasources has completed their commit operations. The
wiki
Well I found out that I needed to lookup java:/JmsXA as the ConnectionFactory.
I thought I already did that before and got a ClassCast Exception, but I guess
I did something else wrong at that time.
So could you please be a little more specifc about what else im doing wrong.
Also I have read
Hi
I have a annoying problem with JMS and transactions. From a Session bean with
trans-attribute=Required I construct a message and send it to a Queue. I want
the QueueSession to synchronize its commit with the SessionBean's commit, but
the QueueSession is never being committed.
I Create the
Hi
As of what I can understand, the default jms behaviour when used in transacted
beans is to automatically commit/rollback the QueueSessions used when the beans
transactions is committed/rollbacked
But I can seem to get this behaviour working. In the ejbCreate method of a
stateless
