[Celerity-users] memory leaks and serialize blockage
jason franklin-stokes
jasoninclass at googlemail.com
Fri Dec 11 03:30:41 EST 2009
aha, Jari, I think i see the problem with serializable, the htmlunit listeners implement serialiazeable so could it be that when a jruby object block has been set to them that they cannot serialize because the block does not impliment serializable?.
On Dec 11, 2009, at 1:55 AM, Jari Bakken wrote:
> On Thu, Dec 10, 2009 at 11:28 PM, jason franklin-stokes
> <jasoninclass at googlemail.com> wrote:
>> Jari,
>>
>> so serialize works when i take @web_client out of the initialize in Listener
>
> I'd be very surprised if that was the case. Are you sure you didn't
> change anything else?
> I tried making the same change and I still get:
>
> org/apache/commons/lang/SerializationUtils.java:111:in `serialize':
> org.apache.commons.lang.SerializationException:
> java.io.NotSerializableException: org.jruby.gen.InterfaceImpl874503039
> (NativeException)
> from org/apache/commons/lang/SerializationUtils.java:133:in `serialize'
> from test.rb:7
>
> Since the JRuby interface implementation is still being added to the
> WebClient, that makes total sense.
> _______________________________________________
> Celerity-users mailing list
> Celerity-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/celerity-users
More information about the Celerity-users
mailing list