August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4026) Create Version 5 of the Elytron subsystem model and schema.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-4026: ---------------------------------------- Summary: Create Version 5 of the Elytron subsystem model and schema. Key: WFCORE-4026 URL: https://issues.jboss.org/browse/WFCORE-4026 Project: WildFly Core Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-364) Kiali's 'istio-1.0' branch testing

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-364?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan closed SWSQE-364. -------------------------------- Resolution: Done branch is merged to master > Kiali's 'istio-1.0' branch testing > ---------------------------------- > > Key: SWSQE-364 > URL: https://issues.jboss.org/browse/SWSQE-364 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10383) Multiple test failures due to Weld class init problem

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-10383?page=com.atlassian.jira.plugin... ] Martin Kouba resolved WFLY-10383. --------------------------------- Resolution: Done > Multiple test failures due to Weld class init problem > ----------------------------------------------------- > > Key: WFLY-10383 > URL: https://issues.jboss.org/browse/WFLY-10383 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Reporter: David Lloyd > Assignee: Martin Kouba > Priority: Critical > Labels: security-manager > > This is the upstream tracking issue for WELD-2496. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10383) Multiple test failures due to Weld class init problem

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-10383?page=com.atlassian.jira.plugin... ] Martin Kouba updated WFLY-10383: -------------------------------- Fix Version/s: 14.0.0.CR1 > Multiple test failures due to Weld class init problem > ----------------------------------------------------- > > Key: WFLY-10383 > URL: https://issues.jboss.org/browse/WFLY-10383 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Reporter: David Lloyd > Assignee: Martin Kouba > Priority: Critical > Labels: security-manager > Fix For: 14.0.0.CR1 > > > This is the upstream tracking issue for WELD-2496. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-84) [Artemis 2.x upgrade] MDB deployed on EAP 7.2.0 with new Artemis cannot connect to queue deployed on EAP6

by Martyn Taylor (JIRA)

[ https://issues.jboss.org/browse/WFWIP-84?page=com.atlassian.jira.plugin.s... ] Martyn Taylor reassigned WFWIP-84: ---------------------------------- Assignee: Martyn Taylor (was: Justin Bertram) > [Artemis 2.x upgrade] MDB deployed on EAP 7.2.0 with new Artemis cannot connect to queue deployed on EAP6 > --------------------------------------------------------------------------------------------------------- > > Key: WFWIP-84 > URL: https://issues.jboss.org/browse/WFWIP-84 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis, JMS > Reporter: Martin Švehla > Assignee: Martyn Taylor > Priority: Blocker > Labels: activemq, feature-branch-blocker > > I'm not able to connect with MDB deployed on WF14/EAP 7.2.0 with new Artemis to destination deployed on EAP6. > CLI for configuration EAP7: > {code} > /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-eap6-binding:add(port=6445) > /subsystem=messaging-activemq/server=default/remote-connector=remote-eap6-connector:add(socket-bidning=remote-eap6-binding) > /subsystem=messaging-activemq/server=default/pooled-connection-factory=remote-eap6:add(connectors=[remote-eap6-connector], entries=["jms/remote-eap6", "java:jboss/exported/jms/remote-eap6"], protocol-manager-factory="org.apache.activemq.artemis.core.protocol.hornetq.client.HornetQClientProtocolManagerFactory) > {code} > The MDB is annotated with > {code} > @MessageDriven(activationConfig = { > @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"), > @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), > @ActivationConfigProperty(propertyName = "destination", propertyValue = "InQueue"), > @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge") > }) > @ResourceAdapter("remote-eap6") > {code} > This setup worked with EAP 7.1.x and EAP 7.2.0.Beta with older Artemis -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-84) [Artemis 2.x upgrade] MDB deployed on EAP 7.2.0 with new Artemis cannot connect to queue deployed on EAP6

by Martyn Taylor (JIRA)

[ https://issues.jboss.org/browse/WFWIP-84?page=com.atlassian.jira.plugin.s... ] Martyn Taylor closed WFWIP-84. ------------------------------ Resolution: Duplicate Issue > [Artemis 2.x upgrade] MDB deployed on EAP 7.2.0 with new Artemis cannot connect to queue deployed on EAP6 > --------------------------------------------------------------------------------------------------------- > > Key: WFWIP-84 > URL: https://issues.jboss.org/browse/WFWIP-84 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis, JMS > Reporter: Martin Švehla > Assignee: Martyn Taylor > Priority: Blocker > Labels: activemq, feature-branch-blocker > > I'm not able to connect with MDB deployed on WF14/EAP 7.2.0 with new Artemis to destination deployed on EAP6. > CLI for configuration EAP7: > {code} > /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-eap6-binding:add(port=6445) > /subsystem=messaging-activemq/server=default/remote-connector=remote-eap6-connector:add(socket-bidning=remote-eap6-binding) > /subsystem=messaging-activemq/server=default/pooled-connection-factory=remote-eap6:add(connectors=[remote-eap6-connector], entries=["jms/remote-eap6", "java:jboss/exported/jms/remote-eap6"], protocol-manager-factory="org.apache.activemq.artemis.core.protocol.hornetq.client.HornetQClientProtocolManagerFactory) > {code} > The MDB is annotated with > {code} > @MessageDriven(activationConfig = { > @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"), > @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), > @ActivationConfigProperty(propertyName = "destination", propertyValue = "InQueue"), > @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge") > }) > @ResourceAdapter("remote-eap6") > {code} > This setup worked with EAP 7.1.x and EAP 7.2.0.Beta with older Artemis -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-14) [Artemis upgrade] MDB cannot connect to remote server via RA if destination is not deployed locally

by Martyn Taylor (JIRA)

[ https://issues.jboss.org/browse/WFWIP-14?page=com.atlassian.jira.plugin.s... ] Martyn Taylor closed WFWIP-14. ------------------------------ Resolution: Duplicate Issue > [Artemis upgrade] MDB cannot connect to remote server via RA if destination is not deployed locally > --------------------------------------------------------------------------------------------------- > > Key: WFWIP-14 > URL: https://issues.jboss.org/browse/WFWIP-14 > Project: WildFly WIP > Issue Type: Bug > Components: JMS > Reporter: Erich Duda > Assignee: Martyn Taylor > Priority: Blocker > Labels: activemq, feature-branch-blocker > > For more information about origin of this issue see JBEAP-13857. > *Scenario* > * There are two servers called JMS servers which have deployed destinations > * There are two servers called MDB servers which have configured RA to connect to JMS servers and have deployed MDBs > * MDBs resend messages from InQueue to OutQueue > *Issue:* RA on MDB servers is not able to connect to JMS servers. > *Detailed description of the issue* > There is an MDB with following activation config: > {code} > @MessageDriven(name = "mdb1", > activationConfig = { > @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), > @ActivationConfigProperty(propertyName = "destination", propertyValue = "jms/queue/InQueue"), > @ActivationConfigProperty(propertyName = "rebalanceConnections", propertyValue = "true"), > @ActivationConfigProperty(propertyName = "hA", propertyValue = "true"), > @ActivationConfigProperty(propertyName = "messageSelector", propertyValue = "color = 'RED'")}) > {code} > In ActiveMQActivation::setupDestination method there is a code which tries to do a JNDI lookup. If it fails the destination is created using the ActiveMQJMSClient::createQueue where the destination name is created from the JNDI name. > {code} > try { > destination = (ActiveMQDestination) ActiveMQRaUtils.lookup(ctx, destinationName, destinationType); > } catch (Exception e) { > if (destinationName == null) { > throw ActiveMQRABundle.BUNDLE.noDestinationName(); > } > String calculatedDestinationName = destinationName.substring(destinationName.lastIndexOf('/') + 1); > logger.debug("Unable to retrieve " + destinationName + > " from JNDI. Creating a new " + destinationType.getName() + > " named " + calculatedDestinationName + " to be used by the MDB."); > // If there is no binding on naming, we will just create a new instance > if (isTopic) { > destination = (ActiveMQDestination) ActiveMQJMSClient.createTopic(calculatedDestinationName); > } else { > destination = (ActiveMQDestination) ActiveMQJMSClient.createQueue(calculatedDestinationName); > } > } > {code} > When the destination is not deployed locally (on the same server as MDB is deployed), the lookup fails and the destination is created using {{ActiveMQJMSClient::createQueue}} method, where {{calculatedDestinationName}} is {{InQueue}}. > Later in the code, when RA tries to connect to the remote EAP server, it uses this destination when it creates a consumer. Since on the remote server there is no destination with core address {{InQueue}}, the request to create the consumer fails and it is being periodically retried. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-84) [Artemis 2.x upgrade] MDB deployed on EAP 7.2.0 with new Artemis cannot connect to queue deployed on EAP6

by Martyn Taylor (JIRA)

[ https://issues.jboss.org/browse/WFWIP-84?page=com.atlassian.jira.plugin.s... ] Martyn Taylor reopened WFWIP-84: -------------------------------- > [Artemis 2.x upgrade] MDB deployed on EAP 7.2.0 with new Artemis cannot connect to queue deployed on EAP6 > --------------------------------------------------------------------------------------------------------- > > Key: WFWIP-84 > URL: https://issues.jboss.org/browse/WFWIP-84 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis, JMS > Reporter: Martin Švehla > Assignee: Justin Bertram > Priority: Blocker > Labels: activemq, feature-branch-blocker > > I'm not able to connect with MDB deployed on WF14/EAP 7.2.0 with new Artemis to destination deployed on EAP6. > CLI for configuration EAP7: > {code} > /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-eap6-binding:add(port=6445) > /subsystem=messaging-activemq/server=default/remote-connector=remote-eap6-connector:add(socket-bidning=remote-eap6-binding) > /subsystem=messaging-activemq/server=default/pooled-connection-factory=remote-eap6:add(connectors=[remote-eap6-connector], entries=["jms/remote-eap6", "java:jboss/exported/jms/remote-eap6"], protocol-manager-factory="org.apache.activemq.artemis.core.protocol.hornetq.client.HornetQClientProtocolManagerFactory) > {code} > The MDB is annotated with > {code} > @MessageDriven(activationConfig = { > @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"), > @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), > @ActivationConfigProperty(propertyName = "destination", propertyValue = "InQueue"), > @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge") > }) > @ResourceAdapter("remote-eap6") > {code} > This setup worked with EAP 7.1.x and EAP 7.2.0.Beta with older Artemis -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-84) [Artemis 2.x upgrade] MDB deployed on EAP 7.2.0 with new Artemis cannot connect to queue deployed on EAP6

by Martyn Taylor (JIRA)

[ https://issues.jboss.org/browse/WFWIP-84?page=com.atlassian.jira.plugin.s... ] Martyn Taylor closed WFWIP-84. ------------------------------ Resolution: Done > [Artemis 2.x upgrade] MDB deployed on EAP 7.2.0 with new Artemis cannot connect to queue deployed on EAP6 > --------------------------------------------------------------------------------------------------------- > > Key: WFWIP-84 > URL: https://issues.jboss.org/browse/WFWIP-84 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis, JMS > Reporter: Martin Švehla > Assignee: Justin Bertram > Priority: Blocker > Labels: activemq, feature-branch-blocker > > I'm not able to connect with MDB deployed on WF14/EAP 7.2.0 with new Artemis to destination deployed on EAP6. > CLI for configuration EAP7: > {code} > /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-eap6-binding:add(port=6445) > /subsystem=messaging-activemq/server=default/remote-connector=remote-eap6-connector:add(socket-bidning=remote-eap6-binding) > /subsystem=messaging-activemq/server=default/pooled-connection-factory=remote-eap6:add(connectors=[remote-eap6-connector], entries=["jms/remote-eap6", "java:jboss/exported/jms/remote-eap6"], protocol-manager-factory="org.apache.activemq.artemis.core.protocol.hornetq.client.HornetQClientProtocolManagerFactory) > {code} > The MDB is annotated with > {code} > @MessageDriven(activationConfig = { > @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"), > @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), > @ActivationConfigProperty(propertyName = "destination", propertyValue = "InQueue"), > @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge") > }) > @ResourceAdapter("remote-eap6") > {code} > This setup worked with EAP 7.1.x and EAP 7.2.0.Beta with older Artemis -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1624) BC FIPS with CLI: Could not connect to remote+https://127.0.0.1:9993. The connection timed out

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1624?page=com.atlassian.jira.plugin.s... ] Martin Choma commented on ELY-1624: ----------------------------------- [~fjuma] thank you for this deep investigation. This is really interesting. Couple of questions comes to my mind. - Does this change has performance implication? Eg. bigger memory footprint on environment with lot of ssl connections? Is it worth to have this parameter configurable (at least through system property in xnio)? So users have option to keep the old behaviour? - How is it possible root exception was hidden to me? - When will this fix make it into WF? > BC FIPS with CLI: Could not connect to remote+https://127.0.0.1:9993. The connection timed out > ---------------------------------------------------------------------------------------------- > > Key: ELY-1624 > URL: https://issues.jboss.org/browse/ELY-1624 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Reporter: Martin Choma > Assignee: Farah Juma > Priority: Blocker > Attachments: eap_server.log, jboss-cli.log, keystore.bcfks, standalone.xml > > > I am trying to connect from jboss-cli.sh to EAP server. Server and client run with BC FIPS. > {code:java|title=jboss-cli.log} > 11:48:08,992 TRACE [org.jboss.remoting.remote] Attempting to connect to "remote+https://127.0.0.1:9993" with options {org.xnio.Options.SSL_STARTTLS=>false,org.xnio.Options.SSL_ENABLED=>true} > 11:48:14,005 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:304) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45) > at org.jboss.modules.Module.run(Module.java:352) > at org.jboss.modules.Module.run(Module.java:320) > at org.jboss.modules.Main.main(Main.java:593) > Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at 127.0.0.1:9993 > at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1447) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1226) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328) > ... 5 more > Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+https://127.0.0.1:9993. The connection timed out > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75) > at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1394) > ... 9 more > Caused by: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+https://127.0.0.1:9993. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:130) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:167) > at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:192) > at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:126) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) > {code} > It works when I use > - non-FIPS java for CLI and FIPS java for server when connecting to secured 9993 port > - FIPS java for CLI and non-FIPS java for server when connecting to unsecured port 9990 > Here I get getting over ELY-1621 and ELY-1622 > I would appreciate any hint for way of investigation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2018