ConnectionFactoryRepository not being Serialiazble? Potential HA issues

[rickcr]

I'm a bit worried about some of these errors I'm seeing on JBoss. Is it possible when our code is moved to production there will be some high availability issues if we try do some session replication?

I haven't dug into the source code that deeply in this regard, but I'm wondering if all the code related to the ProviderSigninAttempt that is put in the session is going to come over correctly? Looks like certain things are Serializable that will need to be?...

10:24:33,770 ERROR [JBossCacheService] externalizeSession(): exception occurred externalizing session SessionBasedClusteredSession[id: J2Ipc
kGtWNTVdgzLIFY6UA** lastAccessedTime: 1328887472645 version: 33 lastOutdated: 0]
java.io.NotSerializableException: org.springframework.social.connect.support.ConnectionFactoryRegistry
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164)
        at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
        at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
        at java.util.Hashtable.writeObject(Hashtable.java:824)
        at sun.reflect.GeneratedMethodAccessor417.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)

[netke]

I have the same problem on Tomcat when using session replication. Is there a JIRA ticket for this to vote?

[habuma]

There's not currently an open issue for this, but feel free to open one at https://jira.springsource.org/browse/SOCIAL and we'll look into it.

Since recreating this kind of thing can sometimes be tricky, it would be helpful if you could give steps to recreate the problem reliably so that (1) we can confirm it's a problem and (2) we can confirm that any fix we perform actually corrects the problem. I don't mind digging and trying to recreate it myself, but it'll be a big timesaver if you can give me the steps you're performing so that I know that you and I are looking at the same thing.

[netke]

Well, it is tricky indeed. One way is to setup two Tomcats in a cluster with session replication (http://tomcat.apache.org/tomcat-6.0-...ter-howto.html) and observe the logs while using provider sign in functionality. Another way is to create a unit test that will serialize the ProviderSignInAttempt object.