[wildfly-dev] Failed to persist sessions: java.io.NotSerializableException at undeploy time

[Scott Marlow]

http://pastie.org/9075691 shows what we are using and that we do have 
"<persistent-sessions path="persistent-web-sessions" 
relative-to="jboss.server.data.dir"/>"

On 04/12/2014 03:15 PM, Jason Greene wrote:
> It looks like it does:
>
>                  <persistent-sessions path="persistent-web-sessions" relative-to="jboss.server.data.dir"/>
>
> We should pull that out. It’s a development feature, and it’s reliant on everything that is put in the session is serializable which is not strictly required. It’s odd though why it would intermittently fail. It should be deterministic.
>
> On Apr 12, 2014, at 2:11 PM, Jason Greene <jason.greene at redhat.com> wrote:
>
>> Does the TCK config have this in it, under the undertow servlet section?:
>>
>>   <persistent-sessions/>
>>
>>
>> On Apr 12, 2014, at 2:06 PM, Scott Marlow <smarlow at redhat.com> wrote:
>>
>>> I'm running some tests with WildFly 8.0.1 master branch and seeing an
>>> intermittent failure.  Any ideas why http://pastie.org/9075646 might be
>>> occurring?  I see a number of these errors during an EJB test.  It is
>>> possible that this error is expected, I'm not sure.
>>>
>>> Scott
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>> --
>> Jason T. Greene
>> WildFly Lead / JBoss EAP Platform Architect
>> JBoss, a division of Red Hat
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>