WebLogic 7.0 + SP2 + SP4 (not working) != WebLogic 7.0 + SP4 (working) - Weblogic

This is a discussion on WebLogic 7.0 + SP2 + SP4 (not working) != WebLogic 7.0 + SP4 (working) - Weblogic ; Upgrading WebLogic 7.0 SP2 (+ various patches to SP2), followed by running the SP4 upgrade installer (+ various patches to SP4) appears to give a different result to installing WebLogic 7.0 SP4 (+ various patches to SP4) directly. Furthermore, for ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: WebLogic 7.0 + SP2 + SP4 (not working) != WebLogic 7.0 + SP4 (working)

  1. WebLogic 7.0 + SP2 + SP4 (not working) != WebLogic 7.0 + SP4 (working)

    Upgrading WebLogic 7.0 SP2 (+ various patches to SP2), followed by
    running the SP4 upgrade installer (+ various patches to SP4) appears
    to give a different result to installing WebLogic 7.0 SP4 (+ various
    patches to SP4) directly.

    Furthermore, for me at least 7.0 SP2 SP4 can't start managed servers.
    An identical 7.0 SP4 configuration works fine.

    Working on Solaris 8.

    Comparing a 7.0 SP2 to a 7.0 SP2 SP4 install, I see differences in the
    following files (below /local/bea) :-

    managed/bmes2L/test_server-home/test_server/.internal/uddi.war
    managed/bmes2L/test_server-home/test_server/.internal/uddiexplorer.war
    managed/bmes2L/test_server-home/test_server/.internal/wl_management_internal1.war
    user_projects/bmes2L/admin/.internal/console.war
    user_projects/bmes2L/admin/.internal/uddi.war
    user_projects/bmes2L/admin/.internal/uddiexplorer.war
    user_projects/bmes2L/admin/.internal/wl_management_internal1.war
    user_projects/bmes2L/admin/.internal/wl_management_internal2.war

    Comparing 7.0 SP2 SP4 install with 7.0 SP4, I see the following new
    files

    user_projects/bmes2L/admin/.wlnotdelete/admin_uddi_uddi/jarfiles/WEB-INF/lib/jsse2676.jar
    user_projects/bmes2L/admin/.wlnotdelete/admin_uddi_uddi/jarfiles/WEB-INF/lib/soap2677.jar
    user_projects/bmes2L/admin/.wlnotdelete/admin_uddi_uddi/jarfiles/WEB-INF/lib/xalan2678.jar
    user_projects/bmes2L/admin/.wlnotdelete/admin_uddi_uddi/jarfiles/cls2675.jar
    user_projects/bmes2L/admin/.wlnotdelete/admin_uddiexplorer_uddiexplorer/jarfiles/cls2671.jar
    user_projects/bmes2L/admin/.wlnotdelete/admin_wl_management_internal1_wl_management_intern al1/jarfiles/cls2673.jar
    user_projects/bmes2L/admin/.wlnotdelete/admin_wl_management_internal2_wl_management_intern al2/jarfiles/cls2672.jar

    And I wonder if it is significant as when I try to start my managed
    server on the 7.0 SP2 SP4 system, I get the following

    ####
    <> <101202>
    ####
    <> <101158> while loading uddi: java.lang.ClassCastException: java.lang.String>
    java.lang.ClassCastException: java.lang.String
    at $Proxy7.isWeblogicPluginEnabled(Unknown Source)
    at weblogic.management.configuration.ServerMBean_Cach ingStub.isWeblogicPluginEnabled(ServerMBean_Cachin gS
    at weblogic.servlet.internal.WebAppServletContext.ini tSecurity(WebAppServletContext.java:1273)
    at weblogic.servlet.internal.WebAppServletContext.ini t(WebAppServletContext.java:1063)
    at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:1013)
    at weblogic.servlet.internal.HttpServer.loadWebApp(Ht tpServer.java:599)
    at weblogic.servlet.internal.WebAppModule.prepare(Web AppModule.java:382)
    at weblogic.j2ee.J2EEApplicationContainer.prepareWebM odule(J2EEApplicationContainer.java:1607)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2E EApplicationContainer.java:739)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2E EApplicationContainer.java:555)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2E EApplicationContainer.java:458)
    at weblogic.management.deploy.slave.SlaveDeployer.pre pareAllStagedApplications(SlaveDeployer.java:516)
    at weblogic.management.deploy.slave.SlaveDeployer.ini tialize(SlaveDeployer.java:271)
    at weblogic.management.deploy.DeploymentManagerServer LifeCycleImpl.initialize(DeploymentManagerServerLi fe
    at weblogic.t3.srvr.ServerLifeCycleList.initialize(Se rverLifeCycleList.java:54)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:78 2)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594 )
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)

    I've been googling looking for similar things with no success as yet.
    Has anyone seen anything similar, or successfully done WebLogic 7.0 +
    SP2 + SP4?

    {{{ Andy

  2. Re: WebLogic 7.0 + SP2 + SP4 (not working) != WebLogic 7.0 + SP4 (working)

    Differences in files explained by silent update installer ignoring
    -silent_xml file argument.
    Worked around by putting an additional copy of the file in
    /usr/local/bea/installoptions.bea.
    So now file contents match, although often a numeric part of the
    filename does not match (eg: cls1234.jar on 7.0+SP2+SP4 might match
    cls2345.jar on 7.0+SP4).

    However, exceptions remain as originally indicated, and thus still
    cannot start managed server.

    {{{ Andy

+ Reply to Thread