[JBoss JIRA] (DROOLS-1518) Undecipherable stacktrace from rule that failed with exception
by Martin Sivak (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1518?page=com.atlassian.jira.plugi... ]
Martin Sivak updated DROOLS-1518:
---------------------------------
Description:
One of my rules failed, but I can't really tell which because the stacktrace is not telling me anything useful.
{{
java.lang.NullPointerException: null
at ConditionEvaluatora9ca906eae5d402ebbfea1f192edea08.evaluate(Unknown Source) ~[na:na]
at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:258) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.rule.constraint.MvelConstraint.isAllowedCachedRight(MvelConstraint.java:241) ~[drools-core-6.4.0.Final.jar:6.4.0.
Final]
at org.drools.core.common.DoubleBetaConstraints.isAllowedCachedRight(DoubleBetaConstraints.java:120) ~[drools-core-6.4.0.Final.jar:6
.4.0.Final]
at org.drools.core.phreak.PhreakJoinNode.doRightInserts(PhreakJoinNode.java:162) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.phreak.PhreakJoinNode.doNode(PhreakJoinNode.java:72) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:519) ~[drools-core-6.4.0.Final.jar:6.4.0
.Final]
at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:505) ~[drools-core-6.4.0.Final.jar:6.4.0.Final
]
at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:341) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:301) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:136) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:94) ~[drools-core-6.4.0.Final.jar:6.4.0.Fin
al]
at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:194) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:73) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1007) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1350) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1288) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1306) ~[drools-core-6.4.
0.Final.jar:6.4.0.Final]
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1297) ~[drools-core-6.4.0.Final.
jar:6.4.0.Final]
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1278) ~[drools-core-6.4.0.Final.
jar:6.4.0.Final]
}}
was:
One of my rules failed, but I can't really tell which because the stacktrace is not telling me anything useful.
{{
java.lang.NullPointerException: null
at ConditionEvaluatora9ca906eae5d402ebbfea1f192edea08.evaluate(Unknown Source) ~[na:na]
at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:258) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.rule.constraint.MvelConstraint.isAllowedCachedRight(MvelConstraint.java:241) ~[drools-core-6.4.0.Final.jar:6.4.0.
Final]
at org.drools.core.common.DoubleBetaConstraints.isAllowedCachedRight(DoubleBetaConstraints.java:120) ~[drools-core-6.4.0.Final.jar:6
.4.0.Final]
at org.drools.core.phreak.PhreakJoinNode.doRightInserts(PhreakJoinNode.java:162) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.phreak.PhreakJoinNode.doNode(PhreakJoinNode.java:72) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:519) ~[drools-core-6.4.0.Final.jar:6.4.0
.Final]
at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:505) ~[drools-core-6.4.0.Final.jar:6.4.0.Final
]
at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:341) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:301) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:136) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:94) ~[drools-core-6.4.0.Final.jar:6.4.0.Fin
al]
at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:194) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:73) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1007) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1350) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1288) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1306) ~[drools-core-6.4.
0.Final.jar:6.4.0.Final]
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1297) ~[drools-core-6.4.0.Final.
jar:6.4.0.Final]
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1278) ~[drools-core-6.4.0.Final.
jar:6.4.0.Final]}}
> Undecipherable stacktrace from rule that failed with exception
> --------------------------------------------------------------
>
> Key: DROOLS-1518
> URL: https://issues.jboss.org/browse/DROOLS-1518
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.4.0.Final
> Reporter: Martin Sivak
> Assignee: Mario Fusco
>
> One of my rules failed, but I can't really tell which because the stacktrace is not telling me anything useful.
> {{
> java.lang.NullPointerException: null
> at ConditionEvaluatora9ca906eae5d402ebbfea1f192edea08.evaluate(Unknown Source) ~[na:na]
> at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:258) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
> at org.drools.core.rule.constraint.MvelConstraint.isAllowedCachedRight(MvelConstraint.java:241) ~[drools-core-6.4.0.Final.jar:6.4.0.
> Final]
> at org.drools.core.common.DoubleBetaConstraints.isAllowedCachedRight(DoubleBetaConstraints.java:120) ~[drools-core-6.4.0.Final.jar:6
> .4.0.Final]
> at org.drools.core.phreak.PhreakJoinNode.doRightInserts(PhreakJoinNode.java:162) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
> at org.drools.core.phreak.PhreakJoinNode.doNode(PhreakJoinNode.java:72) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
> at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:519) ~[drools-core-6.4.0.Final.jar:6.4.0
> .Final]
> at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:505) ~[drools-core-6.4.0.Final.jar:6.4.0.Final
> ]
> at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:341) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:301) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:136) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:94) ~[drools-core-6.4.0.Final.jar:6.4.0.Fin
> al]
> at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:194) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:73) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
> at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1007) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
> at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1350) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1288) ~[drools-core-6.4.0.Final.jar:6.4.0.Final]
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1306) ~[drools-core-6.4.
> 0.Final.jar:6.4.0.Final]
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1297) ~[drools-core-6.4.0.Final.
> jar:6.4.0.Final]
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1278) ~[drools-core-6.4.0.Final.
> jar:6.4.0.Final]
> }}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2641) Authentication through http-interface with Elytron authentication and legacy SSL (without configured authentication) is not possible
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2641?page=com.atlassian.jira.plugi... ]
Ondrej Lukas updated WFCORE-2641:
---------------------------------
Description:
When http-interface uses http-authentication-factory attribute for authentication and security-realm attribute for SSL, and referenced security-realm does not include authentication, then authentication through http-interface is not possible.
When Management Console is used, then page with _The Red Hat JBoss Enterprise Application Platform 7 is running. However you have not yet added any users to be able to access the admin console._ is displayed.
When https://localhost:9993/management?operation=attribute&name=server-state is accessed then following output is returned:
{code}
{
"outcome" : "failed",
"failure-description" : "WFLYDMHTTP0006: The security realm is not ready to process requests, see https://localhost:9993/error",
"rolled-back" : "true"
}
{code}
When security-realm includes also authentication (which is not used) then authentication through http-interface works as expected.
was:
When http-interface uses http-authentication-factory attribute for authentication and security-realm attribute for SSL, and references security-realm does not include authentication, then authentication through http-interface is not possible.
When Management Console is used, then page with _The Red Hat JBoss Enterprise Application Platform 7 is running. However you have not yet added any users to be able to access the admin console._ is displayed.
When https://localhost:9993/management?operation=attribute&name=server-state is accessed then following output is returned:
{code}
{
"outcome" : "failed",
"failure-description" : "WFLYDMHTTP0006: The security realm is not ready to process requests, see https://localhost:9993/error",
"rolled-back" : "true"
}
{code}
When security-realm includes also authentication (which is not used) then authentication through http-interface works as expected.
> Authentication through http-interface with Elytron authentication and legacy SSL (without configured authentication) is not possible
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2641
> URL: https://issues.jboss.org/browse/WFCORE-2641
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Affects Versions: 3.0.0.Beta13
> Reporter: Ondrej Lukas
> Assignee: Brian Stansberry
> Priority: Blocker
>
> When http-interface uses http-authentication-factory attribute for authentication and security-realm attribute for SSL, and referenced security-realm does not include authentication, then authentication through http-interface is not possible.
> When Management Console is used, then page with _The Red Hat JBoss Enterprise Application Platform 7 is running. However you have not yet added any users to be able to access the admin console._ is displayed.
> When https://localhost:9993/management?operation=attribute&name=server-state is accessed then following output is returned:
> {code}
> {
> "outcome" : "failed",
> "failure-description" : "WFLYDMHTTP0006: The security realm is not ready to process requests, see https://localhost:9993/error",
> "rolled-back" : "true"
> }
> {code}
> When security-realm includes also authentication (which is not used) then authentication through http-interface works as expected.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2641) Authentication through http-interface with Elytron authentication and legacy SSL (without configured authentication) is not possible
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFCORE-2641:
------------------------------------
Summary: Authentication through http-interface with Elytron authentication and legacy SSL (without configured authentication) is not possible
Key: WFCORE-2641
URL: https://issues.jboss.org/browse/WFCORE-2641
Project: WildFly Core
Issue Type: Bug
Components: Domain Management, Security
Reporter: Ondrej Lukas
Assignee: Brian Stansberry
Priority: Blocker
When http-interface uses http-authentication-factory attribute for authentication and security-realm attribute for SSL, and references security-realm does not include authentication, then authentication through http-interface is not possible.
When Management Console is used, then page with _The Red Hat JBoss Enterprise Application Platform 7 is running. However you have not yet added any users to be able to access the admin console._ is displayed.
When https://localhost:9993/management?operation=attribute&name=server-state is accessed then following output is returned:
{code}
{
"outcome" : "failed",
"failure-description" : "WFLYDMHTTP0006: The security realm is not ready to process requests, see https://localhost:9993/error",
"rolled-back" : "true"
}
{code}
When security-realm includes also authentication (which is not used) then authentication through http-interface works as expected.
We request blocker flag because this issue blocks RFE EAP7-545. This issue is reported in EAP 7.1.0.DR16 because this configuration could not be set on application server due to JBEAP-7428, which was fixed in EAP 7.1.0.DR16.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2641) Authentication through http-interface with Elytron authentication and legacy SSL (without configured authentication) is not possible
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2641?page=com.atlassian.jira.plugi... ]
Ondrej Lukas updated WFCORE-2641:
---------------------------------
Description:
When http-interface uses http-authentication-factory attribute for authentication and security-realm attribute for SSL, and references security-realm does not include authentication, then authentication through http-interface is not possible.
When Management Console is used, then page with _The Red Hat JBoss Enterprise Application Platform 7 is running. However you have not yet added any users to be able to access the admin console._ is displayed.
When https://localhost:9993/management?operation=attribute&name=server-state is accessed then following output is returned:
{code}
{
"outcome" : "failed",
"failure-description" : "WFLYDMHTTP0006: The security realm is not ready to process requests, see https://localhost:9993/error",
"rolled-back" : "true"
}
{code}
When security-realm includes also authentication (which is not used) then authentication through http-interface works as expected.
was:
When http-interface uses http-authentication-factory attribute for authentication and security-realm attribute for SSL, and references security-realm does not include authentication, then authentication through http-interface is not possible.
When Management Console is used, then page with _The Red Hat JBoss Enterprise Application Platform 7 is running. However you have not yet added any users to be able to access the admin console._ is displayed.
When https://localhost:9993/management?operation=attribute&name=server-state is accessed then following output is returned:
{code}
{
"outcome" : "failed",
"failure-description" : "WFLYDMHTTP0006: The security realm is not ready to process requests, see https://localhost:9993/error",
"rolled-back" : "true"
}
{code}
When security-realm includes also authentication (which is not used) then authentication through http-interface works as expected.
We request blocker flag because this issue blocks RFE EAP7-545. This issue is reported in EAP 7.1.0.DR16 because this configuration could not be set on application server due to JBEAP-7428, which was fixed in EAP 7.1.0.DR16.
> Authentication through http-interface with Elytron authentication and legacy SSL (without configured authentication) is not possible
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2641
> URL: https://issues.jboss.org/browse/WFCORE-2641
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Affects Versions: 3.0.0.Beta13
> Reporter: Ondrej Lukas
> Assignee: Brian Stansberry
> Priority: Blocker
>
> When http-interface uses http-authentication-factory attribute for authentication and security-realm attribute for SSL, and references security-realm does not include authentication, then authentication through http-interface is not possible.
> When Management Console is used, then page with _The Red Hat JBoss Enterprise Application Platform 7 is running. However you have not yet added any users to be able to access the admin console._ is displayed.
> When https://localhost:9993/management?operation=attribute&name=server-state is accessed then following output is returned:
> {code}
> {
> "outcome" : "failed",
> "failure-description" : "WFLYDMHTTP0006: The security realm is not ready to process requests, see https://localhost:9993/error",
> "rolled-back" : "true"
> }
> {code}
> When security-realm includes also authentication (which is not used) then authentication through http-interface works as expected.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2641) Authentication through http-interface with Elytron authentication and legacy SSL (without configured authentication) is not possible
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2641?page=com.atlassian.jira.plugi... ]
Ondrej Lukas updated WFCORE-2641:
---------------------------------
Affects Version/s: 3.0.0.Beta13
> Authentication through http-interface with Elytron authentication and legacy SSL (without configured authentication) is not possible
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2641
> URL: https://issues.jboss.org/browse/WFCORE-2641
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Affects Versions: 3.0.0.Beta13
> Reporter: Ondrej Lukas
> Assignee: Brian Stansberry
> Priority: Blocker
>
> When http-interface uses http-authentication-factory attribute for authentication and security-realm attribute for SSL, and references security-realm does not include authentication, then authentication through http-interface is not possible.
> When Management Console is used, then page with _The Red Hat JBoss Enterprise Application Platform 7 is running. However you have not yet added any users to be able to access the admin console._ is displayed.
> When https://localhost:9993/management?operation=attribute&name=server-state is accessed then following output is returned:
> {code}
> {
> "outcome" : "failed",
> "failure-description" : "WFLYDMHTTP0006: The security realm is not ready to process requests, see https://localhost:9993/error",
> "rolled-back" : "true"
> }
> {code}
> When security-realm includes also authentication (which is not used) then authentication through http-interface works as expected.
> We request blocker flag because this issue blocks RFE EAP7-545. This issue is reported in EAP 7.1.0.DR16 because this configuration could not be set on application server due to JBEAP-7428, which was fixed in EAP 7.1.0.DR16.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-8537) Unmanaged transitive dependencies in JMS client BOM dependency tree
by Petr Sakař (JIRA)
[ https://issues.jboss.org/browse/WFLY-8537?page=com.atlassian.jira.plugin.... ]
Petr Sakař reassigned WFLY-8537:
--------------------------------
Assignee: Tomaz Cerar (was: Petr Sakař)
> Unmanaged transitive dependencies in JMS client BOM dependency tree
> -------------------------------------------------------------------
>
> Key: WFLY-8537
> URL: https://issues.jboss.org/browse/WFLY-8537
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Petr Sakař
> Assignee: Tomaz Cerar
> Priority: Critical
>
> There are upstream dependencies in JMS client BOM dependency tree:
> {code}
> commons-collections:commons-collections:jar:3.2.2:compile
> com.google.guava:guava:jar:19.0:compile
> org.wildfly.client:wildfly-client-config:jar:1.0.0.Beta2:compile
> {code}
> Full dependency tree is:
> {code}
> \- org.jboss.eap:wildfly-jms-client-bom:pom:7.1.0.Beta1-redhat-1:compile
> +- commons-beanutils:commons-beanutils:jar:1.9.3.redhat-1:compile
> | \- commons-collections:commons-collections:jar:3.2.2:compile
> +- io.netty:netty-all:jar:4.1.5.Final-redhat-2:compile
> +- org.apache.activemq:artemis-commons:jar:1.5.4.002-redhat-1:compile
> | \- com.google.guava:guava:jar:19.0:compile
> +- org.apache.activemq:artemis-core-client:jar:1.5.4.002-redhat-1:compile
> +- org.apache.activemq:artemis-hqclient-protocol:jar:1.5.4.002-redhat-1:compile
> +- org.apache.activemq:artemis-jms-client:jar:1.5.4.002-redhat-1:compile
> | \- org.apache.activemq:artemis-selector:jar:1.5.4.002-redhat-1:compile
> +- org.glassfish:javax.json:jar:1.0.4.redhat-1:compile
> +- org.jboss.logging:jboss-logging:jar:3.3.1.Final-redhat-1:compile
> +- org.jboss.marshalling:jboss-marshalling:jar:2.0.0.Beta5-redhat-1:compile
> +- org.jboss.marshalling:jboss-marshalling-river:jar:2.0.0.Beta5-redhat-1:compile
> +- org.jboss.remoting:jboss-remoting:jar:5.0.0.Beta19-redhat-1:compile
> | \- org.wildfly.client:wildfly-client-config:jar:1.0.0.Beta2:compile
> +- org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:jar:1.0.0.Final-redhat-1:compile
> +- org.jboss.xnio:xnio-api:jar:3.5.0.Beta4-redhat-1:compile
> +- org.jboss.xnio:xnio-nio:jar:3.5.0.Beta4-redhat-1:compile
> +- org.jgroups:jgroups:jar:3.6.13.Final-redhat-1:compile
> +- org.slf4j:jcl-over-slf4j:jar:1.7.22.redhat-1:compile
> +- org.slf4j:slf4j-api:jar:1.7.22.redhat-1:compile
> +- org.wildfly:wildfly-naming-client:jar:1.0.0.Beta13-redhat-1:compile
> +- org.wildfly.common:wildfly-common:jar:1.2.0.Beta9-redhat-1:compile
> \- org.wildfly.security:wildfly-elytron:jar:1.1.0.Beta34-redhat-1:compile
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-8537) Unmanaged transitive dependencies in JMS client BOM dependency tree
by Petr Sakař (JIRA)
[ https://issues.jboss.org/browse/WFLY-8537?page=com.atlassian.jira.plugin.... ]
Petr Sakař moved JBEAP-10207 to WFLY-8537:
------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8537 (was: JBEAP-10207)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: Maven Repository)
Affects Version/s: (was: 7.1.0.DR16)
> Unmanaged transitive dependencies in JMS client BOM dependency tree
> -------------------------------------------------------------------
>
> Key: WFLY-8537
> URL: https://issues.jboss.org/browse/WFLY-8537
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Petr Sakař
> Assignee: Petr Sakař
> Priority: Critical
>
> There are upstream dependencies in JMS client BOM dependency tree:
> {code}
> commons-collections:commons-collections:jar:3.2.2:compile
> com.google.guava:guava:jar:19.0:compile
> org.wildfly.client:wildfly-client-config:jar:1.0.0.Beta2:compile
> {code}
> Full dependency tree is:
> {code}
> \- org.jboss.eap:wildfly-jms-client-bom:pom:7.1.0.Beta1-redhat-1:compile
> +- commons-beanutils:commons-beanutils:jar:1.9.3.redhat-1:compile
> | \- commons-collections:commons-collections:jar:3.2.2:compile
> +- io.netty:netty-all:jar:4.1.5.Final-redhat-2:compile
> +- org.apache.activemq:artemis-commons:jar:1.5.4.002-redhat-1:compile
> | \- com.google.guava:guava:jar:19.0:compile
> +- org.apache.activemq:artemis-core-client:jar:1.5.4.002-redhat-1:compile
> +- org.apache.activemq:artemis-hqclient-protocol:jar:1.5.4.002-redhat-1:compile
> +- org.apache.activemq:artemis-jms-client:jar:1.5.4.002-redhat-1:compile
> | \- org.apache.activemq:artemis-selector:jar:1.5.4.002-redhat-1:compile
> +- org.glassfish:javax.json:jar:1.0.4.redhat-1:compile
> +- org.jboss.logging:jboss-logging:jar:3.3.1.Final-redhat-1:compile
> +- org.jboss.marshalling:jboss-marshalling:jar:2.0.0.Beta5-redhat-1:compile
> +- org.jboss.marshalling:jboss-marshalling-river:jar:2.0.0.Beta5-redhat-1:compile
> +- org.jboss.remoting:jboss-remoting:jar:5.0.0.Beta19-redhat-1:compile
> | \- org.wildfly.client:wildfly-client-config:jar:1.0.0.Beta2:compile
> +- org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:jar:1.0.0.Final-redhat-1:compile
> +- org.jboss.xnio:xnio-api:jar:3.5.0.Beta4-redhat-1:compile
> +- org.jboss.xnio:xnio-nio:jar:3.5.0.Beta4-redhat-1:compile
> +- org.jgroups:jgroups:jar:3.6.13.Final-redhat-1:compile
> +- org.slf4j:jcl-over-slf4j:jar:1.7.22.redhat-1:compile
> +- org.slf4j:slf4j-api:jar:1.7.22.redhat-1:compile
> +- org.wildfly:wildfly-naming-client:jar:1.0.0.Beta13-redhat-1:compile
> +- org.wildfly.common:wildfly-common:jar:1.2.0.Beta9-redhat-1:compile
> \- org.wildfly.security:wildfly-elytron:jar:1.1.0.Beta34-redhat-1:compile
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-8536) Unmanaged transitive dependencies in EJB client BOM dependency tree
by Petr Sakař (JIRA)
[ https://issues.jboss.org/browse/WFLY-8536?page=com.atlassian.jira.plugin.... ]
Petr Sakař moved JBEAP-10206 to WFLY-8536:
------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8536 (was: JBEAP-10206)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: EJB
(was: Maven Repository)
Affects Version/s: (was: 7.1.0.DR16)
> Unmanaged transitive dependencies in EJB client BOM dependency tree
> -------------------------------------------------------------------
>
> Key: WFLY-8536
> URL: https://issues.jboss.org/browse/WFLY-8536
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Petr Sakař
> Assignee: Tomaz Cerar
> Priority: Critical
>
> There are upstream dependencies in EJB client BOM dependency tree:
> {code}
> org.wildfly.discovery:wildfly-discovery-client:jar:1.0.0.Beta10:compile
> org.wildfly.transaction:wildfly-transaction-client:jar:1.0.0.Beta19:compile
> org.jboss.spec.javax.resource:jboss-connector-api_1.7_spec:jar:1.0.0.Final:compile
> org.wildfly.client:wildfly-client-config:jar:1.0.0.Beta2:compile
> {code}
> Full dependency tree is:
> {code}
> \- org.jboss.eap:wildfly-ejb-client-bom:pom:7.1.0.Beta1-redhat-1:compile
> +- org.jboss:jboss-ejb-client:jar:4.0.0.Beta24-redhat-1:compile
> | +- org.wildfly.discovery:wildfly-discovery-client:jar:1.0.0.Beta10:compile
> | \- org.wildfly.transaction:wildfly-transaction-client:jar:1.0.0.Beta19:compile
> | \- org.jboss.spec.javax.resource:jboss-connector-api_1.7_spec:jar:1.0.0.Final:compile
> +- org.jboss.logging:jboss-logging:jar:3.3.1.Final-redhat-1:compile
> +- org.jboss.marshalling:jboss-marshalling:jar:2.0.0.Beta5-redhat-1:compile
> +- org.jboss.marshalling:jboss-marshalling-river:jar:2.0.0.Beta5-redhat-1:compile
> +- org.jboss.remoting:jboss-remoting:jar:5.0.0.Beta19-redhat-1:compile
> | \- org.wildfly.client:wildfly-client-config:jar:1.0.0.Beta2:compile
> +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.1.Final-redhat-1:compile
> +- org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar:1.0.0.Final-redhat-1:compile
> +- org.jboss.xnio:xnio-api:jar:3.5.0.Beta4-redhat-1:compile
> +- org.jboss.xnio:xnio-nio:jar:3.5.0.Beta4-redhat-1:compile
> +- org.wildfly:wildfly-naming-client:jar:1.0.0.Beta13-redhat-1:compile
> +- org.wildfly.common:wildfly-common:jar:1.2.0.Beta9-redhat-1:compile
> \- org.wildfly.security:wildfly-elytron:jar:1.1.0.Beta34-redhat-1:compile
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months