Argh, on what planet was I when I wrote the previous message. I can
barely understand it myself... Let me try again... :-)
What happened was that I had a page with an inner class which I used as
an application state object registered in hivemind (and which therefore
went into the http session). However I accidently forgot to make the
inner class static (which means that it will have a reference to an
instance of the page it was constructed in). When I shut down my tomcat
it would try and serialize the session and give me all kinds of
java.io.Serializable exceptions on the page class. It took me a while to
figure out why this was happening as I was certain I wasn't putting the
page in the session and I couldn't figure out how it got there!
Ok, hope that was more understandable, sorry for the last post... :-)
Greetings,
Sebastiaan
Sebastiaan van Erk wrote:
I once had a page in the HttpSession, and it took me a while to figure
out why (since I definately did not put it there explicitly!!!).
Anyway, it turned out that somewhere where I used an inner class for a
something I *did* put in the session, and I had forgotten to make it a
*static* inner class... :-)
Took me a while to figure that one...
Greetings,
Sebastiaan
Sergei Dubov wrote:
Are you actually storing pages in the HttpSession?.. :-) Wow.
-S
RR wrote:
I have an application with multiple pages, all of which implement
Serializable and contain multiple persistent properties. Implementing
the abstract model suggested in TIA, all of these pages are also
abstract and thus "enhanced" on-the-fly. Upon testing the application
in a clustered Tomcat 5.0.30 environment, I'm witnessing:
12:24:43,788 ERROR
org.apache.catalina.cluster.tcp.TcpReplicationThread[2]
[Delt
aManager]
Unable to receive message through TCP channel
java.lang.ClassNotFoundException:
org.test.pages.organizations.OrgInfo$Enhan
ce_63
So my question is, are abstract pages with persistent-properties
really clusterable?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
