In Resin 4 seems to use Hessian for
serializing the session values.
This causes some trouble for us since Hessian in some cases tries to
access uninitialized Hibernate collections after the session/transaction
is closed.
Is there a way to revert Resin 4 to the old behaviour...?
--
___
On Aug 26, 2009, at 8:37 AM, Mattias Jiderhamn wrote:
> In Resin 4 seems to use Hessian for
> serializing the session values.
> This causes some trouble for us since Hessian in some cases tries to
> access uninitialized Hibernate collections after the session/
> transaction
> is closed.
> Is th
I am trying to investigate why some of the requests from users are ending up on
2
different app-tier servers during the course of the session.
I turned on fine logging for com.caucho.servlets.HmuxLoadBalanceServlet on the
load
balancer and noticed these errors in the logs.
What could cause th
You put Hibernate objects into the session?
jon
On Wed, Aug 26, 2009 at 8:37 AM, Mattias Jiderhamn <
mj-li...@expertsystems.se> wrote:
> In Resin 4 seems to use Hessian for
> serializing the session values.
> This causes some trouble for us since Hessian in some cases tries to
> access uninitial
Hi,
Is it really so that nobody uses JSPs and SecurityManager with Resin?
:) Could this problem be solved by pre-compiling jsps to Java classes?
Now we just let Resin handle the compilation from directories under
WEB-INF.
Cheers,
Kai
2009/8/25 Kai Virkki :
> Hi!
>
> We are trying to use Securit