Reporting bugs against old versions is futile (especially when they this one
was fixed/worked around over a year ago).
It is actually a bug in oswego's concurrent.jar
Thanks for the hint. I will replace our concurrent.jar and see how it goes.
We are experiencing the same problem here with 4.0.1, do we need to upgrade the concurrent.jar aswell or does 4.0.1 ship with a fixed version?
Since we upgraded the concurrent.jar, we have not seen this problem re-occur.
I see no harm in trying it out. From the size of the jar distributed with 4.0.1, I suspect it is not the latest version.
Thanks for the heads up.
We are upgrading to the latest concurrent-1.3.4
which has a QueuedExecutor fix.
I examined concurrent.jar from both JBoss 4.0.0 and JBoss 3.2.5. Both of these have the same version of concurrent.jar (ie: 1.3.3) but with different file sizes -
JBoss 4.0.0 - 165 KB
JBoss 3.2.5 - 168KB
For the same MDB issue as reported by Karthik in earlier posts, I want to replace my concurrent.jar in JBoss 3.2.1. Could anybody let me know, which jar should i use...one with JBoss 4.0 or the one with JBoss 3.2.5..?
Also, I could not find ver 1.3.4 for the same. Is it advisable to use that with my JBoss 3.2.1...?
Thanks karthik. Will let you guys know once this is moved into production as well!!! :)
I too have the same issue, my MDB processes 2000-4000 messages from the Q and stops after that. I checked up the console for the number of MDB's and it always shows 0, i tried trace and saw the MDB count is always says using 0/10 free instances in the pool. once MDB stops processing messages, the Q ultimates piles up with messages. I had to restart the server for it to process messages again
we are using Jboss-4.0.4.GA, JDK 1.5.0_09 on sun solaris.
We are having the same problem in a production system running on JBoss 4.0.4 on Windows 2003 server.
Our Message driven bean stops receiving messages, althought the message queue has many messages to deliver.
Up until now the only workaround we found is to restart the application server.
Any ideas on what is causing this problem?
Is there any other workaround?
Thanks in advance
Am facing a similar issue for JBOSS Version: jboss-4.0.5.GA. We have the concurrent.jar of the version 1.3.4. But still this issue is not resolved. Do you have any thoughts on this? Thank you.