We are using JBpm 3.1.1 on a big insurance application. We are having memory problems. After using a profiler we have seen that for some reason all our actionHandlers(delegations) do not clean from memory. Since these actions are basically stateless it strikes me as odd.
When a process is running it creates actionHandlers, these handlers don't clean up after the process has ended, they just stay in memory for ever.
Before I start dumping information here please advice...
Hmm... I'm not a real specialist on the deep dark dungeons of jBPM, but the first thing that comes to mind is 'hibernate cache'... not sure why but my initial thought was that the components in that cache could hold a handle to acrionhandlers.
I'd be interested in information though. If you could put it up on a site somewhere I'll have a look.