| Anonymous | Login | Signup for a new account | 12-17-2024 08:34 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0001586 | [Resin] | minor | always | 01-24-07 20:53 | 02-12-07 10:15 | ||||
| Reporter | gschemmel | View Status | public | ||||||
| Assigned To | ferg | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | 3.0.22 | ||||||
| Summary | 0001586: Some timeout defaults for ConnectionPool are wrong. | ||||||||
| Description |
Looks like the default values for <max-active-time> and <max-pool-time> are not correct in com.cauch.jca.ConnectionPool (~ 4.16 Days and 16.67 Days, respectively). Here's the relevant code snippet: // time before an idle connection is closed (30s default) private long _maxIdleTime = 30000L; // time before an active connection is closed (6h default) private long _maxActiveTime = 6L * 60000L * 1000L; // time a connection is allowed to be used (24h default) private long _maxPoolTime = 24L * 60000L * 1000L; |
||||||||
| Additional Information | A viable workaround is to override the defaults in web.xml. | ||||||||
| Attached Files | |||||||||
|
|
|||||||||
 Relationships |
|
| There are no notes attached to this issue. |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 01-24-07 20:53 | gschemmel | New Issue | |
| 01-25-07 11:29 | gschemmel | Issue Monitored: gschemmel | |
| 02-12-07 10:15 | ferg | Assigned To | => ferg |
| 02-12-07 10:15 | ferg | Status | new => closed |
| 02-12-07 10:15 | ferg | Resolution | open => fixed |
| 02-12-07 10:15 | ferg | Fixed in Version | => 3.1.1 |
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |  |
