Hi,
when I use the
com.amazonaws.services.dynamodb.sessionmanager.DynamoDBSessionManager I get
classloader issues when a session gets deserialized and my session contains
classes which are not available to the shared loader.
My question:
Is this a bug
On Oct 31, 2013, at 8:19 AM, spr...@gmx.eu wrote:
Hi,
when I use the
com.amazonaws.services.dynamodb.sessionmanager.DynamoDBSessionManager I get
class loader issues
Can you be more specific here? What stack trace do you see?
when a session gets deserialized and my session contains
2013/10/31 spr...@gmx.eu:
Hi,
when I use the
com.amazonaws.services.dynamodb.sessionmanager.DynamoDBSessionManager I get
classloader issues when a session gets deserialized and my session contains
classes which are not available to the shared loader.
My question:
Is this a bug
1.) Seeing as it's their code, have you asked Amazon? Not
sure if this is you, but seems like a similar issue.
https://github.com/aws/aws-dynamodb-session-tomcat/issues/1
Oh yes, same issue.
2.) Have you tried one of Tomcat's included persistent
session managers? Do you see the same
Their code (DynamoDBSessionStore.load(...)) uses ObjectInputStream
Tomcat code (e.g. o.a.catalina.session.FileStore.load(..)) uses
CustomObjectInputStream which knows how to deal with class loaders.
Yes.
It is their bug (or feature).
:)
Thank you!
