Inside jboss probably means InVM
InVM has a pretty small latency (no network), so I don't think that should be really an issue.
Are you using MDBs? You will have a TX on every message received anyways.. I don't think you would have an issue here.
yes i'm using invm connection, but with jms messagelistener :
Session session = queueConnection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
MessageConsumer consumer = session.createConsumer(queue, getMessageSelector());
(oh yes i forgot to mention we are using selector on queue ;-) )
Then if in my onMessage() i throw a runtimeException i was thinking that there is only this message that will be placed in scheduling but what happens is that all messages in queue are placed in scheduling.
yes.. that's expected for now at least
ok, maybe i can make a feature request to reintegrate buffered messages directly on queue instead of scheduling them ?
sure. you can do the feature request.
There's also a feature request to pause consuming for a few seconds. not just re-schedule it. A few users were complaining about order issues.