SA-3266

Summary

Stale database connections visible in SMA

Error Messages

at com.pega.pegarules.data.internal.access.DataSourceManager.getConnection(DataSourceManager.java:318)
at com.pega.pegarules.data.internal.access.DatabaseConnectionImpl.activate(DatabaseConnectionImpl.java:1296)
at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:1302)
at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:969)
at com.pega.pegarules.data.internal.access.ThreadConnectionStoreImpl.getConnection(ThreadConnectionStoreImpl.java:389)
at com.pega.pegarules.data.internal.access.RuleCandidateIterator.init(RuleCandidateIterator.java:160)
at com.pega.pegarules.data.internal.access.RuleCandidateUnfilteredResultSetIterator.<init>(RuleCandidateUnfilteredResultSetIterator.java:112)
at com.pega.pegarules.data.internal.access.RuleResolver.getRuleCandidateIterator(RuleResolver.java:1930)
at com.pega.pegarules.data.internal.access.RuleResolver.lookupFirstLevelCandidates(RuleResolver.java:2085)
at com.pega.pegarules.data.internal.access.RuleResolver.getFirstLevelCandidates(RuleResolver.java:1793)
at com.pega.pegarules.data.internal.access.RuleResolver.getFirstLevelCandidates(RuleResolver.java:1712)

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules.  Database connections not closed properly.

Resolution

This issue is resolved by hotfix item HFix-10302.