If we use ObjectOutputStream to write the session to disk we can read it back on the same jvm. However, a separate jvm cannot read the file -- we get the same StreamCorruptedException. What could be jvm-specific?
Thank you, Scott On Mon, Mar 24, 2008 at 4:35 PM, Scott Swank <[EMAIL PROTECTED]> wrote: > Using the HttpSessionStore pushes this exception to JBoss. It seems > that something in the session just can't be deserialized by a separate > jvm. > > > > On Mon, Mar 24, 2008 at 3:54 PM, Scott Swank <[EMAIL PROTECTED]> wrote: > > We run JBoss and haven't tried this on other app servers. Could the > > fact that we're running Java 6 be relevant? The specific type code in > > the exception varies each time, and this occurs every time we fail > > over from one node to another. > > > > We have don't a test case, but if you have a JBoss cluster we could > > maybe send you a war. :) > > > > Thank you, > > Scott > > > > > > > > > > On Mon, Mar 24, 2008 at 3:25 PM, Johan Compagner <[EMAIL PROTECTED]> > wrote: > > > Stream corrupt exceptio, invalid type code? > > > It seems that the byte array on that side isnt correct. Do you have a > > > setup/testcase for this? Do you get it on other app servers? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
