|
Mantis - Resin
|
|
Viewing Issue Advanced Details |
|
|
ID:
|
Category:
|
Severity:
|
Reproducibility:
|
Date Submitted:
|
Last Update:
|
|
1707 |
|
crash |
always |
04-25-07 15:23 |
05-01-07 16:57 |
|
|
Reporter:
|
wilsonpenha |
Platform:
|
|
|
|
Assigned To:
|
ferg |
OS:
|
|
|
|
Priority:
|
normal |
OS Version:
|
|
|
|
Status:
|
closed |
Product Version:
|
3.1.0 |
|
|
Product Build:
|
|
Resolution:
|
fixed |
|
|
Projection:
|
none |
|
|
|
|
ETA:
|
none |
Fixed in Version:
|
3.1.1 |
|
|
|
Summary:
|
0001707: Closing dangling connections. All connections must have a close() in a finally block. |
|
Description:
|
Since the versions 3.0.x/3.1.x, it has became a very grave issue, today most of persistence framework has your own ConnectionPool manager with a customized and trackable way to do DB Connections, with this finally block crap has became a very odd style, doesn't allow the app to encapsulate the getonnection methods, one big example of this is one transaction block where we get the same session DB connection by passing the session ID and getting one remain connection with some transaction opened for more hits,
So please take off this finally crap or put one property allowing to us to configure this thing.
|
|
Steps To Reproduce:
|
|
|
Additional Information:
|
This finally crap is for beginners, we won't be slave of this, I do prefer to move to another container, and as you well know has other mush better than Resin,
I'm using this at this moment because my customer ask me for, but I you won't to fix this finally crap, we really will move to Tomcat or Jboss or something else
|
| Relationships | |
|
Attached Files:
|
|