Openbravo Issue Tracking System - Java Client POS | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0003907 | Java Client POS | (No Category) | public | 2006-10-16 13:12 | 2008-10-07 11:56 |
| Reporter | user71 | ||||
| Assigned To | user71 | ||||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | acknowledged | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Regression date | |||||
| Regression introduced by commit | |||||
| Regression level | |||||
| Review Assigned To | |||||
| OBNetwork customer | |||||
| 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. | ||||
| Steps To Reproduce | |||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| 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) | ||
| Notes | |||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||