Previous Topic: All Application Logs Redirected to the AFM Log File in JBossNext Topic: Application Does Not Detect Backup Data Source Availability in JBoss


Risk Evaluation from State Manager Fails Due to Class Loading Issues

Symptom:

In JBoss application server, after deploying the AFM, State Manager, and sample application-specific WAR files, the WAR files are not extracted based on how the applications are deployed. This might cause risk evaluation from State Manager to fail due to class loading issues.

Solution:

Follow these steps:

  1. Explode one of the WAR files to a local directory.
  2. Create a new file, jboss-web.xml in App_Exploded_Location\App_Name\WEB-INF

    where,

    App_Exploded_Location is the location where JBoss has extracted the application

    App_Name is the name of the application, for example, arcotafm or arcotsm..

  3. Copy the following into the jboss-web.xml file:
    <jboss-web>  
      <class-loading java2ClassLoadingCompliance="false">  
        <loader-repository> 
          com.arcot:loader=<UniquenameforClassLoader>
          <loader-repository-config>
            java2ParentDelegation=false
          </loader-repository-config>  
        </loader-repository>  
      </class-loading>  
    </jboss-web>
    

    UniquenameforClassloader must be unique for each application. For example, you can use ArcotAFMClassloader for AFM, ArcotSMClassloader for State Manager, and so on.

  4. If a jboss-classloading.xml file is present in the App_Exploded_Location\App_Name\WEB-INF directory, then delete the file.
  5. Restart the application server.

Repeat this procedure for the AFM, State Manager, and SAML sample applications.