[jbosstools-issues] [JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck

Martin Malina (JIRA) issues at jboss.org
Tue Jul 21 05:17:04 EDT 2015 

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

Martin Malina commented on JBIDE-19641:
---------------------------------------

[~rob.stryker], I tested this with EAP 6.4, WF 8.2, 9.0 and AS 7.1.1 and it works with all but AS 7.1.1.
{code}
Could not publish to the server.
java.util.concurrent.ExecutionException: Operation failed
{code}
Server log:
{code}
11:10:52,883 ERROR [org.jboss.remoting.remote.connection] (Remoting "nattura:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
11:11:21,566 ERROR [stderr] (Remoting "nattura:MANAGEMENT" task-3) Exception in thread "Remoting "nattura:MANAGEMENT" task-3" java.lang.OutOfMemoryError: Java heap space
11:11:21,567 ERROR [stderr] (Remoting "nattura:MANAGEMENT" task-3) 	at org.jboss.as.controller.remote.OperationAttachmentsProxy$ProxiedInputStream$1.handleRequest(OperationAttachmentsProxy.java:151)
11:11:21,567 ERROR [stderr] (Remoting "nattura:MANAGEMENT" task-3) 	at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:245)
11:11:21,568 ERROR [stderr] (Remoting "nattura:MANAGEMENT" task-3) 	at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleRequest(AbstractMessageHandler.java:210)
11:11:21,568 ERROR [stderr] (Remoting "nattura:MANAGEMENT" task-3) 	at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:113)
11:11:21,569 ERROR [stderr] (Remoting "nattura:MANAGEMENT" task-3) 	at org.jboss.as.protocol.mgmt.ManagementChannelReceiver$1.handleMessage(ManagementChannelReceiver.java:57)
11:11:21,569 ERROR [stderr] (Remoting "nattura:MANAGEMENT" task-3) 	at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:79)
11:11:21,570 ERROR [stderr] (Remoting "nattura:MANAGEMENT" task-3) 	at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:437)
11:11:21,570 ERROR [stderr] (Remoting "nattura:MANAGEMENT" task-3) 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
11:11:21,572 ERROR [stderr] (Remoting "nattura:MANAGEMENT" task-3) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
11:11:21,573 ERROR [stderr] (Remoting "nattura:MANAGEMENT" task-3) 	at java.lang.Thread.run(Thread.java:695)
11:11:21,693 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014612: Operation ("add") failed - address: ([("deployment" => "dynproj.war")]): java.lang.RuntimeException: JBAS014761: Thread was interrupted waiting to read attachment input stream from remote caller
	at org.jboss.as.controller.remote.OperationAttachmentsProxy$ProxiedInputStream.read(OperationAttachmentsProxy.java:111) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
	at java.io.InputStream.read(InputStream.java:151) [classes.jar:1.6.0_65]
	at java.io.BufferedInputStream.read1(BufferedInputStream.java:256) [classes.jar:1.6.0_65]
	at java.io.BufferedInputStream.read(BufferedInputStream.java:317) [classes.jar:1.6.0_65]
	at java.io.FilterInputStream.read(FilterInputStream.java:90) [classes.jar:1.6.0_65]
	at org.jboss.as.repository.ContentRepository$Factory$ContentRepositoryImpl.addContent(ContentRepository.java:150)
	at org.jboss.as.server.deployment.DeploymentAddHandler.addFromContentAdditionParameter(DeploymentAddHandler.java:191)
	at org.jboss.as.server.deployment.DeploymentAddHandler.execute(DeploymentAddHandler.java:147)
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.controller.CompositeOperationHandler.execute(CompositeOperationHandler.java:85) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:466) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:287) [jboss-as-protocol-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:487) [jboss-as-protocol-7.1.1.Final.jar:7.1.1.Final]
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_65]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_65]
	at java.lang.Thread.run(Thread.java:695) [classes.jar:1.6.0_65]
	at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
{code}
Error view:
{code}
org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.util.concurrent.ExecutionException: Operation failed
	at org.jboss.ide.eclipse.as.internal.management.wildfly9.DeploymentOperationResult.getStatus(DeploymentOperationResult.java:54)
	at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.waitFor(Wildfly9Manager.java:149)
	at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.deploySync(Wildfly9Manager.java:159)
	at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.deploySync(Wildfly9ManagerService.java:111)
	at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.deploySync(JBoss7ManagerServiceProxy.java:53)
	at org.jboss.ide.eclipse.as.internal.management.as71x.JBoss71xManagerService.deploySync(JBoss71xManagerService.java:62)
	at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.deploySync(JBoss7ManagerServiceProxy.java:53)
	at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.publishModule(ManagementPublishController.java:287)
	at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:143)
	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
	at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3157)
	at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.util.concurrent.ExecutionException: Operation failed
	at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
	at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268)
	at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:57)
	at org.jboss.as.controller.client.impl.ConvertingDelegatingAsyncFuture.get(ConvertingDelegatingAsyncFuture.java:64)
	at org.jboss.as.controller.client.impl.ConvertingDelegatingAsyncFuture.get(ConvertingDelegatingAsyncFuture.java:41)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:76)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
	at org.jboss.ide.eclipse.as.internal.management.wildfly9.DeploymentOperationResult.getStatus(DeploymentOperationResult.java:51)
	... 15 more
Caused by: org.xnio.BrokenPipeException: Remote side closed the message stream
	at org.jboss.remoting3.remote.OutboundMessage$1.accept(OutboundMessage.java:124)
	at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:122)
	at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:110)
	at org.xnio.streams.BufferPipeOutputStream.getBuffer(BufferPipeOutputStream.java:74)
	at org.xnio.streams.BufferPipeOutputStream.write(BufferPipeOutputStream.java:92)
	at org.jboss.remoting3.remote.OutboundMessage.write(OutboundMessage.java:272)
	at java.io.DataOutputStream.write(DataOutputStream.java:107)
	at org.jboss.as.protocol.mgmt.FlushableDataOutputImpl.write(FlushableDataOutputImpl.java:49)
	at org.jboss.as.protocol.StreamUtils.copyStream(StreamUtils.java:60)
	at org.jboss.as.controller.client.helpers.standalone.impl.DeploymentPlanBuilderImpl$FileStreamEntry.copyStream(DeploymentPlanBuilderImpl.java:440)
	at org.jboss.as.controller.client.impl.AbstractModelControllerClient$ReadAttachmentInputStreamRequestHandler$1.execute(AbstractModelControllerClient.java:227)
	at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:298)
	at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
	at org.jboss.threads.JBossThread.run(JBossThread.java:320)
{code}

I guess we can live AS 7.1.1 not working, but I'm wondering why that would be since you said it should work with AS 7.1.

> Big war deployment via management API gets stuck
> ------------------------------------------------
>
>                 Key: JBIDE-19641
>                 URL: https://issues.jboss.org/browse/JBIDE-19641
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.3.0.Alpha2
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.3.0.Beta2
>
>         Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log
>
>
> When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through.
> This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

More information about the jbosstools-issues mailing list