Results 1 to 6 of 6

Thread: Problems upgrading to m2 release

Hybrid View

  1. #1
    Join Date
    Sep 2004
    Posts
    346

    Default Problems upgrading to m2 release

    I got errors like following:

    Caused by: java.lang.ClassNotFoundException: org.springframework.beans.factory.support.ManagedP roperties: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
    at weblogic.j2ee.ApplicationManager.loadClass(Applica tionManager.java:344)
    at weblogic.j2ee.ApplicationManager.loadClass(Applica tionManager.java:258)
    at weblogic.j2ee.ApplicationManager.loadClass(Applica tionManager.java:253)
    at weblogic.rjvm.MsgAbbrevInputStream.resolveClass(Ms gAbbrevInputStream.java:324)

    reverting to m1 the error did not occur. Any thoughts?

  2. #2
    Join Date
    Aug 2004
    Posts
    2,715

    Default

    Hmm. According to the javadoc this class doesn't seem to exist in M1. Maybe there has been some refactoring and you have to deploy an additional spring jar?

    I haven't downloaded M2 yet. So just guessing.
    Andreas

  3. #3
    Join Date
    Sep 2004
    Posts
    346

    Default Spring jars...

    I have spring.jar, spring-hibernate3.jar and spring-portlet.jar. Am I missing something?

  4. #4
    Join Date
    Jan 2005
    Location
    Bucharest, Romania
    Posts
    5,403

    Default

    Are you using any cluster settings? according to the logs you need to update all jars inside the cluster - probably there is an pre-m2 jar available somewhere that doesn't contain the class added in m2.
    Costin Leau
    SpringSource - http://www.SpringSource.com- Spring Training, Consulting, and Support - "From the Source"
    http://twitter.com/costinl
    Please use [ c o d e ] [ / c o d e ] tags

  5. #5
    Join Date
    Sep 2004
    Posts
    346

    Default We are not using cluster

    We are not using cluster

  6. #6
    Join Date
    Jan 2005
    Location
    Bucharest, Romania
    Posts
    5,403

    Default

    Try clearing your app server cache and turn on logging to see if you can get more details. The stack trace shows that the server is not able to find the approapriate Spring class - this is where your problem lies.
    Costin Leau
    SpringSource - http://www.SpringSource.com- Spring Training, Consulting, and Support - "From the Source"
    http://twitter.com/costinl
    Please use [ c o d e ] [ / c o d e ] tags

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •