You are viewing a plain text version of this content. The canonical link for it is here.
Posted to kandula-dev@ws.apache.org by Jimmy <ma...@live.cn> on 2008/03/10 04:04:23 UTC

Two questions about Kandula2

Hi, everyone:
  First, I want to take a look at messages exchanged in Kandula2 ,but how? I've tried tcpmonitor, but it doesn't work well.
    Second, I found a file named endpoints.conf which contains ten properties. Can anybody tell me what does these properties stand for and how they are used, espeically for these four:
    host=127.0.0.1
    port=8081
    tcpmon_enable=false
    KANDULA_LISTENER_PORT=5050

  Thanks in advance!

Re: Two questions about Kandula2

Posted by Thilina Gunarathne <cs...@gmail.com>.
Hi,

>     Second, I found a file named endpoints.conf which contains ten
> > properties. Can anybody tell me what does these properties stand for and
> how
> > they are used, espeically for these four:
> >     host=127.0.0.1
>
This is your coordinator's address.. We made it configurable so that you can
specify it, if proxy or DNS is used. We use this address when setting
replyTo Epr in messages. <http://127.0.0.1>
>     port=8081
This is the port which will be used when setting the replyTo EPR for
messages. If you deployed Kandula2 in Tomcat under 8080 and then had this as
8081, then you can add a mapping to tcpmon from 8081 to 8080 to monitor the
messages coming to server from the services.
>     tcpmon_enable=false
>     KANDULA_LISTENER_PORT=5050
Kandula2 sets up a listener in the client side to listen for the outcome.
Kandula sets up the listener in the given port. When tcpmon_enable is
"true", kandula sets up the listener in the given port, but add a 1 to the
port number used in registering with the coordinator, so that you can
monitor the messages using tcpmon. In the above settings you have to enable
is to true, add a tcpmon mapping from 5051 to 5050..

thanks,
Thilina

I'm not familiar with Kandula2 but my guess would be that host/port tells
> where
> to send messages addressed to the axis2 server and 5050 indicates where
> the
> axis2 client is listening. I could be wrong.
>
> If possible, try Kandula1, for that is more tested.
>
> -- dasarath
>
> >
> >   Thanks in advance!
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>


-- 
Thilina Gunarathne - http://thilinag.blogspot.com

Re: Two questions about Kandula2

Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Jimmy <ma...@live.cn>:

> Hi, everyone:
>   First, I want to take a look at messages exchanged in Kandula2 ,but how?
> I've tried tcpmonitor, but it doesn't work well.

Could you please describe the problem with tcpmonitor? I do not think there is
an alternative. Any problem if tcpmonitor needs to go to axis(2?)-user list.

>     Second, I found a file named endpoints.conf which contains ten
> properties. Can anybody tell me what does these properties stand for and how
> they are used, espeically for these four:
>     host=127.0.0.1
>     port=8081
>     tcpmon_enable=false
>     KANDULA_LISTENER_PORT=5050


I'm not familiar with Kandula2 but my guess would be that host/port tells where
to send messages addressed to the axis2 server and 5050 indicates where the
axis2 client is listening. I could be wrong.

If possible, try Kandula1, for that is more tested.

-- dasarath

> 
>   Thanks in advance!



---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org