The message is left in the queue when a non-recoverable exception occurs.
Currently only StaleStateException and LockAcquisitionException are treated as
recoverable. System exceptions, such a connection acquisition problem, need
administrative action before proceeding, so they are not recovered
Certainly not a limitation, but an indication that you have to allocate more
resources. JMS persistent messages, EJB timers and jBPM sessions all use
database connections, possibly from different data sources. Does each data
source have a pool large enough?
View the original post :
Thanks for replying Alex.
I can allocate more resources but my main concern is why my messages are left
in the queue. What happens to them after that? When a thread cannot get hold of
any database connection, is that when the message is left in the queue? But I
would imagine the StartListener
