This was added to the 1.4 branch for the following jira
https://jira.jboss.org/jira/browse/JBMESSAGING-1620
You might try 1.4.4. It should be fixed in that version. If you want to port
the change back to 1.4.1 GA, you can, it's a really easy fix.
http://fisheye.jboss.org/browse/Messaging/bran
Yeah that was my reaction to... We never said we supported that feature.
Which was why I was hesitant to raise it as a jira until speaking with you.
I'll raise it as a feature reqeust and add it in to the next cp. I don't think
there are going to be any side effects from it, but I'll test we
JBM 1.4.0 sp3 CP04
If I want a notification on the server side that a connection has been
closed(either called close on the connection or closed due to network error),
how do you get a server notification.
I've tried to use the aspects, but the connection advised doesn't get called
when the co
When you get alot of messages in memory, we begin to page them to disk. This
is a safeguard so we don't consume all the memory in the box. As consumers
pull messages out of the queues, we pull messages out of the db and load them
back in to memory.
The page ord is the order in which messages
