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

Rob Stryker (JIRA) issues at jboss.org
Thu May 28 23:28:02 EDT 2015


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

Rob Stryker commented on JBIDE-19641:
-------------------------------------

So I will note that the method in the trace  (waitFor) is simply a busy-loop basically. We're just verifying the monitor isn't canceled, and the future object that jboss client jars returns me isn't "complete" yet.   The busy-loop also increments the progress monitor slightly in what's called an infinite-progress-monitor style... ie,  the monitor keeps moving forward, but slower and slower.   The reason it seems to stop at 72% is because the last 30% or so is done in publish.performFinish(),  so its basically sitting at 99%, which means the infinite progress monitor is just sitting at 99% and has nowhere else to go. 

As for why it's freezing at all, I have absolutely no idea.  The stack traces on both client and server indicate that the threads are all still active and actual transfering should still be occurring as far as I can tell.  I'll ask on wf-dev

> 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.Beta1
>
>         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