July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9106) Hard-code default values in messaging-activemq subsystem.

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-9106: --------------------------------- Summary: Hard-code default values in messaging-activemq subsystem. Key: WFLY-9106 URL: https://issues.jboss.org/browse/WFLY-9106 Project: WildFly Issue Type: Bug Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil The messaging-activemq subsystem defines plenty of attributes that maps to Artemis configuration. Most of these attributes have default values. The default values are taken from Artemis API (ActiveMQClient.*, ActiveMQDefaultConfiguration.*) This has the advantages that we use the sensible default values provided by Artemis itself. However there some unintended consequences. When Artemis change one of this default, it also changes the default value of the corresponding WildFly attribute. We have strict rule to handle this (with resource transformers, etc.) but this should not be something by happen by accident. We don't have a mechanism today that catch this kind of issue. Some of this may be caught by transformers tests *if* the resource is actually defined in the transformers configuration (but usually I only add a resource to the transformer when I am explicitly changing its definition). We should hard-code *all* default values of the messaging-activemq subsystem instead of relying on Artemis API (the actual value will often be the same than the one provided by Artemis though). This will protect us of Artemis API changes so that we can decide to change a default value when it makes sense separately of Artemis upgrades. However, we will have to sync with Artemis when they do such changes to figure out if we should do that too or keep the previous value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9105) Add an example domain-ec2.xml file to the docs/examples/config directory

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-9105?page=com.atlassian.jira.plugin.... ] Farah Juma moved JBEAP-12224 to WFLY-9105: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9105 (was: JBEAP-12224) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) > Add an example domain-ec2.xml file to the docs/examples/config directory > ------------------------------------------------------------------------ > > Key: WFLY-9105 > URL: https://issues.jboss.org/browse/WFLY-9105 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Farah Juma > Assignee: Farah Juma > > The {{docs/examples/config}} directory already contains an example {{standalone-ec2-ha.xml}} file and an example {{standalone-ec2-full-ha.xml}} file. Once an example {{domain-ec2.xml}} file has also been added to this directory, the EAP 7.1 AMIs will be able to switch over to using these EC2 example configuration files directly instead of manually creating custom example EC2 configuration files. > My current changes to get a domain-ec2.xml file added can be seen here: > https://github.com/fjuma/wildfly/commit/602e5e78c3a6887acab07a28d3439aad3... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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: ---------------------------------- Adding reasonable default into *messaging-activemq* subsystem is blocked by ARTEMIS-1299. For now can be resolved in test, by setting *enabled-protocols* in test setup task: https://issues.jboss.org/secure/attachment/12422489/commit-c333ea8-fix > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9104) Upgrade HAL to 2.9.12.Final

by Harald Pehl (JIRA)

Harald Pehl created WFLY-9104: --------------------------------- Summary: Upgrade HAL to 2.9.12.Final Key: WFLY-9104 URL: https://issues.jboss.org/browse/WFLY-9104 Project: WildFly Issue Type: Component Upgrade Components: Web Console Reporter: Harald Pehl Assignee: Harald Pehl Fix For: 11.0.0.Beta1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9104) Upgrade HAL to 2.9.12.Final

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-9104?page=com.atlassian.jira.plugin.... ] Harald Pehl updated WFLY-9104: ------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/10249) > Upgrade HAL to 2.9.12.Final > --------------------------- > > Key: WFLY-9104 > URL: https://issues.jboss.org/browse/WFLY-9104 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9103) WildFly Elytron Tool, Vault command should support set security provider to convert vaults to custom credential store implementation.

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-9103: ---------------------------------- Summary: WildFly Elytron Tool, Vault command should support set security provider to convert vaults to custom credential store implementation. Key: WFLY-9103 URL: https://issues.jboss.org/browse/WFLY-9103 Project: WildFly Issue Type: Bug Components: Security Reporter: Hynek Švábek Assignee: Darran Lofthouse WildFly Elytron Tool, Vault command should support set security provider to convert vaults to custom credential store implementation. Something similar to credential-store command. http://undertheelytron.blogspot.cz/2017/07/custom-test-credential-store.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-143) Manual - Run smoke set of manual tests - Results in Polarion

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-143?page=com.atlassian.jira.pl... ] Sunil kondkar commented on HAWKULARQE-143: ------------------------------------------ Manual smoke test is pass Test run: https://polarion-sharedservices.rhev-ci-vms.eng.rdu2.redhat.com/polarion/... > Manual - Run smoke set of manual tests - Results in Polarion > ------------------------------------------------------------ > > Key: HAWKULARQE-143 > URL: https://issues.jboss.org/browse/HAWKULARQE-143 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Sunil kondkar > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-143) Manual - Run smoke set of manual tests - Results in Polarion

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-143?page=com.atlassian.jira.pl... ] Sunil kondkar resolved HAWKULARQE-143. -------------------------------------- Resolution: Done > Manual - Run smoke set of manual tests - Results in Polarion > ------------------------------------------------------------ > > Key: HAWKULARQE-143 > URL: https://issues.jboss.org/browse/HAWKULARQE-143 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Sunil kondkar > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-143) Manual - Run smoke set of manual tests - Results in Polarion

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-143?page=com.atlassian.jira.pl... ] Sunil kondkar reassigned HAWKULARQE-143: ---------------------------------------- Assignee: Sunil kondkar (was: Michael Foley) > Manual - Run smoke set of manual tests - Results in Polarion > ------------------------------------------------------------ > > Key: HAWKULARQE-143 > URL: https://issues.jboss.org/browse/HAWKULARQE-143 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Sunil kondkar > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8990) Add unit test for CLI Capability completion

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFLY-8990?page=com.atlassian.jira.plugin.... ] Jean-Francois Denise updated WFLY-8990: --------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10326 (was: https://github.com/wildfly/wildfly/pull/10282) > Add unit test for CLI Capability completion > ------------------------------------------- > > Key: WFLY-8990 > URL: https://issues.jboss.org/browse/WFLY-8990 > Project: WildFly > Issue Type: Task > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > That is a follow up for WFCORE-2993. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 July 2017