Thank you for our answers. jaikiran were absolutely right - the bean used
Container managed transaction. I added a:
@TransactionManagement( value=TransactionManagementType.BEAN)
annotation and now it works as a charm, concurrently processing and sending
messages.
The "normal" use case of the J
anonymous wrote : If I wish to send a large number of messages in sequence, the
MessageListener won't start processing the messages until the sender has
finished sending all its messages - the while()-loop has ended and the method
invoked in the Stateless Session EJB has finished.
This is what
Hey
Reading the explanation of your problem, I would suspect that it is a design
issue and hardware limitations. Here is what I think. You probably have a
single processor machine and while publishing the messages in the loop you
taking most of the resources of the machine. Also, since message
