Uploaded image for project: 'Spymemcached Java Client'
  1. Spymemcached Java Client
  2. SPY-80

timeout error causing application to crash.

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: .next
    • Component/s: None
    • Security Level: Public
    • Labels:
      None
    • Environment:
      membase 1.7.2r
      spy 2.7.3

      Description

      We have a customer on membase 1.7.2r and spy 2.7.3 that saw a application issue during rebalance.

      Their devs said that the app received timeout errors and the exception below:

      Because of the timeout issues with rebalance, they ended up deleting the bucket and creating and repopulating them.

      They'd like to know on the spy side, the cause for the timeout and if this is fixed in the new java client?

      thanks

      -Alex.

      java.lang.RuntimeException: Exception waiting for value
      at net.spy.memcached.MemcachedClient.gets(MemcachedClient.java:1103)
      at net.spy.memcached.MemcachedClient.gets(MemcachedClient.java:1161)
      at com.playtika.common.dal.vs.MembaseDAO.getUserMessages(MembaseDAO.java:343)
      at com.playtika.cache.CacheDao.getUserMessage(CacheDao.java:978)
      at com.playtika.servlets.Common.getUserMessages(Common.java:276)
      at com.playtika.servlets.Common.doPost(Common.java:142)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at com.playtika.filters.RequestsLoggerFilter.doFilter(RequestsLoggerFilter.java:78)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at com.playtika.filters.LoggerFilter.doFilter(LoggerFilter.java:75)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at com.playtika.filters.SessionFilter.doFilter(SessionFilter.java:89)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at com.playtika.stats.StatisticFilter.doFilter(StatisticFilter.java:46)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at com.playtika.filters.RequestAccountMappingFilter.doFilter(RequestAccountMappingFilter.java:50)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at com.playtika.filters.CharsetEncodingFilter.doFilter(CharsetEncodingFilter.java:13)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
      at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
      at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
      at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
      at java.lang.Thread.run(Thread.java:662)
      Caused by: java.util.concurrent.ExecutionException: OperationException: SERVER: Internal error
      at net.spy.memcached.internal.OperationFuture.get(OperationFuture.java:81)
      at net.spy.memcached.MemcachedClient.gets(MemcachedClient.java:1098)
      ... 37 more
      Caused by: OperationException: SERVER: Internal error
      at net.spy.memcached.protocol.BaseOperationImpl.handleError(BaseOperationImpl.java:135)
      at net.spy.memcached.protocol.binary.OperationImpl.getStatusForErrorCode(OperationImpl.java:184)
      at net.spy.memcached.protocol.binary.OperationImpl.finishedPayload(OperationImpl.java:150)
      at net.spy.memcached.protocol.binary.OperationImpl.readFromBuffer(OperationImpl.java:139)
      at net.spy.memcached.protocol.binary.GetsOperationImpl.readFromBuffer(GetsOperationImpl.java:5)
      at net.spy.memcached.MemcachedConnection.handleReads(MemcachedConnection.java:504)
      at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:418)
      at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:275)
      at net.spy.memcached.MemcachedClient.run(MemcachedClient.java:2030)

      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        alex Alex Ma created issue -
        ingenthr Matt Ingenthron made changes -
        Field Original Value New Value
        Assignee Raghavan Srinivas [ rags ] Michael Nitschinger [ daschl ]
        Hide
        daschl Michael Nitschinger added a comment -

        Hi Alex,

        I know it's been a long time, but do you recall if this issue persisted even with a newer release of the client? 2.7 is old now and we recommend upgrading (we'll release 2.9 soon).

        If this has not seen any progress, I think we can close this - right?

        Show
        daschl Michael Nitschinger added a comment - Hi Alex, I know it's been a long time, but do you recall if this issue persisted even with a newer release of the client? 2.7 is old now and we recommend upgrading (we'll release 2.9 soon). If this has not seen any progress, I think we can close this - right?
        daschl Michael Nitschinger made changes -
        Assignee Michael Nitschinger [ daschl ] Alex Ma [ alex ]
        daschl Michael Nitschinger made changes -
        Fix Version/s .next [ 10205 ]

          People

          • Assignee:
            alex Alex Ma
            Reporter:
            alex Alex Ma
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Gerrit Reviews

              There are no open Gerrit changes