geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-1613) CI failure: ConnectionPoolDUnitTest.test021ClientGetOfInvalidServerEntry
Date Thu, 07 Jul 2016 17:29:11 GMT

    [ https://issues.apache.org/jira/browse/GEODE-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366444#comment-15366444
] 

ASF subversion and git services commented on GEODE-1613:
--------------------------------------------------------

Commit 860c902048d63cc7ae0fe3bf3c2cd329486fa73b in incubator-geode's branch refs/heads/develop
from [~bschuchardt]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=860c902 ]

GEODE-1613 CI failure: ConnectionPoolDUnitTest.test021ClientGetOfInvalidServerEntry

Added a try/catch for scheduling the task to handle RejectedExecutionException
& fixed up the handling of shutdown conditions so the run() method no longer
throws cancellation exceptions.


> CI failure: ConnectionPoolDUnitTest.test021ClientGetOfInvalidServerEntry
> ------------------------------------------------------------------------
>
>                 Key: GEODE-1613
>                 URL: https://issues.apache.org/jira/browse/GEODE-1613
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>            Reporter: Dan Smith
>            Assignee: Bruce Schuchardt
>              Labels: ci
>
> Revision: 49d144bb2cf731d4c62fc86715fd8c9e0a680d45 
> Previously run tests: [CacheServerSSLConnectionDUnitTest, AutoConnectionSourceDUnitTest,
SSLNoClientAuthDUnitTest, ClientServerRegisterInterestsDUnitTest, SnapshotByteArrayDUnitTest,
SnapshotPerformanceDUnitTest, SnapshotDUnitTest, ParallelSnapshotDUnitTest, ConnectionPoolDUnitTest]
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> -----------------------------------------------------------------------
> Found suspect string in log4j at line 1302
> [error 2016/06/28 03:35:22.793 PDT <poolTimer-testPool-3> tid=0x9e5] Unexpected
error in pool task <com.gemstone.gemfire.cache.client.internal.DataSerializerRecoveryListener$RecoveryTask@5f294be2>
> java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@7d3a6dfa
rejected from com.gemstone.gemfire.internal.ScheduledThreadPoolExecutorWithKeepAlive$1@3838ec39[Terminated,
pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 4]
> 	at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047)
> 	at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:326)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:533)
> 	at com.gemstone.gemfire.internal.ScheduledThreadPoolExecutorWithKeepAlive.schedule(ScheduledThreadPoolExecutorWithKeepAlive.java:102)
> 	at com.gemstone.gemfire.internal.ScheduledThreadPoolExecutorWithKeepAlive.schedule(ScheduledThreadPoolExecutorWithKeepAlive.java:97)
> 	at com.gemstone.gemfire.cache.client.internal.DataSerializerRecoveryListener$RecoveryTask.run2(DataSerializerRecoveryListener.java:144)
> 	at com.gemstone.gemfire.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1247)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message