[
http://jira.jboss.com/jira/browse/JBAS-3215?page=comments#action_12363503 ]
David Richmond commented on JBAS-3215:
--------------------------------------
I would off thought this problem, although mundane, would be fairly high on the to do
list. I mean, EJB, Seam, JBossTS etc are all worthless if you cannot deploy your
application reliably.
I would love to help, but my team leader has just left the company, I have 6 projects on
the go, and upgrading from JBoss 4.0.5 to 4.2.0 is proving to be a real pain in the
*&*% - and that just the stuff going on at work ;-)
Dave
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=108746
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=109361
Add 'grace period' to deployment scanner between finding a
new/changed deployment and actually deploying it
-----------------------------------------------------------------------------------------------------------
Key: JBAS-3215
URL:
http://jira.jboss.com/jira/browse/JBAS-3215
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: System service
Affects Versions: JBossAS-4.0.3 SP1, JBossAS-4.0.4.CR2
Environment: jboss-4.0.3SP1 and jboss-4.0.4CR2 on Windows 2000 server using JVM
1.5.04
WAR file is built on JDK 1.5.04 using the ANT 1.6.5 WAR task
Reporter: David Richmond
Assigned To: Dimitris Andreadis
To avoid unpredictable "org.jboss.deployment.DeploymentException: Unexpected end of
ZLIB input stream" exceptions could a grace period (delay) be added to the JBoss
deployment deployer. This delay should be applied as follows:
1. Scanner finds new deployments
2. WAIT for grace period
3. Scanner deploys new deployments
Setting the grace-period to 0 would emulate the current JBoss behaviour
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira