[jboss-jira] [JBoss JIRA] Created: (AS7-1082) NewAbstractModelControllerOperationHandler stuck by logging issues
NewAbstractModelControllerOperationHandler stuck by logging issues
------------------------------------------------------------------
Key: AS7-1082
URL: https://issues.jboss.org/browse/AS7-1082
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Priority: Blocker
Fix For: 7.0.0.CR1
After recent changes on AS7, the
NewAbstractModelControllerOperationHandler$ProxiedInputStream is stuck on wait when
running the JBossWS testsuite, which leverages the
org.jboss.as.webservices.deployer.RemoteDeployer, that uses the management API.
"pool-2-thread-4" prio=10 tid=0x00007ff42402e000 nid=0x66b0 in Object.wait()
[0x00007ff439706000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000000f5aa70d8> (a
org.jboss.as.controller.remote.NewAbstractModelControllerOperationHandler$ProxiedInputStream)
at java.lang.Object.wait(Object.java:502)
at
org.jboss.as.controller.remote.NewAbstractModelControllerOperationHandler$ProxiedInputStream.read(NewAbstractModelControllerOperationHandler.java:159)
- locked <0x00000000f5aa70d8> (a
org.jboss.as.controller.remote.NewAbstractModelControllerOperationHandler$ProxiedInputStream)
at java.io.InputStream.read(InputStream.java:171)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:273)
at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
- locked <0x00000000f5aaa700> (a java.io.BufferedInputStream)
at java.io.FilterInputStream.read(FilterInputStream.java:107)
at
org.jboss.as.server.deployment.repository.impl.ContentRepositoryImpl.addContent(ContentRepositoryImpl.java:100)
- locked <0x00000000e02b6cc8> (a java.security.MessageDigest$Delegate)
at
org.jboss.as.server.deployment.DeploymentAddHandler.execute(DeploymentAddHandler.java:150)
at
org.jboss.as.controller.NewOperationContextImpl.executeStep(NewOperationContextImpl.java:352)
at
org.jboss.as.controller.NewOperationContextImpl.doCompleteStep(NewOperationContextImpl.java:299)
at
org.jboss.as.controller.NewOperationContextImpl.completeStep(NewOperationContextImpl.java:224)
at
org.jboss.as.controller.NewCompositeOperationHandler.execute(NewCompositeOperationHandler.java:84)
at
org.jboss.as.controller.NewOperationContextImpl.executeStep(NewOperationContextImpl.java:352)
at
org.jboss.as.controller.NewOperationContextImpl.doCompleteStep(NewOperationContextImpl.java:299)
at
org.jboss.as.controller.NewOperationContextImpl.completeStep(NewOperationContextImpl.java:224)
at
org.jboss.as.controller.NewModelControllerImpl$DefaultPrepareStepHandler.execute(NewModelControllerImpl.java:350)
at
org.jboss.as.controller.NewOperationContextImpl.executeStep(NewOperationContextImpl.java:352)
at
org.jboss.as.controller.NewOperationContextImpl.doCompleteStep(NewOperationContextImpl.java:299)
at
org.jboss.as.controller.NewOperationContextImpl.completeStep(NewOperationContextImpl.java:224)
at
org.jboss.as.controller.NewModelControllerImpl.execute(NewModelControllerImpl.java:119)
at
org.jboss.as.controller.remote.NewModelControllerClientOperationHandler$ExecuteRequestHandler.writeResponse(NewModelControllerClientOperationHandler.java:107)
at
org.jboss.as.protocol.mgmt.ManagementChannel$RequestReceiver.handleRequest(ManagementChannel.java:137)
at
org.jboss.as.protocol.mgmt.ManagementChannel$RequestReceiver.access$300(ManagementChannel.java:112)
at org.jboss.as.protocol.mgmt.ManagementChannel.doHandle(ManagementChannel.java:63)
at org.jboss.as.protocol.ProtocolChannel.handleMessage(ProtocolChannel.java:149)
at
org.jboss.remoting3.remote.RemoteConnectionChannel$4.run(RemoteConnectionChannel.java:213)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Enabling trace level logs reveals multiple wrong uses of Logger api, causing exceptions
that are swallowed and lost if not on trace level.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira