Hybris 6.4升级至6.7后WCMS无法渲染及组件异常排查求助

What’s Going On #

You’ve upgraded your B2B site to Hybris 6.7, copied over your config and custom folders, migrated data/media, and got the server up—but now WCMS is completely broken. Homepage components won’t load, you’re hitting a NullPointerException about missing extension info, and even though your database has CMSNavigationNodes, Backoffice doesn’t show any WCMS nodes. Let’s fix this.

First, let’s recap the critical error stack trace for context:

WARN [hybrisHTTP37] [DefaultCMSComponentRendererRegistry] Error processing component tag. currentComponent [TKNavigationBarComponentModel (8796148630588@1)] exception: Missing extension info for given extension name
Dec 30, 2019 11:12:31 AM org.apache.catalina.core.ApplicationDispatcher invoke
SEVERE: Servlet.service() for servlet [DispatcherServlet] threw exception
java.lang.NullPointerException: Missing extension info for given extension name
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:805)
at com.thyssenkrupp.b2b.global.baseshop.storefront.filters.AcceleratorAddOnFilter$DefaultExtensionAccessor.getInfo(AcceleratorAddOnFilter.java:272)
at com.thyssenkrupp.b2b.global.baseshop.storefront.filters.AcceleratorAddOnFilter$DefaultExtensionAccessor.getExtensionDir(AcceleratorAddOnFilter.java:267)
at com.thyssenkrupp.b2b.global.baseshop.storefront.filters.AcceleratorAddOnFilter$ResourceAddOnResolver.getExtensionPath(AcceleratorAddOnFilter.java:113)
at com.thyssenkrupp.b2b.global.baseshop.storefront.filters.AcceleratorAddOnFilter$ExecutableResourceAddOnResolver.getAddOnFullPathName(AcceleratorAddOnFilter.java:160)
at com.thyssenkrupp.b2b.global.baseshop.storefront.filters.AcceleratorAddOnFilter.doFilter(AcceleratorAddOnFilter.java:61)

Troubleshooting Steps to Try #

1. Fix Extension Compatibility & Activation

That Missing extension info error is the smoking gun. It means somewhere in your setup, a component or AddOn is referencing an extension that’s either not loaded, incompatible with 6.7, or misconfigured.

• Check extension versions: Your 6.4 custom/third-party extensions might not play nice with 6.7. Rebuild all custom extensions against 6.7 libraries, and verify that any third-party extensions have 6.7-compatible releases.
• Verify extension loading: Run ant all -verbose and scan the logs for warnings about missing extensions or dependency issues. If an extension fails to load, fix its extensioninfo.xml or dependencies first.
• Recheck AddOn setup: Since the error comes from AcceleratorAddOnFilter, double-check your AddOns:
  • Make sure all AddOns listed in localextensions.xml are properly installed with ant addoninstall—Hybris 6.7 changed some AddOn installation workflows from 6.4, so a direct copy might not cut it.
  • Look at project.properties for addonConfiguration entries—typos in extension names here will cause this exact error.

2. Reinitialize WCMS & Backoffice

Even if your database has CMSNavigationNodes, the Backoffice WCMS UI might be missing because the system update didn’t fully set up WCMS components for 6.7.

• Run a targeted system update: Go to HAC → Update, select all WCMS-related extensions (like cms2, cmsbackoffice, and your custom WCMS extensions), check Update running system and Create essential data, then run the update. This will refresh WCMS metadata that might have been skipped during your initial upgrade.
• Reset Backoffice config: If WCMS nodes still don’t show up in Backoffice:
  • Head to Backoffice → System → Backoffice Configuration → Reset to Default (backup any custom Backoffice config first!).
  • Confirm cmsbackoffice is in localextensions.xml and built successfully—without it, WCMS won’t appear in Backoffice.

3. Clean Up WCMS Component References

The error mentions TKNavigationBarComponentModel—this custom component is likely pointing to an extension that no longer exists in your 6.7 environment.

• Query the component: Use HAC’s Flexible Search to run:

  SELECT {pk}, {uid}, {extensionName} FROM {TKNavigationBarComponentModel}
  

  Check if the extensionName value is an extension that’s not in your localextensions.xml anymore.
• Fix the reference: If you find an invalid extension name, update it via Flexible Search (or Backoffice once WCMS is accessible) to point to a valid extension in your 6.7 setup.
• Resync WCMS data: Make sure all WCMS components and media were migrated correctly. If you’re able to do so safely, run ant initialize (note: this will wipe existing data, so only do this in a non-production environment) or use Hybris’s data migration tools to re-sync WCMS items.

4. Validate Accelerator Filter Setup

The AcceleratorAddOnFilter is throwing the NPE, so let’s check its configuration:

• Review web.xml: Ensure the filter is configured correctly in your storefront’s web.xml. Hybris 6.7 updated some filter parameters compared to 6.4, so a direct copy of your old web.xml might have invalid settings.
• Check extension directories: Make sure all custom extensions are in hybris/bin/custom and have valid extensioninfo.xml files—no typos in extension names here, as the filter uses this file to resolve extension paths.

Pro Tips for Hybris 6.7 Upgrades #

Hybris 6.7 made significant changes to WCMS and Accelerator components, so don’t assume copying over your 6.4 config and custom folders will work seamlessly. Always refer to the official Hybris 6.7 upgrade guide for extension-specific migration steps, especially for custom WCMS components and AddOns.

内容的提问来源于stack exchange，提问作者ADIT