<Jun 21, 2001 11:08:00 PM PDT> <Error> <Management> <IOException
opening applica
tion mydomain:Name=course,Type=Application, loading from path
.\config\mydomain\
applications\course.jar
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:110)
at java.util.jar.JarFile.<init>(JarFile.java:115)
at java.util.jar.JarFile.<init>(JarFile.java:82)
at weblogic.utils.jars.VirtualJarFile.<init>(VirtualJarFile.java:24)
at weblogic.management.mbeans.custom.Application.adminLoad(Application.j
ava:257)
at weblogic.management.mbeans.custom.Application.load(Application.java:2
30)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:562)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
at $Proxy6.load(Unknown Source)
at weblogic.management.mbeans.custom.ApplicationManager.addApplication(A
pplicationManager.java:547)
at weblogic.management.mbeans.custom.ApplicationManager.addApplication(A
pplicationManager.java:504)
at weblogic.management.mbeans.custom.ApplicationManager.poll(Application
Manager.java:428)
at weblogic.management.mbeans.custom.ApplicationManager.poll(Application
Manager.java:380)
at weblogic.management.mbeans.custom.ApplicationManager.update(Applicati
onManager.java:152)
at weblogic.management.mbeans.custom.ApplicationManager$ApplicationPolle
r.run(ApplicationManager.java:643)
>
This happens while you are copying a jar file to the applications diretory,
the poller runs to see if there are any new applications. and the server
detects the new jar file and trys to deploy it. but the jar file has not
finished copying, then you will see the error. by default, the server checks
every 3 seconds, we try 3 times before throwing this exception. you can
ignor this exception, or you can change the checking to something bigger,
then you will have enough time to copy a big jar file.
Thanks
Yu
"topsun" <yt_...@yahoo.com> wrote in message
news:8e287fbb.01081...@posting.google.com...