Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-19641

Big war deployment via management API gets stuck

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.3.0.Beta2
    • 4.3.0.Alpha2
    • server
    • None
    • Hide

      1. Create a local server using the management profile (I had EAP 6.3, but should be similar with other servers)
      2. Start the server
      3. Create a dynamic web project and include some really big file such as the jbds installer
      4. Try to deploy the project
      Before JBIDE-19350 the progress would just get stuck at 31 %. Now the percentage is slowly increasing, but nothing is really happening.

      Note that I tried to deploy the same war using jboss-cli directly and that worked fine for me. I exported the compressed war from Eclipse first - I suppose your deployers do the same with management api - first zip the war and then push it to the server. So in my opinion it's not just an issue with the server itself as suggested by you (Rob) in the other JIRA.

      Show
      1. Create a local server using the management profile (I had EAP 6.3, but should be similar with other servers) 2. Start the server 3. Create a dynamic web project and include some really big file such as the jbds installer 4. Try to deploy the project Before JBIDE-19350 the progress would just get stuck at 31 %. Now the percentage is slowly increasing, but nothing is really happening. Note that I tried to deploy the same war using jboss-cli directly and that worked fine for me. I exported the compressed war from Eclipse first - I suppose your deployers do the same with management api - first zip the war and then push it to the server. So in my opinion it's not just an issue with the server itself as suggested by you (Rob) in the other JIRA.

      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.

        1. stuck-deploy-eap-jstack-osx.log
          54 kB
        2. stuck-deploy-eap-jstack-rhel.log
          43 kB
        3. stuck-deploy-jstack-osx.log
          31 kB
        4. stuck-deploy-jstack-rhel.log
          27 kB

              rob.stryker Rob Stryker (Inactive)
              exd-mmalina Martin Malina
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: