We're updating the issue view to help you get more done. 

Missing port properties with JBoss 7.2.0

Description

When creating a standalone JBoss 7.2.0 configuration, some port properties are not available is cargo configuration. The list of JBoss ports is available in the "socket-binding-group" of the standalone.xml JBoss file.

One of these missing properties is mandatory, because used in default configuration, thus JBoss cannot start if another instance is already running. Error is "Address already in use: bind /127.0.0.1:9990".
This port is the "management-http" (default is 9990), used for the JBoss console.
Please note that Cargo already defines a "cargo.jboss.management.port", but it refers to the "management-native" (default 9999) JBoss socket-binding.

Other missing ports are "https" (default 8443), "management-https" (default 9443), "txn-recovery-environment" (default 4712)and "txn-status-manager" (default 4713). Don't know if these are needed, as I'm not using them.

Regards,
Bernard

Status

Assignee

Savas Ali Tokmen

Reporter

S. Ali Tokmen

Components

Fix versions

Affects versions

1.4.3

Priority

Minor