Result for 0FA4D510A698823A352213ED6C0408ABBC1BBDE0

Query result

Key Value
FileNamejakarta-commons-dbcp.spec
FileSize14684
MD5C79FDEDA13A5CBEF7CA854DD2426083E
SHA-10FA4D510A698823A352213ED6C0408ABBC1BBDE0
SHA-256E197211DA54ADDD0C71075ECFB382909FBA5A4C9DF8A7D2DCAE48F202C517E80
SSDEEP384:WrskrsT2jq/asEhH6EXwqqnHAHOEjb8WZMoxYwtHBdzDhucVZJRjKro:WTrjqDE1egTjb8WZMoxYwtX//VZb
TLSHT15862F93732C0E537E8C35BC5DA347B406767821B698BF47871ACA744139B589D2BA07B
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD529131C84DB606AF0D095F6F3F0FFE7FB
PackageArchs390x
PackageDescriptionMany 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.
PackageMaintainerFedora Project
PackageNamejakarta-commons-dbcp
PackageRelease12.5.fc11
PackageVersion1.2.1
SHA-1D0D0DEACFC0F61E2611C9D4F6198D4BB2984B3E8
SHA-25690C2BF33FFC4F02E16D9150CE103988C65297D8C5C0C207DA649EC1004565C82