|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 80 | minor | always | 04-04-05 00:00 | 05-11-05 00:00 | |
|
|
|||||
| Reporter: | user62 | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.0.12 | ||
| Product Build: | 3.0.12 | Resolution: | fixed | ||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.0.13 | ||
|
|
|||||
| Summary: | 0000080: Continuous redeploy after deployment failure | ||||
| Description: |
RSN-71 If I have an EAR and I make some mistake in the deployment, such as missing JMS queues for MDBs, the deployer keeps trying to deploy over and over. This causes a lot of stack traces to go flying by on the console and the only way to get a look at them is to stop the server and look at the log. The deployer should stop after the failure and only redeploy once something important changes (i.e. application.xml, ear file gets a new timestamp, etc). In it's current state, it's very annoying and I know Resin didn't used to have this behavior. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | Windows and OS X, Java 1.4 and 5.0 | ||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||