Hi,
Lately I have started experiencing a weird behavior using jbpm5.4.
Now, if I start a process, the number of instances I get is equal to the id of the process.
What I mean is if the database is clean and I initiate a process, it starts 1 process for me and its id is 1.
If again I start a process, it starts 2 instances and both have ids as 2. Any clue why this is happening?
Logic behind the GUI is correct. Even in the jbpm schema, I can see the same information.
Guys i am still struggling with this issue. Please help. Is tthis a bug?
Maybe a shot in the dark, but are you disposing your ksession?
nope. Not disposing ksession. I have a static ksession object so that I can use the same over and over again. But it might be a reason for the issue I am having. Is there another way you aware of to just clean the session may be and not kill it?
Right, I was thinking you *should* be disposing of the ksession (and maybe this is causing multiple processes to get started). You can keep the KnowledgeBase around, and still dispose the KnowledgeSession.
From the docs:
{noformat}
A knowledge base can be shared across sessions and usually is only created once, at the start of the application (as creating a knowledge base can be rather heavy-weight as it involves parsing and compiling the process definitions). Knowledge bases can be dynamically changed (so you can add or remove processes at runtime).
Sessions can be created based on a knowledge base and are used to execute processes and interact with the engine. You can create as many independent session as you need and creating a session is considered relatively lightweight.
{noformat}
That was some pretty kick ass shooting.. That indeed was the problem. Thanks man.
Lucky, just got lucky this time.
Wow, I think I'll go buy myself a lotto ticket!
Glad to help someone who's been helping others... even if it was just by luck.