You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Janos Cserep <cs...@metaprime.hu> on 2010/07/08 14:09:44 UTC
String not serializable exception coming for interned strings from
Model with JRockit/Weblogic
Hi,
The following seems to be a bug with JRockit or Weblogic, but maybe
someone on this list has seen it before and has a better
workaround/solution.
We have been developing a Wicket application for a government agency
that is going to be used by 15k users. The application will be
deployed on a Weblogic cluster running on JRockit and Red Hat.
We have been experiencing strange "Model object not serializable"
exceptions coming from Model and traced it back to interned (by the
compiler) String objects becoming not serializable after hitting the
server with a few hundred parallel users. Once the exception occurs
for a given String reference it keeps coming consistently for that
reference.
The current workaround is a custom Model class that has an overrided
setObject method which checks the object if it's instanceof
Serializable and if the check fails it sets new String(object) on the
Model. This eliminates the exceptions but would like a better solution
to the problem.
Has anyone seen anything like this?
Thanks and regards,
Janos
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: String not serializable exception coming for interned strings
from Model with JRockit/Weblogic
Posted by Daniel Peters <da...@idealo.de>.
Hello Janos,
i have the excactlty the same problem with Wicket and JRockit R28.
The only way to fix it, was to go back to JRockit R27.
Hopefully they will fix it soon, the new R28.0.1 still has the problem.
A collegue of mine will do a post in the Oracle forums now.
regards
Daniel
On 08.07.2010 14:09, Janos Cserep wrote:
> The following seems to be a bug with JRockit or Weblogic, but maybe
> someone on this list has seen it before and has a better
> workaround/solution.
>
> We have been developing a Wicket application for a government agency
> that is going to be used by 15k users. The application will be
> deployed on a Weblogic cluster running on JRockit and Red Hat.
>
> We have been experiencing strange "Model object not serializable"
> exceptions coming from Model and traced it back to interned (by the
> compiler) String objects becoming not serializable after hitting the
> server with a few hundred parallel users. Once the exception occurs
> for a given String reference it keeps coming consistently for that
> reference.
>
> The current workaround is a custom Model class that has an overrided
> setObject method which checks the object if it's instanceof
> Serializable and if the check fails it sets new String(object) on the
> Model. This eliminates the exceptions but would like a better solution
> to the problem.
>
> Has anyone seen anything like this?
>
> Thanks and regards,
>
> Janos
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
--
Daniel Peters
Idealo Internet GmbH
Fon +49 30 40301033
Fax +49 30 28598351
Zionskirchstr. 73, 10119 Berlin
Geschäftsführer: Martin Sinner, Dr. Albrecht v. Sonntag HRB 76749
Amtsgericht Berlin-Charlottenburg
USt.-ID: DE813070905
www.idealo.de | www.idealo.at | www.idealo.co.uk | www.idealo.fr
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org