search

strugglejl / memcached-session-manager

Automatically exported from code.google.com/p/memcached-session-manager
0 stars 0 forks source link

NoClassDefFoundError ProtocolVersion #162

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. added this to my web app context.xml
<Manager className="de.javakaffee.web.msm.MemcachedBackupSessionManager"
      memcachedNodes="n1:xxxtest-sess1.xxx.com:xxxxx"
      requestUriIgnorePattern=".*\.(ico|png|gif|jpg|css|js)$"
      transcoderFactoryClass="de.javakaffee.web.msm.serializer.kryo.KryoTranscoderFactory" />

2. start up tomcat

What is the expected output? Not getting any errors
What do you see instead?
May 7, 2013 3:30:54 PM de.javakaffee.web.msm.MemcachedSessionService 
updateExpirationInMemcached
INFO: Could not update expiration in memcached for session 
E31094818C0C1B10C54A0C79D1F77D85-n1.xxxtest-app2
java.lang.NoClassDefFoundError: org/apache/http/ProtocolVersion
    at java.lang.Class.getDeclaredFields0(Native Method)
    at java.lang.Class.privateGetDeclaredFields(Class.java:2308)
    at java.lang.Class.getDeclaredFields(Class.java:1760)
    at com.esotericsoftware.kryo.serialize.FieldSerializer.rebuildCachedFields(FieldSerializer.java:61)

What version of the product are you using? 
memcache 1.4.13
kyro 1.6.4

On what operating system?
ubuntu

Please provide any additional information below.

Original issue reported on code.google.com by mmartin2...@gmail.com on 7 May 2013 at 11:08

GoogleCodeExporter commented 8 years ago 
also: 
memcached-session-manager-1.6.4.jar,memcached-session-manager-tc6-1.6.4.jar,spym
emcached-2.8.4.jar,couchbase-client-1.1.4.jar

Original comment by mmartin2...@gmail.com on 7 May 2013 at 11:12

GoogleCodeExporter commented 8 years ago 
Which version of tomcat are you using?

Original comment by martin.grotzke on 8 May 2013 at 6:03

GoogleCodeExporter commented 8 years ago 
Tomcat 6 - we got this solved by adding in the httpcore jar that was needed

Original comment by mmartin2...@gmail.com on 8 May 2013 at 3:24

GoogleCodeExporter commented 8 years ago 
Was it an inconsistency in your deployment, or what was the issue?

Original comment by martin.grotzke on 8 May 2013 at 7:47

GoogleCodeExporter commented 8 years ago 
I am not sure if we are even using couchbase but the couchbase jar got deployed 
without all the other jars it requires so it refused to start up until we got 
the other jars in there

Original comment by mmartin2...@gmail.com on 8 May 2013 at 7:54

GoogleCodeExporter commented 8 years ago 
Ok, so it's in line with the documentation. Closing.

Original comment by martin.grotzke on 8 May 2013 at 7:57