[#CARGO-405] System properties does not set in standalone configuration - jira.codehaus.org

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Not A Bug
Affects Version/s: 0.2-maven2
Fix Version/s: None
Component/s: JBoss
Labels:
None
Environment:
Maven 2.0.4, JDK 1.5.0_06

Complexity:
Intermediate
Number of attachments :
0

Description

I need to set jboss.bind.address property on start of a standalone configuration. The folloging config does not work:

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Vincent Massol added a comment - 01/Sep/06 4:04 AM

The only thing that <systemProperties> does is to set the system property in the JVM, i.e. the equivalent of -Djboss.bind.address=127.0.0.1.

I don't believe there's any bug with system property support in Cargo. If setting the jboss.bind.property in this manner is correct and it's nor working it probably has to do with the jboss configuration but not with system property support I believe.

I need your help here as I have no idea what jboss.bind.address does nor how to use it.

Show

Vincent Massol added a comment - 01/Sep/06 4:04 AM The only thing that <systemProperties> does is to set the system property in the JVM, i.e. the equivalent of -Djboss.bind.address=127.0.0.1. I don't believe there's any bug with system property support in Cargo. If setting the jboss.bind.property in this manner is correct and it's nor working it probably has to do with the jboss configuration but not with system property support I believe. I need your help here as I have no idea what jboss.bind.address does nor how to use it.

Hide

Permalink

Alexey Kharlamov added a comment - 01/Sep/06 9:03 AM

Several parameters of JBoss container can be adjusted by setting java system properties.
For example, jboss.bind.address can be used to specify which host's interface to use to listen for incoming requests.

So to start up jboss on local loopback only you can use following command:

./run.sh -Djboss.bind.address=127.0.0.1

The -D<> parameters is passed by JVM directly. So on jboss load procedure the property value is used to override
default parameters.

This technique is used for in several places in jboss and by some JEE application (Sync4j for example). So
in general case there is a need a way to set system property on jboss startup. However, in standalone
configuration

Show

Alexey Kharlamov added a comment - 01/Sep/06 9:03 AM Several parameters of JBoss container can be adjusted by setting java system properties. For example, jboss.bind.address can be used to specify which host's interface to use to listen for incoming requests. So to start up jboss on local loopback only you can use following command: ./run.sh -Djboss.bind.address=127.0.0.1 The -D<> parameters is passed by JVM directly. So on jboss load procedure the property value is used to override default parameters. This technique is used for in several places in jboss and by some JEE application (Sync4j for example). So in general case there is a need a way to set system property on jboss startup. However, in standalone configuration

Hide

Permalink

Alexey Kharlamov added a comment - 01/Sep/06 9:04 AM

this does not work.

Show

Alexey Kharlamov added a comment - 01/Sep/06 9:04 AM this does not work.

Hide

Permalink

Neill Alexander added a comment - 31/Jul/07 11:32 AM

I had a similar issue, trying to run JBoss with support for debugging via 'mvn cargo:start'.

At first I used:

<systemProperties>
<JAVA_OPTS>-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005</JAVA_OPTS>
</systemProperties>

This didn't work. After some experimentation I discovered that the following works:

<configuration>
<properties>
<cargo.jvmargs>-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005</cargo.jvmargs>
</properties>
</configuration>

Maybe this would also resolve the problem reported above for jboss.bind.address?

Show

Neill Alexander added a comment - 31/Jul/07 11:32 AM I had a similar issue, trying to run JBoss with support for debugging via 'mvn cargo:start'. At first I used: <systemProperties> <JAVA_OPTS>-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005</JAVA_OPTS> </systemProperties> This didn't work. After some experimentation I discovered that the following works: <configuration> <properties> <cargo.jvmargs>-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005</cargo.jvmargs> </properties> </configuration> Maybe this would also resolve the problem reported above for jboss.bind.address?

Hide

Permalink

Savas Ali Tokmen added a comment - 08/May/10 6:01 PM

As reported, please use cargo.jvmargs instead.

As of version 1.0.1-beta-1, you can even put multiline JVM arguments in your pom file, rendering the XML much more readable.

Show

Savas Ali Tokmen added a comment - 08/May/10 6:01 PM As reported, please use cargo.jvmargs instead. As of version 1.0.1-beta-1, you can even put multiline JVM arguments in your pom file, rendering the XML much more readable.

People

Assignee:

Unassigned

Reporter:

Alexey Kharlamov

Vote (1)

Watch (2)

Dates

Created:

01/Sep/06 2:06 AM

Updated:

08/May/10 6:01 PM

Resolved:

08/May/10 6:01 PM