[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections
by Mohamed Bd (JIRA)
[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ]
Mohamed Bd edited comment on WFLY-10531 at 10/1/18 2:26 PM:
------------------------------------------------------------
I had the same issue while upgrading my applications to wildfly 13/14,
and had to stop using injected JMSContext,
and reverted back to jms 1.1 as a workaround.
was (Author: mohtech):
I had the same issue while upgrading my applications to wildfly 13/14,
and had to stop using inject JMSContext,
and reverted back to jms 1.1 as a workaround.
> 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
> 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.5.0#75005)
5 years, 6 months
[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections
by Mohamed Bd (JIRA)
[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ]
Mohamed Bd commented on WFLY-10531:
-----------------------------------
I had the same issue while upgrading my applications to wildfly 13/14,
and had to stop using inject JMSContext,
and reverted back to jms 1.1 as a workaround.
> 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
> 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.5.0#75005)
5 years, 6 months
[JBoss JIRA] (DROOLS-3059) Serial Version UUID on Declared Types
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-3059:
-----------------------------------
Summary: Serial Version UUID on Declared Types
Key: DROOLS-3059
URL: https://issues.jboss.org/browse/DROOLS-3059
Project: Drools
Issue Type: Enhancement
Components: core engine
Affects Versions: 7.12.0.Final
Reporter: Stylianos Koussouris
Assignee: Mario Fusco
We wish to update DeclaredTypes whilst session is in use but the generated serial version ID changes when the DeclaredType pojo is recompiled resulting InvalidClassExceptions. We therefore suggest the usage of an annotation @SerialVersionUUID to set in a constant manner the UUID
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 6 months
[JBoss JIRA] (WFCORE-4145) --admin-only might be worth marking as deprecated with ./standalone.sh --help
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4145?page=com.atlassian.jira.plugi... ]
Brian Stansberry moved JBEAP-8273 to WFCORE-4145:
-------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-4145 (was: JBEAP-8273)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Management
(was: Management)
Target Release: (was: 7.backlog.GA)
Affects Version/s: (was: 7.1.0.DR10)
> --admin-only might be worth marking as deprecated with ./standalone.sh --help
> -----------------------------------------------------------------------------
>
> Key: WFCORE-4145
> URL: https://issues.jboss.org/browse/WFCORE-4145
> Project: WildFly Core
> Issue Type: Task
> Components: Management
> Reporter: Radim Hatlapatka
> Assignee: Brian Stansberry
> Priority: Optional
>
> As part of [EAP7-636] there was introduced {{\-\-start-mode}} option which allows to define starting mode and basically replaces {{\-\-admin-only}} option and {{\-\-start-mode}} option is more universal one.
> I believe we should mark {{\-\-admin-only}} option as deprecated in favor of {{\-\-start-mode=admin-only}} option in standalone mode.
> [~bstansberry2], WDYT?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 6 months
[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette aesthetics
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2522:
--------------------------------
Attachment: Screen Shot 2018-10-01 at 12.26.15 PM.png
> [DMN Designer] Palette aesthetics
> ---------------------------------
>
> Key: DROOLS-2522
> URL: https://issues.jboss.org/browse/DROOLS-2522
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: drools-tools
> Attachments: DROOLS-2522.mp4, Screen Shot 2018-10-01 at 12.26.15 PM.png, palette.png
>
>
> The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 6 months
[JBoss JIRA] (WFLY-9455) WFLYTX0001: Unable to roll back active transaction thrown for EJB bridge transactions
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-9455?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka commented on WFLY-9455:
---------------------------------------
[~kabirkhan][~pkremens] the backport for CD14 is here: https://github.com/jbossas/jboss-eap7/pull/2807 This PR does not introduces the issue of the JDK11 compilation error.
> WFLYTX0001: Unable to roll back active transaction thrown for EJB bridge transactions
> -------------------------------------------------------------------------------------
>
> Key: WFLY-9455
> URL: https://issues.jboss.org/browse/WFLY-9455
> Project: WildFly
> Issue Type: Bug
> Components: XTS
> Affects Versions: 11.0.0.CR1
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Fix For: 15.0.0.Alpha1
>
>
> It happens to get exception
> {code}
> ERROR [org.jboss.as.txn] (default task-12) WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 0
> ERROR [org.jboss.as.txn] (default task-12) WFLYTX0001: Unable to roll back active transaction: javax.transaction.SystemException: WFTXN0032: Rollback not allowed on imported transaction
> at org.wildfly.transaction.client.LocalTransaction.rollbackAndDissociate(LocalTransaction.java:100)
> at org.wildfly.transaction.client.ContextTransactionManager.rollback(ContextTransactionManager.java:83)
> at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.checkTransactionStatus(TransactionRollbackSetupAction.java:137)
> at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.teardown(TransactionRollbackSetupAction.java:67)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1510)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:326)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> when using XTS transactions bridged to JTA for EJB handling. This happens on change of integration layer for WFTC in WFLY11.
> The integration issues were already discussed as part of the JBTM-2853.
> Here I hit a trouble of having log filled with the exception mentioned above. This does not cause a functionality trouble but the log is ugly filled with ERRORs.
> The trouble seems to be caused by the fact that transaction is imported on ivocation of WS
> https://github.com/wildfly/wildfly/blob/master/webservices/server-integra...
> but as it was suspended in the integration code before
> https://github.com/jbosstm/narayana/blob/master/txbridge/src/main/java/or...
> now the WFTC holds the notion about the transaction even on call of
> https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java...
> and such transaction is tried to be rollback which is forbidden on WFTC for imported ones and thus at least ERROR msg is written to the log.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 6 months
[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections
by Jan-Willem Gmelig Meyling (JIRA)
[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ]
Jan-Willem Gmelig Meyling edited comment on WFLY-10531 at 10/1/18 12:11 PM:
----------------------------------------------------------------------------
After some looking into WFLY-9501, I think the implementation causes an regression that does not close a JMS context at all if it the delegate is not first accessed through a method in tranaction state Active. Ie. any callee in transaction status Committing, NotActive, etc.etc. will not register the cleanUpListener (see: https://github.com/JiriOndrusek/wildfly/blob/6355f48234b1b976230c3c529d5a...) , and the context will also not be closed with the destroyal of the bean due to the removal of the PreDestroy annotation on : https://github.com/JiriOndrusek/wildfly/commit/6355f48234b1b976230c3c529d... . I'm also not sure how the current transaction check handles the slightly different EJB transactions.
[~jondruse] can you please elaborate on your implementation?
was (Author: jwgmeligmeyling):
After some looking into WFLY-9501, I think the implementation causes an regression that does not close a JMS context at all if it the delegate is not first accessed through a method in tranaction state Active. Ie. any callee in transaction status Committing, NotActive, etc.etc. will not register the cleanUpListener (see: https://github.com/JiriOndrusek/wildfly/blob/6355f48234b1b976230c3c529d5a...) , and the context will also not be closed with the destroyal of the bean due to the removal of the PreDestroy annotation on : https://github.com/JiriOndrusek/wildfly/commit/6355f48234b1b976230c3c529d...
[~jondruse] can you please elaborate on your implementation?
> 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
> 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.5.0#75005)
5 years, 6 months
[JBoss JIRA] (JGRP-2288) S3_PING: Under certain conditions, subclusters fail to merge after network partition
by Nick Sawadsky (JIRA)
[ https://issues.jboss.org/browse/JGRP-2288?page=com.atlassian.jira.plugin.... ]
Nick Sawadsky commented on JGRP-2288:
-------------------------------------
Ok, thanks for the update [~belaban]. Really appreciate your looking into it, when time permits.
> S3_PING: Under certain conditions, subclusters fail to merge after network partition
> ------------------------------------------------------------------------------------
>
> Key: JGRP-2288
> URL: https://issues.jboss.org/browse/JGRP-2288
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.15
> Reporter: Nick Sawadsky
> Assignee: Bela Ban
> Fix For: 4.0.16
>
>
> Repro steps:
> 1. Set up a cluster of four nodes, two on one machine (Host 1) and two on another (Host 2). Let's call the nodes A, B, C, and D.
> 2. Configure all 4 nodes with S3_PING as the discovery mechanism. Set remove_all_files_on_view_change to true.
> 3. Start up nodes in the order A, B, C, D.
> 4. In the S3 bucket, there should be a single file with all four nodes listed. Node A should be flagged as the coordinator. Ensure that the UUID for node B is larger than the UUID for node C, when compared as two's complement integers. If this is not the case, shut down all nodes and restart in order. Repeat until the desired relationship is achieved. Note that with two's complement, a UUID having a first hex digit of 8 or higher is treated as negative for comparison purposes. So, for example, a UUID starting with 'a' is less than a UUID starting with 'b' which is less than a UUID starting with '1'.
> 5. On Host 1, use iptables to block all traffic going to and coming from Host 2.
> sudo iptables -A INPUT -s <Host 2 IP addr> -j DROP
> sudo iptables -A OUTPUT -d <Host 2 IP addr> -j DROP
> 6. Allow a few minutes for the nodes to detect the network partition. Eventually you should see two files in the S3 bucket.
> 7. Using Ctrl-C, stop node A.
> 8. You should soon find only a single file in the bucket, containing a single entry for node B. This is a result of the remove_all_files_on_view_change setting on S3_PING, which we set to true to avoid accumulation of old files in the bucket.
> 9. Resolve the network partition:
> sudo iptables -F OUTPUT
> sudo iptables -F INPUT
> 10. You will find that, even after many minutes, the subclusters are not merged.
> I believe the reason why the subclusters are never merged is as follows:
> - MERGE3 on nodes B, C and D uses S3_PING to find members to send INFO messages to. Each one finds only node B in the discovery file. As a result, only node B's view consistency checker has anything to work with.
> - On node B, the consistency checker can see that there are two coordinators, B and C. However, node C has a lower UUID, so node B defers to it to perform the merge. Node C never performs the merge because, as mentioned above, it is not receiving any INFO messages.
> I this this problem would affect FILE_PING as well, and other protocols derived from FILE_PING. Looking at the latest 4.x code, it appears the problem still exists there.
> I think the crux of the issue is that the coordinator on Host 2 (node C) does not re-create its discovery file after it is deleted by node B. Would it be reasonable for FILE_PING.findMembers() to create the discovery file if the node is a coordinator and the file doesn't exist?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 6 months
[JBoss JIRA] (WFLY-11097) XtsAsLogger doesn't compile on JDK11, WildFly can't be build on Java 11
by Kabir Khan (JIRA)
Kabir Khan created WFLY-11097:
---------------------------------
Summary: XtsAsLogger doesn't compile on JDK11, WildFly can't be build on Java 11
Key: WFLY-11097
URL: https://issues.jboss.org/browse/WFLY-11097
Project: WildFly
Issue Type: Bug
Components: Server, XTS
Environment: {noformat}
java version "11" 2018-09-25
Java(TM) SE Runtime Environment 18.9 (build 11+28)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
{noformat}
Reporter: Petr Kremensky
Assignee: Ondra Chaloupka
Priority: Blocker
Compilation failure on JDK 11 introduced by https://github.com/wildfly/wildfly/pull/11702
{noformat}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) on project wildfly-xts: Compilation failure
[ERROR] /home/pkremens/devel/wildfly/xts/target/generated-sources/annotations/org/jboss/as/xts/logging/XtsAsLogger_$logger.java:[11,22] '.' expected
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 6 months