October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11114) Create test for both WFLY-10531 and WFLY-9501 - closing JMS contexts

by Jiri Ondrusek (Jira)

[ https://issues.jboss.org/browse/WFLY-11114?page=com.atlassian.jira.plugin... ] Jiri Ondrusek updated WFLY-11114: --------------------------------- Affects Testing: (was: Regression) > Create test for both WFLY-10531 and WFLY-9501 - closing JMS contexts > -------------------------------------------------------------------- > > Key: WFLY-11114 > URL: https://issues.jboss.org/browse/WFLY-11114 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Environment: openjdk 8 / openjdk 9, Linux > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > Priority: Major > > There are two issues https://issues.jboss.org/browse/WFLY-9501 and https://issues.jboss.org/browse/WFLY-10531. > Both covers problem with automatic closing of injected JMS contexts. > It would be nice to have a test covering both issues. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11114) Create test for both WFLY-10531 and WFLY-9501 - closing JMS contexts

by Jiri Ondrusek (Jira)

[ https://issues.jboss.org/browse/WFLY-11114?page=com.atlassian.jira.plugin... ] Jiri Ondrusek updated WFLY-11114: --------------------------------- Description: There are two issues https://issues.jboss.org/browse/WFLY-9501 and https://issues.jboss.org/browse/WFLY-10531. Both covers problem with automatic closing of injected JMS contexts. It would be nice to have a test covering both issues. was: After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on IJ000453: Unable to get managed connection for java:/JmsXA and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log: WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69) Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time. It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version. > Create test for both WFLY-10531 and WFLY-9501 - closing JMS contexts > -------------------------------------------------------------------- > > Key: WFLY-11114 > URL: https://issues.jboss.org/browse/WFLY-11114 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Environment: openjdk 8 / openjdk 9, Linux > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > Priority: Major > > There are two issues https://issues.jboss.org/browse/WFLY-9501 and https://issues.jboss.org/browse/WFLY-10531. > Both covers problem with automatic closing of injected JMS contexts. > It would be nice to have a test covering both issues. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11114) Create test for both WFLY-10531 and WFLY-9501 - closing JMS contexts

by Jiri Ondrusek (Jira)

[ https://issues.jboss.org/browse/WFLY-11114?page=com.atlassian.jira.plugin... ] Jiri Ondrusek reassigned WFLY-11114: ------------------------------------ Assignee: Jiri Ondrusek (was: Jeff Mesnil) > Create test for both WFLY-10531 and WFLY-9501 - closing JMS contexts > -------------------------------------------------------------------- > > Key: WFLY-11114 > URL: https://issues.jboss.org/browse/WFLY-11114 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Environment: openjdk 8 / openjdk 9, Linux > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > Priority: Major > > After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on > IJ000453: Unable to get managed connection for java:/JmsXA > and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log: > WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69) > Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time. > It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11114) Create test for both WFLY-10531 and WFLY-9501 - closing JMS contexts

by Jiri Ondrusek (Jira)

Jiri Ondrusek created WFLY-11114: ------------------------------------ Summary: Create test for both WFLY-10531 and WFLY-9501 - closing JMS contexts Key: WFLY-11114 URL: https://issues.jboss.org/browse/WFLY-11114 Project: WildFly Issue Type: Bug Affects Versions: 13.0.0.Final Environment: openjdk 8 / openjdk 9, Linux Reporter: Jiri Ondrusek Assignee: Jeff Mesnil After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on IJ000453: Unable to get managed connection for java:/JmsXA and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log: WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69) Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time. It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections

by Jiri Ondrusek (Jira)

[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ] Jiri Ondrusek commented on WFLY-10531: -------------------------------------- [~jwgmeligmeyling] I've found proper reason of this issue. Fix is prepared in https://github.com/wildfly/wildfly/pull/11715. Now I'll prepare test for this and for original issue -> I'll clone this issue to new one for test creation. > Wildfly leaks ActiveMQ connections > ---------------------------------- > > Key: WFLY-10531 > URL: https://issues.jboss.org/browse/WFLY-10531 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Environment: openjdk 8 / openjdk 9, Linux > Reporter: Marcel Šebek > Assignee: Jeff Mesnil > Priority: Major > Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip > > > After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on > IJ000453: Unable to get managed connection for java:/JmsXA > and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log: > WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69) > Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time. > It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections

by Jiri Ondrusek (Jira)

[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ] Jiri Ondrusek updated WFLY-10531: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/11715 > Wildfly leaks ActiveMQ connections > ---------------------------------- > > Key: WFLY-10531 > URL: https://issues.jboss.org/browse/WFLY-10531 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Environment: openjdk 8 / openjdk 9, Linux > Reporter: Marcel Šebek > Assignee: Jeff Mesnil > Priority: Major > Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip > > > After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on > IJ000453: Unable to get managed connection for java:/JmsXA > and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log: > WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69) > Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time. > It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2887) [DMN Designer] Palette icon enhancements

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-2887?page=com.atlassian.jira.plugi... ] Liz Clayton closed DROOLS-2887. ------------------------------- Resolution: Done Closing per Michael > [DMN Designer] Palette icon enhancements > ---------------------------------------- > > Key: DROOLS-2887 > URL: https://issues.jboss.org/browse/DROOLS-2887 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Liz Clayton > Assignee: Brian Dellascio > Priority: Minor > Labels: UX, UXTeam, VisualDesign, drools-tools > Attachments: palette.png > > > Palette icons to be updated as documented at: https://issues.jboss.org/browse/DROOLS-2522 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2887) [DMN Designer] Palette icon enhancements

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-2887?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2887: ------------------------------------- [~manstis] Thanks for pointing that out, I'll close it. > [DMN Designer] Palette icon enhancements > ---------------------------------------- > > Key: DROOLS-2887 > URL: https://issues.jboss.org/browse/DROOLS-2887 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Liz Clayton > Assignee: Brian Dellascio > Priority: Minor > Labels: UX, UXTeam, VisualDesign, drools-tools > Attachments: palette.png > > > Palette icons to be updated as documented at: https://issues.jboss.org/browse/DROOLS-2522 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11113) Update to JAXB 2.3.1

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFLY-11113?page=com.atlassian.jira.plugin... ] Jan Blizňák updated WFLY-11113: ------------------------------- Labels: Java11 (was: ) > Update to JAXB 2.3.1 > -------------------- > > Key: WFLY-11113 > URL: https://issues.jboss.org/browse/WFLY-11113 > Project: WildFly > Issue Type: Component Upgrade > Components: REST, Web Services > Affects Versions: 14.0.0.Final > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Major > Labels: Java11 > > The new release of JAXB should fix some issues with JDK11 (such as warnings WFLY-11044) > Full diff https://github.com/javaee/jaxb-v2/compare/2.3.0...2.3.1 > Note: this release no longer contains jaxb-core artifact which was merged into jaxb-runtime https://github.com/javaee/jaxb-v2/commit/32fda2fbee71c2df04c52fc8eb368769... > Note2: there is a change in dependencies, some of the org.glassfish.jaxb:* artifacts used to depend on relaxngDatatype:relaxngDatatype (which is excluded in WF \[1\],\[2\],\[3\]), now replaced with com.sun.xml.bind.external:relaxng-datatype. WF is using com.github.relaxng:relaxngDatatype instead, not sure, if it is compatible out of the box. > \[1\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L1293-L1298 > \[2\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L3848-L3853 > \[3\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L6728 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11113) Update to JAXB 2.3.1

by Jan Blizňák (Jira)

Jan Blizňák created WFLY-11113: ---------------------------------- Summary: Update to JAXB 2.3.1 Key: WFLY-11113 URL: https://issues.jboss.org/browse/WFLY-11113 Project: WildFly Issue Type: Component Upgrade Components: REST, Web Services Affects Versions: 14.0.0.Final Reporter: Jan Blizňák Assignee: Alessio Soldano The new release of JAXB should fix some issues with JDK11 (such as warnings WFLY-11044) Full diff https://github.com/javaee/jaxb-v2/compare/2.3.0...2.3.1 Note: this release no longer contains jaxb-core artifact which was merged into jaxb-runtime https://github.com/javaee/jaxb-v2/commit/32fda2fbee71c2df04c52fc8eb368769... Note2: there is a change in dependencies, some of the org.glassfish.jaxb:* artifacts used to depend on relaxngDatatype:relaxngDatatype (which is excluded in WF \[1\],\[2\],\[3\]), now replaced with com.sun.xml.bind.external:relaxng-datatype. WF is using com.github.relaxng:relaxngDatatype instead, not sure, if it is compatible out of the box. \[1\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L1293-L1298 \[2\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L3848-L3853 \[3\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L6728 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 October 2018