[jboss-as7-dev] Confusion with arguments for domain.sh, domain controller vs. process controller

[Brian Stansberry]

https://issues.jboss.org/browse/AS7-1863

On 9/19/11 8:07 AM, Rostislav Svoboda wrote:
> Hi Brian.
>
> I tried --pc-port and --interprocess-hc-port args on build from today's sources.
> Argument --pc-port is working as expected, but parameter from --interprocess-hc-port argument isn't reflected. Help says it's port on which the host controller should listen for communication from the process controller.
>
> Shouldn't be there connection 127.0.0.1:11111<-->  127.0.0.1:22222 in my example below ?
>
> $ ./bin/domain.sh --pc-port=11111 --interprocess-hc-port=22222
>
> $ netstat -natup | grep java
> tcp        0      0 127.0.0.1:9999              0.0.0.0:*                   LISTEN      31299/java
> tcp        0      0 127.0.0.1:8080              0.0.0.0:*                   LISTEN      31329/java
> tcp        0      0 127.0.0.1:1240              0.0.0.0:*                   LISTEN      31335/java
> tcp        0      0 127.0.0.1:1241              0.0.0.0:*                   LISTEN      31335/java
> tcp        0      0 127.0.0.1:1090              0.0.0.0:*                   LISTEN      31329/java
> tcp        0      0 127.0.0.1:1091              0.0.0.0:*                   LISTEN      31329/java
> tcp        0      0 127.0.0.1:8230              0.0.0.0:*                   LISTEN      31335/java
> tcp        0      0 127.0.0.1:9990              0.0.0.0:*                   LISTEN      31299/java
> tcp        0      0 127.0.0.1:11111             0.0.0.0:*                   LISTEN      31284/java
> tcp        0      0 127.0.0.1:11111             127.0.0.1:49368             SPOJENO     31284/java
> tcp        0      0 127.0.0.1:9999              127.0.0.1:45597             SPOJENO     31299/java
> tcp        0      0 127.0.0.1:45597             127.0.0.1:9999              SPOJENO     31329/java
> tcp        0      0 127.0.0.1:48827             127.0.0.1:9999              SPOJENO     31335/java
> tcp        0      0 127.0.0.1:49368             127.0.0.1:11111             SPOJENO     31299/java
> tcp        0      0 127.0.0.1:9999              127.0.0.1:48827             SPOJENO     31299/java
>
> NOTE: SPOJENO == ESTABLISHED, PID 31284 is process-controller, PID 31299 is host-controller
>
>
> Rosta
>
> ----- Original Message -----
>> Try building this branch:
>>
>> https://github.com/jbossas/jboss-as/pull/285
>>
>> It has fixes for your recent issues and changes the help text a bit.
>>
>> These settings would be rarely used. When you run domain.sh you
>> create a
>> process called the ProcessController; that process spawns the
>> HostController process and the process for any servers. The PC uses
>> sockets to talk to those processes, by default on localhost and
>> ephemeral ports. If you don't like that you can use these switches to
>> change that.
>>
>> On 9/14/11 6:53 AM, Rostislav Svoboda wrote:
>>> Hi Brian.
>>>
>>> ****** Arguments for domain.sh command
>>>
>>> I have problem to understand some arguments for domain.sh command:
>>>
>>>        --pc-address=<address>                Address of process
>>>        controller socket
>>>        --pc-port=<port>                      Port of process
>>>        controller socket
>>>
>>>        --interprocess-name=<proc>            Name of this process,
>>>        used to register the socket with the server in the process
>>>        controller
>>>        --interprocess-hc-address=<address>   Address this host
>>>        controller's socket should listen onr
>>>        --interprocess-hc-port=<port>         Port of this host
>>>        controller's socket  should listen on
>>>
>>> For example --pc-address and --pc-port are dynamically generated
>>> for host-controller process and when I run for example
>>> ./bin/domain.sh --pc-port 50123 I receive
>>> java.net.ConnectException: Connection refused.
>>>
>>> Are these options really meant to be public? Could you please
>>> provide use cases when it's beneficial to use them? There is no
>>> information on https://docs.jboss.org/author/display/AS7/.
>>>
>>>
>>>
>>> ****** Domain Controller vs. Process Controller
>>>
>>> When I start domain.sh command, 4 new java processes are crated.
>>>
>>> [rsvoboda at rosta-ntb jboss-as7]$ ps aux | grep java
>>>
>>> 1) Process containing 'org.jboss.as.process-controller' - this
>>> seems to be the main process.
>>>
>>> I'm using Domain Controller term when speaking about main process.
>>> Is Process Controller equivalent to Domain Controller?
>>>
>>> Logging+configuration are speaking about Process Controller.
>>> Getting+started+with+JBoss+AS is speaking about Domain Controller.
>>> Getting+Started+Guide is speaking about both Domain and Process
>>> Controller.
>>>
>>>
>>> 2) Process containing 'org.jboss.as.host-controller' - process for
>>> host controller
>>>
>>> Just occurred to me - Isn't Host Controller on main instance called
>>> Domain Controller and Process Controller is only a glue?
>>>
>>> This process has defined '--pc-address rosta-ntb --pc-port 34876'
>>> and it seems it can't be overridden as mentioned before.
>>>
>>>
>>> 3+4) 2 process for server-one and server-two.
>>>
>>>
>>> Maybe adding description of java processes to the Admin Guide would
>>> be nice.
>>>
>>>
>>> Thanks,
>>> Rosta
>>
>>
>> --
>> Brian Stansberry
>> Principal Software Engineer
>> JBoss by Red Hat
>>


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat