Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 aarthi saranya AE (aarthisaranyaA6659)
Aarthi Saranya A

Aarthi Saranya A
US
aarthisaranyaA6659 Member since 2016 1 post
Aarthi Saranya A
Posted: Oct 4, 2017
Last activity: Oct 5, 2017
Posted: 4 Oct 2017 5:34 EDT
Last activity: 5 Oct 2017 16:00 EDT
Closed

weblogic.transaction.internal.TimedOutException

I am seeing this error more frequently no much details present in alert and pega log.Please Suggest

Problem encountered when getting connection for database pegadata: code: 0 SQLState: <none> Message: Transaction BEA1-0EEA8326DD316DB49A03 not active anymore. tx status = Rolled back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 29 seconds BEA1-0EEA8326DD316DB49A03]

To see attachments, please log in.
System Administration

Posted: 7 years ago
Posted: 4 Oct 2017 14:55 EDT
Ankur Das (@nkur.das_GCS) Principal Software Solutions Engineer
Pegasystems Inc.
US

Hi,

The above ERROR message indicates that during processing an active database transaction was unable to get the handle to the active JDBC Connection object to connect to the pegadata schema. Henceforth the transaction was rolledback. Can you confirm and check if there was a database server outage during / around the time when these ERRORs were logged?

Thanks,

Ankur

To see attachments, please log in.

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

Pega Collaboration Center 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