# Codehaus Cargo : JBoss 6.x

Created by S. Ali Tokmen, last modified on Jan 02, 2026

This page has been automatically generated by Cargo's build. Do not edit it directly as it'll be overwritten next time it's generated again.

With the opening of the JBoss EAP to the public and the split between JBoss and WildFly, the below naming correspondence should be used with JBoss EAP containers:

- What Cargo calls JBoss 6.x is what JBoss refers to as JBoss Application Server version 6; i.e. the version released in December 2010
- What Cargo calls JBoss 6.1.x is what JBoss refers to as JBoss Application Server version 6.1; i.e. the version released in August 2011
- What Cargo calls JBoss 7.1.x is what JBoss refers to as JBoss Enterprise Application Platform (EAP) version 6.0; i.e. the build from JBoss Application Server (AS) version 7.1 released in February 2012
- What Cargo calls JBoss 7.2.x is what JBoss refers to as JBoss Enterprise Application Platform (EAP) version 6.1; i.e. the build from JBoss Application Server (AS) version 7.2 released in May 2013
- What Cargo calls JBoss 7.3.x is what JBoss refers to as JBoss Enterprise Application Platform (EAP) version 6.2; i.e. the build from JBoss Application Server (AS) version 7.3 released in October 2013
- What Cargo calls JBoss 7.4.x is what JBoss refers to as JBoss Enterprise Application Platform (EAP) version 6.3; i.e. the build from JBoss Application Server (AS) version 7.4 released in June 2014
- What Cargo calls JBoss 7.5.x is what JBoss refers to as JBoss Enterprise Application Platform (EAP) version 6.4; i.e. the build from JBoss Application Server (AS) version 7.5 released in October 2015
- The WildFly 10.x container can be used with the JBoss Enterprise Application Platform (EAP) version 7.0; i.e. the version released in May 2016
- The WildFly 11.x container can be used with the JBoss Enterprise Application Platform (EAP) version 7.1; i.e. the version released in December 2017
- The WildFly 14.x container can be used with the JBoss Enterprise Application Platform (EAP) version 7.2; i.e. the version released in January 2019
- The WildFly 18.x container can be used with the JBoss Enterprise Application Platform (EAP) version 7.3; i.e. the version released in March 2020
- The WildFly 23.x container can be used with the JBoss Enterprise Application Platform (EAP) version 7.4; i.e. the version released in July 2021
- The WildFly 28.x container can be used with the JBoss Enterprise Application Platform (EAP) version 8.0; i.e. the version released in February 2024

### Container Features

Feature name | Java API | Ant tasks | Maven 3 plugin | Comment
--- | --- | --- | --- | ---
Container Instantiation | `ContainerFactory.createContainer("jboss6x"...)` | `<cargo containerId="jboss6x".../>` | `<containerId>jboss6x</containerId>` |
Local Container |  |  |  |
Container Classpath |  |  |  |
Container Start |  |  |  |
Container Stop |  |  |  |
Container Timeout |  |  |  |
Embedded Container |  |  |  |
Installed Container | `o.c.c.c.jboss.JBoss6xInstalledLocalContainer` |  |  |
Passing system properties |  |  |  |
Installer |  |  |  |
Remote Container | `o.c.c.c.jboss.JBoss6xRemoteContainer` |  |  |

### Configuration Features

Feature name | Java API | Ant tasks | Maven 3 plugin | Comment
--- | --- | --- | --- | ---
Standalone Local Configuration for installed container | `o.c.c.c.jboss.JBoss6xStandaloneLocalConfiguration` |  |  |
Standalone Local Configuration for embedded container |  |  |  |
Existing Local Configuration for installed container | `o.c.c.c.jboss.JBoss6xExistingLocalConfiguration` |  |  |
Existing Local Configuration for embedded container |  |  |  |
Runtime Configuration | `o.c.c.c.jboss.JBoss5x6xRuntimeConfiguration` |  |  |
Static deployment of WAR |  |  |  |
Static deployment of expanded WAR |  |  |  |
Static deployment of EJB |  |  |  |
Static deployment of EAR |  |  |  |
Static deployment of RAR |  |  |  |
Static deployment of (JBoss) HAR |  |  |  |
Static deployment of (JBoss) SAR |  |  |  |
Static deployment of (JBoss) AOP |  |  |  |
Static deployment of files |  |  |  |
Static deployment of OSGi Bundles |  |  |  |

### Deployer Features

Feature name | Java API | Ant tasks | Maven 3 plugin | Comment
--- | --- | --- | --- | ---
Installed Deployer | `o.c.c.c.jboss.JBossInstalledLocalDeployer` |  |  |
Embedded Deployer |  |  |  |
Remote Deployer | `o.c.c.c.jboss.JBoss51x6xRemoteDeployer` |  |  |

### Other Features

Feature name | Java API | Ant tasks | Maven 3 plugin | Comment
--- | --- | --- | --- | ---
Debugging |  |  |  |

### Supported Configuration properties

The tables below list both the general configuration properties as well as the container-specific ones.

#### Standalone Local Configuration Properties

##### For installed container o.c.c.c.jboss.JBoss6xInstalledLocalContainer

Property name | Java Property | Supported? | Default value | Javadoc
--- | --- | --- | --- | ---
cargo.hostname | GeneralPropertySet.HOSTNAME |  | `localhost` |
cargo.java.home | GeneralPropertySet.JAVA_HOME |  | JAVA_HOME version 6 or newer Due to incompatibilities with its JSP environment, JBoss 6.x doesn't run on Java 8 and above |
cargo.jboss.ajp.port | JBossPropertySet.JBOSS_AJP_PORT |  | `8009` |
cargo.jboss.classloading.webservice.port | JBossPropertySet.JBOSS_CLASSLOADING_WEBSERVICE_PORT |  | `8083` |
cargo.jboss.configuration | JBossPropertySet.CONFIGURATION |  | `default` |
cargo.jboss.deployer.keepOriginalWarFilename | JBossPropertySet.DEPLOYER_KEEP_ORIGINAL_WAR_FILENAME |  | `false` |
cargo.jboss.ejb3.remoting.port | JBossPropertySet.JBOSS_EJB3_REMOTING_PORT |  | `3873` |
cargo.jboss.invoker.pool.port | JBossPropertySet.JBOSS_INVOKER_POOL_PORT |  | `4445` |
cargo.jboss.jmx.port | JBossPropertySet.JBOSS_JMX_PORT |  | `1091` |
cargo.jboss.jrmp.invoker.port | JBossPropertySet.JBOSS_JRMP_INVOKER_PORT |  | `4444` |
cargo.jboss.jrmp.port | JBossPropertySet.JBOSS_JRMP_PORT |  | `1090` |
cargo.jboss.naming.port | JBossPropertySet.JBOSS_NAMING_PORT |  | `1098` |
cargo.jboss.remoting.transport.port | JBossPropertySet.JBOSS_REMOTING_TRANSPORT_PORT |  | `4446` |
cargo.jboss.transaction.recoveryManager.port | JBossPropertySet.JBOSS_TRANSACTION_RECOVERY_MANAGER_PORT |  | `4712` |
cargo.jboss.transaction.statusManager.port | JBossPropertySet.JBOSS_TRANSACTION_STATUS_MANAGER_PORT |  | `4713` |
cargo.jvmargs | GeneralPropertySet.JVMARGS |  | N/A |
cargo.logging | GeneralPropertySet.LOGGING |  | `medium` |
cargo.port.offset | GeneralPropertySet.PORT_OFFSET |  | `0` |
cargo.process.spawn | GeneralPropertySet.SPAWN_PROCESS |  | `false` |
cargo.protocol | GeneralPropertySet.PROTOCOL |  | `http` |
cargo.remote.password | RemotePropertySet.PASSWORD |  | N/A |
cargo.remote.username | RemotePropertySet.USERNAME |  | N/A |
cargo.rmi.port | GeneralPropertySet.RMI_PORT |  | `1099` |
cargo.runtime.args | GeneralPropertySet.RUNTIME_ARGS |  | N/A |
cargo.servlet.port | ServletPropertySet.PORT |  | `8080` |
cargo.servlet.users | ServletPropertySet.USERS |  | N/A |
cargo.standalone.ignoreNonExistingProperties | GeneralPropertySet.IGNORE_NON_EXISTING_PROPERTIES |  | N/A |
cargo.start.jvmargs | GeneralPropertySet.START_JVMARGS |  | N/A |

Datasource and Resource configuration

In addition to the forementioned properties, this container configuration can also set up datasources and/or resources.

For more details, please read: DataSource and Resource Support.

A side note on the JBoss ports:

- The `cargo.rmi.port` corresponds to the `Port` parameter of the `jboss:service=Naming` bean.
- The `cargo.jboss.naming.port` corresponds to the `RmiPort` parameter of the `jboss:service=Naming` bean.

#### Existing Local Configuration Properties

##### For installed container o.c.c.c.jboss.JBoss6xInstalledLocalContainer

Property name | Java Property | Supported? | Default value | Javadoc
--- | --- | --- | --- | ---
cargo.hostname | GeneralPropertySet.HOSTNAME |  | `localhost` |
cargo.java.home | GeneralPropertySet.JAVA_HOME |  | JAVA_HOME version 6 or newer Due to incompatibilities with its JSP environment, JBoss 6.x doesn't run on Java 8 and above |
cargo.jboss.ajp.port | JBossPropertySet.JBOSS_AJP_PORT |  | `8009` |
cargo.jboss.classloading.webservice.port | JBossPropertySet.JBOSS_CLASSLOADING_WEBSERVICE_PORT |  | `8083` |
cargo.jboss.configuration | JBossPropertySet.CONFIGURATION |  | `default` |
cargo.jboss.deployer.keepOriginalWarFilename | JBossPropertySet.DEPLOYER_KEEP_ORIGINAL_WAR_FILENAME |  | `false` |
cargo.jboss.ejb3.remoting.port | JBossPropertySet.JBOSS_EJB3_REMOTING_PORT |  | `3873` |
cargo.jboss.invoker.pool.port | JBossPropertySet.JBOSS_INVOKER_POOL_PORT |  | `4445` |
cargo.jboss.jmx.port | JBossPropertySet.JBOSS_JMX_PORT |  | `1091` |
cargo.jboss.jrmp.invoker.port | JBossPropertySet.JBOSS_JRMP_INVOKER_PORT |  | `4444` |
cargo.jboss.jrmp.port | JBossPropertySet.JBOSS_JRMP_PORT |  | `1090` |
cargo.jboss.modules.dir | JBossPropertySet.ALTERNATIVE_MODULES_DIR |  | N/A |
cargo.jboss.naming.port | JBossPropertySet.JBOSS_NAMING_PORT |  | `1098` |
cargo.jboss.remoting.transport.port | JBossPropertySet.JBOSS_REMOTING_TRANSPORT_PORT |  | `4446` |
cargo.jboss.transaction.recoveryManager.port | JBossPropertySet.JBOSS_TRANSACTION_RECOVERY_MANAGER_PORT |  | `4712` |
cargo.jboss.transaction.statusManager.port | JBossPropertySet.JBOSS_TRANSACTION_STATUS_MANAGER_PORT |  | `4713` |
cargo.jvmargs | GeneralPropertySet.JVMARGS |  | N/A |
cargo.port.offset | GeneralPropertySet.PORT_OFFSET |  | `0` |
cargo.process.spawn | GeneralPropertySet.SPAWN_PROCESS |  | `false` |
cargo.protocol | GeneralPropertySet.PROTOCOL |  | `http` |
cargo.remote.password | RemotePropertySet.PASSWORD |  | N/A |
cargo.remote.username | RemotePropertySet.USERNAME |  | N/A |
cargo.rmi.port | GeneralPropertySet.RMI_PORT |  | `1099` |
cargo.runtime.args | GeneralPropertySet.RUNTIME_ARGS |  | N/A |
cargo.servlet.port | ServletPropertySet.PORT |  | `8080` |
cargo.start.jvmargs | GeneralPropertySet.START_JVMARGS |  | N/A |

Datasource and Resource configuration

In addition to the forementioned properties, this container configuration can also set up datasources and/or resources.

For more details, please read: DataSource and Resource Support.

#### Runtime Configuration Properties

Before using the JBoss remote deployer, please read: JBoss Remote Deployer

##### For remote container o.c.c.c.jboss.JBoss6xRemoteContainer

Property name | Java Property | Supported? | Default value | Javadoc
--- | --- | --- | --- | ---
cargo.hostname | GeneralPropertySet.HOSTNAME |  | `localhost` |
cargo.jboss.clustered | JBossPropertySet.CLUSTERED |  | `false` |
cargo.jboss.configuration | JBossPropertySet.CONFIGURATION |  | `default` |
cargo.jboss.deployer.keepOriginalWarFilename | JBossPropertySet.DEPLOYER_KEEP_ORIGINAL_WAR_FILENAME |  | `false` |
cargo.jboss.profile | JBossPropertySet.PROFILE |  | `default` |
cargo.remote.password | RemotePropertySet.PASSWORD |  | N/A |
cargo.remote.uri | RemotePropertySet.URI |  | N/A |
cargo.remote.username | RemotePropertySet.USERNAME |  | N/A |
cargo.rmi.port | GeneralPropertySet.RMI_PORT |  | `1099` |

### Tested On

This container is automatically tested by the Continous Integration (CI) system every time there is a code change.
The server used for tests is downloaded from: https://repository.jboss.org/org/jboss/jbossas/jboss-as-distribution/6.0.0.Final/jboss-as-distribution-6.0.0.Final.zip