Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <480E3262.8030905@christopherschultz.net>
Date: Tue, 22 Apr 2008 14:45:54 -0400
From: Christopher Schultz <chris@christopherschultz.net>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: NotSerializableException: StandardSessionFacade
References: <16758759.post@talk.nabble.com>
 <2828B04F0113CD468E6D1D51DF4362A405C80E82@USEA-EXCH2.na.uis.unisys.com>
 <48088A0E.4000802@christopherschultz.net> <16825405.post@talk.nabble.com>
In-Reply-To: <16825405.post@talk.nabble.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Massimo,

MassimoH wrote:
|
| Christopher Schultz-2 wrote:
|> This shouldn't be a fatal error. All Tomcat versions I have used will
|> simply give-up restoring sessions and continue starting up.
|>
|> The OP didn't post the entire stack trace, so it's tough to tell what's
|> really going on. Massimo, can you re-post the stack trace in its
entirety?
|>
|
| This is not a fatal error, however, I'd like to get this resolved. Can I
| simply turn off restoring sessions? That just means that when I
restart the
| server, I lose client web session data, right? That's not a problem.

Yes, you can turn it off. See
http://tomcat.apache.org/tomcat-5.5-doc/config/manager.html

| The full stack trace? It's quite big. Here it is...
|
| - IOException while loading persisted sessions:
| java.io.WriteAbortedException: writing aborted;
| java.io.NotSerializableException:
| org.apache.catalina.session.StandardSessionFacade
| java.io.WriteAbortedException: writing aborted;
| java.io.NotSerializableException:
| org.apache.catalina.session.StandardSessionFacade
|         at
| java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1333)
|         at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)

That's the weirdest stack trace I've ever see. readObject calls
something that throws a WriteAbortedException? Totally weird. I wonder
if you have a class that implements its own read/write methods that
calls the wrong method (read calls write or similar).

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkgOMmIACgkQ9CaO5/Lv0PDAhQCgqPMWQ8hQJ9N2HyBikbS1UQD0
mCQAnA64tSQdsCBQVDykr/mtwFKjxJ2W
=Z/Bg
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org