Integrations - JBoss Application Server

Article Rating?	1 2 3 4 5

Product Type	Container
Versions Supported	4.0.5
Module Status	Not Applicable - Integrates Directly
Module Availability - Released (latest)	Not Applicable
Module Availability - SNAPSHOT (latest)	Not Applicable
Download with Kit	See latest Terracotta Kit

Additional Documentation

Getting Started with JBoss Application Server

Introduction

The JBoss application server is open source and JEE compliant.

As of the terracotta 2.3.0 release, the JBoss application server is supported directly. Regular DSO roots and sessions can be clustered. However, the sessions configurator does not support the JBoss application server.

Dependencies

None.

Implementation

To support sharing of classes defined in the rest of the JBoss universe (outside of the web container), two classes needed custom instrumentation:

org.jboss.mx.loading.UnifiedClassLoader (UCL) – This is the base class for the loader used to run components in the JBoss application server. The terracotta instrumentation uses the UCL's URL to compute a loader name (see com.tc.object.loaders.NamedClassLoader). The loader's URL is usually an absolute path on disk so it must be trimmed in order to allow JBoss nodes that use different install paths to share classes
org.jboss.Main – The JBoss bootstrap classloader is assigned a name here, and the config is queried to determine the base JBoss install directories.

See the Getting Started with JBoss Application Server for complete instructions.

Known Issues

None.