December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6231) Context initialization exceptions are swallowed on deployment

by jarkko rantavuori (JIRA)

[ https://issues.jboss.org/browse/AS7-6231?page=com.atlassian.jira.plugin.s... ] jarkko rantavuori updated AS7-6231: ----------------------------------- Attachment: jboss-7.2.0.-stacktrace-namespace.txt jboss-7.1.1.-stacktrace-beans.txt jboss-7.1.1.-stacktrace-namespace.txt > 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 > > > 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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6086) Deadlock in org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/AS7-6086?page=com.atlassian.jira.plugin.s... ] Eduardo Martins reassigned AS7-6086: ------------------------------------ Assignee: Eduardo Martins (was: jaikiran pai) > Deadlock in org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler > --------------------------------------------------------------------------------------- > > Key: AS7-6086 > URL: https://issues.jboss.org/browse/AS7-6086 > Project: Application Server 7 > Issue Type: Bug > Components: EJB, Remoting > Affects Versions: 7.1.3.Final (EAP) > Environment: Doesn't matter. > Reporter: Krzysztof Noceń > Assignee: Eduardo Martins > Fix For: No Release > > > Class: > {code} > org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler > {code} > Method: > {code} > public void processMessage(ChannelAssociation, MessageInputStream) throws IOException; > {code} > This code fragment: > {code} > try { > methodParams[i] = unmarshaller.readObject(); > } catch (ClassNotFoundException cnfe) { > /.../ > return; > } > {code} > doesn't catch *java.lang.IllegalArgumentException*. > This causes the server hangs. > Example stacktrace: > {code} > java.lang.IllegalArgumentException: No enum const org.example.ExampleEnum.ENUM_VALUE > at java.lang.Enum.valueOf(Enum.java:196) > at org.jboss.marshalling.river.RiverUnmarshaller.resolveEnumConstant(RiverUnmarshaller.java:1549) > at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1293) > at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272) > at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209) > at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.processMessage(MethodInvocationMessageHandler.java:164) > at org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver.handleMessage(VersionOneProtocolChannelReceiver.java:182) > at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:429) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > {code} > I caught *java.lang.Exception*. It helps. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-5946) jboss-ejb3.xml faults fail silently and result in a hanging thread

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/AS7-5946?page=com.atlassian.jira.plugin.s... ] Eduardo Martins reassigned AS7-5946: ------------------------------------ Assignee: Eduardo Martins (was: David Lloyd) > jboss-ejb3.xml faults fail silently and result in a hanging thread > ------------------------------------------------------------------ > > Key: AS7-5946 > URL: https://issues.jboss.org/browse/AS7-5946 > Project: Application Server 7 > Issue Type: Bug > Components: EE, EJB > Affects Versions: 7.1.3.Final (EAP), 7.2.0.Alpha1 > Environment: MacOS X 10.8.2 > java version "1.6.0_35" > Java(TM) SE Runtime Environment (build 1.6.0_35-b10-428-11M3811) > Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01-428, mixed mode) > Reporter: Stephen Coy > Assignee: Eduardo Martins > Attachments: migration-demo.tar.gz > > > The attached maven application project has a subtle typo in a JNDI name in the jboss-ejb3.xml file. > The deployment process results in a hanging thread shown below. There are no diagnostic log messages at all to indicate what the problem could be. > A second consequence of this hung thread is that the server process can only be terminated with a "kill -9 <pid>". > Note that it is deliberately a JEE5 compatible application. > "management-handler-thread - 4" prio=5 tid=7f843c0bf000 nid=0x10a866000 in Object.wait() [10a864000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <7d42d05f8> (a org.jboss.as.controller.ContainerStateMonitor) > at java.lang.Object.wait(Object.java:485) > at org.jboss.as.controller.ContainerStateMonitor.awaitContainerStateChangeReport(ContainerStateMonitor.java:158) > - locked <7d42d05f8> (a org.jboss.as.controller.ContainerStateMonitor) > at org.jboss.as.controller.ModelControllerImpl.awaitContainerStateChangeReport(ModelControllerImpl.java:442) > at org.jboss.as.controller.OperationContextImpl.awaitModelControllerContainerMonitor(OperationContextImpl.java:147) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:261) > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) > at org.jboss.as.server.deployment.DeploymentHandlerUtil$1.execute(DeploymentHandlerUtil.java:123) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) > at org.jboss.as.server.deployment.DeploymentDeployHandler.execute(DeploymentDeployHandler.java:75) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) > at org.jboss.as.server.deployment.DeploymentAddHandler.execute(DeploymentAddHandler.java:168) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) > at org.jboss.as.controller.CompositeOperationHandler.execute(CompositeOperationHandler.java:85) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) > at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:473) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:126) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:111) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:680) > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Locked ownable synchronizers: > - <7d42a5150> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) > - <7d4f3b598> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-5368) Lookup of UserTransaction should not be allowed in CMT beans

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/AS7-5368?page=com.atlassian.jira.plugin.s... ] Eduardo Martins reassigned AS7-5368: ------------------------------------ Assignee: Eduardo Martins (was: jaikiran pai) > Lookup of UserTransaction should not be allowed in CMT beans > ------------------------------------------------------------ > > Key: AS7-5368 > URL: https://issues.jboss.org/browse/AS7-5368 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.2.0.Alpha1 > Reporter: Cheng Fang > Assignee: Eduardo Martins > > EJB spec 8.3.4 Enterprise Beans Using Container-Managed Transaction Demarcation: > The enterprise bean’s business methods, message listener methods, business method interceptor meth- ods, lifecycle callback interceptor methods, or timeout callback methods must not attempt to obtain or use the javax.transaction.UserTransaction interface. > Currently lookup("java:comp/UserTransaction") returns an instance of org.jboss.tm.usertx.client.ServerVMClientUserTransaction. > Similar to AS7-5331 -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6082) EJbLogger contains messages that should be in EjbMessages

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/AS7-6082?page=com.atlassian.jira.plugin.s... ] Eduardo Martins reassigned AS7-6082: ------------------------------------ Assignee: Eduardo Martins (was: jaikiran pai) > EJbLogger contains messages that should be in EjbMessages > --------------------------------------------------------- > > Key: AS7-6082 > URL: https://issues.jboss.org/browse/AS7-6082 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Reporter: Stuart Douglas > Assignee: Eduardo Martins > Priority: Minor > > The EjbLogger class also contains exception messages, not just log messages. > It also has two loggers (ROOT_LOGGER and EJB3_LOGGER) with the same package name, it would be good to get rid of one of them. -- 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

12 years

1
0
0 / 0

[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

12 years

1
0
0 / 0

[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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6227) DeploymentBrowser doesn't work in web mode

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/AS7-6227?page=com.atlassian.jira.plugin.s... ] Harald Pehl commented on AS7-6227: ---------------------------------- Additional info: Empty groups work. As soon as a deployment is assigned the deployment browser is broken. > DeploymentBrowser doesn't work in web mode > ------------------------------------------ > > Key: AS7-6227 > URL: https://issues.jboss.org/browse/AS7-6227 > Project: Application Server 7 > Issue Type: Bug > Components: Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Priority: Critical > Fix For: 7.2.0.CR1 > > -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6228) jboss-deployment-structure.xml with no namespace should threated as latest version

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6228?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-6228: ----------------------------- Issue Type: Bug (was: Feature Request) > jboss-deployment-structure.xml with no namespace should threated as latest version > ---------------------------------------------------------------------------------- > > Key: AS7-6228 > URL: https://issues.jboss.org/browse/AS7-6228 > Project: Application Server 7 > Issue Type: Bug > Components: Server > Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP) > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 7.2.0.Alpha1 > > > If you don't specify the namespace version for the jboss-deployment-structure.xml it parses it as 1.1 version and not as 1.2 which is currently the latest. -- 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

12 years

1
0
0 / 0

[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

12 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2012