As far as debugging rules go, I'm no drools expert but I believe you can use org.drools.audit.WorkingMemoryFileLogger to log working memory events to file, which may be helpful for working through issues. It should be a snap to set this up - simply create one when the user logs in: | WorkingMemoryFileLogger log = new WorkingMemoryFileLogger(Identity.instance().getSecurityContext()); | log.setFileName("/my/logfile"); | Then you need to call log.writeToDisk() to flush the logger's "buffer" to disk, or alternatively you can probably call log.setMaxEventsInMemory(0). Please let me know if this is helpful (I haven't tried it myself :). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010783#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...