(from Mathias Scharl)
The ConversationManager uses a DUMMY variable set to new Integer(-1). Later in the code this DUMMY is used to check for an invalid conversation id. Unfortunately this check is done via == instead of equals, which works most of the time, but after re-starting an application in tomcat (session is passivated), the DUMMY object is not the same anymore and the check does not work as expected. The solution is to use equals instead of ==.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|8m 56s||1||Jakob Korherr||14/Jul/11 17:21|
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Fix Version/s||1.5 [ 12314460 ]|
|Resolution||Duplicate [ 3 ]|