October 2018 - jboss-jira - Jboss List Archives

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

by Jiri Ondrusek (Jira)

[ https://issues.jboss.org/browse/WFLY-11102?page=com.atlassian.jira.plugin... ] Jiri Ondrusek reassigned WFLY-11102: ------------------------------------ Assignee: Jiri Ondrusek (was: Jeff Mesnil) > Wildfly leaks ActiveMQ connections > ---------------------------------- > > Key: WFLY-11102 > URL: https://issues.jboss.org/browse/WFLY-11102 > 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)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11099) ActiveMQ 2.6.3.jbossorg-001 requires QPid Proton-J 0.27.3 (ClassNotFoundExceptions in messaging subsystem)

by Jan-Willem Gmelig Meyling (Jira)

[ https://issues.jboss.org/browse/WFLY-11099?page=com.atlassian.jira.plugin... ] Jan-Willem Gmelig Meyling commented on WFLY-11099: -------------------------------------------------- OK, thats the version I've used in the PR as well :) > ActiveMQ 2.6.3.jbossorg-001 requires QPid Proton-J 0.27.3 (ClassNotFoundExceptions in messaging subsystem) > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-11099 > URL: https://issues.jboss.org/browse/WFLY-11099 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.1.Final, 14.0.0.Final > Reporter: Jan-Willem Gmelig Meyling > Assignee: Jeff Mesnil > Priority: Major > > With the update from Artemis 1.5.x to 2.6.x in WFLY-9407, Proton-J wasn't updated from 0.16.x to 0.27.3, which leads to class not found exceptions for "Sasl... " classes when remote acceptors are created and connected to (I tested with AMQP protocol). When updating Proton-J to the newest version (0.29.0) my issues are gone. > I'm not sure which other modules are using the proton-j module, but my suggestion is that we bump the version of Proton-j to the required 0.27.3 minimally. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11099) ActiveMQ 2.6.3.jbossorg-001 requires QPid Proton-J 0.27.3 (ClassNotFoundExceptions in messaging subsystem)

by Martyn Taylor (Jira)

[ https://issues.jboss.org/browse/WFLY-11099?page=com.atlassian.jira.plugin... ] Martyn Taylor commented on WFLY-11099: -------------------------------------- The release of Artemis that landed in Wildfly uses 0.27.3, Given that Artemis is the only consumer of this library it makes sense to me to keep these versions the same, bumping could introduce instability with that particular version of Artemis. > ActiveMQ 2.6.3.jbossorg-001 requires QPid Proton-J 0.27.3 (ClassNotFoundExceptions in messaging subsystem) > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-11099 > URL: https://issues.jboss.org/browse/WFLY-11099 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.1.Final, 14.0.0.Final > Reporter: Jan-Willem Gmelig Meyling > Assignee: Jeff Mesnil > Priority: Major > > With the update from Artemis 1.5.x to 2.6.x in WFLY-9407, Proton-J wasn't updated from 0.16.x to 0.27.3, which leads to class not found exceptions for "Sasl... " classes when remote acceptors are created and connected to (I tested with AMQP protocol). When updating Proton-J to the newest version (0.29.0) my issues are gone. > I'm not sure which other modules are using the proton-j module, but my suggestion is that we bump the version of Proton-j to the required 0.27.3 minimally. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3061) [DMN Designer] Automatic Layout Feature

by Daniel José dos Santos (Jira)

[ https://issues.jboss.org/browse/DROOLS-3061?page=com.atlassian.jira.plugi... ] Daniel José dos Santos updated DROOLS-3061: ------------------------------------------- Description: DMN Designer should *autolayout* new imported DMN models. The *autolayout* should position DRG diagram nodes into horizontal layers to minimize crossing of connectors with respect of *Top-Down* importance. It means if nodes *Layer B* are inputs for nodes in *Layer A* then the *Layer B* will be below *Layer A*. The *autolayout* should also try to minimize scrolling needed to see whole DRG diagram. User should also have possibility to invoke *autolayout* feature any time during designing the diagram. In this case the action should be undoable with the *Undo* toolbar button. The approach used to achieve this is the Sugiyama Method, which is done in 4 steps. Each step have its own algorithm: *Step 1 - Cycle breaking:* We break cycles in diagram by reversing some edges (they are de-reversed in the end). This step are required because we need ending points in step 2 while sweeping through graph; *Step 2 - Layering:* We sweep through graph (diagram) and put each node (vertex) in a layer, based on it's distance from others node. This approach usually puts the start nodes at the top and the deepest nodes at the end. In the current implementation we're using Longest Path algorithm. A better approach can be developed in future using Network Simplex; *Step 3 - Node Ordering:* We order each node (vertex) inside its layers in order to reduce crossings; *Step 4 - Node Positioning:* We calculate the position of each node. This step can be divided in two steps: one for horizontal position and other for vertical was: DMN Designer should *autolayout* new imported DMN models. The *autolayout* should position DRG diagram nodes into horizontal layers to minimize crossing of connectors with respect of *Top-Down* importance. It means if nodes *Layer B* are inputs for nodes in *Layer A* then the *Layer B* will be below *Layer A*. The *autolayout* should also try to minimize scrolling needed to see whole DRG diagram. User should also have possibility to invoke *autolayout* feature any time during designing the diagram. In this case the action should be undoable with the *Undo* toolbar button. > [DMN Designer] Automatic Layout Feature > --------------------------------------- > > Key: DROOLS-3061 > URL: https://issues.jboss.org/browse/DROOLS-3061 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > DMN Designer should *autolayout* new imported DMN models. The *autolayout* should position DRG diagram nodes into horizontal layers to minimize crossing of connectors with respect of *Top-Down* importance. It means if nodes *Layer B* are inputs for nodes in *Layer A* then the *Layer B* will be below *Layer A*. The *autolayout* should also try to minimize scrolling needed to see whole DRG diagram. > User should also have possibility to invoke *autolayout* feature any time during designing the diagram. In this case the action should be undoable with the *Undo* toolbar button. > The approach used to achieve this is the Sugiyama Method, which is done in 4 steps. Each step have its own algorithm: > *Step 1 - Cycle breaking:* We break cycles in diagram by reversing some edges (they are de-reversed in the end). This step are required because we need ending points in step 2 while sweeping through graph; > *Step 2 - Layering:* We sweep through graph (diagram) and put each node (vertex) in a layer, based on it's distance from others node. This approach usually puts the start nodes at the top and the deepest nodes at the end. In the current implementation we're using Longest Path algorithm. A better approach can be developed in future using Network Simplex; > *Step 3 - Node Ordering:* We order each node (vertex) inside its layers in order to reduce crossings; > *Step 4 - Node Positioning:* We calculate the position of each node. This step can be divided in two steps: one for horizontal position and other for vertical -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-204) Short host name format yields last part of name instead of first part

by David Lloyd (Jira)

[ https://issues.jboss.org/browse/LOGMGR-204?page=com.atlassian.jira.plugin... ] David Lloyd commented on LOGMGR-204: ------------------------------------ The 2.0 branch uses different code here. > Short host name format yields last part of name instead of first part > --------------------------------------------------------------------- > > Key: LOGMGR-204 > URL: https://issues.jboss.org/browse/LOGMGR-204 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 2.1.4.Final > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Major > Fix For: 2.1.5.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-204) Short host name format yields last part of name instead of first part

by David Lloyd (Jira)

[ https://issues.jboss.org/browse/LOGMGR-204?page=com.atlassian.jira.plugin... ] David Lloyd updated LOGMGR-204: ------------------------------- Fix Version/s: 2.1.5.Final > Short host name format yields last part of name instead of first part > --------------------------------------------------------------------- > > Key: LOGMGR-204 > URL: https://issues.jboss.org/browse/LOGMGR-204 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 2.1.4.Final > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Major > Fix For: 2.1.5.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-204) Short host name format yields last part of name instead of first part

by David Lloyd (Jira)

[ https://issues.jboss.org/browse/LOGMGR-204?page=com.atlassian.jira.plugin... ] David Lloyd updated LOGMGR-204: ------------------------------- Affects Version/s: 2.1.4.Final > Short host name format yields last part of name instead of first part > --------------------------------------------------------------------- > > Key: LOGMGR-204 > URL: https://issues.jboss.org/browse/LOGMGR-204 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 2.1.4.Final > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Major > Fix For: 2.1.5.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-204) Short host name format yields last part of name instead of first part

by David Lloyd (Jira)

David Lloyd created LOGMGR-204: ---------------------------------- Summary: Short host name format yields last part of name instead of first part Key: LOGMGR-204 URL: https://issues.jboss.org/browse/LOGMGR-204 Project: JBoss Log Manager Issue Type: Bug Reporter: David Lloyd Assignee: David Lloyd -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11099) ActiveMQ 2.6.3.jbossorg-001 requires QPid Proton-J 0.27.3 (ClassNotFoundExceptions in messaging subsystem)

by Jan-Willem Gmelig Meyling (Jira)

[ https://issues.jboss.org/browse/WFLY-11099?page=com.atlassian.jira.plugin... ] Jan-Willem Gmelig Meyling commented on WFLY-11099: -------------------------------------------------- I'd rather see 0.29 as well, as I have tested that one already. > ActiveMQ 2.6.3.jbossorg-001 requires QPid Proton-J 0.27.3 (ClassNotFoundExceptions in messaging subsystem) > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-11099 > URL: https://issues.jboss.org/browse/WFLY-11099 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.1.Final, 14.0.0.Final > Reporter: Jan-Willem Gmelig Meyling > Assignee: Jeff Mesnil > Priority: Major > > With the update from Artemis 1.5.x to 2.6.x in WFLY-9407, Proton-J wasn't updated from 0.16.x to 0.27.3, which leads to class not found exceptions for "Sasl... " classes when remote acceptors are created and connected to (I tested with AMQP protocol). When updating Proton-J to the newest version (0.29.0) my issues are gone. > I'm not sure which other modules are using the proton-j module, but my suggestion is that we bump the version of Proton-j to the required 0.27.3 minimally. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11099) ActiveMQ 2.6.3.jbossorg-001 requires QPid Proton-J 0.27.3 (ClassNotFoundExceptions in messaging subsystem)

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11099?page=com.atlassian.jira.plugin... ] Kabir Khan commented on WFLY-11099: ----------------------------------- [~martyn-taylor] says: {code} Looks like JIRA is down. The version in the product should be: version=0.29.0.redhat-00001 {code} However as [~psakar] pointed out, we don't actually use qpid in the product, so for upstream we can use whatever works. But as AMQ uses 0.29, is there any reason not to use that in wildfly right now? > ActiveMQ 2.6.3.jbossorg-001 requires QPid Proton-J 0.27.3 (ClassNotFoundExceptions in messaging subsystem) > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-11099 > URL: https://issues.jboss.org/browse/WFLY-11099 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.1.Final, 14.0.0.Final > Reporter: Jan-Willem Gmelig Meyling > Assignee: Jeff Mesnil > Priority: Major > > With the update from Artemis 1.5.x to 2.6.x in WFLY-9407, Proton-J wasn't updated from 0.16.x to 0.27.3, which leads to class not found exceptions for "Sasl... " classes when remote acceptors are created and connected to (I tested with AMQP protocol). When updating Proton-J to the newest version (0.29.0) my issues are gone. > I'm not sure which other modules are using the proton-j module, but my suggestion is that we bump the version of Proton-j to the required 0.27.3 minimally. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018