| Key: |
JS2-196
|
| Type: |
Improvement
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Legolas Greenleaf
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Windows 2000, JBoss 4.0.1, Jetspeed-2 M1
|
|
| Resolution Date: |
24/Mar/05 08:59 AM
|
|
The deployment of the pam.war fails during start-up, so the war is un-deployed, and a deploy is retried, which also fails. Unless the war file is removed from the file system, this process is iterated infinitely.
The process follows these steps:
1. The ScannerThread detects a new war file in the deploy directory.
2. The Portlet war file is loaded.
3. The Portlet war file is deployed.
4. Error occurs during deployment.
5. The Portlet war file is un-deployed.
6. The Portlet file remains in the deploy dir to be detected when the ScannerThread wakes-up again.
|
|
Description
|
The deployment of the pam.war fails during start-up, so the war is un-deployed, and a deploy is retried, which also fails. Unless the war file is removed from the file system, this process is iterated infinitely.
The process follows these steps:
1. The ScannerThread detects a new war file in the deploy directory.
2. The Portlet war file is loaded.
3. The Portlet war file is deployed.
4. Error occurs during deployment.
5. The Portlet war file is un-deployed.
6. The Portlet file remains in the deploy dir to be detected when the ScannerThread wakes-up again.
|
Show » |
made changes - 24/Mar/05 08:59 AM
| Field |
Original Value |
New Value |
|
Status
|
Open
[ 1
]
|
Closed
[ 6
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
|
Fix Version/s
|
|
2.0-M2
[ 11015
]
|
|
Fix Version/s
|
|
2.0-dev/cvs
[ 10598
]
|
|
Stop trying when hot deployment fails
