Hi Dimuthu, Client -> ESB -> Axis2 Server
In the above scenario ESB is acting as a server as well as a client. 1. Client -> ESB (ESB Acting as a server) 2. ESB -> Axis2 Server (ESB Acting as a client) So 50239 might be the be the Ephemeral port of ESB when it is communicating with axis2 server. On Sat, Nov 30, 2013 at 7:34 PM, Dimuthu Upeksha <[email protected]> wrote: > Hi all, > > I'm an intern of WSO2. I am going through several tutorials about WSO2 ESB > and managed to test some samples given in [1]. As given in the tutorial I > was able to simulate message mediating done in ESB. Then I captured the > packets that are transferred through localhost using Wireshark [2]. I could > see three ports involved in the process. > Port 9000 : Listener port of Axis 2 server > Port 8280 : Port of ESB (I think so) > Port 50238 : Port of the client > Port 50239 : I have no idea about this port however it seems like another > port of the client > > At the first set of packets I could see that client is communicating with > the ESB and ESB is communicating with the Axis2 server : which is legal. > But at the end I could see that Port 50239 is communicating directly with > 9000 (Packet no 11). Is this legal? Shouldn't it communicate with port > 8280? If client communicate with the server directly what is the role of > ESB as a message mediator? Correct me if I'm wrong. > > Thank you > > Best Regards > > [1] http://docs.wso2.org/display/ESB470/Lesson+Two%3A+Mediating+Messages > [2] https://www.dropbox.com/s/skxozdvu61kyd0c/packet_capture > > Dimuthu Upeksha > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Isuru Udana* Senior * Software Engineer* WSO2 Inc.; http://wso2.com email: [email protected] cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ twitter: http://twitter.com/isudana
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
