[JBoss JIRA] (WFLY-12427) Missing io.smallrye.health dependency on org.jboss.logging
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12427?page=com.atlassian.jira.plugin... ]
Brian Stansberry edited comment on WFLY-12427 at 8/24/19 12:44 PM:
-------------------------------------------------------------------
As I commented on the https://github.com/wildfly/wildfly/pull/12527
PR I tried for this (and ultimately closed):
Adding the org.jbss.logging dependency causes all sorts of failures due to:
{code}
org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy jaxws-authentication-ejb.jar: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"jaxws-authentication-ejb.jar\".WeldStartService" => "Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type String with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject io.smallrye.health.SmallRyeHealthReporter.uncheckedExceptionDataStyle
at io.smallrye.health.SmallRyeHealthReporter.uncheckedExceptionDataStyle(SmallRyeHealthReporter.java:0)
"}}}}
org.jboss.arquillian.container.spi.client.container.DeploymentException:
Cannot deploy jaxws-authentication-ejb.jar: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"jaxws-authentication-ejb.jar\".WeldStartService" => "Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type String with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject io.smallrye.health.SmallRyeHealthReporter.uncheckedExceptionDataStyle
at io.smallrye.health.SmallRyeHealthReporter.uncheckedExceptionDataStyle(SmallRyeHealthReporter.java:0)
"}}}}
{code}
It seems that resolving the INFO logged problem in the JIRA produces bigger problems, so perhaps not having the org.jboss.logging dependency was deliberate.
In any case I will downgrade this to Minor as the logging is at INFO, it's just a bit scary looking.
was (Author: brian.stansberry):
As I commented on the PR I tried for this (and ultimately closed):
Adding the org.jbss.logging dependency causes all sorts of failures due to:
{code}
org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy jaxws-authentication-ejb.jar: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"jaxws-authentication-ejb.jar\".WeldStartService" => "Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type String with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject io.smallrye.health.SmallRyeHealthReporter.uncheckedExceptionDataStyle
at io.smallrye.health.SmallRyeHealthReporter.uncheckedExceptionDataStyle(SmallRyeHealthReporter.java:0)
"}}}}
org.jboss.arquillian.container.spi.client.container.DeploymentException:
Cannot deploy jaxws-authentication-ejb.jar: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"jaxws-authentication-ejb.jar\".WeldStartService" => "Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type String with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject io.smallrye.health.SmallRyeHealthReporter.uncheckedExceptionDataStyle
at io.smallrye.health.SmallRyeHealthReporter.uncheckedExceptionDataStyle(SmallRyeHealthReporter.java:0)
"}}}}
{code}
It seems that resolving the INFO logged problem in the JIRA produces bigger problems, so perhaps not having the org.jboss.logging dependency was deliberate.
In any case I will downgrade this to Minor as the logging is at INFO, it's just a bit scary looking.
> Missing io.smallrye.health dependency on org.jboss.logging
> ----------------------------------------------------------
>
> Key: WFLY-12427
> URL: https://issues.jboss.org/browse/WFLY-12427
> Project: WildFly
> Issue Type: Bug
> Components: MP Health
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
>
> I happened to notice this in a server log of a CI job:
> {code}
> 16:03:53,351 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from io.smallrye.health.SmallRyeHealthReporter because of underlying class loading error: Type org.jboss.logging.Logger from [Module "io.smallrye.health" version 1.0.2 from local module loader @4909b8da (finder: local module finder @3a03464 (roots: C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules\system\layers\base,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\modules))] not found. If this is unexpected, enable DEBUG logging to see the full error.
> {code}
> The io.smallrye:smallrye-health-2.0:1.0.2 pom shows a dependency on JBoss Logging but the module.xml for its module does not.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12427) Missing io.smallrye.health dependency on org.jboss.logging
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12427?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFLY-12427:
---------------------------------------
Assignee: Jeff Mesnil (was: Brian Stansberry)
> Missing io.smallrye.health dependency on org.jboss.logging
> ----------------------------------------------------------
>
> Key: WFLY-12427
> URL: https://issues.jboss.org/browse/WFLY-12427
> Project: WildFly
> Issue Type: Bug
> Components: MP Health
> Reporter: Brian Stansberry
> Assignee: Jeff Mesnil
> Priority: Minor
>
> I happened to notice this in a server log of a CI job:
> {code}
> 16:03:53,351 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from io.smallrye.health.SmallRyeHealthReporter because of underlying class loading error: Type org.jboss.logging.Logger from [Module "io.smallrye.health" version 1.0.2 from local module loader @4909b8da (finder: local module finder @3a03464 (roots: C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules\system\layers\base,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\modules))] not found. If this is unexpected, enable DEBUG logging to see the full error.
> {code}
> The io.smallrye:smallrye-health-2.0:1.0.2 pom shows a dependency on JBoss Logging but the module.xml for its module does not.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12427) Missing io.smallrye.health dependency on org.jboss.logging
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12427?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-12427:
-----------------------------------------
As I commented on the PR I tried for this (and ultimately closed):
Adding the org.jbss.logging dependency causes all sorts of failures due to:
{code}
org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy jaxws-authentication-ejb.jar: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"jaxws-authentication-ejb.jar\".WeldStartService" => "Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type String with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject io.smallrye.health.SmallRyeHealthReporter.uncheckedExceptionDataStyle
at io.smallrye.health.SmallRyeHealthReporter.uncheckedExceptionDataStyle(SmallRyeHealthReporter.java:0)
"}}}}
org.jboss.arquillian.container.spi.client.container.DeploymentException:
Cannot deploy jaxws-authentication-ejb.jar: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"jaxws-authentication-ejb.jar\".WeldStartService" => "Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type String with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject io.smallrye.health.SmallRyeHealthReporter.uncheckedExceptionDataStyle
at io.smallrye.health.SmallRyeHealthReporter.uncheckedExceptionDataStyle(SmallRyeHealthReporter.java:0)
"}}}}
{code}
It seems that resolving the INFO logged problem in the JIRA produces bigger problems, so perhaps not having the org.jboss.logging dependency was deliberate.
In any case I will downgrade this to Minor as the logging is at INFO, it's just a bit scary looking.
> Missing io.smallrye.health dependency on org.jboss.logging
> ----------------------------------------------------------
>
> Key: WFLY-12427
> URL: https://issues.jboss.org/browse/WFLY-12427
> Project: WildFly
> Issue Type: Bug
> Components: MP Health
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
>
> I happened to notice this in a server log of a CI job:
> {code}
> 16:03:53,351 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from io.smallrye.health.SmallRyeHealthReporter because of underlying class loading error: Type org.jboss.logging.Logger from [Module "io.smallrye.health" version 1.0.2 from local module loader @4909b8da (finder: local module finder @3a03464 (roots: C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules\system\layers\base,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\modules))] not found. If this is unexpected, enable DEBUG logging to see the full error.
> {code}
> The io.smallrye:smallrye-health-2.0:1.0.2 pom shows a dependency on JBoss Logging but the module.xml for its module does not.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12427) Missing io.smallrye.health dependency on org.jboss.logging
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12427?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-12427:
------------------------------------
Priority: Minor (was: Major)
> Missing io.smallrye.health dependency on org.jboss.logging
> ----------------------------------------------------------
>
> Key: WFLY-12427
> URL: https://issues.jboss.org/browse/WFLY-12427
> Project: WildFly
> Issue Type: Bug
> Components: MP Health
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
>
> I happened to notice this in a server log of a CI job:
> {code}
> 16:03:53,351 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from io.smallrye.health.SmallRyeHealthReporter because of underlying class loading error: Type org.jboss.logging.Logger from [Module "io.smallrye.health" version 1.0.2 from local module loader @4909b8da (finder: local module finder @3a03464 (roots: C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules\system\layers\base,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\modules))] not found. If this is unexpected, enable DEBUG logging to see the full error.
> {code}
> The io.smallrye:smallrye-health-2.0:1.0.2 pom shows a dependency on JBoss Logging but the module.xml for its module does not.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4447) ClassCastException in mvel when updating a List property with modify
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-4447?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-4447:
--------------------------------
Sprint: 2019 Week 35-37
> ClassCastException in mvel when updating a List property with modify
> --------------------------------------------------------------------
>
> Key: DROOLS-4447
> URL: https://issues.jboss.org/browse/DROOLS-4447
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.25.0.Final
> Reporter: Martin Weiler
> Assignee: Mario Fusco
> Priority: Critical
> Labels: support
>
> The following code in the RHS of a rule fails with mvel dialect:
> {noformat}
> + " modify($p) { addresses.add(address) }\n" +
> + " //$p.getAddresses().add(address); update($p);\n" +
> {noformat}
> Exception:
> {noformat}
> Exception executing consequence for rule "addAddress" in defaultpkg: java.lang.ClassCastException: org.mvel2.optimizers.impl.refl.nodes.GetterAccessor cannot be cast to org.mvel2.optimizers.impl.refl.nodes.MethodAccessor
> at org.drools.core.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:39)
> at org.drools.core.common.DefaultAgenda.handleException(DefaultAgenda.java:1242)
> at org.drools.core.phreak.RuleExecutor.innerFireActivation(RuleExecutor.java:439)
> at org.drools.core.phreak.RuleExecutor.fireActivation(RuleExecutor.java:380)
> at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:136)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:89)
> at org.drools.core.concurrent.AbstractRuleEvaluator.internalEvaluateAndFire(AbstractRuleEvaluator.java:34)
> at org.drools.core.concurrent.SequentialRuleEvaluator.evaluateAndFire(SequentialRuleEvaluator.java:43)
> at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1062)
> at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1009)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1001)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1330)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1321)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1305)
> at org.drools.compiler.integrationtests.Misc2Test.testModifyAddToList(Misc2Test.java:9139)
> {noformat}
> Notes:
> * The same rule worked in Drools 6.5.x
> * The alternative syntax (commented out in the snippet above) works
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months