{"action":"opened","issue":{"url":"https://api.github.com/repos/magro/memcached-session-manager/issues/318","repository_url":"https://api.github.com/repos/magro/memcached-session-manager","labels_url":"https://api.github.com/repos/magro/memcached-session-manager/issues/318/labels{/name}","comments_url":"https://api.github.com/repos/magro/memcached-session-manager/issues/318/comments","events_url":"https://api.github.com/repos/magro/memcached-session-manager/issues/318/events","html_url":"https://github.com/magro/memcached-session-manager/issues/318","id":191053683,"number":318,"title":"Using spymemcached-2.11.7","user":{"login":"tuomash","id":2692981,"avatar_url":"https://avatars.githubusercontent.com/u/2692981?v=3","gravatar_id":"","url":"https://api.github.com/users/tuomash","html_url":"https://github.com/tuomash","followers_url":"https://api.github.com/users/tuomash/followers","following_url":"https://api.github.com/users/tuomash/following{/other_user}","gists_url":"https://api.github.com/users/tuomash/gists{/gist_id}","starred_url":"https://api.github.com/users/tuomash/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tuomash/subscriptions","organizations_url":"https://api.github.com/users/tuomash/orgs","repos_url":"https://api.github.com/users/tuomash/repos","events_url":"https://api.github.com/users/tuomash/events{/privacy}","received_events_url":"https://api.github.com/users/tuomash/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-22T16:23:46Z","updated_at":"2016-11-22T16:23:46Z","closed_at":null,"body":"We have been using memcached-session-manager-1.8.3.jar, memcached-session-manager-tc7-1.8.3.jar and spymemcached-2.11.1.jar successfully in our staging environment for a long while, but when we setup another environment using the same library versions (and same Tomcat and Java versions) we ran into some issues.\r\n\r\nIt seems that after a while (a day or so) spymemcached-2.11.1 gets deadlocked like so:\r\n\r\n\"Memcached IO over {MemcachedConnection to /x.x.x.x:11211 /x.x.x.x:11211}\" prio=5 tid=109 BLOCKED\r\n at net.spy.memcached.internal.AbstractListenableFuture.notifyListeners(AbstractListenableFuture.java:144)\r\n at net.spy.memcached.internal.AbstractListenableFuture.notifyListeners(AbstractListenableFuture.java:130)\r\n at net.spy.memcached.internal.GetFuture.signalComplete(GetFuture.java:109)\r\n at net.spy.memcached.MemcachedClient$5.complete(MemcachedClient.java:1041)\r\n       Local Variable: net.spy.memcached.MemcachedClient$5#84\r\n at net.spy.memcached.protocol.BaseOperationImpl.transitionState(BaseOperationImpl.java:167)\r\n       Local Variable: net.spy.memcached.ops.OperationState#4\r\n at net.spy.memcached.protocol.ascii.BaseGetOpImpl.handleLine(BaseGetOpImpl.java:99)\r\n       Local Variable: java.lang.String#410564\r\n at net.spy.memcached.protocol.ascii.OperationImpl.readFromBuffer(OperationImpl.java:154)\r\n at net.spy.memcached.MemcachedConnection.readBufferAndLogMetrics(MemcachedConnection.java:825)\r\n at net.spy.memcached.MemcachedConnection.handleReads(MemcachedConnection.java:804)\r\n       Local Variable: sun.nio.ch.SocketChannelImpl#3Local Variable: java.nio.DirectByteBuffer#33\r\n at net.spy.memcached.MemcachedConnection.handleReadsAndWrites(MemcachedConnection.java:684)\r\n       Local Variable: sun.nio.ch.SelectionKeyImpl#9\r\n at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:647)\r\n       Local Variable: net.spy.memcached.protocol.ascii.AsciiMemcachedNodeImpl#1\r\n at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:418)\r\n       Local Variable: sun.nio.ch.Util$2#1Local Variable: java.util.HashMap$KeyIterator#37265\r\n at net.spy.memcached.MemcachedConnection.run(MemcachedConnection.java:1401)\r\n\r\nThis shows in logs as constant timeouts to the memcached servers, but when I checked with netstat I saw that the Java process had established connections to the memcached servers normally. The only way to recover this situation is to restart Tomcat.\r\n\r\nThis issue seems to be fixed in spymemcached 2.11.2: https://github.com/couchbase/spymemcached/releases/tag/2.11.2.\r\n\r\nSo my question is, is it safe to use the latest spymemcached 2.11 version, which is 2.11.7, with memcached-session-manager version 1.8.3? The SetupdAndConfiguration page suggests using 2.11.1 but has it been updated in a while?"}}
{"actor":{"display_login":"tuomash"}}