[JBoss JIRA] (WFLY-9913) Balancer fails to balance requests according to load provided by custom load metric
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-9913?page=com.atlassian.jira.plugin.... ]
Jan Kašík updated WFLY-9913:
----------------------------
Description:
When balancer uses load provided by custom load metric, it intermittently fails to redirect requests to expected workers. We use following scenario in our test with EAP 7.1.1 nodes:
# Prepare one balancer and three workers with custom load metric which has these attribute values:
{{history: 0, decay: 0, capacity: 1000}} and uses implementation from \[1\].
# The implementation takes dummy load values from files in local filesystem. So the values in files are set then.
# The verification, that expected load factor is loaded is made by running {{"/subsystem=undertow/configuration=filter/mod-cluster=modcluster:read-resource(include-runtime=true, recursive=true, recursive-depth=100)}}.
# 1000+ requests is made on balancer and for each request, the JVM route of handling node is noted.
# It is verified, that expected amount of request went to each node according to load factor.
# Load values in files are changes and verification, that they were loaded is made again.
# 1000+ requests is made on balancer and for each request, the JVM route of handling node is noted.
# After the requests were made, the verification, that all went according to expectations is made. In this step, the verification sometimes fails, because there were unexpected count of requests on each node.
This occurs only on EAP/Wildlfly balancer and we suspect, that this is an error in Undertow mod_cluster implementation. The problem is, that sometimes more requests than expected ends up on the worker with lowest load:
{{java.lang.AssertionError: Assert #5, Request distribution according to the load was supposed to be [jboss-eap-7.2-1:106, jboss-eap-7.2-2:106, jboss-eap-7.2-3:789] with tolerance +/-10, but was: [jboss-eap-7.2-1:36, jboss-eap-7.2-2:35, jboss-eap-7.2-3:930]}}
[1]: https://github.com/Karm/mod_cluster-custom-load-metric
was:
When balancer uses load provided by custom load metric, it intermittently fails to redirect requests to expected workers. We use following scenario in our test with EAP 7.1.1 nodes:
# Prepare one balancer and three workers with custom load metric which has these attribute values:
{{history: 0, decay: 0, capacity: 1000}} and uses implementation from \[1\].
# The implementation takes dummy load values from files in local filesystem. So the values in files are set then.
# The verification, that expected load factor is loaded is made by running {{"/subsystem=undertow/configuration=filter/mod-cluster=modcluster:read-resource(include-runtime=true, recursive=true, recursive-depth=100)}}.
# 1000+ requests is made on balancer and for each request, the JVM route of handling node is noted.
# It is verified, that expected amount of request went to each node according to load factor.
# Load values in files are changes and verification, that they were loaded is made again.
# 1000+ requests is made on balancer and for each request, the JVM route of handling node is noted.
# After the requests were made, the verification, that all went according to expectations is made. In this step, the verification sometimes fails, because there were unexpected count of requests on each node.
[1]: https://github.com/Karm/mod_cluster-custom-load-metric
> Balancer fails to balance requests according to load provided by custom load metric
> -----------------------------------------------------------------------------------
>
> Key: WFLY-9913
> URL: https://issues.jboss.org/browse/WFLY-9913
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster, Web (Undertow)
> Affects Versions: 12.0.0.Beta1
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
>
> When balancer uses load provided by custom load metric, it intermittently fails to redirect requests to expected workers. We use following scenario in our test with EAP 7.1.1 nodes:
> # Prepare one balancer and three workers with custom load metric which has these attribute values:
> {{history: 0, decay: 0, capacity: 1000}} and uses implementation from \[1\].
> # The implementation takes dummy load values from files in local filesystem. So the values in files are set then.
> # The verification, that expected load factor is loaded is made by running {{"/subsystem=undertow/configuration=filter/mod-cluster=modcluster:read-resource(include-runtime=true, recursive=true, recursive-depth=100)}}.
> # 1000+ requests is made on balancer and for each request, the JVM route of handling node is noted.
> # It is verified, that expected amount of request went to each node according to load factor.
> # Load values in files are changes and verification, that they were loaded is made again.
> # 1000+ requests is made on balancer and for each request, the JVM route of handling node is noted.
> # After the requests were made, the verification, that all went according to expectations is made. In this step, the verification sometimes fails, because there were unexpected count of requests on each node.
> This occurs only on EAP/Wildlfly balancer and we suspect, that this is an error in Undertow mod_cluster implementation. The problem is, that sometimes more requests than expected ends up on the worker with lowest load:
> {{java.lang.AssertionError: Assert #5, Request distribution according to the load was supposed to be [jboss-eap-7.2-1:106, jboss-eap-7.2-2:106, jboss-eap-7.2-3:789] with tolerance +/-10, but was: [jboss-eap-7.2-1:36, jboss-eap-7.2-2:35, jboss-eap-7.2-3:930]}}
> [1]: https://github.com/Karm/mod_cluster-custom-load-metric
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9919) Deployment throwing exception on upgrade to JBOSS EAP 7.1
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-9919?page=com.atlassian.jira.plugin.... ]
jaikiran pai updated WFLY-9919:
-------------------------------
Affects Version/s: 11.0.0.Final
> Deployment throwing exception on upgrade to JBOSS EAP 7.1
> ---------------------------------------------------------
>
> Key: WFLY-9919
> URL: https://issues.jboss.org/browse/WFLY-9919
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 11.0.0.Final
> Reporter: Sainath Machupalli
> Assignee: Jason Greene
>
> Our deployment worked on EAP 7 and we started seeing the below exception when we upgraded to EAP 7.1.
>
> 2018-02-07 09:19:46,234 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment inner.war
> 2018-02-07 09:19:46,239 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.subunit."myEAR.ear"."inner.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."myEAR.ear"."inner.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of subdeployment "inner.war" of deployment "myEAR.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: VFS000025: Given parent ("/content/myEAR.ear/inner.war") is not an ancestor of this virtual file
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:119)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:112)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.createBeanArchiveId(BeanArchiveProcessor.java:348)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.processResourceRoot(BeanArchiveProcessor.java:296)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.handleResourceRoot(BeanArchiveProcessor.java:237)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.access$100(BeanArchiveProcessor.java:206)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.deploy(BeanArchiveProcessor.java:113)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
>
> Our jboss-deployment-structure.xml is as below.
>
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure>
> <ear-subdeployments-isolated>false</ear-subdeployments-isolated>
> <sub-deployment name="inner.war">
> <dependencies>
> <module name="org.jboss.remote-naming"/>
> </dependencies>
> <resources>
> <resource-root path="APP-INF/lib/dep1.jar" />
> <resource-root path="APP-INF/lib/dep2.jar" />
> </resources>
> </sub-deployment>
> </jboss-deployment-structure>
>
> Our EAR structure is below,
> >myEAR.ear
> >inner.war
> >APP-INF
> >lib
> >dep1.jar
> >dep2.jar
> >META-INF
> >jboss-deployment-structure.xml
>
> The same structure and jboss-deployment-structure.xml worked for us on JBOSS EAP 7.
>
> Is there any change in deployment structure? or is it a BUG?
> More details @ https://developer.jboss.org/message/980164#980164
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9919) Deployment throwing exception on upgrade to JBOSS EAP 7.1
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-9919?page=com.atlassian.jira.plugin.... ]
jaikiran pai updated WFLY-9919:
-------------------------------
Component/s: CDI / Weld
> Deployment throwing exception on upgrade to JBOSS EAP 7.1
> ---------------------------------------------------------
>
> Key: WFLY-9919
> URL: https://issues.jboss.org/browse/WFLY-9919
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 11.0.0.Final
> Reporter: Sainath Machupalli
> Assignee: Jason Greene
>
> Our deployment worked on EAP 7 and we started seeing the below exception when we upgraded to EAP 7.1.
>
> 2018-02-07 09:19:46,234 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment inner.war
> 2018-02-07 09:19:46,239 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.subunit."myEAR.ear"."inner.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."myEAR.ear"."inner.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of subdeployment "inner.war" of deployment "myEAR.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: VFS000025: Given parent ("/content/myEAR.ear/inner.war") is not an ancestor of this virtual file
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:119)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:112)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.createBeanArchiveId(BeanArchiveProcessor.java:348)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.processResourceRoot(BeanArchiveProcessor.java:296)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.handleResourceRoot(BeanArchiveProcessor.java:237)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.access$100(BeanArchiveProcessor.java:206)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.deploy(BeanArchiveProcessor.java:113)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
>
> Our jboss-deployment-structure.xml is as below.
>
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure>
> <ear-subdeployments-isolated>false</ear-subdeployments-isolated>
> <sub-deployment name="inner.war">
> <dependencies>
> <module name="org.jboss.remote-naming"/>
> </dependencies>
> <resources>
> <resource-root path="APP-INF/lib/dep1.jar" />
> <resource-root path="APP-INF/lib/dep2.jar" />
> </resources>
> </sub-deployment>
> </jboss-deployment-structure>
>
> Our EAR structure is below,
> >myEAR.ear
> >inner.war
> >APP-INF
> >lib
> >dep1.jar
> >dep2.jar
> >META-INF
> >jboss-deployment-structure.xml
>
> The same structure and jboss-deployment-structure.xml worked for us on JBOSS EAP 7.
>
> Is there any change in deployment structure? or is it a BUG?
> More details @ https://developer.jboss.org/message/980164#980164
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9919) Deployment throwing exception on upgrade to JBOSS EAP 7.1
by Jive JIRA Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-9919?page=com.atlassian.jira.plugin.... ]
Jive JIRA Integration updated WFLY-9919:
----------------------------------------
Forum Reference: https://developer.jboss.org/message/980164#980164
> Deployment throwing exception on upgrade to JBOSS EAP 7.1
> ---------------------------------------------------------
>
> Key: WFLY-9919
> URL: https://issues.jboss.org/browse/WFLY-9919
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 11.0.0.Final
> Reporter: Sainath Machupalli
> Assignee: Jason Greene
>
> Our deployment worked on EAP 7 and we started seeing the below exception when we upgraded to EAP 7.1.
>
> 2018-02-07 09:19:46,234 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment inner.war
> 2018-02-07 09:19:46,239 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.subunit."myEAR.ear"."inner.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."myEAR.ear"."inner.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of subdeployment "inner.war" of deployment "myEAR.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: VFS000025: Given parent ("/content/myEAR.ear/inner.war") is not an ancestor of this virtual file
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:119)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:112)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.createBeanArchiveId(BeanArchiveProcessor.java:348)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.processResourceRoot(BeanArchiveProcessor.java:296)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.handleResourceRoot(BeanArchiveProcessor.java:237)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.access$100(BeanArchiveProcessor.java:206)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.deploy(BeanArchiveProcessor.java:113)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
>
> Our jboss-deployment-structure.xml is as below.
>
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure>
> <ear-subdeployments-isolated>false</ear-subdeployments-isolated>
> <sub-deployment name="inner.war">
> <dependencies>
> <module name="org.jboss.remote-naming"/>
> </dependencies>
> <resources>
> <resource-root path="APP-INF/lib/dep1.jar" />
> <resource-root path="APP-INF/lib/dep2.jar" />
> </resources>
> </sub-deployment>
> </jboss-deployment-structure>
>
> Our EAR structure is below,
> >myEAR.ear
> >inner.war
> >APP-INF
> >lib
> >dep1.jar
> >dep2.jar
> >META-INF
> >jboss-deployment-structure.xml
>
> The same structure and jboss-deployment-structure.xml worked for us on JBOSS EAP 7.
>
> Is there any change in deployment structure? or is it a BUG?
> More details @ https://developer.jboss.org/message/980164#980164
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9919) Deployment throwing exception on upgrade to JBOSS EAP 7.1
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-9919?page=com.atlassian.jira.plugin.... ]
jaikiran pai updated WFLY-9919:
-------------------------------
Priority: Major (was: Critical)
> Deployment throwing exception on upgrade to JBOSS EAP 7.1
> ---------------------------------------------------------
>
> Key: WFLY-9919
> URL: https://issues.jboss.org/browse/WFLY-9919
> Project: WildFly
> Issue Type: Bug
> Reporter: Sainath Machupalli
> Assignee: Jason Greene
>
> Our deployment worked on EAP 7 and we started seeing the below exception when we upgraded to EAP 7.1.
>
> 2018-02-07 09:19:46,234 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment inner.war
> 2018-02-07 09:19:46,239 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.subunit."myEAR.ear"."inner.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."myEAR.ear"."inner.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of subdeployment "inner.war" of deployment "myEAR.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: VFS000025: Given parent ("/content/myEAR.ear/inner.war") is not an ancestor of this virtual file
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:119)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:112)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.createBeanArchiveId(BeanArchiveProcessor.java:348)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.processResourceRoot(BeanArchiveProcessor.java:296)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.handleResourceRoot(BeanArchiveProcessor.java:237)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.access$100(BeanArchiveProcessor.java:206)
> at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.deploy(BeanArchiveProcessor.java:113)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
>
> Our jboss-deployment-structure.xml is as below.
>
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure>
> <ear-subdeployments-isolated>false</ear-subdeployments-isolated>
> <sub-deployment name="inner.war">
> <dependencies>
> <module name="org.jboss.remote-naming"/>
> </dependencies>
> <resources>
> <resource-root path="APP-INF/lib/dep1.jar" />
> <resource-root path="APP-INF/lib/dep2.jar" />
> </resources>
> </sub-deployment>
> </jboss-deployment-structure>
>
> Our EAR structure is below,
> >myEAR.ear
> >inner.war
> >APP-INF
> >lib
> >dep1.jar
> >dep2.jar
> >META-INF
> >jboss-deployment-structure.xml
>
> The same structure and jboss-deployment-structure.xml worked for us on JBOSS EAP 7.
>
> Is there any change in deployment structure? or is it a BUG?
> More details @ https://developer.jboss.org/message/980164#980164
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9919) Deployment throwing exception on upgrade to JBOSS EAP 7.1
by Sainath Machupalli (JIRA)
Sainath Machupalli created WFLY-9919:
----------------------------------------
Summary: Deployment throwing exception on upgrade to JBOSS EAP 7.1
Key: WFLY-9919
URL: https://issues.jboss.org/browse/WFLY-9919
Project: WildFly
Issue Type: Bug
Reporter: Sainath Machupalli
Assignee: Jason Greene
Priority: Critical
Our deployment worked on EAP 7 and we started seeing the below exception when we upgraded to EAP 7.1.
2018-02-07 09:19:46,234 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment inner.war
2018-02-07 09:19:46,239 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.subunit."myEAR.ear"."inner.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."myEAR.ear"."inner.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of subdeployment "inner.war" of deployment "myEAR.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: VFS000025: Given parent ("/content/myEAR.ear/inner.war") is not an ancestor of this virtual file
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:119)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:112)
at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.createBeanArchiveId(BeanArchiveProcessor.java:348)
at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.processResourceRoot(BeanArchiveProcessor.java:296)
at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.handleResourceRoot(BeanArchiveProcessor.java:237)
at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.access$100(BeanArchiveProcessor.java:206)
at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.deploy(BeanArchiveProcessor.java:113)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
... 5 more
Our jboss-deployment-structure.xml is as below.
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<ear-subdeployments-isolated>false</ear-subdeployments-isolated>
<sub-deployment name="inner.war">
<dependencies>
<module name="org.jboss.remote-naming"/>
</dependencies>
<resources>
<resource-root path="APP-INF/lib/dep1.jar" />
<resource-root path="APP-INF/lib/dep2.jar" />
</resources>
</sub-deployment>
</jboss-deployment-structure>
Our EAR structure is below,
>myEAR.ear
>inner.war
>APP-INF
>lib
>dep1.jar
>dep2.jar
>META-INF
>jboss-deployment-structure.xml
The same structure and jboss-deployment-structure.xml worked for us on JBOSS EAP 7.
Is there any change in deployment structure? or is it a BUG?
More details @ https://developer.jboss.org/message/980164#980164
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months