This content has been marked as final. Show 1 reply
Couple of things...
- I moved your post from the HornetQ Development forum (meant for discussion about the development of HornetQ itself) to the HornetQ User forum (meant for discussions about using HornetQ).
- Can you be more specific about the issue you're facing? The linked forum post is regarding a classloading issue when using an un-managed message listener in a Java EE container. Are you using an un-managed message listener in JBoss EAP 6.1 and hitting a classloading problem? If so, I think the code solution outlined there would probably be your best solution. The issue here is that since the message listener is un-managed the container is not able to make an intelligent choice about what classloader to set for it (something which is done for message driven beans which are managed message listeners) so you have to do it manually. Another way to solve this would be to not use un-managed message listeners in the container. In my opinion they are generally not a good idea anyway.