Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-697

Exception "Could not deploy to container" should report the real exception why the managed server is failing

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Critical
    • None
    • None
    • None
    • None

    Description

      Currently, when something goes wrong in a managed server, such as ARQ-660, you get a meaningless exception "Could not deploy to container".

      The real exception should be reported, for example "port in use".

      Furthermore, the message is unclear: how far does this "Could not deploy to container" message stretch? If we have a bug in our CDI configuration (such as an Ambiguous dependency) in our war, will it also be reported with this exception or not?

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. WFLY-576 Testsuite tasks (tracking)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is duplicated by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) AS7-3718 Copy cause exception message to DeploymentException: "Could not deploy to container".

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users ARQ-660 Automatically pick an open port: embedded and managed containers should be configurable to automatically pick another open port if their default port is closed, instead of failing all tests with "Could not deploy to container"

          • Critical - To be worked on immediately following BLOCKER issues.
          • Open

          Activity

            People

              ozizka_jira Ondrej Zizka (Inactive)
              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: