Cargo

Unable to set bind address to 0.0.0.0 when starting jboss

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.0.1-beta-1
  • Fix Version/s: 1.0.1-beta-2, 1.0.1-beta-3, 1.0.1
  • Component/s: JBoss
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

To allow jboss to be accessed from remote machines, it must be started with the arguments -b 0.0.0.0 or --host 0.0.0.0. The cargo plugin automatically sets the --host argument to the value of cargo.hostname.

When the cargo.hostname is set to 0.0.0.0, jboss will start up correctly and will be accessible remotely, but will be shutdown because the cargo plugin thinks it failed to startup – it is trying to access a page at the non-existent address http://0.0.0.0:8282/cargo

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. CARGO-1111 Unable to set bind address to 0.0.0.0 when starting JBoss 7.1.x

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Savas Ali Tokmen added a comment -

Attached correction: if the container's JVM arguments parameter contains --host, then the CARGO container will not set the hostname.

As a result, in order to use:

1. In the CARGO configuration, set the hostname
2. In the CARGO configuration's JVM arguments parameter, add in --host 0.0.0.0

Please close issue if satisfied

Show
Savas Ali Tokmen added a comment - Attached correction: if the container's JVM arguments parameter contains --host, then the CARGO container will not set the hostname. As a result, in order to use: 1. In the CARGO configuration, set the hostname 2. In the CARGO configuration's JVM arguments parameter, add in --host 0.0.0.0 Please close issue if satisfied
Hide
Permalink
Savas Ali Tokmen added a comment -

Committed revision 2090.

Show
Savas Ali Tokmen added a comment - Committed revision 2090.
Hide
Permalink
Mark Howard added a comment -

Thanks for the super-quick patch.
--host isn't a valid jvm argument, so the jvm fails to start with the supplied patch. I think it should work if changed to check cargo.runtime.args instead of jvmargs though. It might also be better to check for 0.0.0.0 explicitly - most jboss documentation refers to setting -b 0.0.0.0 rather than --host 0.0.0.0.

Show
Mark Howard added a comment - Thanks for the super-quick patch. --host isn't a valid jvm argument, so the jvm fails to start with the supplied patch. I think it should work if changed to check cargo.runtime.args instead of jvmargs though. It might also be better to check for 0.0.0.0 explicitly - most jboss documentation refers to setting -b 0.0.0.0 rather than --host 0.0.0.0.
Hide
Permalink
Savas Ali Tokmen added a comment - - edited

You're right. Can you please try revision 2092 ?

    // CARGO-758: To allow JBoss to be accessed from remote machines,
    // it must be started with the arguments -b 0.0.0.0 or --host 0.0.0.0
    //
    // As a result, allow the --host or -b to be different than GeneralPropertySet.HOSTNAME
    final String runtimeArguments = getConfiguration().getPropertyValue(GeneralPropertySet.RUNTIME_ARGS);
    if (runtimeArguments == null ||
       (!runtimeArguments.contains("--host 0.0.0.0") && !runtimeArguments.contains("-b 0.0.0.0")))
    {
        java.createArg().setValue(
            "--host=" + getConfiguration().getPropertyValue(GeneralPropertySet.HOSTNAME));
    }
Show
Savas Ali Tokmen added a comment - - edited You're right. Can you please try revision 2092 ? // CARGO-758: To allow JBoss to be accessed from remote machines, // it must be started with the arguments -b 0.0.0.0 or --host 0.0.0.0 // // As a result, allow the --host or -b to be different than GeneralPropertySet.HOSTNAME final String runtimeArguments = getConfiguration().getPropertyValue(GeneralPropertySet.RUNTIME_ARGS); if (runtimeArguments == null || (!runtimeArguments.contains("--host 0.0.0.0") && !runtimeArguments.contains("-b 0.0.0.0"))) { java.createArg().setValue( "--host=" + getConfiguration().getPropertyValue(GeneralPropertySet.HOSTNAME)); }
Hide
Permalink
Mark Howard added a comment -

I will try the new revision as soon as I can. At the moment, it is failing to build with checkstyle violations. I'll try to workaround these for now.
The top-level pom also refers to an old version of the parentpom (4.2-SNAPSHOT rather than 4.3-SNAPSHOT), which caused a few problems with the build (I've never built cargo before)

Show
Mark Howard added a comment - I will try the new revision as soon as I can. At the moment, it is failing to build with checkstyle violations. I'll try to workaround these for now. The top-level pom also refers to an old version of the parentpom (4.2-SNAPSHOT rather than 4.3-SNAPSHOT), which caused a few problems with the build (I've never built cargo before)
Hide
Permalink
Savas Ali Tokmen added a comment -

Fixed the checkstyle violations revision 2093

Sorry for the inconvenience

Show
Savas Ali Tokmen added a comment - Fixed the checkstyle violations revision 2093 Sorry for the inconvenience
Hide
Permalink
Mark Howard added a comment -

This works perfectly now, thanks.
I don't have permissions to close items in this jira, but think it is ok to be closed.

Show
Mark Howard added a comment - This works perfectly now, thanks. I don't have permissions to close items in this jira, but think it is ok to be closed.
Hide
Permalink
Savas Ali Tokmen added a comment -

OK, closing it for you

Thank you for the quick testing

Show
Savas Ali Tokmen added a comment - OK, closing it for you Thank you for the quick testing

People

  • Assignee:
    Savas Ali Tokmen
    Reporter:
    Mark Howard
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: