Many Jakarta projects support interaction with a relational
database. Creating a new connection for each user can be time
consuming (often requiring multiple seconds of clock time),
in order to perform a database transaction that might take
milliseconds. Opening a connection per user can be unfeasible
in a publicly-hosted Internet application where the number of
simultaneous users can be very large. Accordingly, developers
often wish to share a "pool" of open connections between all
of the application's current users. The number of users actually
performing a request at any given time is usually a very small
percentage of the total number of active users, and during
request processing is the only time that a database connection
is required. The application itself logs into the DBMS, and
handles any user account issues internally.
* Bug Fix
- Fix compatibility with JDK 7
Update packages.
N/A
SRPMS
- jakarta-commons-dbcp-1.2.1-13.9.AXS4.src.rpm
MD5: ba7e9c29e389465635bceb414fd333d3
SHA-256: 8d42fca944d8e4a7a8078529ce372e25afe1a50ea8a473ce1adf67cc327060a3
Size: 720.08 kB
Asianux Server 4 for x86
- jakarta-commons-dbcp-1.2.1-13.9.AXS4.noarch.rpm
MD5: 70ea9371a160de09e0efbaea276b66d5
SHA-256: 96771292dc5c34d91bfb347514eaa13c22b5f71124902d96aa305c8d749eb684
Size: 117.38 kB - jakarta-commons-dbcp-tomcat5-1.2.1-13.9.AXS4.noarch.rpm
MD5: 68e555076dcc2e73bfd095d7e76fa5f3
SHA-256: d723cf6226ebd5703bb913d8d92fe5ec2f867f7f5129d917b3f3933ad93c85d3
Size: 109.03 kB
Asianux Server 4 for x86_64
- jakarta-commons-dbcp-1.2.1-13.9.AXS4.noarch.rpm
MD5: 52422e32be52c47cc47b5f9bd8d8aa7c
SHA-256: dd740992ec1ac91f1feff6cc54c05f83f80cc0ff1ac2c4e7575b87ded7b7855e
Size: 116.93 kB - jakarta-commons-dbcp-tomcat5-1.2.1-13.9.AXS4.noarch.rpm
MD5: 9454831ab85926ae7443452c7eda7e6e
SHA-256: e4e41c9422167a381ba881f4bd5219ee645cc35cda9c021d7ac477b5d99463fe
Size: 108.57 kB