OK Adrian. Thanks for taking the time to respond. I just read your workaround
anonymous wrote : | It can be trivially worked around by adding an MBean to the startup sequence that preloads the problem classes on the main thread, thus avoiding the non-thread-safe checking in Sun's code when two threads compete to load classes. | This sounds promising however I have two hurdles to overcome with this. 1) I'm new to mbeans. I understand the basics of what they are but I don't know make one to preload a class. If you could provide an example snippet based on the example exception stack trace and suggest which xml file would be best to put it in I would be extremely grateful! 2) The class that it throws the circularity error on is not exactly the same each time. I find it easy to reproduce the problem since I am opening two jms subscriptions on the same jms connection. However the actual class varies between a variety of different jms related classes (see two examples I provided for two common ones). Would there be a way of just preloading the whole jboss jms jar? Kindest Regards, Gray View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886503#3886503 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886503 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
