Nullpointer when calling a subprocess with param and logging
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-24-2011 08:33 AM
Following 3 criteria must be met:
1. Call a subprocess
2. With a parameter
3. With full logging
java.lang.NullPointerException
at org.activiti.engine.impl.history.handler.HistoryParseListener.determineHistoryLevel(HistoryParseListener.java:147)
at org.activiti.engine.impl.history.handler.HistoryParseListener.fullHistoryEnabled(HistoryParseListener.java:135)
at org.activiti.engine.impl.runtime.ExecutionEntity.initializeActivityInstanceId(ExecutionEntity.java:837)
at org.activiti.engine.impl.runtime.VariableScopeImpl.setVariableInstanceValue(VariableScopeImpl.java:193)
at org.activiti.engine.impl.runtime.VariableScopeImpl.createVariableLocal(VariableScopeImpl.java:219)
at org.activiti.engine.impl.runtime.VariableScopeImpl.setVariable(VariableScopeImpl.java:165)
at org.activiti.engine.impl.bpmn.CallActivityBehaviour.execute(CallActivityBehaviour.java:63)
at org.activiti.engine.impl.pvm.runtime.AtomicOperationActivityExecute.execute(AtomicOperationActivityExecute.java:40)
I use the Spring integration.
Whe you lower the logging, you will not get the exception.
I have created a Jira issue that contains all the info with testcase and potential fix !
http://jira.codehaus.org/browse/ACT-647
Best regards,
Tom.
1. Call a subprocess
2. With a parameter
3. With full logging
java.lang.NullPointerException
at org.activiti.engine.impl.history.handler.HistoryParseListener.determineHistoryLevel(HistoryParseListener.java:147)
at org.activiti.engine.impl.history.handler.HistoryParseListener.fullHistoryEnabled(HistoryParseListener.java:135)
at org.activiti.engine.impl.runtime.ExecutionEntity.initializeActivityInstanceId(ExecutionEntity.java:837)
at org.activiti.engine.impl.runtime.VariableScopeImpl.setVariableInstanceValue(VariableScopeImpl.java:193)
at org.activiti.engine.impl.runtime.VariableScopeImpl.createVariableLocal(VariableScopeImpl.java:219)
at org.activiti.engine.impl.runtime.VariableScopeImpl.setVariable(VariableScopeImpl.java:165)
at org.activiti.engine.impl.bpmn.CallActivityBehaviour.execute(CallActivityBehaviour.java:63)
at org.activiti.engine.impl.pvm.runtime.AtomicOperationActivityExecute.execute(AtomicOperationActivityExecute.java:40)
I use the Spring integration.
Whe you lower the logging, you will not get the exception.
I have created a Jira issue that contains all the info with testcase and potential fix !
http://jira.codehaus.org/browse/ACT-647
Best regards,
Tom.
Labels:
- Labels:
-
Archive
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-24-2011 09:00 AM
Hi,
This issue has been fixed by Joram in the beginning of this month, issue will be gone in 5.3
This issue has been fixed by Joram in the beginning of this month, issue will be gone in 5.3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-24-2011 09:09 AM
Ok,
This gave me a good opportunity to look at the code though …
Thanks.
Tom.
This gave me a good opportunity to look at the code though …
Thanks.
Tom.