June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8977) Mdb Delivery-group is not working

by Flavia Rainone (JIRA)

[ https://issues.jboss.org/browse/WFLY-8977?page=com.atlassian.jira.plugin.... ] Flavia Rainone closed WFLY-8977. -------------------------------- Resolution: Cannot Reproduce Bug It turns out that the cause of the failure was in the test I was performing and not a real bug (for more details: the quickstart for mdb-delivery group contained a typo, in the name of the topic bean, copied from helloworld-mdb quickstart. That was causing the bean to not be associated with the delivery group and that's why it was not working!) > Mdb Delivery-group is not working > --------------------------------- > > Key: WFLY-8977 > URL: https://issues.jboss.org/browse/WFLY-8977 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Flavia Rainone > Assignee: Flavia Rainone > > Delivery-group feature is broken. > Disabling an active delivery-group does not affect delivery of messages in the server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3028) Elytron subsystem fails to boot if SecurityProvider cannot be loaded.

by Martin Choma (JIRA)

Martin Choma created WFCORE-3028: ------------------------------------ Summary: Elytron subsystem fails to boot if SecurityProvider cannot be loaded. Key: WFCORE-3028 URL: https://issues.jboss.org/browse/WFCORE-3028 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Martin Choma Assignee: Darran Lofthouse Trying to run secmgr testsuite under JDK9 results in {noformat} Caused by: java.util.ServiceConfigurationError: java.security.Provider: Provider com.sun.deploy.security.MozillaJSSProvider could not be instantiated at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:581) at java.base/java.util.ServiceLoader.access$100(ServiceLoader.java:390) at java.base/java.util.ServiceLoader$ProviderImpl.newInstance(ServiceLoader.java:799) at java.base/java.util.ServiceLoader$ProviderImpl.get(ServiceLoader.java:721) at java.base/java.util.ServiceLoader$3.next(ServiceLoader.java:1389) at java.base/java.lang.Iterable.forEach(Iterable.java:74) at org.wildfly.extension.elytron//org.wildfly.extension.elytron.ProviderDefinitions$1$1.get(ProviderDefinitions.java:201) at org.wildfly.extension.elytron//org.wildfly.extension.elytron.ProviderDefinitions$1$1.get(ProviderDefinitions.java:158) at org.wildfly.extension.elytron//org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53) at org.jboss.msc//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) at org.jboss.msc//org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) {noformat} and server doesn't start. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1642) Create/augment the ability to use PMML files as resources

by Lance Leverich (JIRA)

Lance Leverich created DROOLS-1642: -------------------------------------- Summary: Create/augment the ability to use PMML files as resources Key: DROOLS-1642 URL: https://issues.jboss.org/browse/DROOLS-1642 Project: Drools Issue Type: Feature Request Components: core engine Reporter: Lance Leverich Assignee: Lance Leverich This requested feature calls for the ability to read PMML files, as a type of Drools resource, and then generate the appropriate business rules. Initially, the PMML files will represent score cards and/or tree models. More details will be added to this description, as more complete requirements become available. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7214) Warning of IllegalStateException on test-connection-pool for DataSources added after previous failure addition

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-7214?page=com.atlassian.jira.plugin.... ] Lin Gao edited comment on WFLY-7214 at 6/28/17 9:34 PM: -------------------------------------------------------- This has been fixed with upgrading of IronJacamar to 1.4.0 was (Author: gaol): This has been fixed. > Warning of IllegalStateException on test-connection-pool for DataSources added after previous failure addition > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7214 > URL: https://issues.jboss.org/browse/WFLY-7214 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Lin Gao > Assignee: Lin Gao > > When a data-source was failed to be added because of missing connection-properties: > {code:} > /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2, connection-url="jdbc:h2:test") > {code} > , it can be added by correcting the information, like: > {code:} > [standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test") > {"outcome" => "success"} > {code} > But the {{test-connection-in-pool()}} operation failed with {{IllegalStateException}} of the new created data-source: > {code:} > [standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool() > { > "outcome" => "failed", > "failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid", > "rolled-back" => true > } > {code} > {panel:title=NOTE FOR THE VERIFY} > Changing the Step 1 to: > {code:} > /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2) > {code} > for the verifying, because of with fixing of https://issues.jboss.org/browse/JBJCA-1331 (also fixed in ironjacamar-1.3.5.Final), the original step 1 will not cause problems any more. > {panel} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7214) Warning of IllegalStateException on test-connection-pool for DataSources added after previous failure addition

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-7214?page=com.atlassian.jira.plugin.... ] Lin Gao resolved WFLY-7214. --------------------------- Resolution: Done This has been fixed. > Warning of IllegalStateException on test-connection-pool for DataSources added after previous failure addition > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7214 > URL: https://issues.jboss.org/browse/WFLY-7214 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Lin Gao > Assignee: Lin Gao > > When a data-source was failed to be added because of missing connection-properties: > {code:} > /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2, connection-url="jdbc:h2:test") > {code} > , it can be added by correcting the information, like: > {code:} > [standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test") > {"outcome" => "success"} > {code} > But the {{test-connection-in-pool()}} operation failed with {{IllegalStateException}} of the new created data-source: > {code:} > [standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool() > { > "outcome" => "failed", > "failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid", > "rolled-back" => true > } > {code} > {panel:title=NOTE FOR THE VERIFY} > Changing the Step 1 to: > {code:} > /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2) > {code} > for the verifying, because of with fixing of https://issues.jboss.org/browse/JBJCA-1331 (also fixed in ironjacamar-1.3.5.Final), the original step 1 will not cause problems any more. > {panel} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3027) (7.1.x) Upgrade undertow from 1.4.17.Final to 1.4.18.Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3027?page=com.atlassian.jira.plugi... ] Stuart Douglas moved JBEAP-11856 to WFCORE-3027: ------------------------------------------------ Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3027 (was: JBEAP-11856) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: (was: Web (Undertow)) > (7.1.x) Upgrade undertow from 1.4.17.Final to 1.4.18.Final > ---------------------------------------------------------- > > Key: WFCORE-3027 > URL: https://issues.jboss.org/browse/WFCORE-3027 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8745) Upgrade mod_cluster to 1.3.7.Final

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8745?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-8745: --------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 10.2.0.Final) > Upgrade mod_cluster to 1.3.7.Final > ---------------------------------- > > Key: WFLY-8745 > URL: https://issues.jboss.org/browse/WFLY-8745 > Project: WildFly > Issue Type: Component Upgrade > Components: mod_cluster > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 11.0.0.Beta1 > > > Changelog https://issues.jboss.org/issues/?jql=project%20%3D%20MODCLUSTER%20AND%20f... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8745) Upgrade mod_cluster to 1.3.7.Final

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8745?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-8745: --------------------------------- Fix Version/s: 10.2.0.Final > Upgrade mod_cluster to 1.3.7.Final > ---------------------------------- > > Key: WFLY-8745 > URL: https://issues.jboss.org/browse/WFLY-8745 > Project: WildFly > Issue Type: Component Upgrade > Components: mod_cluster > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 11.0.0.Beta1 > > > Changelog https://issues.jboss.org/issues/?jql=project%20%3D%20MODCLUSTER%20AND%20f... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3026) Upgrade JBoss Invocation to 1.5.0.CR1

by David Lloyd (JIRA)

David Lloyd created WFCORE-3026: ----------------------------------- Summary: Upgrade JBoss Invocation to 1.5.0.CR1 Key: WFCORE-3026 URL: https://issues.jboss.org/browse/WFCORE-3026 Project: WildFly Core Issue Type: Component Upgrade Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.0.Beta28 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3025) Upgrade JBoss Marshalling to 2.0.0.CR1

by David Lloyd (JIRA)

David Lloyd created WFCORE-3025: ----------------------------------- Summary: Upgrade JBoss Marshalling to 2.0.0.CR1 Key: WFCORE-3025 URL: https://issues.jboss.org/browse/WFCORE-3025 Project: WildFly Core Issue Type: Component Upgrade Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.0.Beta28 -- 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 June 2017