potential db connection leak when no default kernel/ramdisk id is not set
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Eucalyptus |
Fix Released
|
Undecided
|
chris grzegorczyk | ||
| eucalyptus (Ubuntu) |
Fix Released
|
High
|
Dustin Kirkland | ||
Bug Description
When no kernel or ramdisk is listed as the default, by being set in the web interface, each attempt to load the system configuration may leak database connections. The is manifested in the log files as a message to the effect of "remove connection because it has problems: age is XXXXX ms. connection marked for expiry but the last SQL it performed is unknown because the trace property is not enabled."
One way to trigger this is to run multiple clients (16+) at the same time which will result:
16:49:22 [TxHandle:New I/O server worker #1-3] ERROR javax.persisten
...
Caused by: java.sql.
| summary: |
- potential db connection leak when no default kernel/ramdisk id is set + potential db connection leak when no default kernel/ramdisk id is not + set |
| chris grzegorczyk (chris-grze) wrote | #1 |
| Changed in eucalyptus: | |
| assignee: | nobody → chris grzegorczyk (chris-grze) |
| status: | New → In Progress |
| status: | In Progress → Fix Committed |
| Changed in eucalyptus (Ubuntu): | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Dustin Kirkland (kirkland) |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in eucalyptus (Ubuntu): | |
| status: | In Progress → Fix Released |
| Changed in eucalyptus: | |
| status: | Fix Committed → Fix Released |
-------
revno: 1209 [merge]
committer: decker <decker@hawaii>
branch nick: 1.6.2
timestamp: Mon 2010-03-08 23:01:52 -0800
message:
fix LP: #534877 prevent corner case db conn. leak
-------