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

Timer service is not working in development environment

SA-41319

Summary



Flux related issues are observed when the timer service is run in the development environment.


Error Messages



0000003a SystemOut O <Timestamp> <1499682011671> <ERROR> <Thd=CustomObjectsHelper delayed setup thread> <com.chordiant.timer.service.customobjects.TimerCO.setup()> <Flux initilization error <java.lang.NullPointerException> >
0000003a SystemOut O <Timestamp> <1499682011671> <ERROR> <Thd=CustomObjectsHelper delayed setup thread> <com.chordiant.core.customobjects.CustomObjectsHelper.run()> < error on setup of custom object com.chordiant.timer.service.customobjects.TimerCO :Can't initialize flux engine


Steps to Reproduce



Unknown


Root Cause



QRST_Timer.xml file was configured incorrectly in the development environment.

Resolution



Edit the QRST_Timer.xml configuration file; change the timer.persistence property to timer.j2ee.

Published February 16, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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