Am Dienstag, 27. November 2007 schrieb Olivier Fambon:
> BESSON-DEBLON, Pierre (SOGETI HIGH TECH) [27/11/07 16:55]:
> > Hi,
> >
> > I try to identify ports used by sequoia.
> > I have already identified those ones :
> > - controller port (used by clients in JDBC URL), customizable in
> > controller.xml
> > - jmx port (console, dumps), customizable in controller.xml
> > - jgroups communication (GMS logged on controller startup),
> > customizable in sequencer.xml
> > - hsql port (recovery log), customizable on server startup
> >
> > What are the others ?
>
> Just a quick note:
>
> you will want to watch out for the dump server port, in case you
> transfer dumps. These are allocated dynamically by default upon
> each dump transfer, but can be fixed in the dumpServer option of
> your backuper specification - in vdb.xml.
>
> Search the ML, there is a patch there - and a jira entry IIRC - if
> the code did not make it to the release.
You have also to watch out that the controller port has to be open for
TCP *and* UDP. Otherwiese your connection will be closed by the
jdbc-Driver that is trying to ping the controller via UDP.
Regards
Joachim von Thadden
--
Joachim von Thadden
Manager Projekte
Linux Information Systems AG
Ehrenbergstr. 19, 10245 Berlin
Fon: +49 30 726238-19, Fax: +49 30 726238-99
[EMAIL PROTECTED], http://www.linux-ag.com
_______________________________________________________________
Sitz der Gesellschaft: Stefan-George-Ring 8, 81929 München
Amtsgericht München: HRB 128 019
Vorstand: Rudolf Strobl, Sebastian Hetze
Aufsichtsrat: Michael Tarabochia (Vorsitzender)
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
