To change the "Connector" address

[vjger]

Hi.
From the 4.2.x version, the default "connector" address isn't /0.0.0.0 but /127.0.0.1

I would try to change this value using the web-console.

So, I open System -> JMX Beans -> jboss.web and click on jboss.web:type=Connector,port=8080,address=%2F127.0.0.1

In the right view I've the "address" textfield editable.
So, I change with /0.0.0.0 and I click on Apply Changes.
The right page is reloaded and the new address is correct but, my server, in truth, isn't exposed too toward external clients.
In fact, if I change page clicking on another MBean and after on the Connector Bean, I read /127.0.0.1 again.
Where is my mistake?

Thanks in advance.

[peterj]

The mistake is thinking that changing this value causes the app server to rebind the ports. It doesn't.

If you want to bind to 0.0.0.0, start the app server as follows:

run -b 0.0.0.0

[vjger]

ok...thanks.

But why the "address" field is editable?

[peterj]

Because the address field is initialized from data kept in a configuration file, so the field must be write-able. Consider it a write-once field.

[vjger]

"PeterJ" wrote:
Because the address field is initialized from data kept in a configuration file

I imagine this file is "server.xml".

If so, where and how is valorized the ${jboss.bind.address}?
Is it possible to map more ip addresses?

<Connector port="8080" address="${jboss.bind.address}"
 maxThreads="250" strategy="ms" maxHttpHeaderSize="8192"
 emptySessionPath="true"
 enableLookups="false" redirectPort="8443" acceptCount="100"
 connectionTimeout="20000" disableUploadTimeout="true"/>

Thanks again.

[peterj]

No, you can map only one IP address. This is a limitation of the sockets library (so you cannot blame this one either Java or JBoss AS).

'valorized'? Not sure what you mean. But the typical way to set jboss.bind.address is to start the app server using the -b option, as I mentioned earlier. You could, alternately, set the system property directly:

run -Djboss.bind-address=0.0.0.0

[ag03902]

Peter,

I have a question also, my app is remedy web-tier and it uses the Jboss/jboss tomcat ... I am on 4.0.4 and I cannot keep jboss up and running, also .remedy support told me that if I wanted to run on port 80 that I would need to edit the server.xml file which I did, it comes up and stays up for about 15 minutes or so than jboss goes down whether or not it is on 8080 or 80.

[peterj]

ag03902, please do not post unrelated questions on the end of someone else's post; instead start a new post.