Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Error initializing com.isomorphic.base.Init in ServiceMix Fuse 4.4.1

    We have built a WAR using smartgwt Power Edition 2.5. Recently we have upgraded our container to ServiceMix 4.4.1, and could not deploy the same war.

    From initial debugging we observed that isomorphic_core_rpc uses log4j1.2.15;
    ServiceMix Jetty pax-web-extender uses pax-logging-api v 1.6.x which uses log4j v1.2.16, for all logging purposes.
    while deploying the war into embedded jetty on ServiceMix, pax-web-extender throws a NoClassDefFound Error for the package org/apache/log4j/spi/RootCategory. It looks like this class is deprecated in log4j v1.2.16, and we are not aware of a solution so far, for modifying the logger provider for pax-web-extender.

    We have checked smartgwt power 3.0, and found that 1.2.16 is neither supported there.

    Is there a way we can make the existing version of smartgwt power to work with 1.2.16 version of log4j?

    Thanks
    Vamsi Gandrapu

    #2
    In general, you can update any of the dependent libs to more recent versions, so long as the lib is backwards compatible, which seems to be the case here.

    Comment


      #3
      Originally posted by Isomorphic
      In general, you can update any of the dependent libs to more recent versions, so long as the lib is backwards compatible, which seems to be the case here.
      However com.isomorphic.base.Init still expects RootCategory. The original question is about possibility to avoid this, for example use a different logger provider?
      Below is the stack trace:
      Code:
      org.ops4j.pax.web.pax-web-extender-war - 1.0.3 | Registration exception. Skipping.
      java.lang.NoClassDefFoundError: org/apache/log4j/spi/RootCategory
      	at com.isomorphic.base.Init.<clinit>(Init.java:68)
      .....
      Caused by: java.lang.ClassNotFoundException: org.apache.log4j.spi.RootCategory not found by org.ops4j.pax.logging.pax-logging-api.
      Thanks,
      Vamsi Gandrapu

      Comment


        #4
        As you indicated, RootCategory is deprecated, not removed. If there's a ClassNotFoundException for RootCategory, this is a missing library or other faulty deployment issue, not a compatibility issue.

        Comment

        Working...
        X