Catastrophic initialization failure! Shutting down null WAB

RE: Catastrophic initialization failure! Shutting down null WAB

2018-10-05T00:01:15Z

Are you sure it's not the servletContextRegistrationHelper that is null?

If you go into gogo, does your module show as active?

If it does, if you use "scr:list ###" where ### is your bundle id, do all of the components show as active?

I'm wondering if what you are seeing is not really a failure of code as much as it is a failure of a component resulting from, say, an unsatisfied reference of some kind.

RE: Catastrophic initialization failure! Shutting down null WAB

2018-10-04T13:04:51Z

David H Nebinger:

The NPE points at the specific line of code you need to check, use the source code for your exact version of DXP (plus fix pack) and see what is going on: com.liferay.portal.osgi.web.wab.extender.internal.WabBundleProcessor.initContext(WabBundleProcessor.java:445)

David,

This is the same error even I am getting for one of my Spring module migrated to DXP from 6.2.

At the line number 445: we have the below code and I see this is trying to find web.xml file in the current WAB which I have it in that location.

https://github.com/liferay/com-liferay-portal-osgi-web/blob/78f4a986327f6d36d1899895cfe4a4d7a355ef89/portal-osgi-web-wab-extender/src/main/java/com/liferay/portal/osgi/web/wab/extender/internal/WabBundleProcessor.java#L445

RE: Catastrophic initialization failure! Shutting down null WAB

2018-10-04T12:24:24Z

The NPE points at the specific line of code you need to check, use the source code for your exact version of DXP (plus fix pack) and see what is going on: com.liferay.portal.osgi.web.wab.extender.internal.WabBundleProcessor.initContext(WabBundleProcessor.java:445)

RE: Catastrophic initialization failure! Shutting down null WAB

2018-10-04T03:20:20Z

David H Nebinger:

What version of Liferay? Have you checked that line of code? It should point to whatever it is trying to read from your WAR, so it should give you an idea of what isn't right with it...

Thanks David for your quick reply.

We are on Liferay 7.0 DXP.

Which line of code should I look into? I did not get that. could you please point me to the right place.

Regards,

Sai

RE: Catastrophic initialization failure! Shutting down null WAB

2018-10-03T09:29:50Z

What version of Liferay? Have you checked that line of code? It should point to whatever it is trying to read from your WAR, so it should give you an idea of what isn't right with it...

Catastrophic initialization failure! Shutting down null WAB

2018-10-03T04:21:32Z

Im getting below exception after deployment

ERROR [fileinstall-C:/workspaces/downloads/liferay7-sp8/osgi/war][com_liferay_portal_osgi_web_wab_extender:97] Catastrophic initialization failure! Shutting down null WAB due to: null
java.lang.NullPointerException
   at com.liferay.portal.osgi.web.wab.extender.internal.WabBundleProcessor.initContext(WabBundleProcessor.java:445)
   at com.liferay.portal.osgi.web.wab.extender.internal.WabBundleProcessor.init(WabBundleProcessor.java:132)
   at com.liferay.portal.osgi.web.wab.extender.internal.WebBundleDeployer._initWabBundle(WebBundleDeployer.java:186)
   at com.liferay.portal.osgi.web.wab.extender.internal.WebBundleDeployer.doStart(WebBundleDeployer.java:106)
   at com.liferay.portal.osgi.web.wab.extender.internal.WabFactory$WABExtension.start(WabFactory.java:158)
   at org.apache.felix.utils.extender.AbstractExtender.createExtension(AbstractExtender.java:259)
   at org.apache.felix.utils.extender.AbstractExtender.modifiedBundle(AbstractExtender.java:232)
   at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:482)
   at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:1)
   at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:232)
   at org.osgi.util.tracker.BundleTracker$Tracked.bundleChanged(BundleTracker.java:444)
   at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:905)
   at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
   at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
   at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:165)
   at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:75)
   at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:67)
   at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:102)
   at org.eclipse.osgi.container.Module.publishEvent(Module.java:461)
   at org.eclipse.osgi.container.Module.start(Module.java:452)
   at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:402)
   at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1258)
   at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1230)
   at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:512)
   at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:361)
   at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:312)