How to Install and Uninstall apache-commons-dbcp.noarch Package on Amazon Linux 2
Last updated: November 24,2024
1. Install "apache-commons-dbcp.noarch" package
This is a short guide on how to install apache-commons-dbcp.noarch on Amazon Linux 2
$
sudo yum makecache
Copied
$
sudo yum install
apache-commons-dbcp.noarch
Copied
2. Uninstall "apache-commons-dbcp.noarch" package
This is a short guide on how to uninstall apache-commons-dbcp.noarch on Amazon Linux 2:
$
sudo yum remove
apache-commons-dbcp.noarch
Copied
$
sudo yum autoremove
Copied
3. Information about the apache-commons-dbcp.noarch package on Amazon Linux 2
Loaded plugins: ovl, priorities
Available Packages
Name : apache-commons-dbcp
Arch : noarch
Version : 1.4
Release : 17.amzn2
Size : 167 k
Repo : amzn2-core/2/x86_64
Summary : Apache Commons DataBase Pooling Package
URL : http://commons.apache.org/dbcp/
License : ASL 2.0
Description : Many Apache 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.
Available Packages
Name : apache-commons-dbcp
Arch : noarch
Version : 1.4
Release : 17.amzn2
Size : 167 k
Repo : amzn2-core/2/x86_64
Summary : Apache Commons DataBase Pooling Package
URL : http://commons.apache.org/dbcp/
License : ASL 2.0
Description : Many Apache 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.