October 2018 - jboss-jira - Jboss List Archives

[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 edited comment on WFLY-10531 at 10/4/18 8:41 AM: --------------------------------------------------------------- [~jwgmeligmeyling] I'm still trying to figure, what exactly is causing this error. Currently, I've created better test: https://github.com/JiriOndrusek/wildfly/commit/fd84ff61e074ade65d4b9f5a21... (which doesn't exhaust server) My current thoughts about this issue are following: * I have logs from two executions with small amount (the same numbers) of calls of injected contexts with leaking connections and without leaking connections -> error doesn't depend on precise number of calls from reproducer * if I set count of executions to higher values, there is an error with almost 100% certainty * I was able to count registered contexts in transaction synchronization on multiple executions, and then number of closed ones -> I see difference which I can not explain for now I have suspicion, that that problem is caused near registering of synchronization listener. I think that it is possible, that some contexts are not registered for closing at the end of transaction. It answers the questions: - why it is happening only with more injected contexts - and the fact that I see that not all contexts, which should be registered, are not closed by synchronization listener I'll investigate this scenario, to be sure. If my suspicion is correct, then proposed fix works only as workaround. was (Author: jondruse): [~jwgmeligmeyling] I'm still trying to figure, what exactly is causing this error. Currently, I've created better test: https://github.com/JiriOndrusek/wildfly/commit/fd84ff61e074ade65d4b9f5a21... (which doesn't exhaust server) My current thoughts about this issue are following: * I have logs from two executions with small amount (the same numbers) of calls of injected contexts with leaking connections and without leaking connections -> error doesn't depend on precise number of calls from reproducer * if I set count of executions to higher values, there is an error with almost 100% certainty * I was able to count registered contexts in transaction synchronization on multiple executions, and then number of closed ones -> I see difference which I can not explain for now I have suspicion, that that problem is caused near registering of synchronization listener. I think that it is possible, that some contexts are not registered for closing at the end of transaction. It answers the questions: - why it is happening only with more injected contexts - and the fact that I see that not all contexts, which should be registered, are not closed by synchronization listener I'll investigate this scenario, to be sure. > 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 commented on WFLY-10531: -------------------------------------- [~jwgmeligmeyling] I'm still trying to figure, what exactly is causing this error. Currently, I've created better test: https://github.com/JiriOndrusek/wildfly/commit/fd84ff61e074ade65d4b9f5a21... (which doesn't exhaust server) My current thoughts about this issue are following: * I have logs from two executions with small amount (the same numbers) of calls of injected contexts with leaking connections and without leaking connections -> error doesn't depend on precise number of calls from reproducer * if I set count of executions to higher values, there is an error with almost 100% certainty * I was able to count registered contexts in transaction synchronization on multiple executions, and then number of closed ones -> I see difference which I can not explain for now I have suspicion, that that problem is caused near registering of synchronization listener. I think that it is possible, that some contexts are not registered for closing at the end of transaction. It answers the questions: - why it is happening only with more injected contexts - and the fact that I see that not all contexts, which should be registered, are not closed by synchronization listener I'll investigate this scenario, to be sure. > 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-11086) Usage of static fields from java.lang classes as EL expressions in JSPs doesn't work when requested more than once

by Ingo Weiss (Jira)

[ https://issues.jboss.org/browse/WFLY-11086?page=com.atlassian.jira.plugin... ] Ingo Weiss reassigned WFLY-11086: --------------------------------- Assignee: Ingo Weiss (was: Tomas Hofman) > Usage of static fields from java.lang classes as EL expressions in JSPs doesn't work when requested more than once > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-11086 > URL: https://issues.jboss.org/browse/WFLY-11086 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 14.0.0.Final > Reporter: Adam Krajcik > Assignee: Ingo Weiss > Priority: Major > Attachments: jsp-expression-lang.war > > > Java EE7 (which supports EL 3.0 spec) allows JSPs to use EL expressions like: > {code} > <html> > <body> > foo: --- ${Boolean.TRUE} ---<br> > bar: --- ${Integer.MAX_VALUE} ---<br> > </body> > </html> > {code} > However, the > {code} > ${Boolean.TRUE} > {code} > and > {code} > ${Integer.MAX_VALUE} > {code} > in the above example aren't evaluated correctly if request is send more than once, and instead a blank string is rendered for them. The [^jsp-expression-lang.war] used in Steps to reproduce works correctly in 7.2.0.CD13. > More details in the linked forum thread https://developer.jboss.org/thread/271825. > The existing tests([JspELTestCase|https://github.com/wildfly/wildfly/blob/master/tests... doesn't cover the situation when request is sent more than once. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11112) WildFly intermittently fails to add pooled-connection-factory but it still got registered after

by Ivan Straka (Jira)

[ https://issues.jboss.org/browse/WFLY-11112?page=com.atlassian.jira.plugin... ] Ivan Straka updated WFLY-11112: ------------------------------- Attachment: server.log standalone-full.xml > WildFly intermittently fails to add pooled-connection-factory but it still got registered after > ----------------------------------------------------------------------------------------------- > > Key: WFLY-11112 > URL: https://issues.jboss.org/browse/WFLY-11112 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final, 15.0.0.Alpha1 > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Blocker > Attachments: server.log, standalone-full.xml > > > We see following error in log of WildFly (master): > {code} > 2018-10-03 22:28:02,503 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("server" => "default"), > ("pooled-connection-factory" => "activemq-ra") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.JmsXA-bkp"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.JmsXA-bkp]"] > } > {code} > Factory is defined: > {code:java} > <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA-bkp java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/> > {code} > However factory is registered after and deployment is able to use it. Error is logged intermittently. > Log file and xml configuration file are enclosed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11112) WildFly intermittently fails to add pooled-connection-factory but it still got registered after

by Ivan Straka (Jira)

[ https://issues.jboss.org/browse/WFLY-11112?page=com.atlassian.jira.plugin... ] Ivan Straka updated WFLY-11112: ------------------------------- Attachment: (was: JMSProxyMessagingServerCrashRecoveryTestCase_prepareHaltWithAbortFails_jta_before_restore_jbossts_standalone-full.xml) > WildFly intermittently fails to add pooled-connection-factory but it still got registered after > ----------------------------------------------------------------------------------------------- > > Key: WFLY-11112 > URL: https://issues.jboss.org/browse/WFLY-11112 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final, 15.0.0.Alpha1 > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Blocker > > We see following error in log of WildFly (master): > {code} > 2018-10-03 22:28:02,503 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("server" => "default"), > ("pooled-connection-factory" => "activemq-ra") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.JmsXA-bkp"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.JmsXA-bkp]"] > } > {code} > Factory is defined: > {code:java} > <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA-bkp java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/> > {code} > However factory is registered after and deployment is able to use it. Error is logged intermittently. > Log file and xml configuration file are enclosed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11112) WildFly intermittently fails to add pooled-connection-factory but it still got registered after

by Ivan Straka (Jira)

[ https://issues.jboss.org/browse/WFLY-11112?page=com.atlassian.jira.plugin... ] Ivan Straka updated WFLY-11112: ------------------------------- Attachment: (was: JMSProxyMessagingServerCrashRecoveryTestCase_prepareHaltWithAbortFails_jta_server.log) > WildFly intermittently fails to add pooled-connection-factory but it still got registered after > ----------------------------------------------------------------------------------------------- > > Key: WFLY-11112 > URL: https://issues.jboss.org/browse/WFLY-11112 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final, 15.0.0.Alpha1 > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Blocker > > We see following error in log of WildFly (master): > {code} > 2018-10-03 22:28:02,503 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("server" => "default"), > ("pooled-connection-factory" => "activemq-ra") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.JmsXA-bkp"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.JmsXA-bkp]"] > } > {code} > Factory is defined: > {code:java} > <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA-bkp java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/> > {code} > However factory is registered after and deployment is able to use it. Error is logged intermittently. > Log file and xml configuration file are enclosed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11112) WildFly intermittently fails to add pooled-connection-factory but it still got registered after

by Ivan Straka (Jira)

[ https://issues.jboss.org/browse/WFLY-11112?page=com.atlassian.jira.plugin... ] Ivan Straka updated WFLY-11112: ------------------------------- Attachment: JMSProxyMessagingServerCrashRecoveryTestCase_prepareHaltWithAbortFails_jta_before_restore_jbossts_standalone-full.xml JMSProxyMessagingServerCrashRecoveryTestCase_prepareHaltWithAbortFails_jta_server.log > WildFly intermittently fails to add pooled-connection-factory but it still got registered after > ----------------------------------------------------------------------------------------------- > > Key: WFLY-11112 > URL: https://issues.jboss.org/browse/WFLY-11112 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final, 15.0.0.Alpha1 > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Blocker > Attachments: JMSProxyMessagingServerCrashRecoveryTestCase_prepareHaltWithAbortFails_jta_before_restore_jbossts_standalone-full.xml, JMSProxyMessagingServerCrashRecoveryTestCase_prepareHaltWithAbortFails_jta_server.log > > > We see following error in log of WildFly (master): > {code} > 2018-10-03 22:28:02,503 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("server" => "default"), > ("pooled-connection-factory" => "activemq-ra") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.JmsXA-bkp"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.JmsXA-bkp]"] > } > {code} > Factory is defined: > {code:java} > <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA-bkp java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/> > {code} > However factory is registered after and deployment is able to use it. Error is logged intermittently. > Log file and xml configuration file are enclosed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11112) WildFly intermittently fails to add pooled-connection-factory but it still got registered after

by Ivan Straka (Jira)

Ivan Straka created WFLY-11112: ---------------------------------- Summary: WildFly intermittently fails to add pooled-connection-factory but it still got registered after Key: WFLY-11112 URL: https://issues.jboss.org/browse/WFLY-11112 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 14.0.0.Final, 15.0.0.Alpha1 Reporter: Ivan Straka Assignee: Jeff Mesnil We see following error in log of WildFly (master): {code} 2018-10-03 22:28:02,503 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "messaging-activemq"), ("server" => "default"), ("pooled-connection-factory" => "activemq-ra") ]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.JmsXA-bkp"], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.JmsXA-bkp]"] } {code} Factory is defined: {code:java} <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA-bkp java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/> {code} However factory is registered after and deployment is able to use it. Error is logged intermittently. Log file and xml configuration file are enclosed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2804) [DMN Designer] Properties Panel to drill-down to DMN component level

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-2804?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2804: ---------------------------------------- (More customisation of the UI for DMN 1.1 and 1.2....) > [DMN Designer] Properties Panel to drill-down to DMN component level > -------------------------------------------------------------------- > > Key: DROOLS-2804 > URL: https://issues.jboss.org/browse/DROOLS-2804 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > > The Properties Panel currently shows properties for Stunner-level "graph" components. > We need, for DMN, the Properties Panel to show the properties of DMN elements' properties at the "grid" level. For example, when a {{Context}} is selected the Properties Panel should show only the top level properties for the {{Context}} (i.e. not those of its {{ContextEntries}}). Selection of a {{ContextEntry}} should refresh the Properties Panel to show only the top-level properties of the {{ContextEntry}}. Selection of the {{ContextEntry}}'s {{Expression}} should again refresh the Properties Panel to show only the top-level properties of the {{Expression}} and so forth. > h2. Properties on the Grid Level > The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel. > h3. Literal expression > ||Selected item||Properties panel items|| > |Cell|(?)| > h3. Context > ||Selected item||Properties panel items|| > |Row|(?)| > |Column|(?)| > |Cell|(?)| > h3. Decision Table > ||Selected item||Properties panel items|| > |Row|(?)| > |Column|(?)| > |Cell|(?)| > h3. Relation > ||Selected item||Properties panel items|| > |Row|(?)| > |Column|(?)| > |Cell|(?)| > h3. Function > ||Selected item||Properties panel items|| > |Row|(?)| > |Column|(?)| > |Cell|(?)| > h3. Invocation > ||Selected item||Properties panel items|| > |Row|(?)| > |Column|(?)| > |Cell|(?)| > h2. Manual Acceptance Test > - Switching between DRG and Grid editor, check proper fields shown > - Switching between rows, columns, cells in Grid editor, check proper fields > -- In same expression kind > -- Across different expression kinds > - Clear expression kind > - Read only mode - older asset version > - All Grid specific properties saved -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11086) Usage of static fields from java.lang classes as EL expressions in JSPs doesn't work when requested more than once

by Tomas Hofman (Jira)

[ https://issues.jboss.org/browse/WFLY-11086?page=com.atlassian.jira.plugin... ] Tomas Hofman reassigned WFLY-11086: ----------------------------------- Assignee: Tomas Hofman (was: Stuart Douglas) > Usage of static fields from java.lang classes as EL expressions in JSPs doesn't work when requested more than once > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-11086 > URL: https://issues.jboss.org/browse/WFLY-11086 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 14.0.0.Final > Reporter: Adam Krajcik > Assignee: Tomas Hofman > Priority: Major > Attachments: jsp-expression-lang.war > > > Java EE7 (which supports EL 3.0 spec) allows JSPs to use EL expressions like: > {code} > <html> > <body> > foo: --- ${Boolean.TRUE} ---<br> > bar: --- ${Integer.MAX_VALUE} ---<br> > </body> > </html> > {code} > However, the > {code} > ${Boolean.TRUE} > {code} > and > {code} > ${Integer.MAX_VALUE} > {code} > in the above example aren't evaluated correctly if request is send more than once, and instead a blank string is rendered for them. The [^jsp-expression-lang.war] used in Steps to reproduce works correctly in 7.2.0.CD13. > More details in the linked forum thread https://developer.jboss.org/thread/271825. > The existing tests([JspELTestCase|https://github.com/wildfly/wildfly/blob/master/tests... doesn't cover the situation when request is sent more than once. -- 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