December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6551) Incorrect log message in class ClientSessionFactoryImpl

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6551?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-6551: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > Incorrect log message in class ClientSessionFactoryImpl > ------------------------------------------------------- > > Key: WFLY-6551 > URL: https://issues.jboss.org/browse/WFLY-6551 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Chen Maoqian > Assignee: Chen Maoqian > Priority: Minor > Fix For: 11.0.0.Final > > > There is incorrect logging message present in method {{establishNewConnection()}} in class {{org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl}} . > > {noformat} > protected RemotingConnection establishNewConnection() { > .... > RemotingConnection newConnection = clientProtocolManager.connect(...); > newConnection.addFailureListener(new DelegatingFailureListener(newConnection.getID())); > schedulePing(); > if (ActiveMQClientLogger.LOGGER.isTraceEnabled()) { > ActiveMQClientLogger.LOGGER.trace("returning " + connection); > } > return newConnection; > } > {noformat} > Log message says, that it is returning connection (old one, present as an attribute of class), but connection stored in {{newConnection}} variable is returned (and then it is set as this.connection). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4876) Upgrade AESH from 0.33.15 to 0.33.16

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4876?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4876: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > Upgrade AESH from 0.33.15 to 0.33.16 > ------------------------------------ > > Key: WFLY-4876 > URL: https://issues.jboss.org/browse/WFLY-4876 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Ryan Emerson > Assignee: Jason Greene > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3904) Unable to enable statistics via configuration for resource adapters

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3904?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3904: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > Unable to enable statistics via configuration for resource adapters > ------------------------------------------------------------------- > > Key: WFLY-3904 > URL: https://issues.jboss.org/browse/WFLY-3904 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.1.0.Final > Reporter: Daniel Atallah > Assignee: Stefano Maestri > Fix For: 11.0.0.Final > > > The statistics for resource adapters are hard-coded to be disabled at startup: > https://github.com/wildfly/wildfly/blob/47830b44d1bd48c4fcdc2489cecaa3971... > It's not possible to enable the statistics in a persistent way - it needs to be done each time the servers starts e.g. via jmx. > Ideally there'd be a "statistics-enabled" attribute on the "<connection-definition>" element in the configuration file in the same way that there is on "<datasource>". -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8351) Prepare wildfly for multiply dynamic capability parts in core

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8351?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-8351: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > Prepare wildfly for multiply dynamic capability parts in core > ------------------------------------------------------------- > > Key: WFLY-8351 > URL: https://issues.jboss.org/browse/WFLY-8351 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 11.0.0.Final > > > Due to some API changes coming with WFCORE-2202we need to modify code a bit in full before we can merge core PR -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7716) Add tests for XA DataSource statistics

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-7716?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-7716: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > Add tests for XA DataSource statistics > -------------------------------------- > > Key: WFLY-7716 > URL: https://issues.jboss.org/browse/WFLY-7716 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Daniel Simko > Assignee: Daniel Simko > Priority: Minor > Fix For: 11.0.0.Final > > > Add new testcase for testing xa-data-source's pool statistics (XACommitCount, XARollbackCount, XAStartCount). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6154) [Migration][WebToUndertow] RemoteAddrValve and RemoteHostValve are incorrectly migrated

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6154?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-6154: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > [Migration][WebToUndertow] RemoteAddrValve and RemoteHostValve are incorrectly migrated > --------------------------------------------------------------------------------------- > > Key: WFLY-6154 > URL: https://issues.jboss.org/browse/WFLY-6154 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Blocker > Fix For: 11.0.0.Final > > > When migrating {{RemoteHostValve}} or {{RemoteAddrValve}} which contains multiple allows or denies or contains both as in \[1\], it is migrated incorrectly. In the resulting expression the acl attribute should be in format {{acl=\{'xxx allow', 'yyy deny'\}}}, but instead it results in {{acl='xxx allow, yyy deny'}} which is incorrect and results in exception when doing any request to the server. > Marking as critical as that it was migrated incorrectly the customer will not find out during migration but when actually doing request to the server. > Might be interesting to [~ehugonnet] > [1] > {code:xml} > <valve name="request-filter" module="org.jboss.as.web" class-name="org.apache.catalina.valves.RemoteAddrValve"> > <param param-name="deny" param-value="10.0.0.1"/> > <param param-name="allow" param-value="127.*"/> > </valve> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6707) WildFly Test Suite: Integration - XTS is a little bit confusing and needs small cleanup

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6707?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-6707: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > WildFly Test Suite: Integration - XTS is a little bit confusing and needs small cleanup > --------------------------------------------------------------------------------------- > > Key: WFLY-6707 > URL: https://issues.jboss.org/browse/WFLY-6707 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite, XTS > Affects Versions: 10.0.0.Final > Reporter: Daniel Simko > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 11.0.0.Final > > > The line https://github.com/wildfly/wildfly/blob/master/testsuite/integration/xts/... is never reached because exception is thrown from the line before. > The Javadoc https://github.com/wildfly/wildfly/blob/master/testsuite/integration/xts/... is copied from https://github.com/wildfly/quickstart/blob/10.x/wsba-coordinator-completi... and doesn't make sense here. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1589) requiredSecret attribute on the AJP connector

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1589?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1589: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > requiredSecret attribute on the AJP connector > --------------------------------------------- > > Key: WFLY-1589 > URL: https://issues.jboss.org/browse/WFLY-1589 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > Priority: Minor > Fix For: 11.0.0.Final > > Attachments: requiredsecret.diff, requiredsecret.diff > > > In JBoss 5 I could set the requiredSecret attribute of the AJP connector. This is no longer possible in JBoss AS 7 and WildFly > This request is to get it implemented similarly to WFLY-254 for tomcatAuthentication -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5232) Naming store is null before CDI lifecycle BeforeShutdown event fires

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5232?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-5232: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > Naming store is null before CDI lifecycle BeforeShutdown event fires > -------------------------------------------------------------------- > > Key: WFLY-5232 > URL: https://issues.jboss.org/browse/WFLY-5232 > Project: WildFly > Issue Type: Bug > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 11.0.0.Final > > Attachments: reproducer.tar.gz > > > A CDI extension has a BeforeShutdown event handler that looks up the UserTransaction and performs a clean-up operation. If the application is undeployed, all works as expected, but if Wildfly is shut down gracefully the lookup fails. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7205) Enhance coverage of transaction timeout test cases

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-7205?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-7205: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > Enhance coverage of transaction timeout test cases > -------------------------------------------------- > > Key: WFLY-7205 > URL: https://issues.jboss.org/browse/WFLY-7205 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 10.1.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 11.0.0.Final > > > There is not much tests which checks behaviour of CMT/BMT EJBs when transaction timeout occurs. > There should be more such tests. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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