"timfox" wrote : Yes please let's take Spring out of the equation. If you can
demonstrate an issue using an MDB we can investigate further...
Famous last words indeed.
The root cause is some oddness with Spring's listener interacting with the tx
manager. So the sending side was working but the
"timfox" wrote : Are you doing this inside the app server?
|
| You can only use the JMS JCA resource adapter (JmsXA) in a managed
environment...
|
Yep, inside a running jboss-4.2.3.GA instance ("default" configuration,
customised with jboss-messaging-1.4.0, 'jgroups.jar' copied over from
"gaohoward" wrote : Can you also give the client code that consume the messages
here? It may help to find the problem.
Sure, though it's very simple stuff:
| public class SimpleListener implements javax.jms.MessageListener {
| private static final Logger LOG =
LoggerFactory.getLogger(Si
"timfox" wrote : Probably spring isn't enlisting the JBM xa resource properly
with the global tx.
|
| But I can't really comment on the internal workings of Spring. You're best
best is to debug the Spring code, or ask a Spring expert.
Ok so, just to be sure, I have discarded the @Transactio
I'm having a problem with Jboss 4.2.3.GA + Jboss messaging 1.4.0SP3. I am
sending multiple messages within a JTA transaction. However, at transaction
commit time, only the first message sent is actually delivered to the
destination (a topic).
My app is Spring-based and I normally use the JmsTem
