-
Enhancement
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
None
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?
- blocks
-
WFLY-576 Testsuite tasks (tracking)
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- relates to
-
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"
-
- Open
-
