I can also make the error go away by turning the logging up to max. I think this acts to slow down the server such that the 2nd jms subscription request does not initiate classloading as the the 1st jms subscription request has already loaded the jboss classes required for jms.
The relevant part of the log (when it works) is 10:57:03,414 DEBUG [SocketManager] Begin ReadTask.run 10:57:03,414 DEBUG [SocketManager] Begin WriteTask.run 10:57:03,414 DEBUG [SocketManager] Created ObjectOutputStream 10:57:03,414 DEBUG [SocketManager] Begin ReadTask.run 10:57:03,414 DEBUG [SocketManager] Begin WriteTask.run 10:57:03,445 DEBUG [SocketManager] Created ObjectOutputStream 10:57:03,445 DEBUG [SocketManager] Created ObjectInputStream 10:57:03,445 DEBUG [SocketManager] Created ObjectInputStream Note the 2 successive subscription requests View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886279#3886279 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886279 ------------------------------------------------------- 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
