August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3158) Upgrade to xnio 3.5.0.Final

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-3158: ---------------------------------- Summary: Upgrade to xnio 3.5.0.Final Key: WFCORE-3158 URL: https://issues.jboss.org/browse/WFCORE-3158 Project: WildFly Core Issue Type: Component Upgrade Reporter: Kabir Khan -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3158) Upgrade to xnio 3.5.0.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3158?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-3158: ------------------------------- Component/s: Remoting > Upgrade to xnio 3.5.0.Final > --------------------------- > > Key: WFCORE-3158 > URL: https://issues.jboss.org/browse/WFCORE-3158 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: Kabir Khan > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3159) Upgrade to xnio 3.5.0.Final

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-3159: ---------------------------------- Summary: Upgrade to xnio 3.5.0.Final Key: WFCORE-3159 URL: https://issues.jboss.org/browse/WFCORE-3159 Project: WildFly Core Issue Type: Component Upgrade Components: Remoting Reporter: Kabir Khan -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3157) Upgrade to remoting-jmx 3.0.0.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3157?page=com.atlassian.jira.plugi... ] Kabir Khan moved JBEAP-12584 to WFCORE-3157: -------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3157 (was: JBEAP-12584) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Remoting (was: Remoting) > Upgrade to remoting-jmx 3.0.0.Final > ----------------------------------- > > Key: WFCORE-3157 > URL: https://issues.jboss.org/browse/WFCORE-3157 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: Kabir Khan > Assignee: Darran Lofthouse > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9096) JMS client fails to connect with SSL on IBM JDK 8

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-9096?page=com.atlassian.jira.plugin.... ] Jan Kalina edited comment on WFLY-9096 at 8/7/17 7:39 AM: ---------------------------------------------------------- Waiting for *ARTEMIS-1299* fix backport merge: https://github.com/rh-messaging/jboss-activemq-artemis/pull/215 https://github.com/rh-messaging/jboss-activemq-artemis/pull/214 After it can be reopened: https://github.com/wildfly/wildfly/pull/10323 was (Author: honza889): Waiting for *ARTEMIS-1299* fix backport merge: https://github.com/rh-messaging/jboss-activemq-artemis/pull/215 https://github.com/rh-messaging/jboss-activemq-artemis/pull/214 > JMS client fails to connect with SSL on IBM JDK 8 > ------------------------------------------------- > > Key: WFLY-9096 > URL: https://issues.jboss.org/browse/WFLY-9096 > Project: WildFly > Issue Type: Bug > Components: JMS, Security > Affects Versions: 11.0.0.Alpha1 > Environment: IBM JDK 8: > {code} > $ java -version > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxi3280sr4fp2-20170322_01(SR4 FP2)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux x86-32 20170314_340265 (JIT enabled, AOT enabled) > J9VM - R28_20170314_2309_B340265 > JIT - tr.r14.java.green_20170314_134138 > GC - R28_20170314_2309_B340265 > J9CL - 20170314_340265) > JCL - 20170318_01 based on Oracle jdk8u121-b13 > {code} > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > Labels: eap7.1-risks-mitigation > > If server is configured to authenticate JMS client with SSL configured using Elytron SSLContext then if client is using IBM JDK 8, authentication fails with: > {code} > ERROR: AMQ214016: Failed to create netty connection > java.nio.channels.ClosedChannelException > at io.netty.handler.ssl.SslHandler.channelInactive(...)(Unknown Source) > Producer got exception and ended:javax.jms.JMSException: Failed to create session factory > javax.jms.JMSException: Failed to create session factory > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:757) > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:265) > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:260) > at ProducerTransSession.run(ProducerTransSession.java:75) > Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:787) > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:755) > ... 3 more > {code} > If client uses Oracle JDK 8 or SSL authentication is configured on http listener using PicketBox then client connects successfully. > Issue is under investigation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9096) JMS client fails to connect with SSL on IBM JDK 8

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-9096?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-9096: ---------------------------------- Waiting for *ARTEMIS-1299* fix backport merge: https://github.com/rh-messaging/jboss-activemq-artemis/pull/215 https://github.com/rh-messaging/jboss-activemq-artemis/pull/214 > JMS client fails to connect with SSL on IBM JDK 8 > ------------------------------------------------- > > Key: WFLY-9096 > URL: https://issues.jboss.org/browse/WFLY-9096 > Project: WildFly > Issue Type: Bug > Components: JMS, Security > Affects Versions: 11.0.0.Alpha1 > Environment: IBM JDK 8: > {code} > $ java -version > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxi3280sr4fp2-20170322_01(SR4 FP2)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux x86-32 20170314_340265 (JIT enabled, AOT enabled) > J9VM - R28_20170314_2309_B340265 > JIT - tr.r14.java.green_20170314_134138 > GC - R28_20170314_2309_B340265 > J9CL - 20170314_340265) > JCL - 20170318_01 based on Oracle jdk8u121-b13 > {code} > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > Labels: eap7.1-risks-mitigation > > If server is configured to authenticate JMS client with SSL configured using Elytron SSLContext then if client is using IBM JDK 8, authentication fails with: > {code} > ERROR: AMQ214016: Failed to create netty connection > java.nio.channels.ClosedChannelException > at io.netty.handler.ssl.SslHandler.channelInactive(...)(Unknown Source) > Producer got exception and ended:javax.jms.JMSException: Failed to create session factory > javax.jms.JMSException: Failed to create session factory > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:757) > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:265) > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:260) > at ProducerTransSession.run(ProducerTransSession.java:75) > Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:787) > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:755) > ... 3 more > {code} > If client uses Oracle JDK 8 or SSL authentication is configured on http listener using PicketBox then client connects successfully. > Issue is under investigation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3156) Upgrade to jboss-remoting 5.0.0.Final

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-3156: ---------------------------------- Summary: Upgrade to jboss-remoting 5.0.0.Final Key: WFCORE-3156 URL: https://issues.jboss.org/browse/WFCORE-3156 Project: WildFly Core Issue Type: Component Upgrade Components: Remoting Reporter: Kabir Khan Assignee: David Lloyd -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3155) Upgrade to jboss-remoting 5.0.0.Final

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-3155: ---------------------------------- Summary: Upgrade to jboss-remoting 5.0.0.Final Key: WFCORE-3155 URL: https://issues.jboss.org/browse/WFCORE-3155 Project: WildFly Core Issue Type: Component Upgrade Components: Remoting Reporter: Kabir Khan Assignee: David Lloyd -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3154) Upgrade jboss-modules to 1.6.0.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3154?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-3154: ------------------------------- Summary: Upgrade jboss-modules to 1.6.0.Final (was: Upgrade jboss-modules to 2.0.0.Final) > Upgrade jboss-modules to 1.6.0.Final > ------------------------------------ > > Key: WFCORE-3154 > URL: https://issues.jboss.org/browse/WFCORE-3154 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Modules > Reporter: Kabir Khan > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3154) Upgrade jboss-modules to 2.0.0.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3154?page=com.atlassian.jira.plugi... ] Kabir Khan moved JBEAP-12581 to WFCORE-3154: -------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3154 (was: JBEAP-12581) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Modules (was: Class Loading) > Upgrade jboss-modules to 2.0.0.Final > ------------------------------------ > > Key: WFCORE-3154 > URL: https://issues.jboss.org/browse/WFCORE-3154 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Modules > Reporter: Kabir Khan > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017