Kbase P106001: Connection pool is not correctly shared between multiple .NET AppObjects
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  31/01/2006 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.0x
SYMPTOM(s):
Connection pool is not correctly shared between multiple .NET AppObjects
Using session-free connections
A first AppObject is instantiated using a Connection object
A second instantiated AppObject, using this same Connection object, will create a new session pool rather than using the session pool referred by the first AppObject.
This is not reproducible from a Java Open Client
CAUSE:
Bug# 20050526-001
FIX:
Upgrade to OpenEdge 10.1A.
When a session-free AppObject is instantiated using a Connection object, the connection object holds a reference to the session pool.
If another AppObject is created using this same Connection object, the AppObject will use the shared session pool reference rather than creating a new session pool.