This one looks like a very specific bug and needs to be fixed. Can you
please create a JIRA for this and attach that sample project?
As for the overall direction of diagnostics for deployment failures, one
thing that we are considering is improving the service report failure
messages that are usually associated with a deployment failure, to be
more human readable.
-Jaikiran
On Wednesday 14 November 2012 12:20 PM, Stephen Coy wrote:
Hi there,
Has anyone given much thought to providing more diagnostics when things go wrong during
deployment.
For example, I recently encountered a problem with an EAR deployment that failed
silently.
A thread dump revealed that it was stuck at the wait in
org.jboss.as.ee.component.BasicComponent.waitForComponentStart().
I eventually figured out that there was a problem in my jboss-ejb3.xml file, but there
were no clues to go on at all.
Another potential issue with this particular problem is that it's not possible to
perform a regular server shutdown once it's in the state above. A "kill -9"
is required.
I have a sample project that demonstrates this BTW.
Cheers,
Steve Coy
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev