[JBoss JIRA] Created: (JGRP-457) Optimization: make threads return immediately if NAKACK has another active thread for the same sender
by Bela Ban (JIRA)
Optimization: make threads return immediately if NAKACK has another active thread for the same sender
-----------------------------------------------------------------------------------------------------
Key: JGRP-457
URL: http://jira.jboss.com/jira/browse/JGRP-457
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assigned To: Bela Ban
Priority: Minor
Fix For: 2.5
In NAKACK, when a thread places a message for sender S into the NakReceiverWindow NRW, it subsequently acquires a lock on NRW (lock by sender) and removes as many messages as possible and passes them up.
If many threads do this at the same time, all threads but one are blocked, and - when finally unblocked - usually return. This causes context switches and possibly cache flushing, so a better way would be to have the threads check whether another thread is already removing messages using a CAS operation *before* acquiring the lock.
The effect should be that no threads will wait on the lock unnecessarily, and thus fewer context switches, and more threads available to the pool.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2 weeks, 4 days
[JBoss JIRA] (WFLY-4210) Very Slow performance for larger JSF 2 pages.
by Rodney Kite (JIRA)
[ https://issues.jboss.org/browse/WFLY-4210?page=com.atlassian.jira.plugin.... ]
Rodney Kite commented on WFLY-4210:
-----------------------------------
I added the following to standalone.xml to handle larger pages. Also updated the timings for Wildfly 8.2.0. The ajax on the page is faster than previously mentioned. The 2.2.8 mojarra in Wildfly performs much faster than 1.2_15 mojarra found in JBoss AS 7.1.1 when using with tomcat. Mojarra is not the issue. Machine is a Dell 990 with I7-2600 processor and 16 gig of memory.
<system-properties>
<property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="10000"/>
</system-properties>
> Very Slow performance for larger JSF 2 pages.
> ---------------------------------------------
>
> Key: WFLY-4210
> URL: https://issues.jboss.org/browse/WFLY-4210
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.2.0.Final
> Environment: Windows 7 64 bit, Oracle JDK 1.7.0-67 64 bit, Wildfly 8.2.0, Tomcat and JBoss 7.1.1.
> Reporter: Rodney Kite
> Assignee: Remy Maucherat
> Attachments: AjaxTest.xhtml, PageAjaxTest.java, testAppWar.ear, testAppWeb.war
>
>
> Very slow page performance using JSF 2 and Wildfly 8.2.0 for larger pages. I am migrating a large application from JBoss AS 7.1.1 to Wildfly 8.2.0 and page performance on loads and posts is very slow. I created a large JSF 2 test page and took timings for JBoss 7.1.1, Wildfly 8.2.0 and Tomcat 7.x using the same Mojarra 2.2.8 implementation as Wildfly.
> The attached war file contains mojarra 2.2.8 jars for tomcat. The attached ear file is for JBoss deployments and does not contain mojarra jars.
> Example test URL for attached ear and war.
> http://localhost:8080/testAppWeb/jsp/AjaxTest.jsf
> JBoss 7.1.1 Timings
> Page Load: 4.0 Seconds
> Post: 4.5 Seconds
> Ajax: 4.0 Seconds
> Wildfly 8.2.0 Timings
> Page Load: 55.0 Seconds
> Post: 50 Seconds
> Ajax: 7 Seconds
> Tomcat 7.x with 2.2.8 Mojarra
> Page Load 1.0 Seconds
> Post: 0.75 Seconds
> Ajax: 0.3 Seconds
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (WFLY-4210) Very Slow performance for larger JSF 2 pages.
by Rodney Kite (JIRA)
[ https://issues.jboss.org/browse/WFLY-4210?page=com.atlassian.jira.plugin.... ]
Rodney Kite updated WFLY-4210:
------------------------------
Description:
Very slow page performance using JSF 2 and Wildfly 8.2.0 for larger pages. I am migrating a large application from JBoss AS 7.1.1 to Wildfly 8.2.0 and page performance on loads and posts is very slow. I created a large JSF 2 test page and took timings for JBoss 7.1.1, Wildfly 8.2.0 and Tomcat 7.x using the same Mojarra 2.2.8 implementation as Wildfly.
The attached war file contains mojarra 2.2.8 jars for tomcat. The attached ear file is for JBoss deployments and does not contain mojarra jars.
Example test URL for attached ear and war.
http://localhost:8080/testAppWeb/jsp/AjaxTest.jsf
JBoss 7.1.1 Timings
Page Load: 4.0 Seconds
Post: 4.5 Seconds
Ajax: 4.0 Seconds
Wildfly 8.2.0 Timings
Page Load: 55.0 Seconds
Post: 50 Seconds
Ajax: 7 Seconds
Tomcat 7.x with 2.2.8 Mojarra
Page Load 1.0 Seconds
Post: 0.75 Seconds
Ajax: 0.3 Seconds
was:
Very slow page performance using JSF 2 and Wildfly 8.2.0 for larger pages. I am migrating a large application from JBoss AS 7.1.1 to Wildfly 8.2.0 and page performance on loads and posts is very slow. I created a large JSF 2 test page and took timings for JBoss 7.1.1, Wildfly 8.2.0 and Tomcat 7.x using the same Mojarra 2.2.8 implementation as Wildfly.
The attached war file contains mojarra 2.2.8 jars for tomcat. The attached ear file is for JBoss deployments and does not contain mojarra jars.
Example test URL for attached ear and war.
http://localhost:8080/testAppWeb/jsp/AjaxTest.jsf
JBoss 7.1.1 Timings
Page Load: 4.0 Seconds
Post: 4.5 Seconds
Ajax: 4.0 Seconds
Wildfly 8.2.0 Timings
Page Load: 66.0 Seconds
Post: 60 Seconds
Ajax: 55 Seconds
Tomcat 7.x with 2.2.8 Mojarra
Page Load 1.0 Seconds
Post: 0.75 Seconds
Ajax: 0.3 Seconds
> Very Slow performance for larger JSF 2 pages.
> ---------------------------------------------
>
> Key: WFLY-4210
> URL: https://issues.jboss.org/browse/WFLY-4210
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.2.0.Final
> Environment: Windows 7 64 bit, Oracle JDK 1.7.0-67 64 bit, Wildfly 8.2.0, Tomcat and JBoss 7.1.1.
> Reporter: Rodney Kite
> Assignee: Remy Maucherat
> Attachments: AjaxTest.xhtml, PageAjaxTest.java, testAppWar.ear, testAppWeb.war
>
>
> Very slow page performance using JSF 2 and Wildfly 8.2.0 for larger pages. I am migrating a large application from JBoss AS 7.1.1 to Wildfly 8.2.0 and page performance on loads and posts is very slow. I created a large JSF 2 test page and took timings for JBoss 7.1.1, Wildfly 8.2.0 and Tomcat 7.x using the same Mojarra 2.2.8 implementation as Wildfly.
> The attached war file contains mojarra 2.2.8 jars for tomcat. The attached ear file is for JBoss deployments and does not contain mojarra jars.
> Example test URL for attached ear and war.
> http://localhost:8080/testAppWeb/jsp/AjaxTest.jsf
> JBoss 7.1.1 Timings
> Page Load: 4.0 Seconds
> Post: 4.5 Seconds
> Ajax: 4.0 Seconds
> Wildfly 8.2.0 Timings
> Page Load: 55.0 Seconds
> Post: 50 Seconds
> Ajax: 7 Seconds
> Tomcat 7.x with 2.2.8 Mojarra
> Page Load 1.0 Seconds
> Post: 0.75 Seconds
> Ajax: 0.3 Seconds
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (DROOLS-674) Rules with bigdecimal comparison not matched for certain values
by Joseph Alex (JIRA)
[ https://issues.jboss.org/browse/DROOLS-674?page=com.atlassian.jira.plugin... ]
Joseph Alex updated DROOLS-674:
-------------------------------
Description:
For rules which compare BigDecimal inputs against a range considering 2 decimal place precision, match does not happen when the input equals certain upper bounds. Testcase attached.
The rules match when the upper bound is specified with a < condition instead of <= (i.e <70.00 instead of <=69.99) , which seem to indicate value seen by Drools is somewhere between the two.
Envrionment:
Drools : 5.5.0.Final
Java version : Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
OS : CentOS release 6.1 (Final)
was:
For rules which compare BigDecimal inputs against a range considering 2 decimal place precision, match does not happen when the input equals certain upper bounds. Testcase attached.
The rules match when the upper bound is specified with a < condition instead of <= (i.e <70.00 instead of <=69.99) , which seem to indicate value seen by Drools is somewhere between the two.
> Rules with bigdecimal comparison not matched for certain values
> ---------------------------------------------------------------
>
> Key: DROOLS-674
> URL: https://issues.jboss.org/browse/DROOLS-674
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.5.0.Final
> Reporter: Joseph Alex
> Assignee: Mark Proctor
> Priority: Minor
> Attachments: BigDecimalTestFragment.java
>
>
> For rules which compare BigDecimal inputs against a range considering 2 decimal place precision, match does not happen when the input equals certain upper bounds. Testcase attached.
> The rules match when the upper bound is specified with a < condition instead of <= (i.e <70.00 instead of <=69.99) , which seem to indicate value seen by Drools is somewhere between the two.
> Envrionment:
> Drools : 5.5.0.Final
> Java version : Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
> OS : CentOS release 6.1 (Final)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (DROOLS-674) Rules with bigdecimal comparison not matched for certain values
by Joseph Alex (JIRA)
[ https://issues.jboss.org/browse/DROOLS-674?page=com.atlassian.jira.plugin... ]
Joseph Alex updated DROOLS-674:
-------------------------------
Attachment: BigDecimalTestFragment.java
> Rules with bigdecimal comparison not matched for certain values
> ---------------------------------------------------------------
>
> Key: DROOLS-674
> URL: https://issues.jboss.org/browse/DROOLS-674
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.5.0.Final
> Reporter: Joseph Alex
> Assignee: Mark Proctor
> Priority: Minor
> Attachments: BigDecimalTestFragment.java
>
>
> For rules which compare BigDecimal inputs against a range considering 2 decimal place precision, match does not happen when the input equals certain upper bounds. Testcase attached.
> The rules match when the upper bound is specified with a < condition instead of <= (i.e <70.00 instead of <=69.99) , which seem to indicate value seen by Drools is somewhere between the two.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (DROOLS-674) Rules with bigdecimal comparison not matched for certain values
by Joseph Alex (JIRA)
Joseph Alex created DROOLS-674:
----------------------------------
Summary: Rules with bigdecimal comparison not matched for certain values
Key: DROOLS-674
URL: https://issues.jboss.org/browse/DROOLS-674
Project: Drools
Issue Type: Bug
Affects Versions: 5.5.0.Final
Reporter: Joseph Alex
Assignee: Mark Proctor
Priority: Minor
For rules which compare BigDecimal inputs against a range considering 2 decimal place precision, match does not happen when the input equals certain upper bounds. Testcase attached.
The rules match when the upper bound is specified with a < condition instead of <= (i.e <70.00 instead of <=69.99) , which seem to indicate value seen by Drools is somewhere between the two.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (WFLY-4212) REGRESSION: CDI application fails to deploy in 8.2.0 vs 8.1.0
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/WFLY-4212?page=com.atlassian.jira.plugin.... ]
Arcadiy Ivanov commented on WFLY-4212:
--------------------------------------
Running the test case requires a domain with a single server-group "primary-clustered".
{noformat}
Running wfcore488.test.ServiceIT
======
bf40aa60-1792-473b-bc2c-344adf89790c.ear:
/lib/
/lib/wfcore488-lib-1.0.0-SNAPSHOT.jar
/lib/arquillian-junit-container-1.1.5.Final.jar
/lib/wildfly-arquillian-container-domain-remote-1.0.0.Alpha4.jar
/lib/junit-4.11.jar
/lib/arquillian-suite-extension-1.1.1.jar
/lib/mockito-all-1.10.17.jar
/wfcore488-ejb-1.0.0-SNAPSHOT.jar
/test.war
/META-INF/
/META-INF/application.xml
======
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="6">
<library-directory>lib</library-directory>
<module>
<web>
<web-uri>test.war</web-uri>
<context-root>/</context-root>
</web>
</module>
<module>
<ejb>wfcore488-ejb-1.0.0-SNAPSHOT.jar</ejb>
</module>
</application>
======
test.war:
/WEB-INF/
/WEB-INF/classes/
/WEB-INF/classes/wfcore488/
/WEB-INF/classes/wfcore488/web/
/WEB-INF/classes/wfcore488/web/ExampleService.class
/WEB-INF/classes/wfcore488/test/
/WEB-INF/classes/wfcore488/test/ServiceIT.class
/WEB-INF/classes/wfcore488/test/common/
/WEB-INF/classes/wfcore488/test/common/AbstractArquillianSuite.class
/WEB-INF/classes/wfcore488/test/common/ServiceTestBase.class
/META-INF/
/META-INF/arquillian.ArchiveUnderTest
======
{noformat}
Test case is as follows:
# An Arquillian test creates an EAR
# An EAR contains a test.war, an EJB module and a utility Lib (in EAR's lib/)
# WAR injects EJB from an EJB module
# EJB module injects CDI bean from a utility Lib
# The latter injection fails on 8.2.0.
> REGRESSION: CDI application fails to deploy in 8.2.0 vs 8.1.0
> -------------------------------------------------------------
>
> Key: WFLY-4212
> URL: https://issues.jboss.org/browse/WFLY-4212
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 8.2.0.Final
> Reporter: Arcadiy Ivanov
> Assignee: Stuart Douglas
> Priority: Critical
> Attachments: 8.1.0-cluster_logs.2014-12-31T04-01-53.tar.gz, 8.2.0-cluster_logs.2014-12-31T04-19-06.tar.gz
>
>
> While testing an upgrade to 8.2.0 a multi-component integration test that worked on 8.1.0 failed to deploy.
> A distilled clean-room test case reproducing the problem is located here: https://github.com/arcivanov/misc/tree/WFCORE-488/WFCORE-488
> This bug is also accompanied by the failure to undeploy partial deployment in WFCORE-488, although at present the above test case not yet reproduces the behavior.
> The deployment error on 8.2.0 is as follows:
> {noformat}
> 2014-12-31 04:17:11,877 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."bf40aa60-1792-473b-bc2c-344adf89790c.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."bf40aa60-1792-473b-bc2c-344adf89790c.ear".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
> at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:372)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:293)
> at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
> at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:167)
> at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:531)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_25]
> ... 3 more
> 2014-12-31 04:17:11,886 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 66) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "bf40aa60-1792-473b-bc2c-344adf89790c.ear")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
> at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
> "}}
> 2014-12-31 04:17:11,889 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 66) JBAS015870: Deploy of deployment "bf40aa60-1792-473b-bc2c-344adf89790c.ear" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
> at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
> "}}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (WFLY-4212) REGRESSION: CDI application fails to deploy in 8.2.0 vs 8.1.0
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/WFLY-4212?page=com.atlassian.jira.plugin.... ]
Arcadiy Ivanov updated WFLY-4212:
---------------------------------
Attachment: 8.1.0-cluster_logs.2014-12-31T04-01-53.tar.gz
8.2.0-cluster_logs.2014-12-31T04-19-06.tar.gz
How to read the attached log tarballs:
{{domain/host<N>/servers/server<M>/}} contain the server logs
{{domain/master/}} contains domain controller logs
> REGRESSION: CDI application fails to deploy in 8.2.0 vs 8.1.0
> -------------------------------------------------------------
>
> Key: WFLY-4212
> URL: https://issues.jboss.org/browse/WFLY-4212
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 8.2.0.Final
> Reporter: Arcadiy Ivanov
> Assignee: Stuart Douglas
> Priority: Critical
> Attachments: 8.1.0-cluster_logs.2014-12-31T04-01-53.tar.gz, 8.2.0-cluster_logs.2014-12-31T04-19-06.tar.gz
>
>
> While testing an upgrade to 8.2.0 a multi-component integration test that worked on 8.1.0 failed to deploy.
> A distilled clean-room test case reproducing the problem is located here: https://github.com/arcivanov/misc/tree/WFCORE-488/WFCORE-488
> This bug is also accompanied by the failure to undeploy partial deployment in WFCORE-488, although at present the above test case not yet reproduces the behavior.
> The deployment error on 8.2.0 is as follows:
> {noformat}
> 2014-12-31 04:17:11,877 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."bf40aa60-1792-473b-bc2c-344adf89790c.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."bf40aa60-1792-473b-bc2c-344adf89790c.ear".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
> at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:372)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:293)
> at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
> at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:167)
> at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:531)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_25]
> ... 3 more
> 2014-12-31 04:17:11,886 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 66) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "bf40aa60-1792-473b-bc2c-344adf89790c.ear")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
> at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
> "}}
> 2014-12-31 04:17:11,889 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 66) JBAS015870: Deploy of deployment "bf40aa60-1792-473b-bc2c-344adf89790c.ear" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
> at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
> "}}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (WFLY-4212) REGRESSION: CDI application fails to deploy in 8.2.0 vs 8.1.0
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/WFLY-4212?page=com.atlassian.jira.plugin.... ]
Arcadiy Ivanov updated WFLY-4212:
---------------------------------
Description:
While testing an upgrade to 8.2.0 a multi-component integration test that worked on 8.1.0 failed to deploy.
A distilled clean-room test case reproducing the problem is located here: https://github.com/arcivanov/misc/tree/WFCORE-488/WFCORE-488
This bug is also accompanied by the failure to undeploy partial deployment in WFCORE-488, although at present the above test case not yet reproduces the behavior.
The deployment error on 8.2.0 is as follows:
{noformat}
2014-12-31 04:17:11,877 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."bf40aa60-1792-473b-bc2c-344adf89790c.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."bf40aa60-1792-473b-bc2c-344adf89790c.ear".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:372)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:293)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:167)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:531)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_25]
... 3 more
2014-12-31 04:17:11,886 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 66) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "bf40aa60-1792-473b-bc2c-344adf89790c.ear")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService: Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
"}}
2014-12-31 04:17:11,889 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 66) JBAS015870: Deploy of deployment "bf40aa60-1792-473b-bc2c-344adf89790c.ear" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService: Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
"}}
{noformat}
was:
While testing an upgrade to 8.2.0 a multi-component integration test that worked on 8.1.0 failed to deploy.
A distilled clean-room test case reproducing the problem is located here: https://github.com/arcivanov/misc/tree/WFCORE-488/WFCORE-488
This bug is also accompanied by the failure to undeploy partial deployment in WFCORE-488, although at present the above test case not yet reproduces the behavior.
The deployment error is as follows:
{noformat}
2014-12-31 04:17:11,877 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."bf40aa60-1792-473b-bc2c-344adf89790c.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."bf40aa60-1792-473b-bc2c-344adf89790c.ear".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:372)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:293)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:167)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:531)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_25]
... 3 more
2014-12-31 04:17:11,886 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 66) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "bf40aa60-1792-473b-bc2c-344adf89790c.ear")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService: Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
"}}
2014-12-31 04:17:11,889 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 66) JBAS015870: Deploy of deployment "bf40aa60-1792-473b-bc2c-344adf89790c.ear" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService: Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
"}}
{noformat}
> REGRESSION: CDI application fails to deploy in 8.2.0 vs 8.1.0
> -------------------------------------------------------------
>
> Key: WFLY-4212
> URL: https://issues.jboss.org/browse/WFLY-4212
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 8.2.0.Final
> Reporter: Arcadiy Ivanov
> Assignee: Stuart Douglas
> Priority: Critical
>
> While testing an upgrade to 8.2.0 a multi-component integration test that worked on 8.1.0 failed to deploy.
> A distilled clean-room test case reproducing the problem is located here: https://github.com/arcivanov/misc/tree/WFCORE-488/WFCORE-488
> This bug is also accompanied by the failure to undeploy partial deployment in WFCORE-488, although at present the above test case not yet reproduces the behavior.
> The deployment error on 8.2.0 is as follows:
> {noformat}
> 2014-12-31 04:17:11,877 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."bf40aa60-1792-473b-bc2c-344adf89790c.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."bf40aa60-1792-473b-bc2c-344adf89790c.ear".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
> at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:372)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:293)
> at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
> at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:167)
> at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:531)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_25]
> ... 3 more
> 2014-12-31 04:17:11,886 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 66) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "bf40aa60-1792-473b-bc2c-344adf89790c.ear")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
> at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
> "}}
> 2014-12-31 04:17:11,889 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 66) JBAS015870: Deploy of deployment "bf40aa60-1792-473b-bc2c-344adf89790c.ear" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
> at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
> "}}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months