Following holds:
- only required port while creating domain is admin port.
- all the ports required for domain creation can be explicitly specified
while creating domain. setup.xml, chooses a subset of ports for explicit
specification.
- all the ports except admin port have default values.
- if a port is specified explicitly, it must be free else domain
creation fails.
- if a port is not specified, a default value is assumed if the default
is free. If default is not free, a free port is assumed.
Answer to your question: if you modify the setup.xml to search+replace
the (explicitly specified) ports so that they are free, you will not
have conflicts.
If one the other hand, you:
- create a vanilla domain.
- search+replace domain.name and ports and create another domain.
- start II domain.
- then attempt to start I domain.
The I domain will cease to start.
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
>