cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Hybris (Telco+DataHub) 6.7.0.16 Server startup failure with - More than one fragment with the name [spring_web] was found

Former Member
0 Likes
1,826

Getting below error on server startup on various OOTB extensions (e.g. cissubscription , cmswebservices.. and many more )

 [ERROR] [org.apache.catalina.core.ContainerBase] A child container failed during start
 java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/cissubscription]]
         at java.util.concurrent.FutureTask.report(Unknown Source)
         at java.util.concurrent.FutureTask.get(Unknown Source)
         at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:942)
         at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:872)
         at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
         at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1423)
         at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1413)
         at java.util.concurrent.FutureTask.run(Unknown Source)
         at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source)
 Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/cissubscription]]
         at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
         ... 6 common frames omitted
 Caused by: java.lang.IllegalArgumentException: More than one fragment with the name [spring_web] was found. This is not legal with relative ordering. See section 8.2.2 2c of the Servlet specification for details. Consider using absolute ordering.
         at org.apache.tomcat.util.descriptor.web.WebXml.orderWebFragments(WebXml.java:2200)
         at org.apache.tomcat.util.descriptor.web.WebXml.orderWebFragments(WebXml.java:2159)
         at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1124)
         at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:769)
         at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:299)
         at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
         at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5134)
         at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
         ... 6 common frames omitted
 [ERROR] [org.apache.catalina.core.ContainerBase] A child container failed during start
 java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/backoffice]]
         at java.util.concurrent.FutureTask.report(Unknown Source)
         at java.util.concurrent.FutureTask.get(Unknown Source)
         at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:942)
         at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:872)
         at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
         at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1423)
         at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1413)
         at java.util.concurrent.FutureTask.run(Unknown Source)
         at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source)
 Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/backoffice]]
         at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
         ... 6 common frames omitted
 Caused by: java.lang.IllegalArgumentException: More than one fragment with the name [spring_web] was found. This is not legal with relative ordering. See section 8.2.2 2c of the Servlet specification for details. Consider using absolute ordering.
         at org.apache.tomcat.util.descriptor.web.WebXml.orderWebFragments(WebXml.java:2200)
         at org.apache.tomcat.util.descriptor.web.WebXml.orderWebFragments(WebXml.java:2159)
         at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1124)
         at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:769)
         at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:299)
         at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
         at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5134)
         at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
         ... 6 common frames omitted

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Likes

Hi Prashant

Could you help me with this. I am getting the same error when i add cissubscription in my localextensions.xml.

I am using 1905.

Thanks

Tanima

Former Member
0 Likes

Please check the jars and search whether those jars are compatible with the java version that you are using or not. Spring 3.x is not compatible with Java 8. If you want to migrate to Java-8 you should use Spring 4.x version.

This issue could be solved by adding absolute ordering of deployment descriptors.

Servlet 3.0 supports absolute ordering and relative ordering of deployment descriptors. Your specify absolute ordering using the element in the web.xml file. You specify relative ordering with an element in the web-fragment.xml file.

For example, suppose your application includes two web fragments — MyFragment2 and MyFragment3, and also includes a web.xml file. You can declare absolute ordering of the descriptors by specifying the following in the web.xml file for the application:

    <name>MyApp</name>
    <absolute-ordering>
       <name>MyFragment3</name>
       <name>MyFragment2</name>
    </absolute-ordering>
   

Here, the processing order would be as follows:

web.xml. The web.xml descriptor is always processed first.

MyFragment3.

MyFragment2.

Refer attachment -

Former Member
0 Likes

I have just extracted 6.7.0.16 , telco and data hub. Ran the b2c_telco recipe..and after that i am getting these errors, Evertyhing OOTB till now. Even after i make some changes around OOTB web.xml config, i ll never be confident enough to push this upgrade to higher environment.