I also tried isolating the war outside the ear and didn't get any new info.ġ8:29:10,704 INFO (MSC service thread 1-6) JBAS015540: Stopping service .endpoint.''.'(mycompany)ws.war'.'(ourpackage).(DomainObject)WServiceImpl' That's also how I know I can access the libs. I have started by taking an empty war, adding the libs, and adding relevant classes, 1-by-1.I've managed to get a very tiny subsection of the app to deploy. I'm not sure what that's about, but I am otherwise able to use the libs. I got a lot like of warning statements from my POM dependencies:ġ7:27:13,496 WARN (MSC service thread 1-8) Class Path entry commons-beanutils.jar in '/C:/tools/axeda-jboss-as-7.1.1.Final/bin/content//(mycompany)ws.war/WEB-INF/lib/struts-1.1.jar' does not point to a valid jar for a Class-Path reference. There was a WARN here and there, but nothing near the stacktrace and the ones I could find didn't seem related to rejecting a deployment. It is a large legacy app, of varying quality, so I came into this expected quite bit of work to be done to get it running on EAP6. Would I have any more luck on EAP6 Beta? This app will go on EAP, but I am jumpstarting the port on AS7 so we can be ready whenever it is finally released. The console output matches server.log from what I can tell. There were no stracktraces or ERROR messages. Hello Jaikiran, the exact version was 7.1.1.Final.

Roll back java update