[jboss-jira] [JBoss JIRA] Updated: (JBRULES-2487) NPE on line 69 of ConcurrentNodeMemories.java when calling JPAKnowledgeService.loadStatefulKnowledgeSession

[Geoffrey De Smet (JIRA)]

     [ https://issues.jboss.org/browse/JBRULES-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey De Smet updated JBRULES-2487:
--------------------------------------

    Fix Version/s: 5.2.0.CR2
                       (was: 5.2.0.CR1)


> NPE on line 69 of ConcurrentNodeMemories.java when calling JPAKnowledgeService.loadStatefulKnowledgeSession
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-2487
>                 URL: https://issues.jboss.org/browse/JBRULES-2487
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: JBoss 4.2.3, Java 6 64-bit, Windows Vista 64-bit
>            Reporter: hoogenbj
>            Assignee: Edson Tirelli
>            Priority: Blocker
>             Fix For: 5.2.0.CR2
>
>
> Hi,
> I get a NullPointerException on line 69 of ConcurrentNodeMemories when calling JPAKnowledgeService.loadStatefulKnowledgeSession(...) in order to complete a work item using session.getWorkItemManager().completeWorkItem(...).
> Further investigation reveals that the objectType on line 332 of InputMarshaller refers to one of my objects that I passed as part of the second argument object when calling startProcess on the knowledge session that I got with JPAKnowledgeService.newStatefulKnowledgeSession. The objectTypeNode on line 333 of InputMarshaller is null which eventually causes the NPE in ConcurrentNodeMemories.
> This error does not occurr when starting and completing the whole process without retrieving the session from the database. Which seems to indicate that something is not persisted or correctly retrieved from the database.
> This is a serious problem for us. It means we have to find an alternative for Drools flow...

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira