[JBoss JIRA] (AS7-6231) Context initialization exceptions are swallowed on deployment
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/AS7-6231?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar commented on AS7-6231:
----------------------------------
Can you provide simple application/example that demonstrates this problem, this way it will be much easier to fix it.
> 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
>
> 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: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6231) Context initialization exceptions are swallowed on deployment
by jarkko rantavuori (JIRA)
jarkko rantavuori created AS7-6231:
--------------------------------------
Summary: 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
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: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6230) Remoting "Read timed out" when starting multiple servers on a host
by Emanuel Muckenhuber (JIRA)
Emanuel Muckenhuber created AS7-6230:
----------------------------------------
Summary: Remoting "Read timed out" when starting multiple servers on a host
Key: AS7-6230
URL: https://issues.jboss.org/browse/AS7-6230
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.3.Final (EAP)
Reporter: Emanuel Muckenhuber
Assignee: Emanuel Muckenhuber
Fix For: 7.2.0.CR1
Apparently when starting multiple servers on a host some of them fail to connect to the HC and the remote connection times out.
--
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
13 years, 4 months