Hi Oscar

what states the servers log if any created? 

you're saying that the second send() goes out, 

is it received at the servers end?

is it received at the servers method end?

if yes what does the method do with the second request? 

will it just return the payload as an echo too? 

In this case can you see the incoming second response as soap/xml data on the 
wire.

 

Also for ease of use, unless really required, 

I would suggest to use TCP Monitor to watch the wire transfer. 

You can see much better the soap/xml traffic on the wire than with Wireshark.

Nothing against Wireshark, both a very OK.

Josef

 

Von: Oscar Pernas [mailto:os...@pernas.es] 
Gesendet: Dienstag, 26. Februar 2013 12:54
An: c-user@axis.apache.org
Betreff: send_receive blocking

 

Hi all,

 

Im using axis2c trunk version, over Windows 7, and I'm falling into a problem 
with axis2_svc_client_send_receive method.

 

I have a class in c++ where I'm using axis2c api. I have a method init where I 
made all initializations, and a method run where I made the svc_client_create.

 

The first time that I send a message, message is sent correctly and Iam 
receiving the response well. But the second time, petition is sent (I can see 
in wireshark) but I dont have any response (but is received because I see in 
wireshark), axiom node returned by send_receive is null.

 

My code is:

 

void send(){

 

axiom_node_t* payload=buildWSMessage(env,message);

if (payload){

    axiom_node_t* retNode=axis2_svc_client_send_receive(svc_client, env, 
payload);

            if (retNode){

                extractAndSend(retNode);

            }

}

}

 

Im only calling init() and run() one time, and after that I am allways calling 
to this send method. What should I do if i want to use the previous method 
twice? shoud I have to free some structures of svc_client? any help would be 
appreciated!

 

regards

 

-- 
Óscar Pernas Plaza. 

Reply via email to