Disabling audit listener / JPAWorkingMemory in jbpm-console 6

[xmrk]

Hello jBPM 6 team.

First, thank you for all your efforts around jBPM 6. I had a big wish-list coming out of my experience with 5.4 and ya'll seem to be well on your to meeting all my high expectations.  Please accept my appreciation.

I'm investigating capabilities to run jbpm-console in a "lean, mean" fashion where I'm sacrificing auditing/recoverability for performance.  I'm looking for some direction on how the ksession is defined and if I can easily configure it to not use a JPAWorkingMemoryDBLogger and not insert the audit-to-database ProcessEventListener.  I was expecting to find a session.template, or something similar.

Please provide some insight into how I can do this.

Regards,

-mark

[swiderski.maciej]

currently there is not way to disable it easily, it's on the road map to be included in next release - sort of deployment descriptors. For now I guess you could make use of async based audit logger that will utilize JMS for it instead of placing info directly into db. It's transactional so it will ensure data consistency.

HTH

[xmrk]

Thanks for the quick response.  It isn't critical functionality, so we can wait for the delivery.  In my spare time I might poke around and see if there is class implementation that can be dropped in thru a war overlay.

Thanks,

-mark

[rjintur]

Hi  swiderski.maciej,

Does the logs from JMS queue eventually go to History DB? Or how and where are they persisted? We are doing Performance and scalability testing of Activti and jBPM. JBPM seems to be taking a lot of time in history logging. So we are planning to try asynchronous history logging using JMS queue for better performance.

Thanks in advance,

Ritu