AnsweredAssumed Answered

Getting NPE while retrieving bytearray value 

Question asked by sukhveer on Sep 8, 2013
Latest reply on Sep 13, 2013 by trademak
Hi,
This exception is a show stopper for me at the moment. Need to fix this asap, i am using activiti 5.10 and not possible to upgrade it at the moment. I looked around and found that it was fixed in  version 5.0. Maybe something else is causing it.
Here is my stack trace :

Caused by: java.lang.NullPointerException
   at org.activiti.engine.impl.variable.ByteArrayType.getValue(ByteArrayType.java:37)
   at org.activiti.engine.impl.variable.SerializableType.getValue(SerializableType.java:44)
   at org.activiti.engine.impl.persistence.entity.VariableInstanceEntity.getValue(VariableInstanceEntity.java:158)
   at org.activiti.engine.impl.persistence.entity.VariableScopeImpl.getVariable(VariableScopeImpl.java:93)
   at org.activiti.engine.impl.persistence.entity.VariableScopeImpl.getVariable(VariableScopeImpl.java:97)
   at org.activiti.engine.impl.el.VariableScopeElResolver.getValue(VariableScopeElResolver.java:65)
   at org.activiti.engine.impl.javax.el.CompositeELResolver.getValue(CompositeELResolver.java:231)
   at org.activiti.engine.impl.juel.AstIdentifier.eval(AstIdentifier.java:81)
   at org.activiti.engine.impl.juel.AstParameters.eval(AstParameters.java:34)
   at org.activiti.engine.impl.juel.AstMethod.invoke(AstMethod.java:88)
   at org.activiti.engine.impl.juel.AstMethod.eval(AstMethod.java:75)
   at org.activiti.engine.impl.juel.AstEval.eval(AstEval.java:50)
   at org.activiti.engine.impl.juel.AstNode.getValue(AstNode.java:26)
   at org.activiti.engine.impl.juel.TreeValueExpression.getValue(TreeValueExpression.java:114)
   at org.activiti.engine.impl.delegate.ExpressionGetInvocation.invoke(ExpressionGetInvocation.java:33)
   at org.activiti.engine.impl.delegate.DelegateInvocation.proceed(DelegateInvocation.java:37)
   at org.activiti.engine.impl.delegate.DefaultDelegateInterceptor.handleInvocation(DefaultDelegateInterceptor.java:25)

I can get byteArray value using SQL query ao it is definitely not null.
Also it is not happening all the time. Most of the time it appears after production build, means for workflows that are in process while we redeploy war on production machine workflow stops working.
Please suggest me some solution asap.

Thanks in Advance.

Outcomes