Everyone, This one was all our fault. We had some conflicting JARs due to a recent integration with another product. The core JBoss JARs were replicated in multiple areas within the deploy directory. We removed these offending duplicate JARs and everything is back to operating as normal.
For those who did, thanks for taking a look, and hopefully someone else can benefit from this mistake. Brian View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865728#3865728 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865728 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
