Performance Issues with Jboss7 Domain Setup

[ahmedkbn]

Hi All,

I need your help to resolve below issue.

1.We have two linux boxes.

2.First machine is running domain Controller

3. Second machine is running a host controller.

Processes running on First Machine

jboss

13499 13457  0 14:45 pts/0

00:00:01 /app/jdk1.6.0_24/bin/java -D[Process Controller]

jboss

13514 13499  1 14:45 pts/0

00:00:13 /app/jdk1.6.0_24/bin/java -D[Host Controller]

Processes running on Second Machine

jboss

14475 21934  1 15:06 ?

00:00:10 /app/jdk1.6.0_24/bin/java -D[Server:ha-server-1]

jboss

21934 21892  0 Apr28 ?

00:37:24 /app/jdk1.6.0_24/bin/java -D[Process Controller]

jboss

21949 21934  0 Apr28 ?

00:42:28 /app/jdk1.6.0_24/bin/java -D[Host Controller]

This is the configuration on Second machine host.xml

  <servers>

        <server name="ha-server-1" group="ha-server-group" auto-start="true">

            <socket-bindings socket-binding-group="standard-sockets" port-offset="100"/>

        </server>

My question is When i start a host controller on Second machine what is the need for these two processes to get started i.e. Process controller & Host controller Since we are deploying our application only on Server:ha-server-1. These two processes consume memory on the server as we cannot deploy any applications on them. Is this an domain mode architecture issue?

My understanding is that Process controller & Host controller processes must be running on the second machine in order to run in domain mode. Please clarify.

only one process should be running on the second machine i.e.Server:ha-server-1. I have limited RAM available on the server and its causing permormance issues on the server. Please advise me an optimizaed setup.

Thanks In advance

[wdfink]

Hello and welcome to the forum

In your case it is not clear to me why you use the domain mode.

The domain mode is only a administrative help for central configuration and process monitoring.

Host and Process controller will do that work.

In you case the DC will run only admin processed and the second the admin processes plus the 'real' server.

If you do not use the central configuration (as there is only one server) or the process monitoring (auto restart in case of crash) it sound like overkill and you should start the server in standalone mode which only run one JVM, also you only need one machine in this case.

But if you want a domain you can slim down the memory usage of host/process controller. See the domain.conf script for memory settings^, you might overwrite the settings by using the HOST_CONTROLLER* or PROCESS_CONTROLLER_JAVA_OPTS.

[ahmedkbn]

Hi Wolf,

Thanks for your comment.

I am using the domain mode setup to acheive the following.

Domain controller on first machine will manage (meaning start/stop/deploy) the Server:ha-server-1 on second machine. But i dont know how to setup this. I want to see only one jboss process running on second machine.

You can see in the below output. 3 jboss instances are getting created on second machine.

jboss

14475 21934  1 15:06 ?

00:00:10 /app/jdk1.6.0_24/bin/java -D[Server:ha-server-1]

jboss

21934 21892  0 Apr28 ?

00:37:24 /app/jdk1.6.0_24/bin/java -D[Process Controller]

jboss

21949 21934  0 Apr28 ?

00:42:28 /app/jdk1.6.0_24/bin/java -D[Host Controller]

Can i setup host controller(Server:ha-server-1) on second machine without running Process controller & Host controller there?

Thanks again

[ahmedkbn]

Hi,

I think i found what i was looking for at http://blog.akquinet.de/2012/06/29/managing-cluster-nodes-in-domain-mode-of-jboss-as-7-eap-6/.

Conclusion is that each host will have a Host controller and a Process controller plus the 'real' servers.

[wdfink]

Na as I said the HC and PC are necessary in domain mode.

In your case you can deploy with the CLI (bin/jboss-cli.sh) to your server group. But again you do not need a domain for that.

If you want to be able to start and stop the server remote you can use a domain, but here you only need to have one DC, than the server will run at the same machine as the main domain controller.

You can find the domain explanation and more in this document