axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amir Mousavizadegan" <amir.mousavizade...@cox.net>
Subject Re: Help needed with Axis2/C 1.6.0
Date Mon, 15 Nov 2010 18:36:37 GMT
Usage : ...bin\tools\tcpmon.exe [-lp LISTEN_PORT] [-tp TARGET_PORT] [-th 
TARGET_HOST] [-f LOG_FILE][options]

 Options :
        -lp LISTEN_PORT         port number to listen on, default is 9099
        -tp TARGET_PORT         port number to connect and re-direct 
messages, default is 9090
        -th TARGET_HOST         target host to connect, default is localhost
        -f  LOG_FILE            file to write the messages to, default is 
tcpmon_traffic.log
        --format                enable xml formatting
        --test                  enable testing last request/response by 
loggingit separately
 Help :
        -h                      display this help screen.


----- Original Message ----- 
From: "Mystery Admin" <mysteryadmin@comcast.net>
To: "Apache AXIS C User List" <c-user@axis.apache.org>
Sent: Monday, November 15, 2010 1:12 PM
Subject: Re: Help needed with Axis2/C 1.6.0


> Thanks!  I'll give this a whirl.  Will the TCPMON documentation discuss
> configuring it as a proxy?
>
> Thanks!
>
> Peace...
>
> Tom
>
> On 11/15/2010 09:59 AM, Amir Mousavizadegan wrote:
>> Try to set a proxy between your  client session and server by using
>> TCPMON as a  proxy, thus you will be able to see  exchanging payload.
>>
>> Amir
>>
>> ----- Original Message ----- From: "Mystery Admin"
>> <mysteryadmin@comcast.net>
>> To: <c-user@axis.apache.org>
>> Sent: Monday, November 15, 2010 12:45 PM
>> Subject: Help needed with Axis2/C 1.6.0
>>
>>
>>> Hi!  So, I'm using Axis2/C 1.6.0 on a Solaris 10 (SPARC) system to
>>> connect to a third party web service also running on the Solaris system.
>>>
>>> I am using this tutorial:
>>>
>>> http://wso2.org/library/3534#step5
>>>
>>> to use the WSDL2C tool to process the WSDL file supplied by the third
>>> part web service developer and generate the C code I'll need for my
>>> application.
>>>
>>> Right now, I have everything built and integrated into my application.
>>> When I try to get connected to the web service, it appears to crash on
>>> the server side and I need to find out why.  Of course, I'm not posting
>>> to this list to get help with troubleshooting the server-side of this
>>> but I'm looking for client-side debugging tips to make sure the info I'm
>>> sending out is correct.  I do have a log file generated and it indicates
>>> some kind of unknown error occurred.
>>>
>>> Is there a way to see the actual request being sent by the Axis2/C
>>> client-code?  Must I use a network packet sniffer or can the request
>>> being sent be logged somehow?  I want to make sure the endpoint URI is
>>> correct and so on.
>>>
>>> Thanks!
>>>
>>> Peace...
>>>
>>> Tom
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: c-user-help@axis.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
>> For additional commands, e-mail: c-user-help@axis.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: c-user-help@axis.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
For additional commands, e-mail: c-user-help@axis.apache.org


Mime
View raw message