Bug 742523

Summary: Facts are unavailable in loaded persisted session
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Tomas Schlosser <tschloss>
Component: BRE (Expert, Fusion)Assignee: Nobody <nobody>
Status: ASSIGNED --- QA Contact: Lukáš Petrovický <lpetrovi>
Severity: medium Docs Contact:
Priority: unspecified    
Version: BRMS 5.2.0.GACC: atangrin, kverlaen, lpetrovi, mproctor
Target Milestone: ER6   
Target Release: BRMS 5.3.0.GA   
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tomas Schlosser 2011-09-30 12:46:06 UTC 
Description of problem:
When you insert fact into session and then create a new one, the inserted fact is not available in the newly created session.

Version-Release number of selected component (if applicable):
Windows Server 2003
BRMS-5.2.0-ER5

How reproducible:
- most of the time
- only on W2k3

Steps to Reproduce:
1. created persisted session
2. insert fact into session
3. load the session
  
Actual results:
session.getObject.size() returns 0

Expected results:
session.getObject.size() returns 1 and contains the inserted fact

Additional info:
This bug is hardly reproducible, I haven't find exact configuration to include proper test case.
Comment 2 Edson Tirelli 2012-02-07 01:09:11 UTC 
Tomas, need clarification on this one: are you persisting the session before or after inserting a fact into it?
Comment 3 Tomas Schlosser 2012-02-15 07:42:44 UTC 
I use JPAKnowledgeService to create the persisted sessions. Transactions are handled by Drools as well so I guess the session is persisted upon creation and automatically after inserting the fact.

As said before it only happens on W2k3 server (the tests run on variety of systems and W2k8 server does not have the same problem) and is still present in BRMS 5.3.0 ER3
Comment 4 Edson Tirelli 2012-04-13 16:43:13 UTC 
Tomas, I just pushed a load of fixes to the serialization framework. Unfortunately I don't have access to any W2k3 machine. Can you please check if the problem still happens?

FYI, the last commit that fixes the serialization issues is this:

https://github.com/droolsjbpm/drools/commit/6f80adb3b5395eeac3e37f2840d988924a8fe299

Any build after that commit should work.
Comment 5 Tomas Schlosser 2012-04-17 08:12:02 UTC 
BRMS-5.3.0.ER5 still has this issue, I'll get back to it once ER6 is built.
Comment 6 Ryan Zhang 2012-04-23 07:38:35 UTC 
Update status to ON_QA. Please verify them against ER6.
Comment 7 Tomas Schlosser 2012-05-02 13:40:14 UTC 
Unfortunately, this is still an issue in ER6.