Details
-
Bug
-
Resolution: Done
-
Major
-
jboss-fuse-6.1
-
None
-
None
-
%
Description
SCENARIO:
Using fuse 6.1.
We are trying to deploy the application using fuse Fabric.
The profile is deployed perfectly in the root container, but is failing in the child containers
Our application needs a new entry in the jetty.xml. If a new entry does not appears in the jetty.xml the authentication module fails and the war is not deployed:
When the profile that deploy the app is added to the root container, the application is deployed with no error.
When the same profile is added to a child container, then this exception appears:
https://gist.github.com/dvirgiln/f4a794dc66dc74a9f602
The jetty.xml that appears in the etc folder has not been modified.
It has been included a new jetty.xml file in the profile folder.
Seems that if i add a file jetty.xml in the profile, it is not getting read in case of the child container.
Clarifying:
The jetty.xml to be used is included in the profile folder
The root deployment is done correctly but the child container deployment is failing.
Attachments
Issue Links
- relates to
-
ENTESB-1923 Cannot create container in Fuse 6.1R1: Unable to download war:mvn:io.hawt/simple-plugin/1.2-redhat-394/war
- Closed
-
ENTMQ-658 Activemq doesn't start in fabric sometimes
- Closed