Question
DXC Technology
BE
Last activity: 17 May 2018 1:02 EDT
Obj-Open-By-Handle on a common class by two activities
Dear,
I am explaining the scenario based on my question.
There are two activities which use a common class say A-B-C.
Activity1 uses object open by handle on a data page called Page1 of A-B-C. This activity is triggered by an Agent1 which runs every 5 secs.
Acitivity2 also uses object open by handle on a data page called Page2 of A-B-C. This activity is triggered by an Agent2 which runs every 60 secs.
Both object open by handle use lock and ROC (release on commit) features.
Though the data pages are named differently in both activities, will this cause a problem in activity2 if activity1 already is having a lock on pzinskey.
I have a similar issue causing heap space and server crash. Investigating this and needs your precious inputs.
thanks,
Jagan
Pegasystems Inc.
US
Only one requestor would be able to have a lock on the work object at a time. If Agent1 has the lock, then an error will occur when Agent2 attempts to obtain a lock.
Pegasystems Inc.
IN
DXC Technology
BE
Activity1 which runs every 5 secs is doing following :
Iterates on the pxResults of a pageX created with class A-B-C
using Obj open by handle in a step of pageY of same class A-B-C to open the record
Its sets a property value .Old = true
Does an obj-save.
After exiting the loop, sets property .Pro='No'
goes on to do more steps, calls another Activity234 and returns
Then does a Commit.
Activity2 which runs every 60 secs does the following:
Opens a new pageV of class A-B-C
Does an obj-browse on pageV to filter the pzinskey with condition .Pro='No' & .Old=null
Iterates on the result of pageV.pxResult
Create a page-new of pageV2 of class A-B-C (no parameters set)
Does obj-open-by-handle on pageV2 with instance handle as pzinskey. Lock and ROC selected.
This is the place where the issue happened and logs show that it got stuck.
---------------------
What is confusing for me is, in Activity1, the parameter .Old was set to true and .Pro was set to No. When Acitivity2 runs, it browses for .Old as null, but still some how got the same pzinskey.
How is this possible.
Hope the details are clear for you to answer. Let me know if any thing is not clear.
Activity1 which runs every 5 secs is doing following :
Iterates on the pxResults of a pageX created with class A-B-C
using Obj open by handle in a step of pageY of same class A-B-C to open the record
Its sets a property value .Old = true
Does an obj-save.
After exiting the loop, sets property .Pro='No'
goes on to do more steps, calls another Activity234 and returns
Then does a Commit.
Activity2 which runs every 60 secs does the following:
Opens a new pageV of class A-B-C
Does an obj-browse on pageV to filter the pzinskey with condition .Pro='No' & .Old=null
Iterates on the result of pageV.pxResult
Create a page-new of pageV2 of class A-B-C (no parameters set)
Does obj-open-by-handle on pageV2 with instance handle as pzinskey. Lock and ROC selected.
This is the place where the issue happened and logs show that it got stuck.
---------------------
What is confusing for me is, in Activity1, the parameter .Old was set to true and .Pro was set to No. When Acitivity2 runs, it browses for .Old as null, but still some how got the same pzinskey.
How is this possible.
Hope the details are clear for you to answer. Let me know if any thing is not clear.
Pegasystems Inc.
IN
Could you try obj-save with write now option enabled. So that the property change is committed immediately.
After setting .Pro='No', is there an obj-save operation, if not .pro value wouldn't be persisted.