1 of 1 people found this helpful
My guess is that this is most likely a bug in your application, but I wouldn't rule out a bug in JBoss AS itself or HornetQ. In any case, JBoss AS 5 is very old at this point and no longer even supported by current releases of HornetQ. I recommend you upgrade to the latest stable release of Wildfly which will also include a recent release of HornetQ. If you can reproduce the exception there let me know.
We have used Jboss AS 5 for about 7 years. It's a great problem to update it.
The version of HornetQ is 2.00.00.
Community support (i.e. what you get for free on a forum or mailing list like this) is all about the latest and greatest. Just about anybody from the community who helps you is going to have a job whose primary role is something other than providing free support. Since resources are limited it's unlikely anybody is going to devote much effort into investigating issues in old releases that have probably already been fixed. If you can reproduce the issue on a current release then that confirms there is a real issue which means you're more likely to get some help.
If you're stuck on old versions for whatever reason you're simply not likely to get any help. However, if you did the work to make your problem easily reproducible then you'd be more likely to get help.
At this point I recommend you upgrade to the latest stable release of Wildfly, and the next time you start a project think about your upgrade path. If you think you're going to get stuck on a particular version and you still want support then consider purchasing support from Red Hat.
Thank you for your suggestion, we should start the new project with the latest version. in addition, we will think about a strategy to resolve the current problem. replacing the MDB with the new solution.