000011680 - Corrupted deployment files

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000011680
Applies ToSecurID Appliance 3.0.4
Issue<BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean operations-console. Error - weblogic.management.DeploymentException: .weblogic.management.DeploymentException:
java.util.zip.ZipException: Error opening file - /usr/local/RSASecurity/RSAAuthenticationManager/components/oc/wars/operations-console.war Message - Could not find End Of Central Directory
Cause

Due to an power failure a disk corruption occured and after a restart the Operations Console could not be accessed, reviewing the log file of the startup (./imsoc/servers/AdminServer/logs/AdminServer.log these errors are seen:

####<Aug 14, 2012 11:49:51 AM EST> <Error> <Deployer> <rhea.csau.ap.rsa.net> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1344908991768> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean operations-console. Error - weblogic.management.DeploymentException: .
weblogic.management.DeploymentException:
        at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:69)
        at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
        at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
        at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
        at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:90)
        at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)

and

java.util.zip.ZipException: Error opening file - /usr/local/RSASecurity/RSAAuthenticationManager/components/oc/wars/operations-console.war Message - Could not find End Of Central Directory
        at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:76)
        at weblogic.servlet.utils.WarUtils.isWebServices(WarUtils.java:65)
        at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:61)
        at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
        at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
        at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
        at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:90)
        at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)

This is confirmed by testing the integrity of the WAR deployment file as follows:

-bash-3.00$ appserver/jdk/bin/jar -tvf components/oc/wars/operations-console.war
. . .
1748720 Fri Jun 22 05:21:12 EST 2012 WEB-INF/lib/groovy-all-1.0-jsr-05.jar
 14599 Fri Jun 22 05:21:12 EST 2012 WEB-INF/lib/hsqldb-logdb-init.jar
 72589 Fri Jun 22 05:21:12 EST 2012 WEB-INF/lib/iScreen-1-1-0rsa-2.jar
 14318 Fri Jun 22 05:21:12 EST 2012 WEB-INF/lib/iScreen-ognl-1-1-0rsa-2.jar
 21511 Fri Jun 22 05:21:12 EST 2012 WEB-INF/lib/ims-gen-replica-pkg.jar
java.io.EOFException: Unexpected end of ZLIB input stream
        at java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:216)
        at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:134)
        at java.util.zip.ZipInputStream.read(ZipInputStream.java:146)
        at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:98)
        at sun.tools.jar.Main.list(Main.java:743)
        at sun.tools.jar.Main.run(Main.java:191)
        at sun.tools.jar.Main.main(Main.java:903)

This confirms that the file has become corrupted and needs to be replaced 

ResolutionObtain a copy of the same file from another machine (running at the same patch level) and overwrite the corrupted file. If the system has been patched then recent patch procedures store copies of the updated WAR files in the ./upgrades folder so this is also a valid location to obtain an uncorrupted file (use the same test procedure with the jar command to confirm this file is valid)
Legacy Article IDa59394

Attachments

    Outcomes