we're posting messages to a jms queue, 1000 of them, the mdb is marked as required transaction, and it passes control over to a stateless session ejb to do the "business work". the method being called on the slsb is also marked as required transaction. the problem is that not all 1000 messages (orders) get posted to the db. somewhere in there the jms message gets "committed" but the calls to oracle never seem to get there.
we're using oracle's xa driver on wls 8.1 sp2. we know we're running out of oracle connections. my impression is that when we get a connection unavailable or somesuch error message, that the entire transcation should be rolled back.
i noticed that some slsb's are getting static data by calling another slsb in its ejbCreate method. this, could be a potential problem since, the ejbCreate isn't guaranteed to be called until a "business" method is called on the bean. it also could be a problem since the ejbCreate runs under an unspecified transaction context. that shouldn't effect the fact that the mdb is running _in_ a transactional context, no?
i still can't understand how if the mdb is marked as required for transaction, and the slsb throws a create exception because of a problem in it's ejbCreate, why the mdb might not roll back the message to the container?
does anyone have some thoughts on this?
we're planning to increase the db connections in the pool, but i'm afraid that'll hide the problem and not really solve it.
-- i forgot to mention that the mdb is throwing an illegal state exception when it tries to call context.setRollbackOnly() [ August 10, 2004: Message edited by: Mark Lybarger ]