Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0015339 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| feature request | [Openbravo ERP] A. Platform | minor | sometimes | 2010-12-01 11:55 | 2022-02-01 08:08 | |||||||
| Reporter | alostale | View Status | public | |||||||||
| Assigned To | Triage Platform Base | |||||||||||
| Priority | urgent | Resolution | open | Fixed in Version | ||||||||
| Status | scheduled | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Oracle | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | SCM revision | |||||||||||
| Review Assigned To | ||||||||||||
| Web browser | ||||||||||||
| Modules | Core | |||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0015339: Unexpected errors after database user password expiration | |||||||||||
| Description | When expires Openbravo database user password, new DB connection cannot be created. As consequence of this, existent connections in connection pool can be reused but in case a new connection is required, an error is raised. The failures the user can see from that moment can be different, typically it can be logged out of his session. | |||||||||||
| Steps To Reproduce | -Start Openbravo -Change Openbravo database user password -Try to operate the application When the error happens it can be identified in Openbravo log but the user is not properly informed about this. | |||||||||||
| Proposed Solution | To solve this issue, it is needed to reset the password. You can find instructions to do so here: http://wiki.openbravo.com/wiki/Openbravo_SMB_Network_One_Administrator's_Manual_2.40#Database_password_expiration [^] This situation should be notified to the user in a clean way. Possible communications could be: -System alert -Login failure -Community branding -... | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2010-12-01 11:55 | alostale | New Issue | |
| 2010-12-01 11:55 | alostale | Assigned To | => alostale |
| 2010-12-01 11:55 | alostale | Modules | => Core |
| 2010-12-01 11:56 | alostale | Proposed Solution updated | |
| 2010-12-01 11:57 | alostale | Steps to Reproduce Updated | View Revisions |
| 2010-12-03 08:26 | alostale | Proposed Solution updated | |
| 2010-12-06 07:46 | alostale | Status | new => scheduled |
| 2012-02-28 13:22 | alostale | Type | defect => feature request |
| 2017-04-10 14:37 | alostale | Assigned To | alostale => platform |
| 2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |