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

Server adapter states <synchronized> even if deploy to remote host failed

XMLWordPrintable

    • Hide

      1) make sure you have a dynamic web project that you can deploy.
      2) launch a new deltacloud instance:

      • on page2, only "Create RSE Connection", do NOT "Create Server Adapter"
        3) create a new server adapter in remote mode for the jboss as 6 that runs on your instance:
      • use a bogus "Remote Server Home"
        4) Start you server adapter
        5) add your web app to your server adapter
        6) wait until deploy finishes

      Result:

      • the server adapter states [Started, Synchronized]
      • Check the error log by choosing "Show in->Server Log": the web app could NOT be deployed since the path to the server home does not exist on the remote host

      Expected:
      The server adapter should show the user that the deploy was not successful. The state might have to be [Started, Error] instead of [Stated, Synchronized] or should have some error decoration or something that tells the user that the deploy did not succeed.

      Show
      1) make sure you have a dynamic web project that you can deploy. 2) launch a new deltacloud instance: on page2, only "Create RSE Connection", do NOT "Create Server Adapter" 3) create a new server adapter in remote mode for the jboss as 6 that runs on your instance: use a bogus "Remote Server Home" 4) Start you server adapter 5) add your web app to your server adapter 6) wait until deploy finishes Result: the server adapter states [Started, Synchronized] Check the error log by choosing "Show in->Server Log": the web app could NOT be deployed since the path to the server home does not exist on the remote host Expected: The server adapter should show the user that the deploy was not successful. The state might have to be [Started, Error] instead of [Stated, Synchronized] or should have some error decoration or something that tells the user that the deploy did not succeed.
    • Hide
      When attempting deployment to a remote host, the server adaptor would return a state of synchronization even if deployment failed. This issue has been fixed by ensuring that in the event of an exception, the module's publish state is set to republish and the running state to unknown. If this occurs, the server adaptor will attempt resynchronization.
      Show
      When attempting deployment to a remote host, the server adaptor would return a state of synchronization even if deployment failed. This issue has been fixed by ensuring that in the event of an exception, the module's publish state is set to republish and the running state to unknown. If this occurs, the server adaptor will attempt resynchronization.
    • Documented as Resolved Issue

      yes - server adapter needs to get a more consistent error handling.

            rob.stryker Rob Stryker (Inactive)
            adietish@redhat.com André Dietisheim
            Isaac Rooskov Isaac Rooskov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: