[JBoss JIRA] (WFLY-11290) Look up of RemoteConnectionFactory with discovery-group is null
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFLY-11290?page=com.atlassian.jira.plugin... ]
Miroslav Novak updated WFLY-11290:
----------------------------------
Steps to Reproduce:
Steps to reproduce:
{code}
git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout master
groovy -DEAP_ZIP_URL=http://download.jboss.org/wildfly/14.0.1.Final/wildfly-14.0.1.Final.zip PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=RemoteBrokerTestCase#testConnectionFactoryWithDiscoveryGroup -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.2.0.CD14.CR2 | tee log
{code}
> Look up of RemoteConnectionFactory with discovery-group is null
> ---------------------------------------------------------------
>
> Key: WFLY-11290
> URL: https://issues.jboss.org/browse/WFLY-11290
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Reporter: Miroslav Novak
> Assignee: ehsavoie Hugonnet
> Priority: Major
>
> If RemoteConnectionFactory is defined with discovery-group like (note that it's defined directly in messaging subsystem, not in <server>...</server>):
> {code}
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:4.0">
> <discovery-group name="dg-group1" jgroups-channel="ee" jgroups-cluster="artemis-cluster" initial-wait-timeout="30000"/>
> <connection-factory name="RemoteConnectionFactory" discovery-group="dg-group1" entries="java:jboss/exported/jms/RemoteConnectionFactory java:/jms/RemoteConnectionFactory"/>
> </subsystem>
> {code}
> then it registers to JNDI "java:/jms/RemoteConnectionFactory" but with {{null}}. See JNDI view:
> {code}
> [standalone@localhost:9990 subsystem=naming] /subsystem=naming/:jndi-view
> ...
> "jms" => {
> "class-name" => "javax.naming.Context",
> "children" => {
> "RemoteConnectionFactory" => {
> "class-name" => "java.lang.Object",
> "value" => "null"
> },
> {code}
> Result:
> If EE deployment looks up or injects such CF then it fails on NullPointerException.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11290) Look up of RemoteConnectionFactory with discovery-group is null
by Miroslav Novak (Jira)
Miroslav Novak created WFLY-11290:
-------------------------------------
Summary: Look up of RemoteConnectionFactory with discovery-group is null
Key: WFLY-11290
URL: https://issues.jboss.org/browse/WFLY-11290
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 14.0.0.Final
Reporter: Miroslav Novak
Assignee: Jeff Mesnil
If RemoteConnectionFactory is defined with discovery-group like (note that it's defined directly in messaging subsystem, not in <server>...</server>):
{code}
<subsystem xmlns="urn:jboss:domain:messaging-activemq:4.0">
<discovery-group name="dg-group1" jgroups-channel="ee" jgroups-cluster="artemis-cluster" initial-wait-timeout="30000"/>
<connection-factory name="RemoteConnectionFactory" discovery-group="dg-group1" entries="java:jboss/exported/jms/RemoteConnectionFactory java:/jms/RemoteConnectionFactory"/>
</subsystem>
{code}
then it registers to JNDI "java:/jms/RemoteConnectionFactory" but with {{null}}. See JNDI view:
{code}
[standalone@localhost:9990 subsystem=naming] /subsystem=naming/:jndi-view
...
"jms" => {
"class-name" => "javax.naming.Context",
"children" => {
"RemoteConnectionFactory" => {
"class-name" => "java.lang.Object",
"value" => "null"
},
{code}
Result:
If EE deployment looks up or injects such CF then it fails on NullPointerException.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11290) Look up of RemoteConnectionFactory with discovery-group is null
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFLY-11290?page=com.atlassian.jira.plugin... ]
Miroslav Novak reassigned WFLY-11290:
-------------------------------------
Assignee: ehsavoie Hugonnet (was: Jeff Mesnil)
> Look up of RemoteConnectionFactory with discovery-group is null
> ---------------------------------------------------------------
>
> Key: WFLY-11290
> URL: https://issues.jboss.org/browse/WFLY-11290
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Reporter: Miroslav Novak
> Assignee: ehsavoie Hugonnet
> Priority: Major
>
> If RemoteConnectionFactory is defined with discovery-group like (note that it's defined directly in messaging subsystem, not in <server>...</server>):
> {code}
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:4.0">
> <discovery-group name="dg-group1" jgroups-channel="ee" jgroups-cluster="artemis-cluster" initial-wait-timeout="30000"/>
> <connection-factory name="RemoteConnectionFactory" discovery-group="dg-group1" entries="java:jboss/exported/jms/RemoteConnectionFactory java:/jms/RemoteConnectionFactory"/>
> </subsystem>
> {code}
> then it registers to JNDI "java:/jms/RemoteConnectionFactory" but with {{null}}. See JNDI view:
> {code}
> [standalone@localhost:9990 subsystem=naming] /subsystem=naming/:jndi-view
> ...
> "jms" => {
> "class-name" => "javax.naming.Context",
> "children" => {
> "RemoteConnectionFactory" => {
> "class-name" => "java.lang.Object",
> "value" => "null"
> },
> {code}
> Result:
> If EE deployment looks up or injects such CF then it fails on NullPointerException.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11290) Look up of RemoteConnectionFactory with discovery-group is null
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFLY-11290?page=com.atlassian.jira.plugin... ]
Miroslav Novak commented on WFLY-11290:
---------------------------------------
[~ehugonnet] Could you take a look, please?
> Look up of RemoteConnectionFactory with discovery-group is null
> ---------------------------------------------------------------
>
> Key: WFLY-11290
> URL: https://issues.jboss.org/browse/WFLY-11290
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Reporter: Miroslav Novak
> Assignee: ehsavoie Hugonnet
> Priority: Major
>
> If RemoteConnectionFactory is defined with discovery-group like (note that it's defined directly in messaging subsystem, not in <server>...</server>):
> {code}
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:4.0">
> <discovery-group name="dg-group1" jgroups-channel="ee" jgroups-cluster="artemis-cluster" initial-wait-timeout="30000"/>
> <connection-factory name="RemoteConnectionFactory" discovery-group="dg-group1" entries="java:jboss/exported/jms/RemoteConnectionFactory java:/jms/RemoteConnectionFactory"/>
> </subsystem>
> {code}
> then it registers to JNDI "java:/jms/RemoteConnectionFactory" but with {{null}}. See JNDI view:
> {code}
> [standalone@localhost:9990 subsystem=naming] /subsystem=naming/:jndi-view
> ...
> "jms" => {
> "class-name" => "javax.naming.Context",
> "children" => {
> "RemoteConnectionFactory" => {
> "class-name" => "java.lang.Object",
> "value" => "null"
> },
> {code}
> Result:
> If EE deployment looks up or injects such CF then it fails on NullPointerException.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11289) Artemis AMQP protocol requires proton-j...jar if SASL is used
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFLY-11289?page=com.atlassian.jira.plugin... ]
Miroslav Novak commented on WFLY-11289:
---------------------------------------
[~ehugonnet] [~jmesnil] This one was hit by community member for AMQP protocol. The question is whether to add proton-j to amqp protocol module.
> Artemis AMQP protocol requires proton-j...jar if SASL is used
> -------------------------------------------------------------
>
> Key: WFLY-11289
> URL: https://issues.jboss.org/browse/WFLY-11289
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Reporter: Miroslav Novak
> Assignee: ehsavoie Hugonnet
> Priority: Major
>
> If AMQP client uses SASL authentication then connection fails with:
> {code}
> 2018-11-05 12:08:01,636 TRACE [org.jboss.modules] (Thread-1 (activemq-netty-threads)) Class org.apache.qpid.proton.engine.SaslListener not found from Module "org.apache.activemq.artemis.protocol.amqp" from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /apps/wildfly14.0/modules,/apps/wildfly14.0/modules/system/layers/base))
> 2018-11-05 12:08:01,636 WARN [org.jboss.modules.define] (Thread-1 (activemq-netty-threads)) Failed to define class org.apache.activemq.artemis.protocol.amqp.proton.handler.ProtonHandler in Module "org.apache.activemq.artemis.protocol.amqp" from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /apps/wildfly14.0/modules,/apps/wildfly14.0/modules/system/layers/base)): java.lang.NoClassDefFoundError: Failed to link org/apache/activemq/artemis/protocol/amqp/proton/handler/ProtonHandler (Module "org.apache.activemq.artemis.protocol.amqp" from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /apps/wildfly14.0/modules,/apps/wildfly14.0/modules/system/layers/base))): org/apache/qpid/proton/engine/SaslListener
> {code}
> It requires proton-j-0.27.3.jar to be added to org.apache.activemq.artemis.protocol.amqp module. It appears to missing and should be added.
> See: https://developer.jboss.org/message/986253 for more information.
> Credit for finding this problem goes to [~ninjasftw]
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11289) Artemis AMQP protocol requires proton-j...jar if SASL is used
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFLY-11289?page=com.atlassian.jira.plugin... ]
Miroslav Novak reassigned WFLY-11289:
-------------------------------------
Assignee: ehsavoie Hugonnet (was: Jeff Mesnil)
> Artemis AMQP protocol requires proton-j...jar if SASL is used
> -------------------------------------------------------------
>
> Key: WFLY-11289
> URL: https://issues.jboss.org/browse/WFLY-11289
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Reporter: Miroslav Novak
> Assignee: ehsavoie Hugonnet
> Priority: Major
>
> If AMQP client uses SASL authentication then connection fails with:
> {code}
> 2018-11-05 12:08:01,636 TRACE [org.jboss.modules] (Thread-1 (activemq-netty-threads)) Class org.apache.qpid.proton.engine.SaslListener not found from Module "org.apache.activemq.artemis.protocol.amqp" from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /apps/wildfly14.0/modules,/apps/wildfly14.0/modules/system/layers/base))
> 2018-11-05 12:08:01,636 WARN [org.jboss.modules.define] (Thread-1 (activemq-netty-threads)) Failed to define class org.apache.activemq.artemis.protocol.amqp.proton.handler.ProtonHandler in Module "org.apache.activemq.artemis.protocol.amqp" from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /apps/wildfly14.0/modules,/apps/wildfly14.0/modules/system/layers/base)): java.lang.NoClassDefFoundError: Failed to link org/apache/activemq/artemis/protocol/amqp/proton/handler/ProtonHandler (Module "org.apache.activemq.artemis.protocol.amqp" from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /apps/wildfly14.0/modules,/apps/wildfly14.0/modules/system/layers/base))): org/apache/qpid/proton/engine/SaslListener
> {code}
> It requires proton-j-0.27.3.jar to be added to org.apache.activemq.artemis.protocol.amqp module. It appears to missing and should be added.
> See: https://developer.jboss.org/message/986253 for more information.
> Credit for finding this problem goes to [~ninjasftw]
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (ELY-1663) BC FIPS, Management Interface, ELY04001: No algorithm found matching TLS/SSL protocol selection criteria
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/ELY-1663?page=com.atlassian.jira.plugin.s... ]
Martin Choma commented on ELY-1663:
-----------------------------------
Sure, I assume this is not going to be for 1.6.x stream. So I am putting priority of this task after EAP GA work and WF 15 feature freeze work.
> BC FIPS, Management Interface, ELY04001: No algorithm found matching TLS/SSL protocol selection criteria
> --------------------------------------------------------------------------------------------------------
>
> Key: ELY-1663
> URL: https://issues.jboss.org/browse/ELY-1663
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.6.0.Final
> Reporter: Martin Choma
> Assignee: Farah Juma
> Priority: Blocker
>
> Rarely 1:30 it happens there occures error accessing http management interface secured with TLS with BC FIPS
> {code}
> Operation {"operation" => "add","address" => [("subsystem" => "elytron"),("server-ssl-context" => "test-server-ssl-context")],"key-manager" => "key-manager-name_test-server-ssl-context","cipher-suite-filter" => "TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA256,TLS_DHE_DSS_WITH_AES_256_CBC_SHA,TLS_DHE_DSS_WITH_AES_256_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256","trust-manager" => "trust-manager-name_test-server-ssl-context","protocols" => ["TLSv1.2"],"need-client-auth" => true} failed: {"outcome" => "failed","failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.test-server-ssl-context" => "java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria
> Caused by: java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria"}},"rolled-back" => true}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service org.wildfly.security.ssl-context.test-server-ssl-context: org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.test-server-ssl-context: java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria
> at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:982)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria
> at org.wildfly.security.ssl.SSLUtils.lambda$createSslContextFactory$1(SSLUtils.java:130)
> at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:340)
> at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53)
> at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:980)
> ... 9 more
> {code}
> Some facts
> * It happens only on management interface BC FIPS TLS tests
> * It does not occur on Undertow secured with BC FIPS
> * Previously there was issue with similar error but that happened everywhere https://issues.jboss.org/browse/ELY-1618
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2569) [DMN Designer] Marshalling of magnet positions
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2569?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2569:
--------------------------------
Description:
When attaching connectors to different magnets (other than "centre") re-opening a DMN diagram resets connections to the "centre" magnet. IDK if this is an issue with writing magnet positions to the XML or recreating the connections from the XML.
[~tari_manga] could you please liaise with [~roger600] to understand where the issue is?
h2. PR Acceptance test
In DMN Designer, change magnet position in:
- Source node
-- BKM(/), BKS (/), Decision(/), Input (/)
- Target node
-- BKM(/), BKS(/), Decision (/), Annotation (/)
was:
When attaching connectors to different magnets (other than "centre") re-opening a DMN diagram resets connections to the "centre" magnet. IDK if this is an issue with writing magnet positions to the XML or recreating the connections from the XML.
[~tari_manga] could you please liaise with [~roger600] to understand where the issue is?
h2. PR Acceptance test
In DMN Designer, change magnet position in:
- Source node
-- BKM(/), BKS (/), Decision(/), Input (/)
- Target node
-- BKM(/), BKS(/), Decision (/), Annotation (x)
> [DMN Designer] Marshalling of magnet positions
> ----------------------------------------------
>
> Key: DROOLS-2569
> URL: https://issues.jboss.org/browse/DROOLS-2569
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Matteo Mortari
> Priority: Major
> Labels: drools-tools
> Attachments: after_save.png, before_save.png
>
>
> When attaching connectors to different magnets (other than "centre") re-opening a DMN diagram resets connections to the "centre" magnet. IDK if this is an issue with writing magnet positions to the XML or recreating the connections from the XML.
> [~tari_manga] could you please liaise with [~roger600] to understand where the issue is?
> h2. PR Acceptance test
> In DMN Designer, change magnet position in:
> - Source node
> -- BKM(/), BKS (/), Decision(/), Input (/)
> - Target node
> -- BKM(/), BKS(/), Decision (/), Annotation (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11289) Artemis AMQP protocol requires proton-j...jar if SASL is used
by Miroslav Novak (Jira)
Miroslav Novak created WFLY-11289:
-------------------------------------
Summary: Artemis AMQP protocol requires proton-j...jar if SASL is used
Key: WFLY-11289
URL: https://issues.jboss.org/browse/WFLY-11289
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 14.0.0.Final
Reporter: Miroslav Novak
Assignee: Jeff Mesnil
If AMQP client uses SASL authentication then connection fails with:
{code}
2018-11-05 12:08:01,636 TRACE [org.jboss.modules] (Thread-1 (activemq-netty-threads)) Class org.apache.qpid.proton.engine.SaslListener not found from Module "org.apache.activemq.artemis.protocol.amqp" from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /apps/wildfly14.0/modules,/apps/wildfly14.0/modules/system/layers/base))
2018-11-05 12:08:01,636 WARN [org.jboss.modules.define] (Thread-1 (activemq-netty-threads)) Failed to define class org.apache.activemq.artemis.protocol.amqp.proton.handler.ProtonHandler in Module "org.apache.activemq.artemis.protocol.amqp" from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /apps/wildfly14.0/modules,/apps/wildfly14.0/modules/system/layers/base)): java.lang.NoClassDefFoundError: Failed to link org/apache/activemq/artemis/protocol/amqp/proton/handler/ProtonHandler (Module "org.apache.activemq.artemis.protocol.amqp" from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /apps/wildfly14.0/modules,/apps/wildfly14.0/modules/system/layers/base))): org/apache/qpid/proton/engine/SaslListener
{code}
It requires proton-j-0.27.3.jar to be added to org.apache.activemq.artemis.protocol.amqp module. It appears to missing and should be added.
See: https://developer.jboss.org/message/986253 for more information.
Credit for finding this problem goes to [~ninjasftw]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months