NAM 5.1 IdP Fails to Start After Pushing Advanced File Configurator Files

Upgraded a NAM 5.0 SP4 environment to NAM 5.1 and then immediately applied patch 5.1.0.1, which supposedly fixes the Advanced Configurator issues with NAM 5.1.

Went into NAM Admin console after upgrade, I could see the advanced file configurator files now, they don't disappear like they did with NAM 5.1 shipping, so I figured it was fixed.

Pick all files and folders and push them out to the IdP cluster.

Clicked Update on the cluster.

It restarted tomcat and now the IdP won't start.  I see this error in the Catalina.out:

SEVERE: Error deploying web application directory [/opt/novell/nam/idp/webapps/nidp]
java.lang.IllegalStateException: Error starting child
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:686)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:658)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:661)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1175)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1888)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1086)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:470)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1584)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:312)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:114)
at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:345)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:893)
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:794)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:171)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1332)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1322)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:866)
at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:248)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:171)
at org.apache.catalina.core.StandardService.startInternal(StandardService.java:433)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:171)
at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:925)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:171)
at org.apache.catalina.startup.Catalina.start(Catalina.java:735)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:345)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:473)
Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.JarResourceSet@13dae445]
at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:419)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:130)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:161)
at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:725)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:171)
at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4575)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4708)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:171)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:683)
... 37 more
Caused by: java.lang.IllegalArgumentException: java.util.zip.ZipException: error in opening zip file
at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:141)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:127)
... 44 more
Caused by: 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:236)
at java.util.zip.ZipFile.<init>(ZipFile.java:162)
at java.util.jar.JarFile.<init>(JarFile.java:171)
at java.util.jar.JarFile.<init>(JarFile.java:135)
at org.apache.tomcat.util.compat.JreCompat.jarFileNewInstance(JreCompat.java:290)
at org.apache.tomcat.util.compat.JreCompat.jarFileNewInstance(JreCompat.java:275)
at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:138)
... 45 more

Upon looking back in the Advanced File Configurator, it looks like anything that was a Folder (which is a ZIP files) did not deploy correctly.  I tried to delete/remove/untrack the folder, but the IdP will no longer start.  I'm guessing the zip files were either corrupted by the upgrade or not deployed correctly.  But now I cannot get the IdP started.

Anyone know any work around to get the IdP started?  How exactly does the Adv. File Configurator deploy the files?  Is it stored in the device store maybe?  I cannot find them.

Apparently this is still NOT fixed, so beware if upgrading to NAM 5.1.

I think NAM 5.1 has been the worst release of NAM I've ever seen, I'd strongly advise against upgrading to it.

Matt

 

  • Verified Answer

    +1  

    I figured out the issue.  I had a custom auth class jar file in the Adv. File Configurator.  The upgrade to NAM 5.1 (even with the 5.1.0.1 patch) corrupts anything that is zipped in the advanced file configurator (regular text files are fine).  So when I deployed all the files, that custom jar file was deployed into the nidp lib directory and was causing the failure on tomcat startup.

    Easy fix, but took a while to find.

    Pretty disappointing that the Adv. File Configurator STILL gets screwed up on an upgrade even with the fix that was supposed to fix it.

    Matt