Just yesterday, we had a customer with multiple domains on a single
Windows box run into an issue where Windows decided to allocate client
port numbers used by one domain, to connect to JMS, in a range needed
for TCP services that were needed for another domain on startup. This
caused the domain startup to fail.
This happened during a failover, and their failover strategy had a
primary and a secondary. Their strategy was to fail over to the
secondary, fix the primary, and then fail back over to the primary.
Interestingly, there was a port conflict on the same port on both
primary and secondary servers for the same port number: the range
Windows chose to use was the same. The JMS for the first domain was
listening on 15007, and a client connection was made /consistently/, on
both servers, from 15104, an allocation controlled by the OS. Because of
this, the second domain was not then able to open a listening port on 15104.
Regards
Jason
On 1/25/2011 11:17 AM, Bobby Bissett wrote:
> That makes sense, but wouldn't the domain that was just stopped also be listening on those ports, so if there were a conflict it should already have happened? In the case you mention, I think it'd be more exact to say "shut down the domain to be upgraded, and then don't start any new ones that conflict," but it's simpler to keep the text as-is and shut everything down.
>
> Thanks,
> Bobby
>
> On Jan 25, 2011, at 1:08 PM, Tom Mueller wrote:
>
>
>> A running domain might be listening on ports that might be needed by the domain being upgraded.
>> Tom
>>
>> On 1/25/2011 12:00 PM, Bobby Bissett wrote:
>>
>>> Howdy,
>>>
>>> In the upgrade guide we suggest "Ensure that you have stopped all domains in the source server before you start the upgrade process." But I'm wondering if the user only needs to stop the domain that is going to be upgraded. Can a running domainX do anything to the configuration of a domainY?
>>>
>>> It's probably safest all around to shut everything down, but I'm curious if it's truly necessary.
>>>
>>> Cheers,
>>> Bobby
>>>
>>>
>
>