jQuery in Action, 3rd edition
The moose likes BEA/Weblogic and the fly likes issue when migrating weblogic9.2 to weblogic10.0 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "issue when migrating weblogic9.2 to weblogic10.0" Watch "issue when migrating weblogic9.2 to weblogic10.0" New topic

issue when migrating weblogic9.2 to weblogic10.0

guru prasanth
Ranch Hand

Joined: Aug 20, 2009
Posts: 102
Iam migrating my application from weblogic 9.2 to weblogic 10.0 also from jdk1.5 to jdk1.6.

Iam getting sevaral access exeption like the one below.

Exception in thread "main" java.lang.ExceptionInInitializerError
at weblogic.Home.getFileSource(Home.java:70)
at weblogic.Home.<init>(Home.java:33)
at weblogic.Home.<init>(Home.java:18)
at weblogic.Home$HomeSingleton.<clinit>(Home.java:24)
at weblogic.Home.getInstance(Home.java:88)
at weblogic.Home.getPath(Home.java:96)
at weblogic.Server.getLibraryExtensions(Server.java:231)
at weblogic.Server.getExtensionJars(Server.java:198)
at weblogic.Server.intializeClassloader(Server.java:135)
at weblogic.Server.main(Server.java:66)
Caused by: java.security.AccessControlException: access denied (java.io.FilePermission C:\Program Files
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
at java.security.AccessController.checkPermission(AccessController.java:401)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
at java.lang.SecurityManager.checkRead(SecurityManager.java:863)
at java.io.File.exists(File.java:678)
at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:360)
at java.io.File.getCanonicalPath(File.java:513)
at weblogic.utils.classloaders.ClasspathClassFinder2.<clinit>(ClasspathClassFinder2.java:24)
... 10 more

On modifying the access policy iam getting the following error.

java.security.AccessControlException: access denied (java.lang.RuntimePermission shutdownHooks)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:323)
at java.security.AccessController.checkPermission(AccessController.java:546)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
at java.lang.Runtime.addShutdownHook(Runtime.java:190)
at java.util.logging.LogManager.<init>(LogManager.java:237)
Truncated. see log file for complete stacktrace
The WebLogic Server encountered a critical failure
Reason: Assertion violated
Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize class weblogic.protocol.ServerIdentityManager$Initializer
at weblogic.protocol.ServerIdentityManager.findServerIdentity(ServerIdentityManager.java:65)
at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:172)
at weblogic.server.ServerLifeCycleRuntime.getLifeCycleOperationsRemote(ServerLifeCycleRuntime.java:687)
at weblogic.t3.srvr.ServerRuntime.sendStateToAdminServer(ServerRuntime.java:412)
at weblogic.t3.srvr.ServerRuntime.updateRunState(ServerRuntime.java:398)
at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:172)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:389)
at weblogic.Server.main(Server.java:67)

Please let me know what's the change in policy files between weblogic9.2 to weblogic10.0
Deepak Bala

Joined: Feb 24, 2006
Posts: 6662

I am not aware of a change in policy. Do you have a custom policy for the security manager to load ?

SCJP 6 articles - SCJP 5/6 mock exams - More SCJP Mocks
guru prasanth
Ranch Hand

Joined: Aug 20, 2009
Posts: 102
Yes there is a custom policy file for the application.But that policy file was working well with weblogic9.2.
Joseph Antoine Raja
Ranch Hand

Joined: Feb 01, 2010
Posts: 32
hi guru,

When we have migrated the env from WSL8 to WLS 9 we did not migrate the user credentials/security roles/policie. we have manually configured after the upgrade.

I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: issue when migrating weblogic9.2 to weblogic10.0
It's not a secret anymore!