December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4266) Fix HTML5 quickstart minify profile when importing to JBDS

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4266?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4266: ----------------------------- Fix Version/s: 9.0.0.Final > Fix HTML5 quickstart minify profile when importing to JBDS > ---------------------------------------------------------- > > Key: WFLY-4266 > URL: https://issues.jboss.org/browse/WFLY-4266 > Project: WildFly > Issue Type: Bug > Reporter: Rafael Benevides > Assignee: Rafael Benevides > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2371) SizeRotatingHandlerTestCase.rotationTest fails with "the file is bigger than allowed size"

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2371?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2371: ----------------------------- Fix Version/s: 9.0.0.Final > SizeRotatingHandlerTestCase.rotationTest fails with "the file is bigger than allowed size" > ------------------------------------------------------------------------------------------ > > Key: WFLY-2371 > URL: https://issues.jboss.org/browse/WFLY-2371 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Beta1 > Reporter: Petr Kremensky > Assignee: Petr Kremensky > Fix For: 9.0.0.Final > > > The test org.jboss.as.test.integration.logging.operations.SizeRotatingHandlerTestCase.rotationTest consistently fails with: > java.lang.AssertionError: This file is bigger than allowed rotate-size: size-rotating-reload-rotationTest.log.1 > Link to job: > https://jenkins.mw.lab.eng.bos.redhat.com/job/eap-6x-manu-acceptance-as-t... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3688) datasources subsystem: datasource and xa-datasource properties do not support the use of multiple values for one property

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3688?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3688: ----------------------------- Fix Version/s: 9.0.0.Final > datasources subsystem: datasource and xa-datasource properties do not support the use of multiple values for one property > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-3688 > URL: https://issues.jboss.org/browse/WFLY-3688 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.1.0.Final > Reporter: Tom Fonteyne > Assignee: Jeff Zhang > Fix For: 9.0.0.Final > > > The oracle JDBC driver had a method: > setConnectionProperties(java.util.Properties value) > which is needed to set several connection properties for datasources. > Most (all?) of these connection properties do not have individual setters. > WildFly does not support setting a "Properties" value for "datasource-property" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3721) CommandDispatcher hides exceptions

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3721?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3721: ----------------------------- Fix Version/s: 9.0.0.Final > CommandDispatcher hides exceptions > ---------------------------------- > > Key: WFLY-3721 > URL: https://issues.jboss.org/browse/WFLY-3721 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 8.1.0.Final > Reporter: Rich DiCroce > Assignee: Paul Ferraro > Fix For: 9.0.0.Final > > > The implementations of CommandDispatcher#submitOnCluster and #executeOnCluster completely hide any exceptions that occur while trying to send the command. This makes it very difficult to debug things like serialization exceptions. (Note: In the 8.x branch, the implementation is in ServiceCommandDispatcher. In master, it has moved to ChannelCommandDispatcher, but the code is essentially the same and the issue still exists.) > Instead of hiding the exception, the implementation should expose the exception to the developer in some way. A couple possibilities: > - Don't catch the exception. > - Catch the exception and return a Map with one entry, where the key is the local node and the value is a Future or CommandResponse that contains the exception. > - Catch the exception and return an empty map, but also log the exception. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3606) Porting to IronJacamar 1.2.Beta3

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3606?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3606: ----------------------------- Fix Version/s: 9.0.0.Final > Porting to IronJacamar 1.2.Beta3 > -------------------------------- > > Key: WFLY-3606 > URL: https://issues.jboss.org/browse/WFLY-3606 > Project: WildFly > Issue Type: Task > Components: JCA > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1781) XTS subsystem doesn't list the DUP phase order in Phase.java

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1781?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1781: ----------------------------- Fix Version/s: 9.0.0.Final > XTS subsystem doesn't list the DUP phase order in Phase.java > ------------------------------------------------------------ > > Key: WFLY-1781 > URL: https://issues.jboss.org/browse/WFLY-1781 > Project: WildFly > Issue Type: Bug > Components: XTS > Affects Versions: 8.0.0.Alpha3 > Reporter: jaikiran pai > Assignee: Paul Robinson > Fix For: 9.0.0.Final > > > https://github.com/wildfly/wildfly/blob/master/xts/src/main/java/org/jbos... does: > {code} > processorTarget.addDeploymentProcessor(XTSExtension.SUBSYSTEM_NAME, Phase.POST_MODULE, Phase.POST_MODULE_WELD_PORTABLE_EXTENSIONS + 10, new CDIExtensionProcessor()); > {code} > The phase number should all be centrally maintained in Phase.java so that those can be tracked. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3813) Upgrade Narayana to 5.0.3.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3813?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3813: ----------------------------- Fix Version/s: 9.0.0.Final > Upgrade Narayana to 5.0.3.Final > ------------------------------- > > Key: WFLY-3813 > URL: https://issues.jboss.org/browse/WFLY-3813 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 9.0.0.Final > > > This is useful for JBCTS-1387 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4301) Quickstart ejb-multi-server does not work

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4301?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4301: ----------------------------- Fix Version/s: 9.0.0.Final > Quickstart ejb-multi-server does not work > ----------------------------------------- > > Key: WFLY-4301 > URL: https://issues.jboss.org/browse/WFLY-4301 > Project: WildFly > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Fix For: 9.0.0.Final > > > After changing the maven artifactId of the project the created application ear/war files are named different and the deployment script deploy-domain.cli will not work. > Also the ejb lookup names has change because of this and need to be adapted. > related commit 10f95488c0a6f765c25d70a7dcbd566e59230fd2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4119) Support Slow Consumer Policy

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4119?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4119: ----------------------------- Fix Version/s: 9.0.0.Final > Support Slow Consumer Policy > ---------------------------- > > Key: WFLY-4119 > URL: https://issues.jboss.org/browse/WFLY-4119 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 9.0.0.Final > > > Support HornetQ Slow consumer policy to KILL or NOTIFY if consumers starts to be to slow consuming messages. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1893) Restarting server with a disabled DS enables the DS

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1893?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1893: ----------------------------- Fix Version/s: 9.0.0.Final > Restarting server with a disabled DS enables the DS > --------------------------------------------------- > > Key: WFLY-1893 > URL: https://issues.jboss.org/browse/WFLY-1893 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Kabir Khan > Assignee: Stefano Maestri > Fix For: 9.0.0.Final > > > See https://issues.jboss.org/browse/WFLY-1874 > If you add a datasource with > subsystem=datasources/data-source=Test:add(jndi-name=java:/Test,jta=false,use-ccm=false,connection-url=url,driver-class=org.h2.Driver,driver-name=h2,user-name=user,password=pass,validate-on-match=false,background-validation=false,share-prepared-statements=false) > it shows up as not enabled/undefined: > {code} > [standalone@localhost:9990 /] /subsystem=datasources/data-source=Test:read-resource{ "outcome" => "success", > "result" => { > ... > "enabled" => false, > {code} > {code} > [standalone@localhost:9990 /] /subsystem=datasources/data-source=Test:read-resource(include-defaults=false) > { > "outcome" => "success", > "result" => { > ... "enabled" => undefined, > {code} > This is persisted as > {code} > <datasource jta="false" jndi-name="java:/Test" pool-name="Test" enabled="false" use-ccm="false"> > <connection-url>url</connection-url> > <driver-class>org.h2.Driver</driver-class> > <driver>h2</driver> > <security> > <user-name>user</user-name> > <password>pass</password> > </security> > <validation> > <validate-on-match>false</validate-on-match> > <background-validation>false</background-validation> > </validation> > <statement> > <share-prepared-statements>false</share-prepared-statements> > </statement> > </datasource> > {code} > Now if you stop and start the server again you end up with enabled=true. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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