java.lang.ExceptionInInitializerError

Oracle Community | 807573 | 10 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Policy Agent 2.2 on Glassfish 2: Invalid application password specified

    Oracle Community | 10 years ago | 807573
    java.lang.ExceptionInInitializerError
  2. 0

    Openam - Unable to get Application SSO Token

    Stack Overflow | 2 years ago
    java.lang.ExceptionInInitializerError
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

  4. 0

    OpenAM J2EE Agent is installed within Weblogic application server 10.3.3. Therefore policy agent authentication provider for WebLogic AmWLAuthProvider is registered. If WLS admin server tries to start up and OpenAM is not available an ExceptionInInitializerError arises: java.lang.ExceptionInInitializerError at com.sun.identity.agents.arch.Manager.<clinit>(Manager.java:643) at com.sun.identity.agents.weblogic.v10.AmWLAuthProvider.initialize(AmWLAuthProvider.java:57) at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:65) at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363) ... Caused By: java.lang.RuntimeException: Failed to load configuration: ApplicationSSOTokenProvider.getApplicationSSOToken(): Unable to get Application SSO Token at com.sun.identity.agents.arch.AgentConfiguration.bootStrapClientConfiguration(AgentConfiguration.java:795) at com.sun.identity.agents.arch.AgentConfiguration.initializeConfiguration(AgentConfiguration.java:1148) at com.sun.identity.agents.arch.AgentConfiguration.<clinit>(AgentConfiguration.java:1587) at com.sun.identity.agents.arch.Manager.<clinit>(Manager.java:643) at com.sun.identity.agents.weblogic.v10.AmWLAuthProvider.initialize(AmWLAuthProvider.java:57) at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:65) at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363) at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315) at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257) ... WLS admin and managed server will not startup. Expected result: WLS admin and managed server correctly start up without authentication provider functionality (AmWLAuthProvider). If AmWLAuthProvider is required, optional or sufficient for application server (j2ee agent) authentication (WLS Default Authenticator) the WLS control flag should be correctly configured.

    ForgeRock JIRA | 6 years ago | segl1de
    java.lang.ExceptionInInitializerError

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.ExceptionInInitializerError

      No message provided

      at com.sun.identity.agents.arch.Manager.<clinit>()
    2. com.sun.identity
      Manager.<clinit>
      1. com.sun.identity.agents.arch.Manager.<clinit>(Manager.java:622)
      1 frame