Hi Asankha,

thanks for your reply. Please see my comments below.

> > regarding the other issue with the bind addresses it would be nice
if
> you could provide a complete list of all LISTEN ports of the WSO2 ESB
> including a description of how to configure the bind address. As I
found
> out, I currently only know hot to configure the binding address of the
> http as well as the https listeners.
> >
> Standalone Tomcat
>  - Admin console port (https) - 9444 (tomcat.properties)
> 
> Transports
>  - http - 8280 (axis2.xml)
>  - https - 8243 (axis2.xml)
> 
> Clustering Lieten port - 4000 (axis2.xml)
> 
> RMI Registry port for JMX - 1099 (server.xml)
> 
> Embedded Database (Derby) port - 1528 (server.xml - started if
> "StartEmbeddedDerby" is "true")
> 
> In addition, if you use the DataSource definition feature on the
> synapse.properties file, you may configure to use the provider over
port
> 2199

This list does not seem to be complete to me. If I do something like:
lsof -p 29600 | grep LISTEN 
where 29600 is the pid of the ESB process, I get the following output:

50147945                TCP localhost:32000 (LISTEN)
50147963                TCP *:47401 (LISTEN)
50147965                TCP *:11817 (LISTEN)
50147972                TCP *:11816 (LISTEN)
50148005                TCP *:11815 (LISTEN)
50148022                TCP FULL_QUALIFIED_HOSTNAME_REMOVED:11812
(LISTEN)
50148023                TCP FULL_QUALIFIED_HOSTNAME_REMOVED:11811
(LISTEN)
50148031                TCP *:11810 (LISTEN)


We changed the default ports like that:
Standalone Tomcat https amdin console -> 11810
http listener -> 11811
https listener -> 11812
RMI Registry (JMX)-> 11815
Wrapper Remote (JMX) -> 11816
RMI Registry for DB Connection Pools -> 11817
Tanuki Service Wrapper -> 32000
???? -> 47401 (this port seems to be dynamic, possibly a DGC Client)

Clustering is not activated, Derby is deactivated.

Any chance to get some info about the last one? We need to be able to 
define all LISTEN-ports and bind them to a specific IP.
I could not find details in your mail about how to configure the bind
address for these services. Right now I only know how to do it for the
transports.

Regards,
   Eric

PS: I like the idea of a wiki page or better a documentation setting as
these are typical questions when it goes to deployment.

_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev

Reply via email to