Quantcast
Channel:
Viewing all articles
Browse latest Browse all 43869

Wiki Page: What causes java.io.WriteAbortedException thrown at WAR loading after restarting BES?

$
0
0
Problem: Product Name: Borland Enterprise Server Product Version: 5.2.1 Product Component: WebContainer Platform/OS Version: All JDK/Compiler Version: JDK 1.4.1 What causes java.io.WriteAbortedException thrown at WAR loading after restarting BES? Resolution: The exception will occur if classes used in the JSPs and Servlets are not Serializable. These classes may not require being Serializable since they are not sent "over the wire" but will so as a requirement imposed by Tomcat. Please see http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/manager.html#Restart%20Persistence Whenever Catalina is shutdown normally and restarted, or when an application reload is triggered, the standard Manager implementation will attempt to serialize all currently active sessions to a disk file located via the pathname attribute. All such saved sessions will then be deserialized and activated (assuming they have not expired in the mean time) when the application reload is completed. In order to successfully restore the state of session attributes, all such attributes MUST implement the java.io.Serializable interface.

Viewing all articles
Browse latest Browse all 43869

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>