As part of the process to patch our environments, we usually start deploying SAP Commerce On-Prem in a local computer (not a server), and last time we were able to successfully start Hybris (hybrisserver.bat) we applied the 2205.25 package. Now we are trying to move to 2205.31 and we are seeing issues related to what I believe is a solr configuration problem. Does anyone know if we are missing something?
This a portion of the logs, thank you!
Caused by: java.lang.NullPointerException: Cannot invoke "de.hybris.platform.solrfacetsearch.model.config.SolrServerConfigModel.getName()" because "source" is null
INFO | jvm 1 | main | 2024/12/02 14:04:50.903 | at de.hybris.platform.solrfacetsearch.converters.populator.DefaultSolrServerConfigPopulator.populate(DefaultSolrServerConfigPopulator.java:42)
INFO | jvm 1 | main | 2024/12/02 14:04:50.904 | at de.hybris.platform.solrfacetsearch.converters.populator.DefaultSolrServerConfigPopulator.populate(DefaultSolrServerConfigPopulator.java:33)
INFO | jvm 1 | main | 2024/12/02 14:04:50.904 | at com.spareparts.core.converters.GACAbstractPopulatingConverter.populate(GACAbstractPopulatingConverter.java:33)
INFO | jvm 1 | main | 2024/12/02 14:04:50.904 | at de.hybris.platform.converters.impl.AbstractConverter.convert(AbstractConverter.java:34)
INFO | jvm 1 | main | 2024/12/02 14:04:50.904 | at de.hybris.platform.solrfacetsearch.converters.populator.DefaultIndexConfigPopulator.getSolrConfigFromItems(DefaultIndexConfigPopulator.java:135)
INFO | jvm 1 | main | 2024/12/02 14:04:50.905 | at de.hybris.platform.solrfacetsearch.converters.populator.DefaultIndexConfigPopulator.populate(DefaultIndexConfigPopulator.java:46)
INFO | jvm 1 | main | 2024/12/02 14:04:50.905 | at de.hybris.platform.solrfacetsearch.converters.populator.DefaultIndexConfigPopulator.populate(DefaultIndexConfigPopulator.java:34)
INFO | jvm 1 | main | 2024/12/02 14:04:50.905 | at com.spareparts.core.converters.GACAbstractPopulatingConverter.populate(GACAbstractPopulatingConverter.java:33)
INFO | jvm 1 | main | 2024/12/02 14:04:50.905 | at de.hybris.platform.converters.impl.AbstractConverter.convert(AbstractConverter.java:34)
INFO | jvm 1 | main | 2024/12/02 14:04:50.905 | at de.hybris.platform.solrfacetsearch.converters.populator.DefaultFacetSearchConfigPopulator.getIndexConfigFromItems(DefaultFacetSearchConfigPopulator.java:53)
INFO | jvm 1 | main | 2024/12/02 14:04:50.905 | at de.hybris.platform.solrfacetsearch.converters.populator.DefaultFacetSearchConfigPopulator.populate(DefaultFacetSearchConfigPopulator.java:30)
INFO | jvm 1 | main | 2024/12/02 14:04:50.905 | ... 56 more
INFO | jvm 1 | main | 2024/12/02 14:04:50.905 |
INFO | jvm 1 | main | 2024/12/02 14:04:50.905 | Dec 02, 2024 2:04:50 PM org.apache.catalina.core.StandardContext startInternal
INFO | jvm 1 | main | 2024/12/02 14:04:50.905 | SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file
INFO | jvm 1 | main | 2024/12/02 14:04:50.905 | Dec 02, 2024 2:04:50 PM org.apache.catalina.core.StandardContext startInternal
INFO | jvm 1 | main | 2024/12/02 14:04:50.906 | SEVERE: Context [/backoffice] startup failed due to previous errors
INFO | jvm 1 | main | 2024/12/02 14:04:52.279 | Dec 02, 2024 2:04:52 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesObjectStreamClassCaches
INFO | jvm 1 | main | 2024/12/02 14:04:52.283 | WARNING: When running on Java 9 or later you need to add "--add-opens=java.base/java.io=ALL-UNNAMED" to the JVM command line arguments to enable ObjectStream cache memory leak protection. Alternatively, you can suppress this warning by disabling ObjectStream class cache memory leak protection.
INFO | jvm 1 | main | 2024/12/02 14:04:52.302 | Dec 02, 2024 2:04:52 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesRmiTargets
INFO | jvm 1 | main | 2024/12/02 14:04:52.302 | WARNING: When running on Java 9 or later you need to add "--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED" to the JVM command line arguments to enable RMI Target memory leak detection. Alternatively, you can suppress this warning by disabling RMI Target memory leak detection.
INFO | jvm 1 | main | 2024/12/02 14:04:52.318 | Dec 02, 2024 2:04:52 PM org.apache.coyote.AbstractProtocol start
INFO | jvm 1 | main | 2024/12/02 14:04:52.319 | INFO: Starting ProtocolHandler ["http-nio-9001"]
INFO | jvm 1 | main | 2024/12/02 14:04:52.349 | Dec 02, 2024 2:04:52 PM org.apache.coyote.AbstractProtocol start
INFO | jvm 1 | main | 2024/12/02 14:04:52.350 | INFO: Starting ProtocolHandler ["https-jsse-nio-9002"]
INFO | jvm 1 | main | 2024/12/02 14:04:52.350 | Dec 02, 2024 2:04:52 PM org.apache.coyote.AbstractProtocol start
INFO | jvm 1 | main | 2024/12/02 14:04:52.351 | INFO: Starting ProtocolHandler ["ajp-nio-0.0.0.0-8009"]
INFO | jvm 1 | main | 2024/12/02 14:04:52.351 | Dec 02, 2024 2:04:52 PM org.apache.catalina.startup.Catalina start
INFO | jvm 1 | main | 2024/12/02 14:04:52.351 | INFO: Server startup in [657597] milliseconds
INFO | jvm 1 | main | 2024/12/02 14:05:00.766 | Dec 02, 2024 2:05:00 PM org.apache.catalina.loader.WebappClassLoaderBase checkStateForResourceLoading
INFO | jvm 1 | main | 2024/12/02 14:05:00.766 | INFO: Illegal access: this web application instance has been stopped already. Could not load [com.hybris.cockpitng.core.spring.RequestOperationContextHolder]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
INFO | jvm 1 | main | 2024/12/02 14:05:00.768 | java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [com.hybris.cockpitng.core.spring.RequestOperationContextHolder]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
SAP Commerce #hybris #SAP Commerce On-Premise #Patching Hybris
Regards,
Frank
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.