Thanks for the great tip. By making it transient everything works.
Regards.
On Mon, 2004-01-05 at 18:55, Michael Nash JGlobal.com wrote:
Santanu: If it's private, you should just be able to mark it transient - that'll skip it in serialization and we won't need any other changes (theoretically!) :-) Mike On Mon, 5 Jan 2004 18:28:01 -0500 (EST) Santanu Dutt <[EMAIL PROTECTED]> wrote: > Mike, > It's getting set in the DefaultUserEnvironment to obtain the Subject. It's defined as a private variable in the class and as a result I guess the whole class is not Serializable. I have worked around by setting the Subject directly on the DefaultUserEnvironment from AbstractAuthenticationManager. I agree with you that the LoginContext is not needed at all in the ComparableContext. I had to make changes in some classes for this and have not yet checked the stuff in. I will do some more testing and let you know. In the mean time please let me know if you find the need for setting LoginContext in Keel context anywhere. Anyway we cannot do it and if needed we have to figure a workaround. > Thanks and Regards. > Santanu > > On Jan 05, 2004 06:07 PM, Michael Nash JGlobal.com <[EMAIL PROTECTED]> wrote: > > > Santanu: > > > > I'm not at all sure why the LoginContext needs to be in there - and I don't immediately see where it's being added....but I'll keep digging! > > > > Mike > > > > On Mon, 5 Jan 2004 16:13:29 -0500 (EST) > > Santanu Dutt <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > Sorry to post this again. Did not have the right heading previously.... > > > I just got all the latest modules from CVS for openjms-struts deployment. Ran ANT to deploy and had no problem. Tried to run the app and got this error on the jms front. > > > java.io.NotSerializableException: javax.security.auth.login.LoginContext > > > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054) > > > at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332) > > > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304) > > > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247) > > > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) > > > > > > Obviously when KeelAbstractServer is trying to synchronize the context by posting the JMS event it is failing because javax.security.auth.login.LoginContext is not serializable. This was working before fine. Somehow now the AbstractAuthenticationManager is setting the LoginContext in Keel UserEnvironment and this breaks keel in distributed environment. I need to fix this. Please let me know if LoginContext is required in the Keel Context. Thanks. > > > > > > Santanu Dutt > > > Senior Consultant > > > Platinumsolutions Inc. > > > ph:703-471-9793 ext 203 > > > fax:703-471-7140 > > > email:[EMAIL PROTECTED] > > > web:www.platinumsolutions.com > > > > > > > > > Michael Nash > > > > JGlobal Ltd > > Next-Generation Web Application Development and Open Source Support > > http://www.jglobal.com > > > > Bahamas Commerce and Trade > > Offshore eCommerce Hosting and Business Services > > http://www.bahamascommerce.com > > > > Santanu Dutt > Senior Consultant > Platinumsolutions Inc. > ph:703-471-9793 ext 203 > fax:703-471-7140 > email:[EMAIL PROTECTED] > web:www.platinumsolutions.com > Michael Nash JGlobal Ltd Next-Generation Web Application Development and Open Source Support http://www.jglobal.com Bahamas Commerce and Trade Offshore eCommerce Hosting and Business Services http://www.bahamascommerce.com
