[JBoss JIRA] (ISPN-8902) Client hangs forever when IP address not accessible
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-8902?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on ISPN-8902:
-----------------------------------
[~galder.zamarreno] It's not related to KQueue but your system configuration in general. Notice that when the test attempts to connect to 127.0.0.1 it gets refused immediately, when you try to connect to 127.0.0.[2-4] you're getting "Connection timed out" - I got these refused right away. When I run
{code}
08:44:54@rvansa infinispan$ ip route show table local
...
local 127.0.0.0/8 dev lo proto kernel scope host src 127.0.0.1
local 127.0.0.1 dev lo proto kernel scope host src 127.0.0.1
{code}
So I recommend adding similar route. Regarding 'real' IPs that don't respond quickly: how would you like handle this? You can always lower your connection timeout... I could imagine having a 'soft' limit that would trigger connection to another server (but not fail the previous connection attempt) but that would be an enhancement, not a bug fix.
> Client hangs forever when IP address not accessible
> ---------------------------------------------------
>
> Key: ISPN-8902
> URL: https://issues.jboss.org/browse/ISPN-8902
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 9.2.0.Final
> Reporter: Galder Zamarreño
> Assignee: Radim Vansa
> Fix For: 9.2.1.Final
>
> Attachments: infinispan.log
>
>
> Can be replicated with code [here|https://github.com/galderz/jdg-sandbox/blob/master/client/src/main/j...]
> Thread dump is [here|https://gist.github.com/galderz/89b387b9e8b644456c18653e7b3c3c38].
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (ISPN-8930) RestOperationsTest#shouldPutImmortalEntryWithZeroTtlAndIdleTime random failure
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-8930?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-8930:
--------------------------------
Description:
This test can fail randomly with a NPE
{code}
java.lang.NullPointerException
at org.infinispan.rest.BaseRestOperationsTest.shouldPutImmortalEntryWithZeroTtlAndIdleTime(BaseRestOperationsTest.java:853)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
... Removed 16 stack frames
{code}
This is caused by the thread being stalled for > 100 ms after the put but before reading.
was:
This test can fail randomly with a NPE
{code}
java.lang.NullPointerException
at org.infinispan.rest.BaseRestOperationsTest.shouldPutImmortalEntryWithZeroTtlAndIdleTime(BaseRestOperationsTest.java:853)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
... Removed 16 stack frames
{code}
This is caused by the thread being stalled for > 100 ms after the put but before reading. Thus the expiration is not being overridden properly.
> RestOperationsTest#shouldPutImmortalEntryWithZeroTtlAndIdleTime random failure
> ------------------------------------------------------------------------------
>
> Key: ISPN-8930
> URL: https://issues.jboss.org/browse/ISPN-8930
> Project: Infinispan
> Issue Type: Bug
> Components: REST
> Affects Versions: 9.2.0.Final
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.2.1.Final, 9.3.0.Alpha1
>
>
> This test can fail randomly with a NPE
> {code}
> java.lang.NullPointerException
> at org.infinispan.rest.BaseRestOperationsTest.shouldPutImmortalEntryWithZeroTtlAndIdleTime(BaseRestOperationsTest.java:853)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
> ... Removed 16 stack frames
> {code}
> This is caused by the thread being stalled for > 100 ms after the put but before reading.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (ISPN-8930) RestOperationsTest#shouldPutImmortalEntryWithZeroTtlAndIdleTime random failure
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-8930?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-8930:
--------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/5828
> RestOperationsTest#shouldPutImmortalEntryWithZeroTtlAndIdleTime random failure
> ------------------------------------------------------------------------------
>
> Key: ISPN-8930
> URL: https://issues.jboss.org/browse/ISPN-8930
> Project: Infinispan
> Issue Type: Bug
> Components: REST
> Affects Versions: 9.2.0.Final
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.2.1.Final, 9.3.0.Alpha1
>
>
> This test can fail randomly with a NPE
> {code}
> java.lang.NullPointerException
> at org.infinispan.rest.BaseRestOperationsTest.shouldPutImmortalEntryWithZeroTtlAndIdleTime(BaseRestOperationsTest.java:853)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
> ... Removed 16 stack frames
> {code}
> This is caused by the thread being stalled for > 100 ms after the put but before reading. Thus the expiration is not being overridden properly.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (ISPN-8930) RestOperationsTest#shouldPutImmortalEntryWithZeroTtlAndIdleTime random failure
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-8930?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-8930:
--------------------------------
Fix Version/s: 9.2.1.Final
9.3.0.Alpha1
> RestOperationsTest#shouldPutImmortalEntryWithZeroTtlAndIdleTime random failure
> ------------------------------------------------------------------------------
>
> Key: ISPN-8930
> URL: https://issues.jboss.org/browse/ISPN-8930
> Project: Infinispan
> Issue Type: Bug
> Components: REST
> Affects Versions: 9.2.0.Final
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.2.1.Final, 9.3.0.Alpha1
>
>
> This test can fail randomly with a NPE
> {code}
> java.lang.NullPointerException
> at org.infinispan.rest.BaseRestOperationsTest.shouldPutImmortalEntryWithZeroTtlAndIdleTime(BaseRestOperationsTest.java:853)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
> ... Removed 16 stack frames
> {code}
> This is caused by the thread being stalled for > 100 ms after the put but before reading. Thus the expiration is not being overridden properly.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years