[jboss-jira] [JBoss JIRA] Commented: (JBRULES-945) Can't passivate WorkingMemory with JBoss cache because ActivationGroupImpl is not serializable

[Gilles Dubuc (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBRULES-945?page=comments#action_12366773 ] 
            
Gilles Dubuc commented on JBRULES-945:
--------------------------------------

I got some info on IRC that made me understand that the rulebase is needed for the working memory to be deserialized. That explains the exception encountered in my last comment. Regardless of that the original issue of this bug is still true (ActivationGroupImpl preventing the workingmemory from being serialized).

> Can't passivate WorkingMemory with JBoss cache because ActivationGroupImpl is not serializable
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-945
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-945
>             Project: JBoss Rules
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.0.6
>         Environment: JBoss AS 4.2 + JBoss Cache + JBoss Rules 3.0.6
>            Reporter: Gilles Dubuc
>         Assigned To: Mark Proctor
>            Priority: Minor
>
> When attempting to put a WorkingMemory that contains rules relying on activation groups into a TreeCache (which passivates with a JDBC connection), the following happens:
> 16:55:00,925 ERROR [JDBCCacheLoader] Failed to insert node: org.drools.common.ActivationGroupImpl
> java.io.NotSerializableException: org.drools.common.ActivationGroupImpl
> ...
> Surely enough, checking the javadoc (4.0 included) shows that indeed ActivationGroupImpl is not serializable.
> And strangely its "cousin" AgendaGroupImpl is serializable.
> Any particular reason why ActivationGroupImpl is not serializable?
> It prevents us from caching our working memories, we'll have to passivate the rule bases instead, which has a big performance impact on our rule-heavy system. I hope there's an easy fix to that.
> In the meantime, I'll try to simply modify the source code to add "implements Serializable" to that class and see what happens. I'll add findings here.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira