Interesting... I would say that this is NOT a @propertyReactive issue, since you say that the CCE is thrown even with 1 or 2 properties. I do wonder how could @propertyReactive mitigate the exception, though.. could you provide more details on your environment? i.e. Drools version, how you build the knowledge base (KnowledgeAgent? Serialization?), the full stack of the CCE, etc... We had similar issues in the past, and usually it was due to some problem with the configuration of the KnowledgeBase classloader
The 5.6 release process is supposed to start today/tomorrow, so if there is a bug, you have a VERY SHORT time frame to help us understand what is going wrong. Thanks Davide On 10/14/2013 06:22 PM, richie wrote: > Thanks Mario. > > The fact and properties are generated from object in our system, it may > reach the limitation cause the fields of object may be larger than 64. > > If propertyreactive is disabled, when fire the rule, it will throw > ClassCastException: class a.b can not be cast to a.b, it's very strange > cause it's same class. > > If I remove the @propertyreactive in drl file, even amount of properties is > less than 64, such as only 1 or 2, it will throw the ClassCastException too, > not sure why this would happen. > > > > -- > View this message in context: > http://drools.46999.n3.nabble.com/Why-disable-properyreactive-if-amount-of-properties-larger-than-or-equals-to-64-tp4026359p4026365.html > Sent from the Drools: User forum mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users > _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
