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_internal
1.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/jarf
iles/cls2671.jar
user_projects/bmes2L/admin/.wlnotdelete/admin_wl_management_internal1_wl_man
agement_internal1/jarfiles/cls2673.jar
user_projects/bmes2L/admin/.wlnotdelete/admin_wl_management_internal2_wl_man
agement_internal2/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

####<Jun 17, 2004 5:41:53 PM BST> <Info> <HTTP> <ubns32> <test_server>
<main> <kernel identity> <> <101202> <uddi:uddi preparing>
####<Jun 17, 2004 5:42:03 PM BST> <Debug> <HTTP> <ubns32>
<test_server> <main> <kernel identity> <> <101158> <Exception thrown
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_CachingStub.isWeblogicPlugi
nEnabled(ServerMBean_CachingS
at weblogic.servlet.internal.WebAppServletContext.initSecurity(WebAppServlet
Context.java:1273)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.
java:1063)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContex
t.java:1013)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:599)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationCo
ntainer.java:1607)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.j
ava:739)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.j
ava:555)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.j
ava:458)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplicatio
ns(SlaveDeployer.java:516)
at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.j
ava:271)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initializ
e(DeploymentManagerServerLife
at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:
54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
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

[ Post a follow-up to this message ]

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

[ Post a follow-up to this message ]