Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | |||||||||||
| 0003907 | |||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
| feature request | [Java Client POS] (No Category) | minor | always | 2006-10-16 13:12 | 2008-10-07 11:56 | ||||||
| Reporter | user71 | View Status | public | ||||||||
| Assigned To | user71 | ||||||||||
| Priority | normal | Resolution | open | Fixed in Version | |||||||
| Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
| Projection | none | ETA | none | Target Version | |||||||
| OS | Any | Database | Any | Java version | |||||||
| OS Version | Database version | Ant version | |||||||||
| Product Version | SCM revision | ||||||||||
| Regression date | |||||||||||
| Regression introduced by commit | |||||||||||
| Regression level | |||||||||||
| Review Assigned To | |||||||||||
| OBNetwork customer | No | ||||||||||
| Support ticket | |||||||||||
| Regression introduced in release | |||||||||||
| Summary | 0003907: handle database reconnections | ||||||||||
| Description | Currently when the database connection is dropped for some reason, tinapos fails with a error. To get everything working again, tinapos has to be restarted. This is a big problem when deploying tinapos over wan/vpn links as connections do drop, in some cases many times a day. To fix this, tinapos should detect connection drops & try to reconnect, possibly failing after certain number of tries or after a prespecified timeout. Adrian has suggested other fixes to this problem, as using HA jdbc drivers, but in my opinion this would complicate tinapos deployment to a degree that is not suitable. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
Notes |
|
|
(0007463) user71 2007-02-07 01:54 edited on: 2008-06-12 10:08 |
Logged In: YES user_id=421591 Originator: NO adrian, what about a reconnect method in the "catch {}" section or something like try { blah blah } catch (databaseexecption e) { if !(db.isconnected()); //checks for connections db.connect(); //if not, then connect } It should be easy to implement this... |
|
(0007631) user71 2005-06-01 00:00 edited on: 2008-06-12 10:12 |
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis. You can see the original bug report in: https://sourceforge.net/support/tracker.php?aid=1578072 [^] |
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2008-10-07 11:56 | adrianromero | Status | new => acknowledged |
| 2012-11-07 09:40 | priyam | Category | 01 - General => (No Category) |
| Copyright © 2000 - 2009 MantisBT Group |