It's an internal consistency check. Usually it means that a non-value class (a class whose identity, defined by hashCode()/equals(), changes during a run) is being used in an indexed field. Look at this section of the manual and see if you can use it to fix the problem:
http://www.jessrules.com/jess/docs/71/functions.html#set-value-class In the past, very rarely, this message indicated a bug in Jess. I don't think this will be the case here - I think any bugs that trigger this assert were found and fixed long ago. From: owner-jess-us...@sandia.gov [mailto:owner-jess-us...@sandia.gov] On Behalf Of Dwight Hare Sent: Wednesday, May 29, 2013 5:05 PM To: jess-users Subject: JESS: [EXTERNAL] Corrupted Negcnt Error During a run I started getting the error Jess reported an error in routine NodeNot2.tokenMatchesRight while executing rule LHS (Node2) while executing rule LHS (TECT). Message: Corrupted Negcnt (< 0) . Any idea what this means? Dwight
