You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Bruce Schuchardt (JIRA)" <ji...@apache.org> on 2016/03/16 17:21:33 UTC

[jira] [Created] (GEODE-1103) intermittent suspect string in server cache during shutdown

Bruce Schuchardt created GEODE-1103:
---------------------------------------

             Summary: intermittent suspect string in server cache during shutdown
                 Key: GEODE-1103
                 URL: https://issues.apache.org/jira/browse/GEODE-1103
             Project: Geode
          Issue Type: Bug
          Components: client/server
            Reporter: Bruce Schuchardt


I frequently see this exception logged in cache servers during shutdown:

system.log: [warning 2016/03/15 23:55:08.852 PDT bridgegemfire_1_2_carlos_18051 <Cache Server Selector /0:0:0:0:0:0:0:0:24996 local port: 24996> tid=0x5c] unexpected
java.lang.InterruptedException
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2067)
	at java.util.concurrent.ThreadPoolExecutor.awaitTermination(ThreadPoolExecutor.java:1465)
	at com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.close(AcceptorImpl.java:1648)
	at com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.runSelectorLoop(AcceptorImpl.java:1185)
	at com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$4.run(AcceptorImpl.java:709)
	at java.lang.Thread.run(Thread.java:745)

The logs show that the server is shutting down and the shutdown code in AcceptorImpl clearly shows that it interrupts the acceptor thread so there's no reason for that thread to think this is an unexpected event.



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