Bugs item #583619, was opened at 2002-07-19 04:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=583619&group_id=22866
Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Wont Fix Priority: 5 Submitted By: Russell Black (rblack) Assigned to: Nobody/Anonymous (nobody) Summary: invalid LOC header (bad signature) Initial Comment: With JBoss-3.0.0 / Jetty, when hot-deploying a new war over an existing one, an "invalid LOC header (bad signature)" error occurs, with a stack trace that looks something like this 2002-07-17 14:52:00,050 ERROR [org.jboss.deployment.MainDeployer] could not start deployment: njar:file:/C:/jboss3/server/default/tmp/deploy/server/defaul t/deploy/macausms.ear/59.macausms.ear^/macausms.w ar java.lang.InternalError: jzentry == 0, jzfile = 7857776, total = 37, name = C:\WINDOWS\TEMP\Jetty__80_sendsms_eric- chow_com__\webapp\WEB-INF\lib\macausms-web.jar, i = 33, message = invalid LOC header (bad signature) at java.util.zip.ZipFile$2.nextElement(ZipFile.java:303) at java.util.jar.JarFile$1.nextElement(JarFile.java:200) at org.apache.jasper.compiler.TldLocationsCache.tldConfigJ ar(TldLocationsCache.java:234) ... This error is consistenly reproducable. For more details and steps to reproduce, see http://jboss.org/forums/thread.jsp? forum=52&thread=17978 ---------------------------------------------------------------------- Comment By: Rickard �berg (rickardoberg) Date: 2003-01-07 07:43 Message: Logged In: YES user_id=28931 Are there any plans to fix this? Until it is, JBoss hot deploy is just broken. For development I'd guess most people who have large apps use exploded EAR's/WAR's, and this bug happens all the time, so a reboot is needed whenever an update is made. It's just really bad. For production it is also convenient to use exploded EAR's since it allows easy patching instead of having to replace the entire EAR (which in our case is getting pretty large). ---------------------------------------------------------------------- Comment By: Scott M Stark (starksm) Date: 2002-07-26 21:21 Message: Logged In: YES user_id=175228 This will happen if the update is not done as an atomic operation and the deployer thread tries to read the incompletely updated war. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=583619&group_id=22866 ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
