Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
10.14.1.0
-
None
-
None
-
Normal
-
Performance, Seen in production
Description
Hi,
Below is the complete description of the issue,
- Running a java application which creates a good number of connections with derby on the machine X.
- We are running the derby database server on the machine lets say Y.
- We explicitly block the listening of 1527 port of system X traffics on system Y in the network until it thrown connection exception and then again established the network between the two systems.
- After the java application has finished execution we found there are still some connections remained open in derby.
- We can see open connections in derby although we have terminated the java application.
- We have restarted derby to free up these connection.
- Concern here is, how these connection are generated, is these connections are broken /stale connection made during the network reset, if YES then, how to these connection will be auto deleted or handled in derby ?
Attachments
Attachments
Issue Links
- is related to
-
DERBY-6815 Connection timeout
- Open
-
DERBY-3908 Add a mechanism for cancelling runaway transactions.
- Open