• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

[JSF2] Warning message during redeploy

 
Ranch Hand
Posts: 107
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I got WEB0517 during redeploy my web applcation
Description of WEB0517 follows here:


WEB0517 Unable to restore sessions for web module [{0}] from previous deployment

Cause:
An HTTP session that was supposed to survive the redeployment of the web module failed to be restored (deserialized). This can happen if an application class that was used as a session attribute has changed incompatibly

Solution:
Make sure that any application classes that are being used as session attributes change only in a compatible way during redeployments



However, this warning invokes even if I didn't modified any of the session-scoped bean
Moreover, the exception should be 'InvalidClassException', not 'NullPointerException' if I changed the session-scoped bean incompatible way.

I use Glassfish v3 and bundled JSF library.

Server log follows here:


 
Saloon Keeper
Posts: 27764
196
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Your exception occurred in JBoss Weld, so you'd probably be better off asking in a JBoss forum.

Platform-specific considerations aside, one problem that often occurs when restoring sessions comes from when a Session object incorporates a non-serialiable object. For example, if I was foolish enough to attempt to store a JDBC Connection in a backing bean.
 
Bupjae Lee
Ranch Hand
Posts: 107
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for reply.

First, I'm not using JBoss; I'm using Glassfish v3, and it seems that there are no Glassfish forum

Since I'm using JSF, I checked all of @SessionScoped bean classes' fields, and it doesn't seem I have non-serializable object

 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic