Agent processing fails in the destination server
You have a scheduled agent that runs and fetches data from the source database and then places it in the destination server as a file.
The file is generated in the right place, but contains no data, and there are related errors in the logs.
There was a problem committing a transaction on database PegaRULES 0 Connection is not associated with a managed your_ser[email protected]527e6f35
Caused by SQL Problems.
Problem #1, SQLState null, Error code 0: java.sql.SQLException: Connection is not associated with a managed your_server[email protected]6f35
Steps to Reproduce
The root cause of this problem is defect or misconfiguration in the operating environment.
As per the error message, jdbc connection that was given to Pega application is stale. There is no information in the activity rule execution about the failure.
This issue is resolved by making the following change to the operating environment:
- Enable the pre-test jdbc connection feature at JBOSS data source level using ‘<check-valid-connection-sql>’.
- Add an additional diagnostic by the application to understand the stages of the agent processing.
Note: While processing this activity, add steps that write status of the processing. For instance, if the filter criteria for the data being collected, collect information like "how many records collected for this run and whether successfully completed the task or not".
These information helps if the problem reoccurs in the future.
Published November 6, 2015 - 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.