Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Issue with batch job which creates multiple users

SA-4680

Summary



There is an issue being reported in production with a batch job for creating multiple user accounts at the same time. The job is giving error with message “Role not found in database for name: callcenteragent”. This behavior has been observed after the cache value was changed from 10000 to 20000

Error Messages



Role not found in database for name: callcenteragent


Steps to Reproduce



There is an issue being reported in production with a batch job for creating multiple Trio user accounts at the same time. The job is erroring out with message “Role not found in database for name: callcenteragent”. This behaviour has been observed after the cache value was changed from 10000 to 20000


Root Cause



The root cause of this problem is a defect in production environment setting wherein cache size was not updated in a particular JVM where the batch job was run. Cache size for DefaultCache region had to be updated in all the JVMs.



Resolution



The root cause of this problem is defect/misconfiguration in the custom environment. DefaultCache region value was updated(from 10000 to 20000) in the JVM to resolve this issue.
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us