The log message is created when
org.apache.catalina.session.setAttribute() is called; a series of
checks is made; none of these emit the Attribute name. This is the one
in question:
if ((manager != null)
&& manager.getDistributable()
&& !isSerializable(value)) {
throw new IllegalArgumentException
(sm.getString("standardSession.setAttribute.iae"));
I don't know how the code could be "shared" here; it's a simple fix,
but one the web team will have to take up.
Isn't the object being bound something your app is doing? What about
using a debugger to set a breakpoint there?
Lloyd
On Oct 27, 2008, at 9:41 PM, Satyajit Tripathi wrote:
> Hi there,
>
> We have created a GlassFish V2 UR2 cluster with two instances on the
> same machine and deployed a JavaEE application. After successful
> login to the app we observed the following Error in the server log
> file
> ______________________________________________
> java.lang.IllegalArgumentException: PWC2788: setAttribute: Non-
> serializable attribute
> ______________________________________________
>
>
> Question is : Is there a way in "GlassFish V2 UR2" to find out the
> name of the Attribute which is causing the issue and is not
> serializable ? We understand that there is a fix incorporated in
> GlassFish V3 which will print the Attribute name. Also, recently
> JLuehe provided a jar file to incoporate in GlassFish V2.1.
>
> Can you please share the code for GlassFish V2 UR2 which will print
> the Attribute name ?
>
> Thanks & regards
> --Satya
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> SATYAJIT TRIPATHI
> ISV Engineering APAC
>
> Sun Microsystems India Private Limited
> Bangalore 560025
> DID : +91 80 66937865
> Mobile: +91 9886019892
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> --------------------------------------------------------------------- To
> unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net For
> additional commands, e-mail: admin-help_at_glassfish.dev.java.net