Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0016984 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| design defect | [Openbravo ERP] A. Platform | major | have not tried | 2011-05-03 17:35 | 2012-05-08 16:36 | |||||||
| Reporter | plujan | View Status | public | |||||||||
| Assigned To | marvintm | |||||||||||
| Priority | normal | Resolution | open | Fixed in Version | ||||||||
| Status | scheduled | 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 | pi | 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 | 0016984: Functional flow after a failed build has reached a dead lock | |||||||||||
| Description | I got an error when installing a module (see steps). After that, I receive a warning message on login, but I have no action available. So I can do nothing to get rid of that message using the Openbravo's interface. | |||||||||||
| Steps To Reproduce | 1. Install a module under issue 0016982 conditions 2. Rebuild the system and get the error message. 3. Close the window. Note that most of the window is grayed out, so no action can be taken but logout. Click logout. 4. Log in again. A message is shown (see screenshot) 5. Accept the message and go to Module Management Window. The window shows the IDL as installed, and no action is possible. You cannot uninstall IDL (an error about Local Changes will be shown on rebuild), you cannot restart Tomcat, and you cannot relaunch the failed build. | |||||||||||
| Proposed Solution | It should be a way to brake this deadlock. Either to launch a -Dforce from GUI, or to prevent the login if this situation must be fixed from command line | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files |  SystemUnderMaintenance.PNG [^] (52,332 bytes) 2011-05-03 17:35
| |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2011-05-03 17:35 | plujan | New Issue | |
| 2011-05-03 17:35 | plujan | Assigned To | => marvintm |
| 2011-05-03 17:35 | plujan | File Added: SystemUnderMaintenance.PNG | |
| 2011-05-03 17:35 | plujan | Modules | => Core |
| 2011-05-05 09:09 | alostale | Status | new => scheduled |
| 2012-05-08 16:36 | marvintm | Type | defect => design defect |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |