| Anonymous | Login | Signup for a new account | 11-21-2024 22:31 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0000080 | [Resin] | minor | always | 04-04-05 00:00 | 05-11-05 00:00 | ||||
| Reporter | user62 | View Status | public | ||||||
| Assigned To | |||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | 3.0.12 | ||||||
| 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. |
||||||||
| Additional Information | Windows and OS X, Java 1.4 and 5.0 | ||||||||
| Attached Files | |||||||||
|
|
|||||||||
 Relationships |
|
|
Notes |
|
|
(0000086) ferg 04-04-05 00:00 |
This has been resolved with the deploy refactoring. |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 04-04-05 00:00 | user62 | New Issue | |
| 11-30-05 00:00 | administrator | Fixed in Version | => 3.0.13 |
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
33 total queries executed. 27 unique queries executed. |  |
