Announcement Announcement Module
Collapse

Spring Modules forum decommissioned in favor of Spring Extensions

As the Spring Modules project has been replaced by the Spring Extensions (http://www.springsource.org/extensions) project, this forum has been decommissioned in favour of Spring Extensions one at:
http://forum.springsource.org/forumdisplay.php?f=44

Please see the Spring Extensions home page for a complete list of current projects in Java, .NET and ActionScript. You can also propose one if you want.

Cheers,
Costin Leau
SpringSource - http://www.SpringSource.com- Spring Training, Consulting, and Support - "From the Source"
http://twitter.com/costinl
See more
See less
IncompatibleClassChangeError Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • IncompatibleClassChangeError

    I tried the tutorial that starts at http://static.springframework.org/sp...ep-Part-1.html

    I followed the steps and managed to build, deploy and execute successfully on Apache Tomcat 5.5.

    Then I modified the ant scripts to allow me to build and deploy the WAR file to WebLogic 8.1 instead of Tomcat.

    The WAR deploys successfully, however when I try to run the application, I receive an error and stack trace (see the end of this post). I took a quick look at line 93 of Spring's HttpServletBean.java source code. Here is an excerpt:

    92: public final void init() throws ServletException {
    93: if (logger.isInfoEnabled()) {
    94: logger.info("Initializing servlet '" + getServletName() + "'");
    95: }

    So it looks like it is failing on the logger.isInfoEnabled() method. If that is the case, do I have to do anything in addition to configure WebLogic 8.1 for Spring, e.g. the logging configuration?

    Any help regarding this error and/or tips on successfully running on or deploying a Spring application to WebLogic 8.1 (not 9.x) would be appreciated.

    Thanks,
    TR
    -----------------------------------------------------------------
    The error and stack trace that I received:

    Error 500--Internal Server Error
    java.lang.IncompatibleClassChangeError
    at org.springframework.web.servlet.HttpServletBean.in it(HttpServletBean.java:93)
    at javax.servlet.GenericServlet.init(GenericServlet.j ava:258)
    at weblogic.servlet.internal.ServletStubImpl$ServletI nitAction.run(ServletStubImpl.java:1094)
    at weblogic.security.acl.internal.AuthenticatedSubjec t.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Se curityManager.java:121)
    at weblogic.servlet.internal.ServletStubImpl.createSe rvlet(ServletStubImpl.java:970)
    at weblogic.servlet.internal.ServletStubImpl.createIn stances(ServletStubImpl.java:949)
    at weblogic.servlet.internal.ServletStubImpl.prepareS ervlet(ServletStubImpl.java:888)
    at weblogic.servlet.internal.ServletStubImpl.getServl et(ServletStubImpl.java:598)
    at weblogic.servlet.internal.ServletStubImpl.invokeSe rvlet(ServletStubImpl.java:406)
    at weblogic.servlet.internal.ServletStubImpl.invokeSe rvlet(ServletStubImpl.java:348)
    at weblogic.servlet.internal.WebAppServletContext$Ser vletInvocationAction.run(WebAppServletContext.java :6981)
    at weblogic.security.acl.internal.AuthenticatedSubjec t.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Se curityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.inv okeServlet(WebAppServletContext.java:3892)
    at weblogic.servlet.internal.ServletRequestImpl.execu te(ServletRequestImpl.java:2766)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThrea d.java:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.ja va:183)

  • #2
    You'd better ask this question on the Web forums. I assume you have some class problems (maybe your project is compiled wth different libraries then you have inside Weblogic).

    Comment


    • #3
      Our classes are compiled with jdk142_08 and our release of WebLogic 8.1 is also running this JDK release. From what I can see in the release notes for Spring version 1.2.5, it has been compiled with JDK 1.5 (Tiger). So, as I think you imply, we have an issue with JDK 1.4 code calling JDK 1.5 code.

      I going to try and re-compile the Spring 1.2.5 with dependencies release using a 1.4 target setting and re-try the application.

      Thanks for your recommendation. By the way, which 'Web forums' (in your reply) would you recommend posting this issue to?

      Comment


      • #4
        Web forum: http://forum.springframework.org/forumdisplay.php?f=25
        I don't recall Spring being compiled with 1.5 - even though it should be compiled with compatibility options on. However, do a recompile and see what you get.

        Comment

        Working...
        X