[JBoss JIRA] (WFLY-11038) Ensure org.apache.geronimo.specs are excluded from tests
by Yeray Borges (JIRA)
Yeray Borges created WFLY-11038:
-----------------------------------
Summary: Ensure org.apache.geronimo.specs are excluded from tests
Key: WFLY-11038
URL: https://issues.jboss.org/browse/WFLY-11038
Project: WildFly
Issue Type: Task
Affects Versions: 14.0.0.Final
Reporter: Yeray Borges
Assignee: Yeray Borges
When we are compiling the compatibility test suite, the geronimo-jta_1.1_spec library could come transitively from different dependencies. Some of those dependencies are using wildcards to exclude it.
Since there is a bug in maven enforcer plugin [MENFORCER-302|https://issues.apache.org/jira/browse/MENFORCER-302] for the Dependency Convergence rule, when we are creating the product branches; the enforcer plugin finds (due to its bug) a productized version of geronimo-jta_1.1_spec and the transitive dependencies coming from the compatibility test suite, failing in that case.
As a workaround to avoid this problem, we need to add explicitly the exclusions of geronimo-jta_1.1_spec in the compatibility test suite.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11037) Intermittent Agoral warnings during startup
by Rich DiCroce (JIRA)
Rich DiCroce created WFLY-11037:
-----------------------------------
Summary: Intermittent Agoral warnings during startup
Key: WFLY-11037
URL: https://issues.jboss.org/browse/WFLY-11037
Project: WildFly
Issue Type: Bug
Components: Agroal
Affects Versions: 14.0.0.Final
Reporter: Rich DiCroce
Sometimes during startup, Agroal spams the log with this:
{code}
2018-09-18 10:35:46,226 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state CHECKED_IN
2018-09-18 10:35:46,226 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,226 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,227 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,227 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,227 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,227 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,228 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,228 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,228 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,228 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,233 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
{code}
I'm not sure why, and it doesn't always happen. It appears to have something to do with idle-removal being on, as I was not able to reproduce the issue without it.
My pool configuration with the problem (sometimes) happening is:
{code}
<connection-pool max-size="${database.maxPool:20}" background-validation="30000" idle-removal="30"/>
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11037) Intermittent Agroal warnings during startup
by Rich DiCroce (JIRA)
[ https://issues.jboss.org/browse/WFLY-11037?page=com.atlassian.jira.plugin... ]
Rich DiCroce updated WFLY-11037:
--------------------------------
Summary: Intermittent Agroal warnings during startup (was: Intermittent Agoral warnings during startup)
> Intermittent Agroal warnings during startup
> -------------------------------------------
>
> Key: WFLY-11037
> URL: https://issues.jboss.org/browse/WFLY-11037
> Project: WildFly
> Issue Type: Bug
> Components: Agroal
> Affects Versions: 14.0.0.Final
> Reporter: Rich DiCroce
>
> Sometimes during startup, Agroal spams the log with this:
> {code}
> 2018-09-18 10:35:46,226 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state CHECKED_IN
> 2018-09-18 10:35:46,226 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,226 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,227 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,227 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,227 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,227 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,228 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,228 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,228 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,228 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> 2018-09-18 10:35:46,233 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
> {code}
> I'm not sure why, and it doesn't always happen. It appears to have something to do with idle-removal being on, as I was not able to reproduce the issue without it.
> My pool configuration with the problem (sometimes) happening is:
> {code}
> <connection-pool max-size="${database.maxPool:20}" background-validation="30000" idle-removal="30"/>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2409) Memory Leak in sliding window
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2409?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-2409:
-------------------------------------
[~ev.srinivas] Please share your reproducer (attach it to this ticket) and I'll give a look asap. Thanks.
> Memory Leak in sliding window
> -----------------------------
>
> Key: DROOLS-2409
> URL: https://issues.jboss.org/browse/DROOLS-2409
> Project: Drools
> Issue Type: Feature Request
> Components: core engine
> Affects Versions: 7.6.0.Final
> Environment: Mac with Java 1.8 using Spring Boot (see attached demo project)
> Reporter: Mike Baranski
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: complete.tar.gz
>
>
> See attached project.
> `gradle test` causes an out of memory exception on my machine after ~2.6 million events. Events should be released for GC after 1 second, but that does not appear to be happening.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JGRP-2293) Graceful concurrent leaving of coordinator(s) leaves the cluster with wrong views
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/JGRP-2293?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated JGRP-2293:
---------------------------------
Description:
JGroups does not handle concurrent leaving of nodes correctly. This is a typical use case in cloud environment when scaled down with an autoscaler/manually which we need to handle.
A simple test can be devised which fails first n (where n>1) nodes from a cluster, reproducer PR https://github.com/belaban/JGroups/pull/397
was:
JGroups does not handle concurrent leaving of nodes correctly. This is a typical use case in cloud environment when scaled down with an autoscaler/manually which we need to handle.
A simple test can be devised which fails first n (where n>1) nodes from a cluster.
> Graceful concurrent leaving of coordinator(s) leaves the cluster with wrong views
> ---------------------------------------------------------------------------------
>
> Key: JGRP-2293
> URL: https://issues.jboss.org/browse/JGRP-2293
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.14
> Reporter: Radoslav Husar
> Assignee: Bela Ban
> Priority: Critical
>
> JGroups does not handle concurrent leaving of nodes correctly. This is a typical use case in cloud environment when scaled down with an autoscaler/manually which we need to handle.
> A simple test can be devised which fails first n (where n>1) nodes from a cluster, reproducer PR https://github.com/belaban/JGroups/pull/397
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JGRP-2293) Graceful concurrent leaving of coordinator(s) leaves the cluster with wrong views
by Radoslav Husar (JIRA)
Radoslav Husar created JGRP-2293:
------------------------------------
Summary: Graceful concurrent leaving of coordinator(s) leaves the cluster with wrong views
Key: JGRP-2293
URL: https://issues.jboss.org/browse/JGRP-2293
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0.14
Reporter: Radoslav Husar
Assignee: Bela Ban
Priority: Critical
JGroups does not handle concurrent leaving of nodes correctly. This is a typical use case in cloud environment when scaled down with an autoscaler/manually which we need to handle.
A simple test can be devised which fails first n (where n>1) nodes from a cluster.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JGRP-2286) VERIFY_SUSPECT can return false positives if member is killed and immediately restarted
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/JGRP-2286?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed JGRP-2286.
------------------------------
Resolution: Rejected
False alarm.
> VERIFY_SUSPECT can return false positives if member is killed and immediately restarted
> ---------------------------------------------------------------------------------------
>
> Key: JGRP-2286
> URL: https://issues.jboss.org/browse/JGRP-2286
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.13
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
>
> When a member is killed, it is suspected and VERIFY_SUSPECT attempts to send a message to the member to verify that it has left. If, however, the member is restarted before the VERIFY_SUSPECT sends its message, the newly started member (with same physical address, but different UUID) can receive it and erroneously reply with an I_AM_NOT_DEAD response. This results in a zombie member in the view that will remain until the reincarnated member leaves.
> To fix this, we should add the address of the suspected member to the VerifyHeader and validate that the member is us before sending an I_AM_NOT_DEAD response.
> Additionally, we can respond with a new MBR_IS_DEAD response on behalf of the suspected member, in the case that the message was receive by the reincarnated member to expedite the removal of the suspected member from the view.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months