Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

Hi all,

I'm working with terracotta 2.4,
session configurator,
sun java 1.5.11,
Tomcat 5.5 (embedded in terracotta tools).

The session replication are working well but sometimes, throw an strange exception. can someone explain me this exception?

GRAVE: An exception or error occurred in the container during the request processing java.lang.AssertionError: Precondition Failed

(see the attachment for full stack trace)

thanks in advance

aldarana,

Thanks for reporting this problem.

It'd be helpful if you could supply some information to help me reproduce this problem.

Did it happen while running one of the session demo apps included in the kit, or did you import an application using session configurator?

Is there any special sequence of steps to reliably reproduce this?

How frequently does it happen?

Is it just a message in the log file, or you see effects of this error in the browser?

Thanks!

Alex,

Did it happen while running one of the session demo apps included in the kit, or did you import an application using session configurator?

no, just with my application.

Is there any special sequence of steps to reliably reproduce this?

no, all semm to be ok in browser and in my application, but I want to know the meening of this exception. I can't put in production system this exception.

How frequently does it happen?

too much

Is it just a message in the log file, or you see effects of this error in the browser?

there are no visible effects....

My application is built with spring 2.0 (session scope replication),
I have clustered Struts view (module 1.1.0)

no other framework are involved

Thanks in advance
Simone Federici

aldarana wrote:

My application is built with spring 2.0 (session scope replication), I have clustered Struts view (module 1.1.0)

Simone, is your application storing anything into http session outside of Spring's session scoped beans?

I also wonder if you could extract some small subset of your application (probably stuff that is using scoped beans), that would allow to reproduce this issue?

regards,
Eugene