Oliver:
I am a bit confused.
Is this how things work (It is similar to FTP):
I go t the CLC of a controller (lets say controller 1)
and tell it to transfer a dump to controller 2. When
I tell controller 1 to do the transfer, I give it the
IP address and JMX port of controller 2.
Controller 1 communicates with controller 2 (Using its
JMX port) to tell it to receive the dump.
Then, controller 2 binds to a port (choosing one dynamically)
and tells controller 1 which port it is listening on.
Controller 1 then connects to that port to transfer
the data for the dump to controller 2.
Is this how it works?
Thanks,
Neil
--
Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
FREE! Eliminate junk email and reclaim your inbox.
Visit http://www.spammilter.com for details.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Olivier Fambon
> Sent: Wednesday, October 25, 2006 12:18 PM
> To: Sequoia general mailing list
> Subject: Re: [Sequoia] Network layout for two geographically
> separate machines
>
> Neil Aggarwal wrote [10/25/2006 07:01 PM]:
> >
> > Regarding the backupers, it looks like they use
> > the JMX port on the remote controllers so I need
> > remote access to a total of 3 ports.
> >
> > Am I missing something?
> >
>
> Well, except if by some sort of magic the JMX infrastructure
> managed to
> eat the backupers private system, backup and jmx ports are un-related.
>
> You have indeed 3 'well known' _fixed_ ports per controller
> (jdbc, jmx
> and group-comm), plus a dynamic server port when you do a
> transfer dump.
> The temporary dump-server server socket is bound to null, the
> effective
> port number is left to the system to choose...
>
>
> A+O.
>
> _______________________________________________
> Sequoia mailing list
> [email protected]
> https://forge.continuent.org/mailman/listinfo/sequoia
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
