System and method for handling lazy deserialization exceptions in an application server environment

A method for handling lazy deserialization exceptions in an application server environment, comprising:

• providing, at a system comprising one or more computers, including:
• an application server environment that enables deployment and execution of software applications, wherein the application server environment is associated with a domain configuration that is used at runtime to define a domain for execution of the software applications;
• a front end module;
• and
• a server cluster, the server cluster being defined within the domain, the server cluster comprising a plurality of managed servers;
• performing, within the application server environment, a patching process to apply patches to the plurality of managed servers in the server cluster in a controlled manner that maintains operations of the domain without interruption;
• wherein the system is adapted to handle a lazy deserialization exception in the application server environment;
• and
• detecting the lazy deserialization exception upon a client request being directed to a first managed server of the plurality of managed servers in the server cluster, wherein the first managed server of the plurality of managed servers in the server cluster is unable to deserialize a first session state due to a difference in patch state between a server that serialized the first session state and the first managed server of the plurality of managed servers in the server cluster.

A non-transitory computer readable storage medium, including instructions stored for handling lazy deserialization exceptions in an application server environment thereon which when read and executed by one or more computers cause the one or more computers to perform a method comprising:

• providing, at a system comprising one or more computers, including:
• an application server environment that enables deployment and execution of software applications, wherein the application server environment is associated with a domain configuration that is used at runtime to define a domain for execution of the software applications;
• a front end module;
• and
• a server cluster, the server cluster being defined within the domain, the server cluster comprising a plurality of managed servers;
• performing, within the application server environment, a patching process to apply patches to the plurality of managed servers in the server cluster in a controlled manner that maintains operations of the domain without interruption;
• wherein the system is adapted to handle a lazy deserialization exception in the application server environment;
• and
• detecting the lazy deserialization exception upon a client request being directed to a first managed server of the plurality of managed servers in the server cluster, wherein the first managed server of the plurality of managed servers in the server cluster is unable to deserialize a first session state due to a difference in patch state between a server that serialized the first session state and the first managed server of the plurality of managed servers in the server cluster.