|
Re: Login not working for specific Roles [message #742715 is a reply to message #742712] |
Thu, 20 October 2011 19:04 |
Vikram Kodak Messages: 72 Registered: October 2011 |
Member |
|
|
We think ag.carnot.workflow.runtime.utils.AuthorizationContext.setActivityDataWithScopePi(AuthorizationContext.java:270)
is already sending in a null value.
That would be:
public void setActivityDataWithScopePi(long scopeProcessInstanceOid, long activityRtOid,
long modelOid, long currentPerformer, long currentUserPerformer, long department){
ModelManager mm = getModelManager();
setModelElementData(mm.findActivity(modelOid, activityRtOid));
...........
If the ModelManager could not find an Activity for the specified modelOid + activityRtOid then this would explain the NPE.
To find the culprit, you could set a break point and check the values of the method parameters.
public void setActivityDataWithScopePi(long scopeProcessInstanceOid, long activityRtOid,
long modelOid, long currentPerformer, long currentUserPerformer, long department)
Then you can use these values to check the consistency of your database.
We can expect same behaviour if for some reason the modelCache was not in sync with the audit trail.
A server restart would refresh the cache and solve the issue.
The inconsistency between model information and audit trail runtime information could be caused by a (invalid) model overwrite. If you removed an activity from the model and overwrote the model afterwards, then the audit trail could still contain runtime information which does not have a matching activity in the latest model. In that case you could overwrite the model again with the old version and the redeploy the new version without overwriting.
Alternatively you can archive/cleanup the invalid audit trail runtime information.
[Updated on: Fri, 21 October 2011 04:18] Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.03610 seconds