Mark Thomas wrote:
> There might be a problem in clustered mode. That will take longer to test
> because I know I don't have a test case ready to go.
To summarise:
Unclustered - As far as I can see, everything works as per the spec
Clustered - This is a little tricky. The spec defines what should
Mark Thomas wrote:
> Jess Holle wrote:
>> I sent the patch quite some time back now, so I'm not sure where it is.
>>
>> Being similarly lazy I'm attaching an excerpt of the patched
>> StandardSession.java (from 5.5.23) with changes embedded in it.
>
> Thanks for that. I checked the archives and th
Jess Holle wrote:
> I sent the patch quite some time back now, so I'm not sure where it is.
>
> Being similarly lazy I'm attaching an excerpt of the patched
> StandardSession.java (from 5.5.23) with changes embedded in it.
Thanks for that. I checked the archives and the patch was e-mailed to dev
I believe similar changes were still necessary in 6.0.14 as well (and
previously were needed in 5.0.30).
Jess Holle wrote:
I sent the patch quite some time back now, so I'm not sure where it is.
Being similarly lazy I'm attaching an excerpt of the patched
StandardSession.java (from 5.5.23) wi
I sent the patch quite some time back now, so I'm not sure where it is.
Being similarly lazy I'm attaching an excerpt of the patched
StandardSession.java (from 5.5.23) with changes embedded in it.
Mark Thomas wrote:
Jess Holle wrote:
The HttpSession activation and passivation listeners in
Jess Holle wrote:
> The HttpSession activation and passivation listeners in Tomcat are
> /quite/ broken -- at least last time I checked.
>
> I've been in the habit of patching this part of the code. I submitted a
> patch once, but I mixed in a few other things that were broken in this
> area and
The HttpSession activation and passivation listeners in Tomcat are
/quite/ broken -- at least last time I checked.
I've been in the habit of patching this part of the code. I submitted a
patch once, but I mixed in a few other things that were broken in this
area and it was not accepted -- and
I had faced the same problem, in order to 'activate' a deserialized
object coming from an other VM the session object has to implement the
HttpSessionBindingListener interface, not the
*HttpSessionActivationListener* .
The valueBound method is invoked by setAttibute's HttpSession method,
inside the
Hello
I am using a tomcat clustered environment using two tomcat 5.5.20
servers in the Windows machine. I am using the in-memory replication for
replicating the session. In my code, I have a session attribute that
implements HttpSessionActivationListener interface. I expect this
Listener to be cal