]
Brian Stansberry commented on AS7-6231:
---------------------------------------
There is some logging system property setting that if set results in these message
re-appearing -- disabling per-deployment logging or something. I remember seeing it
recently in a comment on another issue.
I'm not saying that makes this not a bug; it's just a clue to the problem and a
possible workaround.
Context initialization exceptions are swallowed on deployment
-------------------------------------------------------------
Key: AS7-6231
URL:
https://issues.jboss.org/browse/AS7-6231
Project: Application Server 7
Issue Type: Bug
Components: EE
Affects Versions: 7.2.0.Alpha1
Environment: Windows 7
Reporter: jarkko rantavuori
Assignee: David Lloyd
Attachments: jboss-7.1.1.-stacktrace-beans.txt,
jboss-7.1.1.-stacktrace-namespace.txt, jboss-7.2.0.-stacktrace-namespace.txt,
spring-app-1.0.0-BUILD-SNAPSHOT-startupexception.war
On 7.2.0.Alpha1, trying to deploy a simple spring app with problems in context
initialization, all exceptions are swallowed, and only a meaningless error
org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start
context at
org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:161)
is shown, making it impossible to find out the root cause.
On 7.1.1., meaningful exception is shown, like
Configuration problem: Unable to locate Spring NamespaceHandler for XML schema namespace
[
http://www.osgi.org/xmlns/blueprint/v1.0.0]
Offending resource: ServletContext resource [/WEB-INF/spring/root-context.xml]
or
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException
Caused by: org.xml.sax.SAXParseException; lineNumber: 6; columnNumber: 108; cvc-elt.1:
Cannot find the declaration of element 'beans'.
which allows the developer to fix the problem.
--
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: