Bug 833140 - Explain jbpmSessionId.ser file
Explain jbpmSessionId.ser file
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: doc-BRMS_Business_Process_Management_Guide (Show other bugs)
BRMS 5.3.0.GA
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: lcarlon
Jiri Locker
Depends On:
  Show dependency treegraph
Reported: 2012-06-18 13:18 EDT by Jiri Locker
Modified: 2012-08-06 16:47 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-08-06 16:47:16 EDT
Type: Task
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jiri Locker 2012-06-18 13:18:34 EDT
Description of problem:
The file is used by Business Central to store session ID of the most recently used persisted session. If the file doesn't exist a new session is created and the ID is stored in that file. If the file exists, the ID is read and the session is loaded from database. This way the session can be reloaded after server restart.

The file is stored in jboss-as/server/${profile}/tmp directory by default and the location can be changed by setting jbpm.console.tmp.dir property in jbpm.console.properties file inside busines-central-server.war

Version-Release number of selected component (if applicable):
Comment 1 lcarlon 2012-06-18 20:24:47 EDT
Hi Jiri,

I've updated the Console chapter to include the jbpm.console.tmp.dir property among those listed in jbpm.console.properties.

In the persistence chapter under the Configuring Persistence section I have added a small section 'session ID'

Thanks Jiri
Comment 3 lcarlon 2012-08-06 16:47:16 EDT
I'm closing the bug as the issue has been verified.

Note You need to log in before you can comment on or make changes to this bug.