RE: HistoryRelatedAssignmentManager with cache disabled problem

Hi Sasa,

I didn't find your answer.
I was hoping to try it with shark 1.1, but I've haven't gotten around to it.
Glad to ear that it should be fixed.

I was in fact passing the SharkTransaction parameter.

Thanks,
João Nelas

-----Original Message-----
From: Sasa Bojanic [mailto:[email protected]] 
Sent: quarta-feira, 22 de Junho de 2005 14:00
To: [email protected]
Subject: Re: [shark] HistoryRelatedAssignmentManager with cache disabled problem

Hi,

as I explained, it didn't work without shark LRU caches in previous versions of shark (before February this year), but now it should work.
Also, it could be that in your AssignmentManager you didn't call shark's method with SharkTransaction parameter (the one you get as an input parameter of AssignmetManager's method.

Regards,
Sasa.

----- Original Message -----
From: "João Nelas" <[email protected]>
To: <[email protected]>
Sent: Tuesday, June 21, 2005 4:46 PM
Subject: RE: [shark] HistoryRelatedAssignmentManager with cache disabled problem


Hi Jean!

I've encountered a similar problem, on an AssignmentManager I've written.
It seems that the Activity hasn't been persisted by the time that getAssignments is called, so when you get to line 1330 in SharkUtilities :

1329:      WfActivityInternal act=SharkUtilities.getActivity(t,procId,actId);
1330:      Activity aDef=SharkUtilities.
             getActivityDefinition(t,
                               act,
                               SharkUtilities.
                                  getWorkflowProcess(act.container(t).package_id(t),
                                                     act.container(t).manager_version(t),
                                                     act.container(t).process_definition_id(t)),
                               act.block_activity(t));

act is null, and a NullPointerException is raised.

I'll bet that if you use the Admin Client to re-evaluate the assigments, you won't see the error.

I'm sorry to say that I haven't been able to find a solution to this problem.
It seems to be a bug.

Does anyone have any pointers?

Thanks,
João Nelas


-----Original Message-----
From: Jean O Angelo [mailto:[email protected]]
Sent: terça-feira, 31 de Maio de 2005 20:53
To: [email protected]
Subject: [shark] HistoryRelatedAssignmentManager with cache disabled problem

Hi All
I am having a problem using
HistoryRelatedAssignmentManager with cache disabled.

When I try to use StandardAssignmentManager implementation with cache disabled:

AssignmentManagerClassName=org.enhydra.shark.assignment.StandardAssignmentManager

#AssignmentManagerClassName=org.enhydra.shark.assignment.HistoryRelatedAssignmentManager
#HistoryRelatedAssignmentManager.username=admin
#HistoryRelatedAssignmentManager.password=enhydra
#HistoryRelatedAssignmentManager.extAttrReassignToOriginalPerformer=ReassignToOriginalPerformer
#HistoryRelatedAssignmentManager.extAttrAssignToPerformerOfActivity=AssignToPerformerOfActivity
#HistoryRelatedAssignmentManager.extAttrDoNotAssignToPerformerOfActivity=DoNotAssignToPerformerOfActivity

#CacheManagerClassName=org.enhydra.shark.caching.LRUCacheMgr

DatabaseManager.defaults.cache.maxCacheSize=0
DatabaseManager.defaults.cache.maxSimpleCacheSize=0
DatabaseManager.defaults.cache.maxComplexCacheSize=0

It works like a charm.


When I try to use HistoryRelatedAssignmentManager with cache enabled:
#AssignmentManagerClassName=org.enhydra.shark.assignment.StandardAssignmentManager

AssignmentManagerClassName=org.enhydra.shark.assignment.HistoryRelatedAssignmentManager
HistoryRelatedAssignmentManager.username=admin
HistoryRelatedAssignmentManager.password=enhydra
HistoryRelatedAssignmentManager.extAttrReassignToOriginalPerformer=ReassignToOriginalPerformer
HistoryRelatedAssignmentManager.extAttrAssignToPerformerOfActivity=AssignToPerformerOfActivity
HistoryRelatedAssignmentManager.extAttrDoNotAssignToPerformerOfActivity=DoNotAssignToPerformerOfActivity

CacheManagerClassName=org.enhydra.shark.caching.LRUCacheMgr

DatabaseManager.defaults.cache.maxCacheSize=100
DatabaseManager.defaults.cache.maxSimpleCacheSize=50
DatabaseManager.defaults.cache.maxComplexCacheSize=25

It works fine too.


But when i try to use HistoryRelatedAssignmentManager with cache disabled:

#AssignmentManagerClassName=org.enhydra.shark.assignment.StandardAssignmentManager

AssignmentManagerClassName=org.enhydra.shark.assignment.HistoryRelatedAssignmentManager
HistoryRelatedAssignmentManager.username=admin
HistoryRelatedAssignmentManager.password=enhydra
HistoryRelatedAssignmentManager.extAttrReassignToOriginalPerformer=ReassignToOriginalPerformer
HistoryRelatedAssignmentManager.extAttrAssignToPerformerOfActivity=AssignToPerformerOfActivity
HistoryRelatedAssignmentManager.extAttrDoNotAssignToPerformerOfActivity=DoNotAssignToPerformerOfActivity

#CacheManagerClassName=org.enhydra.shark.caching.LRUCacheMgr

DatabaseManager.defaults.cache.maxCacheSize=0
DatabaseManager.defaults.cache.maxSimpleCacheSize=0
DatabaseManager.defaults.cache.maxComplexCacheSize=0

I get the following error when I will start some
process:

java.lang.NullPointerException
at
org.enhydra.shark.SharkUtilities.getActivitiesExtendedAttributes(SharkUtilities.java:1330)
at
org.enhydra.shark.AdminMiscImpl.getActivitiesExtendedAttributes(AdminMiscImpl.java:219)
at
org.enhydra.shark.assignment.HistoryRelatedAssignmentManager.getAssignments(HistoryRelatedAssignmentManager.java:107)
at
org.enhydra.shark.SharkUtilities.getAssignments(SharkUtilities.java:870)
at
org.enhydra.shark.WfActivityImpl.createAssignments(WfActivityImpl.java:862)
at
org.enhydra.shark.WfActivityImpl.activate(WfActivityImpl.java:995)
at
org.enhydra.shark.WfProcessImpl.startActivity(WfProcessImpl.java:711)
at
org.enhydra.shark.WfProcessImpl.run(WfProcessImpl.java:588)
at
org.enhydra.shark.WfProcessImpl.start(WfProcessImpl.java:282)
at
org.enhydra.shark.WfProcessWrapper.start(WfProcessWrapper.java:445)

Is this a bug? Thanks in advantage.

Jean O Angelo


__________________________________________________
Converse com seus amigos em tempo real com o Yahoo! Messenger http://br.download.yahoo.com/messenger/





--------------------------------------------------------------------------------


>
> --
> You receive this message as a subscriber of the [email protected] mailing list.
> To unsubscribe: mailto:[email protected]
> For general help: mailto:[email protected]?subject=help
> ObjectWeb mailing lists service home page: 
> http://www.objectweb.org/wws
>

--
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws