What you posted is an excerpt from the report that the deployer logs after depliyment is done. This rpeort rarely offers any clues as to what went wrong. You need to search the console log for the first exception stack trace that shows up after that the app server and post that stack trace.
If the console log scrolled off of the console buffer, you will either have to increase the console buffer size (I have mine set to 9000 lines) and try again, or look the exception up in the server.log files (usually difficult because various stack traces show up as debug log entries and those are not important), or start JBossAS up without having your app deployed then wait until you see the "Started in xxx seconds" log entry and then deploy your app - you can then post everything after the "Started in" entry. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177253#4177253 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177253 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
