WebLogic Admin Console won't work with java security manager enabled.

By just enabling the security manager on the command line with -Djava.security.manager and using the default weblogic.policy in the server/lib directory, the admin console will not work. I just see a blank page when I try to access the admin console with permission errors all over on the server console.
In looking at the admin console's weblogic.xml it should have access to everything since it contains:
grant {
permission java.security.AllPermission;
Are there known issues with this? If I add this permission to the weblogic.policy file everything works fine but then I might as well not turn on the security manager.
Thanks,
Dave

David,
I was glad to see your post regarding WLS 9.2 and the troubles with enabling Java Security Manager.
Were you able to learn any more on things like - why doesn't the admin console work when the security manager is enabled with the default policy file. Also, why is it so difficult to add permissions for your own applications and get them to actually work.
I'd be curious to see if you were able to get it to work or if you have any insights or resources that can help with this as we are really struggling to get a restrictive policy file that works.
Thanks,
D

Similar Messages

  • Trouble with java security manager

    I have set up a security manager for my webapp running on Tomcat. The application enables the user to write his own scripts using Javascript, that's why I need to set up a security manager.
    Using Rhino as script interpreter, it is possible to use the standard java security mechanisms, e.g. using the security manager to handle the scripts' rights.
    I've added the following lines to my policy file:
    // give server all rights
    grant codeBase "file:webapp/WEB-INF/-" {
         permission java.security.AllPermission;
    //rights granted to scripts
    grant codeBase "file:restrictedClient" {
         permission java.io.FilePermission "webapp/WEB-INF/lib/js.jar", "read";
    I've assigned the scripts to the "restrictedClient" code base. However, the script execution fails as the script does not have the permission to access or define classes of any package (even standard java packages like java.lang or java.math).
    In java.security, I have found the following comment:
    # List of comma-separated packages that start with or equal this string
    # will cause a security exception to be thrown when
    # passed to checkPackageDefinition unless the
    # corresponding RuntimePermission ("defineClassInPackage."+package) has
    # been granted.
    # by default, no packages are restricted for definition, and none of
    # the class loaders supplied with the JDK call checkPackageDefinition.
    #package.definition=
    I now wonder, why the checkPackageDefinition is checked though there's no entry for any package to be checked.
    Extending the policy file like
    grant codeBase "file:restrictedClient" {
         permission java.lang.RuntimePermission "accessClassInPackage.webapp/WEB-INF/classes/org/mozilla/javascript";
         permission java.io.FilePermission "webapp/WEB-INF/lib/js.jar", "read";
         permission java.lang.RuntimePermission "defineClassInPackage.java.io";
         permission java.lang.RuntimePermission "defineClassInPackage.java.util";
         permission java.lang.RuntimePermission "defineClassInPackage.java.net";
         permission java.lang.RuntimePermission "defineClassInPackage.java.sql";
         permission java.lang.RuntimePermission "defineClassInPackage.java.lang";
         permission java.lang.RuntimePermission "defineClassInPackage.java.math";
         permission java.lang.RuntimePermission "de.methodpark.pkit.facade.impl";
    works, but an unpleasant feeling remains :-).
    Rhino creates an own classloader for script execution. Could that be the source of the strange behaviour?
    Any help would be appreciated!
    Regards,
    Matthias

    David,
    I was glad to see your post regarding WLS 9.2 and the troubles with enabling Java Security Manager.
    Were you able to learn any more on things like - why doesn't the admin console work when the security manager is enabled with the default policy file. Also, why is it so difficult to add permissions for your own applications and get them to actually work.
    I'd be curious to see if you were able to get it to work or if you have any insights or resources that can help with this as we are really struggling to get a restrictive policy file that works.
    Thanks,
    D

  • OC4J admin console does not work with 9.0.3

    I even tried this on a fresh installation.
    As per the docs, "java -jar oc4j.jar -console" opens an admin interface with a swing GUI for admin purposes.
    Has anyone a clue or this is a bug in this version ?
    I have seen this working in a previous version.
    Thanks,
    Sunil

    Are you talking about this, <provider>org.hibernate.ejb.HibernatePersistence</provider>? Is this the correct provider name for JPA with HIbernate 3?
    or
    You are talking about other configuration in the persistence.xml.
    I appreciate you helps, but can you point out what exact is wrong in my configuration or provide examples? I have not found the correct name for Hibernate provider.

  • New Version 4 won't work with Java. Had to go back to older version.

    I checked all my plugins disabling/enabling. Ran Malware. Reinstalled Java. Reinstalled FF Version 4. Still couldn't get my website edit context to load, but it would on IE. So I uninstalled the Version 4 and went back to Version 3.6.16. All is well now. Don't like the new version. Wasted 2-3 hrs fooling around.

    * Firefox 4 requires at least OS X 10.5 and an Intel Mac.
    * Firefox 3.0 versions and later require at least Mac OS X 10.4
    * http://www.mozilla.com/firefox/4.0/system-requirements/
    The last Firefox version that works on OS X 10.3.x is 2.0.0.20.<br />
    * https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/2.0.0.20/mac/en-US/
    Other browsers that you can look at:
    * http://caminobrowser.org/download/releases/ (#os10.3.8)
    * [http://en.wikipedia.org/wiki/ICab iCab]: http://www.icab.de/

  • IPod touch won't work with WPA secured network

    I'm trying to put my touch on my home network which has WPA security. I have a problem in that one of the characters in my 50 characters WPA key is not available on my iPod! (The " ` " character. It's not an apostrophe like " ' ". It's the one on the tilde button.) I don't even know if I had that character that it would work. Is there anyway that I can change my WPA key, or have a simpler password? It seems like I shouldn't have to input like 50 characters if I want to access my network. Is there something I configure in my network settings? Any help is appreciated.

    I use WPA2 and have no problems connecting. I must clarify that I have a mixed network of Airport Extreme 802.11n (operating on 5GHz) & 802.11g (operating on 2.4GHz) routers. Only the 802.11g router's network shows on the Touch though.
    You should replace the character that's not on the iPod in your network password. It should work if it's operating on the standard (default?) 2.4GHz. I don't think that 802.11g or n matters. As for entering the password on the Touch every time you want to join your network, that won't be necessary. I just double -checked. The network name and settings are memorized by the Touch.

  • Pogo won't play games java won;t work with firefox

    I was playing pogo and it came up to update Java. Did it and now can't play most of the games like canasta. Says java won't work with firefox.....it did before. try for 4 days not and no luck

    Java is working properly. Still not loading games

  • Just updated the lion os x, and now when I try to use my optus dongle, it comes up with the message saying that it won't work because Java Runtime needs to be installed.  Help?

    just updated the lion os x, and now when I try to use my optus dongle, it comes up with the message saying that it won't work because Java Runtime needs to be installed.  Help?

    Have you run Software Update.  You have Java already installed, but it needs to be updated.

  • Weblogic admin console fails to start when commons logging is used.

    I have an application that requires commons logging.
    I followed the instructions as per the documentation and other forum entries such as How to use log4j into weblogic 10.3 to add the commons logging jar from apache and the weblogic jar specified. Plus I set the system property for the LogFactory.
    When I start up the application server I see messages as expected from my application. But when I start up the weblogic Admin console I get and exception and the console fails to start. I even tried to put the jars in my applicaiton instead of the domain/lib directory to try to iscolate the issue but still got issues with starting the Console.
    Any ideas on why this is occuring?
    See the error below:
    ####<May 19, 2010 4:16:04 PM EDT> <Notice> <Stdout> <TE001XU-CATOR1> <AdminServer> <Check Retention Schedule Setting> <<WLS Kernel>> <> <> <1274300164672> <BEA-000000> <----------------------------------------Retention Init()---------------------------------------->
    ####<May 19, 2010 4:16:04 PM EDT> <Notice> <Stdout> <TE001XU-CATOR1> <AdminServer> <Check Retention Schedule Setting> <<WLS Kernel>> <> <> <1274300164672> <BEA-000000> <Thu May 20 05:00:00 EDT 2010>
    ####<May 19, 2010 4:16:06 PM EDT> <Info> <Health> <TE001XU-CATOR1> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <> <1274300166060> <BEA-310002> <81% of the total memory in the server is free>
    ####<May 19, 2010 4:35:03 PM EDT> <Info> <WorkManager> <TE001XU-CATOR1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274301303146> <BEA-002901> <Creating WorkManager "consoleWorkManager" for module "null" and application "consoleapp">
    ####<May 19, 2010 4:35:17 PM EDT> <Error> <HTTP> <TE001XU-CATOR1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274301317582> <BEA-101216> <Servlet: "AppManagerServlet" failed to preload on startup in Web application: "console".
    java.lang.ExceptionInInitializerError
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    at weblogic.servlet.AsyncInitServlet.createDelegate(AsyncInitServlet.java:44)
    at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:98)
    at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
    at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
    at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: org.apache.commons.logging.LogConfigurationException: The chosen LogFactory implementation does not extend LogFactory. Please check your configuration. (Caused by java.lang.ClassCastException: weblogic.logging.commons.LogFactoryImpl cannot be cast to org.apache.commons.logging.LogFactory)
    at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:574)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:517)
    at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:254)
    at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
    at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.<clinit>(MBeanUtilsInitSingleFileServlet.java:23)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    at weblogic.servlet.AsyncInitServlet.createDelegate(AsyncInitServlet.java:44)
    at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:98)
    at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
    at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
    at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    Thank you for replying. Yes that is the first place we looked and tried. Actually to be more specific we followed the instrcutions under: "How to Use the Commons API with WebLogic Logging Services" of the same link.
    Are you thinking that maybe we are we missing a step somewhere else within the site?
    Not sure if I was clear before but we are using Weblogic 10.3 and also tried up to version 10.3.3. And we get the same results.
    We prefer to use the method with commons logging for our application.
    One more specific here what we did on our last attempt.
    1. added this to the startWeblogic script JAVAOPTIONS -Dorg.apache.commons.logging.LogFactory=weblogic.logging.commons.LogFactoryImpl
    2. we put the WebLogic-specific Commons classes, $BEA_HOME/modules/com.bea.core.weblogic.commons.logging_1.3.0.0.jar, together with the commons-logging.jar file in one of the following locations: APP-INF/LIB or WEB-INF/LIB directory or DOMAIN_NAME/LIB directory server CLASSPATH
    We are still not able to get the Weblogic admin console to start
    Any other ideas?
    Edited by: user13094648 on May 21, 2010 10:29 AM
    Edited by: user13094648 on May 21, 2010 10:37 AM

  • Weblogic Admin console applet does not load

    I have installed Weblogic 6.1 SP3 with JDK 1.4.2_03. The admin console applet was
    working initially but when I installed oracle 8.1, the applet failed to load.
    A cross sign appears instead of navigation applet tree in the console application.
    I have set the classpath and java_home variables correctly. I tried to point java_home
    to jdk1.3.1 (java version shipped with Weblogic 6.1) and also changed entire classpath
    to point to jdk1.3.1 but no effect. The same configuration works on another machine
    where oracle is not installed.
    Please help...
    Thanks in advance
    Mahesh

    If you have any pride you will get off Tripod as quickly as possible. It forces popups and other unwanted advertising on visitors. Any time I see that a site is on Tripod or About, I just ignore it and click the next choice.
    BTW if you stay on Tripod, you should consider changing the 'e' in your user name to an 'o'.

  • Embedded weblogic admin console will not start

    Hi Forum members,
    I'm using JDeveloper Studio Edition Version 11.1.1.0.2 and trying to start the WebLogic admin console for
    JDeveloper's embedded WebLogic Server.
    The admin login screen appears, but after entering userid and password, the admin console crashes.
    The log entries are below; thanks for your assistance.
    <Nov 4, 2009 12:44:55 PM PST> <Error> <netuix> <BEA-423103> <[consolehelp] Deployment descriptor /WEB-INF/netuix-config.xml malformed.>
    <Nov 4, 2009 12:44:55 PM PST> <Error> <netuix> <BEA-423443> <Exception while initializing SingleFileServlet: [javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could not initialize class com.bea.netuix.servlets.manager.types.netuix_config.WeblogicPortalAppDocument].
    javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could not initialize class com.bea.netuix.servlets.manager.types.netuix_config.WeblogicPortalAppDocument
         at com.bea.netuix.util.ThrowServletException.throwServletException(ThrowServletException.java:28)
         at com.bea.netuix.servlets.manager.AppDescriptor.loadDescriptor(AppDescriptor.java:1053)
         at com.bea.netuix.servlets.manager.SingleFileServlet.reinitInternal(SingleFileServlet.java:124)
         at com.bea.netuix.servlets.manager.SingleFileServlet.initInternal(SingleFileServlet.java:84)
         at com.bea.netuix.servlets.manager.SingleFileServlet.access$100(SingleFileServlet.java:48)
         Truncated. see log file for complete stacktrace
    java.lang.NoClassDefFoundError: Could not initialize class com.bea.netuix.servlets.manager.types.netuix_config.WeblogicPortalAppDocument
         at com.bea.netuix.servlets.manager.types.netuix_config.WeblogicPortalAppDocument$Factory.parse(WeblogicPortalAppDocument.java:533)
         at com.bea.netuix.servlets.manager.AppDescriptor.loadConfig(AppDescriptor.java:670)
         at com.bea.netuix.servlets.manager.AppDescriptor.loadDescriptor(AppDescriptor.java:1040)
         at com.bea.netuix.servlets.manager.SingleFileServlet.reinitInternal(SingleFileServlet.java:124)
         at com.bea.netuix.servlets.manager.SingleFileServlet.initInternal(SingleFileServlet.java:84)
         Truncated. see log file for complete stacktrace
    >
    <Nov 4, 2009 12:45:24 PM PST> <Error> <netuix> <BEA-423540> <No IPreferenceStore implementation has been registered in WEB-INF/netuix-config.xml. See the javadoc for com.bea.portlet.prefs.spi.IPreferenceStore for information on how to configure a preference store. Using a no-op store as a default.>
    <Nov 4, 2009 12:45:57 PM PST> <Error> <netuix> <BEA-423203> <The included control tree for URI [PortalConfig/snmp/Snmp.book] is invalid.
    com.bea.netuix.nf.UIControlException: Error creating tree from uri [PortalConfig/snmp/Snmp.book].
         at com.bea.netuix.servlets.controls.content.ValidatedContent.validateContent(ValidatedContent.java:91)
         at com.bea.netuix.servlets.manager.SingleFileProcessor.getMergedControlFromFile(SingleFileProcessor.java:358)
         at com.bea.netuix.servlets.manager.UIServletInternal.processStream(UIServletInternal.java:272)
         at com.bea.netuix.servlets.manager.UIServletInternal.getTree(UIServletInternal.java:230)
         at com.bea.netuix.servlets.manager.UIServletInternal.createUIContext(UIServletInternal.java:105)
         Truncated. see log file for complete stacktrace
    com.bea.netuix.nf.UIControlException: One or more validation error(s) occurred during parsing [PortalConfig/snmp/Snmp.book]. The error(s) were: [Parser Error...
    org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'netuix:meta'. One of '{"http://www.bea.com/servers/netuix/xsd/controls/netuix/1.0.0":toggleButton, "http://www.bea.com/servers/netuix/xsd/controls/netuix/1.0.0":content}' is expected.
         at com.bea.netuix.servlets.controls.content.ValidatedContent.validateContent(ValidatedContent.java:80)
         at com.bea.netuix.servlets.manager.SingleFileProcessor.getMergedControlFromFile(SingleFileProcessor.java:358)
         at com.bea.netuix.servlets.manager.UIServletInternal.processStream(UIServletInternal.java:272)
         at com.bea.netuix.servlets.manager.UIServletInternal.getTree(UIServletInternal.java:230)
         at com.bea.netuix.servlets.manager.UIServletInternal.createUIContext(UIServletInternal.java:105)
         Truncated. see log file for complete stacktrace
    >
    <Nov 4, 2009 12:46:26 PM PST> <Warning> <netuix> <BEA-423319> <A default encoding was not found for webapp [console]. You can set a default encoding for portals in netuix-config.xml. Defaulting to [UTF-8].>
    <Nov 4, 2009 12:46:27 PM PST> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@3ee3a0 - appName: 'consoleapp', name: 'console', context-path: '/console', spec-version: '2.5', request: weblogic.servlet.internal.ServletRequestImpl@13442f1[
    GET /console/console.portal HTTP/1.1
    User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.14) Gecko/2009082707 (CK-zz) Firefox/3.0.14
    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
    Accept-Language: en-us,en;q=0.5
    Accept-Encoding: gzip,deflate
    Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
    Keep-Alive: 300
    Connection: keep-alive
    Referer: http://127.0.0.1:7101/console/login/LoginForm.jsp
    Cookie: JSESSIONID=jWpJKxnS1N3pd3ryQRGShJF7qbkZt2KrP9DdTPCphJh9vwvyJndL!662735321; ADMINCONSOLESESSION=5012KxnLnRNpnk679vWrWSbX2SXrhv0nqN11JcwGzJvhbjNy7L4R!662735321
    ]] Root cause of ServletException.
    java.lang.NoClassDefFoundError: Could not initialize class schemacom_bea_xml.system.sF6C6DB196AAE83D234595A687AE0370E.TypeSystemHolder
         at sun.misc.Unsafe.ensureClassInitialized(Native Method)
         at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:25)
         at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:122)
         at java.lang.reflect.Field.acquireFieldAccessor(Field.java:918)
         at java.lang.reflect.Field.getFieldAccessor(Field.java:899)
         Truncated. see log file for complete stacktrace

    The Fusion Middleware is installed on my Windows XP laptop. To start my admin server, I use the Windows start button and navigate to "Oracle Fusion Middleware 11.1.1.0.2" -> "User Projects" -> "base-domain" -> "Start Admin Server for WebLogic Server Domain" menu item.
    After the admin server is running, I use the Windows start button and navigate to "Oracle Fusion Middleware 11.1.1.0.2" -> "User Projects" -> "base-domain" -> "Admin Server Console" menu item.
    A web browser pops up and after a few minutes, the login screen appears. After logging in, the admin console return a error screen. The log file contains the previous posted entries.

  • Applets not working with Java 1.7.0_51 in MII 14.0 SP4 Patch 5

    Hi,
    I'm currently evaluating the migration of our MII 12.0 developments to MII 14.
    But I'm running in several issues just trying to use simple things like a SQL query template with an iGrid Display template in test mode.
    Used versions are: MII 14.0 SP4 Patch 5 and on client side the latest Mozilla Firefox with Java 1.7.0_51
    At first I always get a java security warning when the applet is being loaded about unsigned applications.
    At second the applet itself is not running. It always shows "No data available" and the java console shows the following errors (iResult is the id of the applet):
    iResult [ERROR] - Couldn't set query template: No Query Defined
    iResult [ERROR] - Couldn't set display template: null
    iResult [ERROR] - Couldn't set display template: null
    Is this perhaps a general problem, that the MII applets are not working with Java 1.7.x versions?
    If I call the same MII page from a client with Java 1.6.x it is working without errors.
    Do you have some suggestions for me?
    Regards Timo

    please clear your JAVA Cache. that should solve the JRE issue. thanks

  • Is there a way to disable concurrent Weblogic Admin Console sessions for the same user?

    A coworker on another workstation and I are able to log into same user account on the Weblogic Admin Console at the same time. I would like to restrict access so only one session per user account can be logged in to the Admin Console. Is this possible?
    Alternatively, is there a way to log identifiable information (IP/workstation) when multiple sessions for one account occur at the same time?
    I am using 10.3.6.0

    Hi,
    You could also check the http access logs for such info. There you could see records for the received requests, with each record starting with the source IP that initiated the request.
    The default location for access logs is ${DOMAIN_HOME}/servers/${SERVER_NAME}/logs. Of course in your case, the ${SERVER_NAME} would be your admin server name (AdminServer if left as default).
    Regards,
    Mohab

  • Problem while Deploying application in weblogic admin console

    Hi all,
    Recently i got an issue while deploying application through weblogic admin console,
    I have logged in the weblogic console and clicked on the deployment option, i got the page of install the application, then i have click the install option, i was getting the page of blank white screen. checking the log file of the admin server i cannot find any error. The admin server was running state was ok. before many times i have done deploying application in the same weblogic admin console.
    My weblogic 10.3 was running in windows 2008 r2
    Kindly need a help to resolve this problem ASAP.
    Regards,
    Rakhi

    Hi sir,
    thanks for ur reply.. but while troubleshooting on this issue i am facing another problem,
    The weblogic server is running on windows os box, i have stop the weblogic admin server from the windows services and again started the weblogic admin server, the server was running in proper state and i have open the console and try the same thing clicking on the deployment and install options but the same issue i faced. getting the white blank screen, while trying to refresh the page i cannot get the weblogic console waiting for long time also. again after restarting the server i can get the weblogic console.
    Then i have tried in another way, i removed the window services and started the weblogic server from command prompt,after starting the server i have opened the admin console and click on the deployment and install option, it is working fine. i tried the same for many times its working fine. but while starting from windows services the problem i was facing same as blank white screen,
    Kindly give me a perfect resolution on this issue. because i was so confused on this part.
    Regards,
    Rakhi..

  • Why cannot login to weblogic admin console . no error.

    Why I cannot login to weblogic admin console. I keep getting login screen. I reset the userid and password but still cannot login
    Here is what's in the log file:
    Sep 26, 2010 8:55:14 PM EDT> <Warning> <HTTP> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914272> <BEA-101296> <Unable to load the default compiler class "com.sun.tools.javac.Main". Using the default javac compiler to compile JSPs.>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914319> <BEA-000365> <Server state changed to STANDBY>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914335> <BEA-000365> <Server state changed to STARTING>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Info> <SAFService> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914351> <BEA-281003> <SAF Service has been initialized.>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Info> <SAFService> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914351> <BEA-281002> <SAF Service has been started.>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Info> <WseeCore> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914351> <BEA-220502> <The Wsee Service is starting>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Deployer> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914366> <BEA-149209> <Resuming.>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Diagnostics> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914413> <BEA-320000> <The Diagnostics subsystem is initializing on Server myserver.>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Store> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914413> <BEA-280008> <Opening the persistent file store "WLS_DIAGNOSTICS" for recovery: directory=C:\mydomain\servers\myserver\data\store\diagnostics requestedWritePolicy="Disabled" fileLockingEnabled=true driver="wlfileio3".>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Store> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914413> <BEA-280009> <The persistent file store "WLS_DIAGNOSTICS" (430fff8d-1448-4efe-ae57-8e17de6fd97a) has been opened: blockSize=512 actualWritePolicy="Disabled(single-handle-non-direct)" explicitIOEnforced=false records=0.>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Log Management> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914429> <BEA-170025> <Initialized Domain Logging. Domain log events will be written to C:\mydomain\servers\myserver\logs/mydomain.log.>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <Log Management> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914429> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Diagnostics> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914507> <BEA-320077> <Initialized the Diagnostic Accessor Service.>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914538> <BEA-000365> <Server state changed to ADMIN>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914569> <BEA-000365> <Server state changed to RESUMING>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Management> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914663> <BEA-141052> <The auto deployment poller has started.>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Server> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914694> <BEA-002610> <Dynamic Listener Service initialized.>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <Server> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914694> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <Server> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914694> <BEA-002613> <Channel "Default" is now listening on 172.16.37.59:7001 for protocols iiop, t3, ldap, snmp, http.>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914694> <BEA-000331> <Started WebLogic Admin Server "myserver" for domain "mydomain" running in Development Mode>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914741> <BEA-000365> <Server state changed to RUNNING>
    ####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914741> <BEA-000360> <Server started in RUNNING mode>
    ####<Sep 26, 2010 8:55:15 PM EDT> <Info> <J2EE> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548915429> <BEA-160151> <Registered library Extension-Name: bea_wls_async_response (JAR).>
    ####<Sep 26, 2010 8:55:15 PM EDT> <Info> <EJB> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548915569> <BEA-010008> <EJB Deploying file: mejb.jar>
    ####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916085> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceHttps for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916179> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceJms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916194> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseService for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916194> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Jms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916210> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12 for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916210> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Https for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Sep 26, 2010 8:55:16 PM EDT> <Info> <EJB> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548916288> <BEA-010009> <EJB Deployed EJB with JNDI name ejb.mgmt.MEJB.>
    ####<Sep 26, 2010 8:55:27 PM EDT> <Info> <WorkManager> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548927226> <BEA-002901> <Creating WorkManager "consoleWorkManager" for module "null" and application "consoleapp">
    ####<Sep 26, 2010 8:55:28 PM EDT> <Info> <netuix> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548928226> <BEA-423101> <[console] Initializing the NetUIx container>
    ####<Sep 26, 2010 8:55:28 PM EDT> <Info> <netuix> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548928523> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [console//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
    ####<Sep 26, 2010 8:55:29 PM EDT> <Info> <netuix> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548929164> <BEA-423101> <[consolehelp] Initializing the NetUIx container>
    ####<Sep 26, 2010 8:55:29 PM EDT> <Info> <netuix> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548929195> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [consolehelp//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
    ####<Sep 26, 2010 8:56:14 PM EDT> <Info> <Health> <TAXWARE_TEST> <myserver> <weblogic.GCMonitor> <<anonymous>> <> <> <1285548974540> <BEA-310002> <86% of the total memory in the server is free>

    There is no error. Is there another domain on your OS? can you please put here your config.xml file and your login screen image here.
    May be you use wrong console to login.

  • Authentication denied on Weblogic admin console

    I was playing with security policy for web applications and now I can't login from
    console any more. It gives following error : Authentication Denied
    The username or password has been refused by WebLogic Server. Please try again.
    I can start the server from command line. How can I find out what is the problem
    and how can I fix it ?
    Thanks,
    MK

    Hi AB.
    You can write your own pages and add them to WebLogic admin console by writing a console extension, here is a link to bea doc http://e-docs.bea.com/wls/docs100/console_ext/understandext.html
    Regards,
    Felix

Maybe you are looking for