[jboss-jira] [JBoss JIRA] (AS7-2322) Stack trace improvements, summarize the things that broke to make them not so intimidating

[Neil Doshi (JIRA)]

    [ https://issues.jboss.org/browse/AS7-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717549#comment-12717549 ] 

Neil Doshi commented on AS7-2322:
---------------------------------

Thanks for the response Brian.

The error thrown by spring that I am trying to see is this:

16:00:47,539 ERROR [stderr] (MSC service thread 1-3) org.springframework.beans.factory.BeanDefinitionStoreException: Inv
alid bean definition with name 'underwritingDecisionHandler' defined in ServletContext resource [/WEB-INF/applicationCon
text.xml]: Could not resolve placeholder 'rules.engine.client.underwriting'^M

I could only see this in EAP6 when the RHEL support rep gave me a custom jboss-web module to replace:
modules\org\jboss\as\web\main\jbossweb-7.0.16.Final-redhat-1


In jboss4, which is what we currently run, I was able to see this with the standard libraries that jboss shipped with.

Any ideas on this?
                
> Stack trace improvements, summarize the things that broke to make them not so intimidating
> ------------------------------------------------------------------------------------------
>
>                 Key: AS7-2322
>                 URL: https://issues.jboss.org/browse/AS7-2322
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Jim Tyrrell
>            Assignee: Brian Stansberry
>            Priority: Critical
>              Labels: eap6-ux
>             Fix For: 7.2.0.Alpha1
>
>         Attachments: log.txt
>
>
> See the typical attached stack dump:
> It would be nice if the stack dump could include all of the information above as a summary as shown below, basically just the first lines of the errors w/o the whole stack dump:
> 11:51:45,391 INFO  [org.jboss.as.server.controller] (HttpManagementService-threads - 5) Deployment of "SpringWAR.war" was rolled back with failure message {"Failed services" => {"jboss.web.deployment.default-host./SpringWAR" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./SpringWAR: failed to start context"}}
> 11:51:45,392 INFO  [org.jboss.as.controller] (HttpManagementService-threads - 5) Service status report
>   Services which failed to start:
>       service jboss.web.deployment.default-host./SpringWAR: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./SpringWAR: failed to start context
> 11:51:45,417 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment SpringWAR.war in 26ms
> 11:51:45,417 Error  Summary of Exceptions in deployment:
>  - [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
>  - [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
>  - [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Error listenerStart
>  - ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Context [/SpringWAR] startup failed due to previous errors
>  - [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Closing Spring root WebApplicationContext
>  - [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.web.deployment.default-host./SpringWAR: 
> ERROR Scroll up to see more info...
> Or 
> 11:51:45,417 Error  Summary of Exceptions in deployment:
>  [1] [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
>  [2] [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
>  [3] [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Error listenerStart
>  [4] ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Context [/SpringWAR] startup failed due to previous errors
>  [5] [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Closing Spring root WebApplicationContext
>  [6] [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.web.deployment.default-host./SpringWAR: 
> ERROR Scroll up to see more info...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira