Questions on bindings-jboss-beans.xml in JBoss 6.1

[michel777]

Hello

I'm coming from Jboss 4.2.3 in which configuration datas, as ports, are made in jboss-service.xml. So, to create an new server on the same physical server, I duplicated default server in a server S and I change its configurations in jboss-service.xml and server.xml (via ant script).

Now, in JBoss 6, ports are set in bindings-jboss-beans.xml into conf/bindingservice.beans/META-INF directory of the server. So, if I copy the default server to create a new server S, and modifiy bindingservice.beans and server.xml in the conf directory of server S, I should obtain the same result than with 4.2.3 version...

My question is what is the goal of the ServiceBindingManager in Jboss6, with the possibility to declare several BindingServiceSet ? I though that the bindings-jboss-beans.xml was unique in the installation and each instance server could use both the default or customized port setting (ports-01, etc.) using the -Djboss.service.binding.set flag and the bind-address flag to specify an IP alias but the copy of the server by default also copy this file bindings-jboss-beans.xml that is no longer unique ...

Thank you for some explanations.

[wdfink]

The meaning is that you might not change the bindings...xml and use the different port-xx with offsets of i.e. 100.

If you try to have different server on the same physical system the server directory 'default' should copied into S1,S2,...

So you have different binding...xml files.

I prefere to use the same ports for all servers if they build a cluster or are production/test etc.

So in JBoss5/6 all ports can be changed by using the bindings file instead of changing different files.

With AS7 you have only one point of configuration

[michel777]

Thank you very much.

I've another question always on the configuration. In Jboss 4.2.3, some parameters as KeepAliveTime, blockingMode, etc in jboss.system:service=ThreadPool bean are no more available in JB6. How can I found their default values ?

There really is not much documentation on JBoss 6 !

Thank you.