Wl 5.1 sp 8 solaris from jdk1.2.2_07 to jdk1.3

Question

Has anyone experienced any problems, issues when migrating jdk's? I have an
issue with ThreadDeaths when shutting down weblogic that may be corrected by
going to jdk 1.3, but before I do, want to know of any traps to look for.
Thanks
Steve Rogers
Senior System Engineer
[email protected]

Answer 1

found in another newsgroup posting:
Add the following to your weblogic.policy file:
permission java.sql.SQLPermission "setLog";
It should be in the last ("general") policy section.
JT
"Steve Rogers" <[email protected]> wrote in message
news:[email protected]...
Well I upgraded, and rebuilt all code with j2se 1.3 And I now get this
stack trace followed by the connection pool unable to be created, andhence
no beans deploying....
Mon Apr 09 20:02:45 EDT 2001:<E> <WebLogicServer> Failed to invoke startup
class
weblogic.jdbc.common.internal.JdbcStartup=weblogic.jdbc.common.internal.Jdbc
Sta
rtup
java.security.AccessControlException: access denied(java.sql.SQLPermission
setL
og)
at
java.security.AccessControlContext.checkPermission(AccessControlConte
xt.java:272)
at
java.security.AccessController.checkPermission(AccessController.java:
399)
at
java.lang.SecurityManager.checkPermission(SecurityManager.java:545)
at java.sql.DriverManager.setLogStream(DriverManager.java:397)
atweblogic.jdbc.common.internal.JdbcInfo.initLog(JdbcInfo.java:66)
atweblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:242)
at
weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at
weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java
:62)
Mon Apr 09 20:02:45 EDT 2001:<I> <JMS> Beginning startup process
Mon Apr 09 20:02:45 EDT 2001:<I> <JMS> Init JMS Security
Mon Apr 09 20:02:45 EDT 2001:<I> <JMS> Init JMS persistent store
Mon Apr 09 20:02:45 EDT 2001:<E> <JMS>
javax.naming.NameNotFoundException: 'weblogic.jdbc.JdbcServices';remaining
name
'jdbc.JdbcServices'
at
weblogic.jndi.toolkit.BasicWLContext.resolveName(BasicWLContext.java:
745)
at
weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:133)
at
weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:574)
at weblogic.jms.server.JMSManager.init(JMSManager.java:311)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1260)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
"Mike Reiche" <[email protected]> wrote in message
news:[email protected]...
It's much faster. Hope that's not a problem.
I had one customer that was using third-party libraries
(OrbixWeb) that did not run propertly with 1.3. \
And you may have to set -XX:MaxPermSize=128m on Solaris.
Other than that, I have not seen any problems.
Mike
"Steve Rogers" <[email protected]> wrote:
Has anyone experienced any problems, issues when migrating jdk's? I
have an
issue with ThreadDeaths when shutting down weblogic that may be
corrected
by
going to jdk 1.3, but before I do, want to know of any traps to look
for.
Thanks
Steve Rogers
Senior System Engineer
[email protected]