I am observing, via CMP log records (and poor system performance), unexpected
relationship loading behavior by JBoss CMP.
No document I've seen has been clear on how CMR works with read-ahead, so I'm
not really sure what I should expect.
The situation:
* JBoss 4.0.2
* Two entities, A and B, wit
So your saying the enlistment of the JMS Session as an XA resource has nothing
to do with JBM (or is completely orthogonal to it)? If not, is there anything
explicit I can do to make this work?
Just curious: the connection factory name java:/JmsXA I'm using returns a
JmsConnectionFactory. Sno
So can I take it that what I am trying to do should be doable?
ataylor: I am using what comes bundled with 4.0.2. I can try moving to 4.2.2
just to know, if you're saying that this pattern is not supported under 4.0.2,
but 4.0.2 is still our production environment.
timfox: The example I used c
I am on 4.0.2
Here is the Interceptor:
package test;
import org.jboss.invocation.Invocation;
import org.jboss.ejb.Interceptor;
import org.jboss.ejb.Container;
import org.jboss.ejb.EntityContainer;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.jms.*;
import javax.
Following the advice in the wiki page:
http://wiki.jboss.org/wiki/JBMXADataSource,
I've almost got it working, except for the intended behavior, which I'm not
seeing.
What I want is for a server component, when a certain event occurs, to send a
message. However, if the transaction that
is
