Dinesh Patil wrote:
> Vince,
> These 5 ports are the configurable ports available through CLI,
actually, all the ports are configurable through the CLI.
> so we are passing these ports to asadmin to create new domain from
> setup.xml.
If these ports are in use, the create-domain fails, right?
> Other ports aren't be configurable so can be picked up free ports by
> the domain creation,
Why do we want the create-domain command to fail if there is a conflict
on one of the 5 specified ports and succeed if there is a conflict
between the "default value" and the currently available ports for the
other 3 ports?
It just doesn't make sense to me.
> but I will leave this to admin domain experts to confirm if won't be a
> conflict.
> thanks
> Dinesh
>
> vince kraemer wrote:
>
>> I just noticed that setup.xml has values defined for 5 ports.
>>
>> I looked in the domain.xml and it looks like there are 8 ports used.
>>
>> If a user downloads, runs ant -f setup.xml, changes the domain.name
>> and *.port properties define in setup.xml to avoid conflicts and
>> runs ant -f setup.xml again, will they be free from port conflicts if
>> they start both instances?
>>
>> vbk
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>