Question
Huntington Bancshares Inc
US
Last activity: 30 Sep 2015 11:47 EDT
PRPC freeze during 'FinishAssignment' activity call in the flow
Sporadically, PRPC freezes while completing an assignment in a flow. We a custom button to go from one assignment (screen) to the other in the flow. Getting database exceptions inserting to pc_assign_worklist table. As per dynaTrace, it occurs during 'FinishAssignment' activity call.
Below is the dynaTrace info during the freeze:
State: Error Detected: Database Exceptions PRPC
1 × insert into pc_assign_worklist (CASESTATUS , CASETYPE , FIRSTNAME , FUNDINGTYPE , LASTNAME , PXAPPLICATION , PXASSIGNEDOPERATORID , PXASSIGNEDORG , PXASSIGNEDORGDIV , PXASSIGNEDORGUNIT , PXASSIGNEDUSERNAME , PXCREATEDATETIME , PXCREATEOPERATOR , PXCREATEOPNAME , PXCREATESYSTEMID , PXDEADLINEEXECUTE , PXDEADLINETIME , PXFLOWINSKEY , PXFLOWNAME , PXGOALEXECUTE , PXGOALTIME , PXINSNAME , PXLATETIME , PXOBJCLASS , PXREFOBJECTCLASS , PXREFOBJECTINSNAME , PXREFOBJECTKEY , PXREFQUEUEKEY , PXSERVICELEVELNAME , PXTA
Updated: 16 Sep 2015 7:09 EDT
Huntington Bancshares Inc
US
XXXXXXXXXXXXXXXXXXXXXXXXX LOG FILE DETAILS REMOVED XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXHi Chunzhi -
The errors were not logged in the log files except in dynatrace. However, I am sharing the logs. Below is the screenshot of dynatrace error.
**********ESS PARAMS**********
User ID:
Target Action:CIP_SUMMARY
Token :{pr}y7xPdETkK07tVR10+Kv78NW/0EvSurgQMBGrsMPN33aTbiBMdCE+ZmuUvpwISERg
CustPermID:29309671
Products:
ChexID:
RETURN_TARGET_ACTION:
TypeOfCust:
HnbSkillSet:
SoleProprietor:
RecommendationMade:
PyQueryString:
AssignKey:
CustType:
WorkObjectID:
CustTaxID:
AccountPermID:
PRPC_TO_ESS_ENV:ess
OfferCode:
XXXXXXXXXXXXXXXXXXXXXXXXX LOG FILE DETAILS REMOVED XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
**********ESS PARAMS**********
User ID:
Target Action:CIP_SUMMARY
Token :{pr}y7xPdETkK07tVR10+Kv78NW/0EvSurgQMBGrsMPN33aTbiBMdCE+ZmuUvpwISERg
CustPermID:38385544
Products:
ChexID:
RETURN_TARGET_ACTION:
TypeOfCust:
HnbSkillSet:
SoleProprietor:
RecommendationMade:
PyQueryString:
AssignKey:
CustType:
WorkObjectID:
CustTaxID:
AccountPermID:
PRPC_TO_ESS_ENV:ess
OfferCode:
**********ESS PARAMS**********
User ID:
Target Action:CIP_SUMMARY
XXXXXXXXXXXXXXXXXXXXXXXXX LOG FILE DETAILS REMOVED XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXHi Chunzhi -
The errors were not logged in the log files except in dynatrace. However, I am sharing the logs. Below is the screenshot of dynatrace error.
**********ESS PARAMS**********
User ID:
Target Action:CIP_SUMMARY
Token :{pr}y7xPdETkK07tVR10+Kv78NW/0EvSurgQMBGrsMPN33aTbiBMdCE+ZmuUvpwISERg
CustPermID:29309671
Products:
ChexID:
RETURN_TARGET_ACTION:
TypeOfCust:
HnbSkillSet:
SoleProprietor:
RecommendationMade:
PyQueryString:
AssignKey:
CustType:
WorkObjectID:
CustTaxID:
AccountPermID:
PRPC_TO_ESS_ENV:ess
OfferCode:
XXXXXXXXXXXXXXXXXXXXXXXXX LOG FILE DETAILS REMOVED XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
**********ESS PARAMS**********
User ID:
Target Action:CIP_SUMMARY
Token :{pr}y7xPdETkK07tVR10+Kv78NW/0EvSurgQMBGrsMPN33aTbiBMdCE+ZmuUvpwISERg
CustPermID:38385544
Products:
ChexID:
RETURN_TARGET_ACTION:
TypeOfCust:
HnbSkillSet:
SoleProprietor:
RecommendationMade:
PyQueryString:
AssignKey:
CustType:
WorkObjectID:
CustTaxID:
AccountPermID:
PRPC_TO_ESS_ENV:ess
OfferCode:
**********ESS PARAMS**********
User ID:
Target Action:CIP_SUMMARY
Token :{pr}y7xPdETkK07tVR10+Kv78NW/0EvSurgQMBGrsMPN33aTbiBMdCE+ZmuUvpwISERg
CustPermID:38396909
Products:
ChexID:
RETURN_TARGET_ACTION:
TypeOfCust:
HnbSkillSet:
SoleProprietor:
RecommendationMade:
PyQueryString:
AssignKey:
CustType:
WorkObjectID:
CustTaxID:
AccountPermID:
PRPC_TO_ESS_ENV:ess
OfferCode:
XXXXXXXXXXXXXXXXXXXXXXXXX LOG FILE DETAILS REMOVED XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
**********ESS PARAMS**********
User ID:
Target Action:UPDATE_OWNERSHIP
Token :{pr}y7xPdETkK07tVR10+Kv78NW/0EvSurgQMBGrsMPN33aTbiBMdCE+ZmuUvpwISERg
CustPermID:38452527
Products:
ChexID:
RETURN_TARGET_ACTION:
TypeOfCust:215
HnbSkillSet:
SoleProprietor:
RecommendationMade:
PyQueryString:
AssignKey:
CustType:PER
WorkObjectID:
CustTaxID:
AccountPermID:
PRPC_TO_ESS_ENV:ess
OfferCode:
XXXXXXXXXXXXXXXXXXXXXXXXX LOG FILE DETAILS REMOVED XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
**********ESS PARAMS**********
User ID:
Target Action:ADD_SEARCH_CUST
Token :{pr}y7xPdETkK07tVR10+Kv78NW/0EvSurgQMBGrsMPN33aTbiBMdCE+ZmuUvpwISERg
CustPermID:38433312
Products:
ChexID:
RETURN_TARGET_ACTION:UPDATE_OWNERSHIP
TypeOfCust:
HnbSkillSet:
SoleProprietor:
RecommendationMade:
PyQueryString:
AssignKey:ASSIGN-WORKLIST HNB-SS-WORK-ACCOUNT UO-2800203!UPDATEOWNERSHIP
CustType:
WorkObjectID:
CustTaxID:
AccountPermID:
PRPC_TO_ESS_ENV:ess
OfferCode:
XXXXXXXXXXXXXXXXXXXXXXXXX LOG FILE DETAILS REMOVED XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXX LOG FILE DETAILS REMOVED XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Huntington Bancshares Inc
US
Yes, there is a connector at this specific example. However, the issue occurs at other assignments also (when moving from one assignment to the other) sporadically where there are no connectors/utilities.
Pegasystems Inc.
JP
If there is a utility/connector shape between the two assignments and Rollback is called in the activity associated with the utility/connector shape, then there is a chance for insert error with workbasket/worklist table.
The reason is that only one assignment is allowed for each executing flow on a work object.
Usually finish assignment will delete current assignment and create next assignment with in one transaction, however if there is a rollback occur between two assignments, the first assignment will not be deleted hence the second assignment can not be created.
Updated: 1 Sep 2015 0:21 EDT
Pegasystems Inc.
JP
"CIP_SUMMARY" is called 3 times in a row and seems each time there was an "Global error occured while invoking mainframe services". Despite these service call error,
following action: UPDATE_OWNERSHIP, ADD_SEARCH_CUST was executed and there was an insert error happened in execution of ADD_SEARCH_CUST.
It is good to check
Rule_Obj_Activity.BeginViewAndEditCIPActivity.HNB_SS_Work_Customer_CustProfile and
Rule_Obj_Activity.HandleGlobalErrors.HNB_SS_Work_Account_VerifyAndOpen,
to see if Rollback is fired explicitly.
PEG
US
The database issues reported in this post have nothing to do with the problem the user is experiencing. I will be closing the post and reopening another which is focused on the actual problem.