Re: AXIS2C - JIRA # 1259
Hi, All seems well in 1.6.0 - thanks for your response. Andy On Thu, Apr 30, 2009 at 12:47 PM, Uthaiyashankar shan...@wso2.com wrote: Hi Andy, I think [1] is your fix... It is in the latest release (1.6.0). Are you getting the same error again? In that case, you can reopen the issue. Regards, Shankar [1] http://svn.apache.org/viewvc?view=revrevision=692995 On Thu, Apr 30, 2009 at 9:06 PM, Andy Karseras akarse...@gmail.comwrote: Hi, I raised a JIRA in September of last year for a bug in 1.4.0 but can't seem to locate the fix in the trunk. Could anyone point me in the location of the fix and maybe also confirm whether the fix made it into subsequent releases ? Many thanks. Andy -- S.Uthaiyashankar Software Architect WSO2 Inc. http://wso2.com/ - The Open Source SOA Company
AXIS2C - JIRA # 1259
Hi, I raised a JIRA in September of last year for a bug in 1.4.0 but can't seem to locate the fix in the trunk. Could anyone point me in the location of the fix and maybe also confirm whether the fix made it into subsequent releases ? Many thanks. Andy
Re: Clean-up and Freeing (and nnexpected close-tags being created)
Many thanks for your suggestions and for fixing the bug.
Andreas
On Mon, Sep 8, 2008 at 2:25 AM, Supun Kamburugamuva [EMAIL PROTECTED]wrote:
Hi Andy,
Thanks for finding this important bug in the axiom code. I've found the bug
and will correct it shortly. I've gone through your code and there are two
things that I like to point out in your code.
1. You are creating an empty node and passing it to the element_create
method. This leads to a memory leak. Correct code is:
axiom_node_t *nodeA = NULL;
axutil_string_t* nodeAString = axutil_string_create
(env,getParameterValues);
axiom_element_create_str(env, NULL, nodeAString, ns, nodeA);
2. You are creating an empty namsespace. This also causes a memory leak.
You should pass NULL instead of this empty namespace.
axiom_element_create_str(env, nodeA, nodeBString, NULL, nodeB);
Thanks,
Supun..
On Fri, Sep 5, 2008 at 11:30 PM, Dimuthu Gamage [EMAIL PROTECTED]wrote:
Hi,
Looks like the axiom node created with axutil_string is having problem, I
too got the same problem with your code, and I tried replacing
axiom_element_create_str with axiom_element_create and it was working
correctly.
axiom_node_t *nodeA = axiom_node_create(env);
/*axutil_string_t* nodeAString = axutil_string_create
(env,getParameterValues); */
const axis2_char_t *nodeAString = getParametervalues;
axiom_element_create(env, NULL, nodeAString, ns, nodeA);
.
I think axutil_string or use of axutil_string inside axiom is having a
bug. Can you please raise an issue on this at
https://issues.apache.org/jira/browse/AXIS2C
Thanks
Dimuthu
On Thu, Sep 4, 2008 at 7:13 PM, Andy Karseras [EMAIL PROTECTED]wrote:
The following code illustrates the problem...
void myClient::testMethod()
{
const axis2_char_t *prefix = cwmp;
const axis2_char_t *uri = urn:dslforum-org:cwmp-1-0;
axiom_namespace_t *ns = axiom_namespace_create(env, uri, prefix);
axiom_namespace_t *empty_ns = axiom_namespace_create(env, uri,
);
axiom_node_t *nodeA = axiom_node_create(env);
axutil_string_t* nodeAString = axutil_string_create
(env,getParameterValues);
axiom_element_create_str(env, NULL, nodeAString, ns, nodeA);
axiom_node_t *nodeB = axiom_node_create(env);
axutil_string_t* nodeBString = axutil_string_create
(env,ParameterNames);
axiom_element_create_str(env, nodeA, nodeBString, empty_ns,
nodeB);
axiom_node_t *nameNode = axiom_node_create(env);
axutil_string_t* nameString = axutil_string_create (env, Name);
axiom_element_create_str(env, nodeB, nameString, empty_ns,
nameNode);
axiom_element_t *ele = (axiom_element_t
*)axiom_node_get_data_element( nameNode, env);
axiom_element_set_text( ele, env, blah, nameNode);
cout axiom_node_to_string(nodeA,env) endl;
axiom_node_free_tree(nodeA, env);
}
The method is called multiple times with a sleep interval in between and
creates the output below.
Note the ParameterNames tag for the last two iterations.
cwmp:getParameterValues
xmlns:cwmp=urn:dslforum-org:cwmp-1-0ParameterNamesNameblah/Name/ParameterNames/cwmp:getParameterValues
cwmp:getParameterValues
xmlns:cwmp=urn:dslforum-org:cwmp-1-0ParameterNamesNameblah/Name/ParameterNames/cwmp:getParameterValues
cwmp:getParameterValues
xmlns:cwmp=urn:dslforum-org:cwmp-1-0ParameterNamesName/blah/Name/ParameterNames/cwmp:getParameterValues
cwmp:getParameterValues xmlns:cwmp=urn:dslforum-org:cwmp-1-0*
ParameterNames/*
Name/blah/Name/ParameterNames/cwmp:getParameterValues
cwmp:getParameterValues xmlns:cwmp=urn:dslforum-org:cwmp-1-0*
ParameterNames/*
Name/blah/Name/ParameterNames/cwmp:getParameterValues
Is this expected due to my incorrect use of the APIs or is this a bug ?
Many thanks.
On Thu, Sep 4, 2008 at 7:52 AM, Andy Karseras [EMAIL PROTECTED]wrote:
Thanks for your reply.
It seems that the problem occurs even when I create a new service client
and payload on each time I resend. Would this be expected ?
On Wed, Sep 3, 2008 at 9:05 PM, Samisa Abeysinghe [EMAIL PROTECTED]wrote:
I think this occurs because you are violating the ownership rules with
OM. Once the payload is passed in, the engine takes over the ownership of
the node and you are not supposed to do anything with the payload
afterwards.
Thanks,
Samisa...
Andy Karseras wrote:
Hi,
I raised this problem in July and thought that it had been resolved
(by doing proper clean-up), although it is now re-occurring.
I am seeing a close tag being created when there shouldn't be.
The incorrect message content is as follows...
cwmp:getParameterValues xmlns:cwmp=urn:dslforum-org:cwmp-1-0
ParameterNames
*Name/**TempAgent./Name
/ParameterNames
/cwmp:getParameterValues
I am sending the same message multiple times to the server and the
error occurs on the third
Re: Clean-up and Freeing (and nnexpected close-tags being created)
Thanks for your reply. It seems that the problem occurs even when I create a new service client and payload on each time I resend. Would this be expected ? On Wed, Sep 3, 2008 at 9:05 PM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: I think this occurs because you are violating the ownership rules with OM. Once the payload is passed in, the engine takes over the ownership of the node and you are not supposed to do anything with the payload afterwards. Thanks, Samisa... Andy Karseras wrote: Hi, I raised this problem in July and thought that it had been resolved (by doing proper clean-up), although it is now re-occurring. I am seeing a close tag being created when there shouldn't be. The incorrect message content is as follows... cwmp:getParameterValues xmlns:cwmp=urn:dslforum-org:cwmp-1-0 ParameterNames *Name/**TempAgent./Name /ParameterNames /cwmp:getParameterValues I am sending the same message multiple times to the server and the error occurs on the third iteration (3rd time the message is sent) so am assuming that I am not doing proper clean-up after each message is created and then sent. My questions as follows... a) Has anybody seen this before ? b) Will calling axiom_node_free_tree on nodeA also clean-up nodeB in the following example ? axiom_node_t *nodeB= axiom_node_get_first_child(nodeA, env); c) Will a node created to be used in axis2_svc_client_add_header, be cleaned-up by axis2_svc_client_free ? d) Is there any other info I can provide to clarify or help explain the problem ? Many thanks. Andy No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.6.15/1649 - Release Date: 9/3/2008 7:15 AM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Clean-up and Freeing (and nnexpected close-tags being created)
The following code illustrates the problem...
void myClient::testMethod()
{
const axis2_char_t *prefix = cwmp;
const axis2_char_t *uri = urn:dslforum-org:cwmp-1-0;
axiom_namespace_t *ns = axiom_namespace_create(env, uri, prefix);
axiom_namespace_t *empty_ns = axiom_namespace_create(env, uri,
);
axiom_node_t *nodeA = axiom_node_create(env);
axutil_string_t* nodeAString = axutil_string_create
(env,getParameterValues);
axiom_element_create_str(env, NULL, nodeAString, ns, nodeA);
axiom_node_t *nodeB = axiom_node_create(env);
axutil_string_t* nodeBString = axutil_string_create
(env,ParameterNames);
axiom_element_create_str(env, nodeA, nodeBString, empty_ns, nodeB);
axiom_node_t *nameNode = axiom_node_create(env);
axutil_string_t* nameString = axutil_string_create (env, Name);
axiom_element_create_str(env, nodeB, nameString, empty_ns,
nameNode);
axiom_element_t *ele = (axiom_element_t
*)axiom_node_get_data_element( nameNode, env);
axiom_element_set_text( ele, env, blah, nameNode);
cout axiom_node_to_string(nodeA,env) endl;
axiom_node_free_tree(nodeA, env);
}
The method is called multiple times with a sleep interval in between and
creates the output below.
Note the ParameterNames tag for the last two iterations.
cwmp:getParameterValues
xmlns:cwmp=urn:dslforum-org:cwmp-1-0ParameterNamesNameblah/Name/ParameterNames/cwmp:getParameterValues
cwmp:getParameterValues
xmlns:cwmp=urn:dslforum-org:cwmp-1-0ParameterNamesNameblah/Name/ParameterNames/cwmp:getParameterValues
cwmp:getParameterValues
xmlns:cwmp=urn:dslforum-org:cwmp-1-0ParameterNamesName/blah/Name/ParameterNames/cwmp:getParameterValues
cwmp:getParameterValues xmlns:cwmp=urn:dslforum-org:cwmp-1-0*
ParameterNames/*
Name/blah/Name/ParameterNames/cwmp:getParameterValues
cwmp:getParameterValues xmlns:cwmp=urn:dslforum-org:cwmp-1-0*
ParameterNames/*
Name/blah/Name/ParameterNames/cwmp:getParameterValues
Is this expected due to my incorrect use of the APIs or is this a bug ?
Many thanks.
On Thu, Sep 4, 2008 at 7:52 AM, Andy Karseras [EMAIL PROTECTED] wrote:
Thanks for your reply.
It seems that the problem occurs even when I create a new service client
and payload on each time I resend. Would this be expected ?
On Wed, Sep 3, 2008 at 9:05 PM, Samisa Abeysinghe [EMAIL PROTECTED] wrote:
I think this occurs because you are violating the ownership rules with OM.
Once the payload is passed in, the engine takes over the ownership of the
node and you are not supposed to do anything with the payload afterwards.
Thanks,
Samisa...
Andy Karseras wrote:
Hi,
I raised this problem in July and thought that it had been resolved (by
doing proper clean-up), although it is now re-occurring.
I am seeing a close tag being created when there shouldn't be.
The incorrect message content is as follows...
cwmp:getParameterValues xmlns:cwmp=urn:dslforum-org:cwmp-1-0
ParameterNames
*Name/**TempAgent./Name
/ParameterNames
/cwmp:getParameterValues
I am sending the same message multiple times to the server and the error
occurs on the third iteration (3rd time the message is sent) so am assuming
that I am not doing proper clean-up after each message is created and then
sent.
My questions as follows...
a) Has anybody seen this before ?
b) Will calling axiom_node_free_tree on nodeA also clean-up nodeB in the
following example ?
axiom_node_t *nodeB= axiom_node_get_first_child(nodeA, env);
c) Will a node created to be used in axis2_svc_client_add_header, be
cleaned-up by axis2_svc_client_free ?
d) Is there any other info I can provide to clarify or help explain the
problem ?
Many thanks.
Andy
No virus found in this incoming message.
Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database:
270.6.15/1649 - Release Date: 9/3/2008 7:15 AM
--
Samisa Abeysinghe Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - The Open Source SOA Company
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Clean-up and Freeing (and nnexpected close-tags being created)
Hi, I raised this problem in July and thought that it had been resolved (by doing proper clean-up), although it is now re-occurring. I am seeing a close tag being created when there shouldn't be. The incorrect message content is as follows... cwmp:getParameterValues xmlns:cwmp=urn:dslforum-org:cwmp-1-0 ParameterNames *Name/**TempAgent./Name /ParameterNames /cwmp:getParameterValues I am sending the same message multiple times to the server and the error occurs on the third iteration (3rd time the message is sent) so am assuming that I am not doing proper clean-up after each message is created and then sent. My questions as follows... a) Has anybody seen this before ? b) Will calling axiom_node_free_tree on nodeA also clean-up nodeB in the following example ? axiom_node_t *nodeB= axiom_node_get_first_child(nodeA, env); c) Will a node created to be used in axis2_svc_client_add_header, be cleaned-up by axis2_svc_client_free ? d) Is there any other info I can provide to clarify or help explain the problem ? Many thanks. Andy
AXIS2C: Unexpected close-tag created
Hi, I am seeing a close tag being created when (I believe) there shouldn't be. The incorrect output is as follows... cwmp:getParameterValues xmlns:cwmp=urn:dslforum-org:cwmp-1-0 ParameterNames *Name/*TempAgent./Name /ParameterNames /cwmp:getParameterValues The code to create the problematic line in the above XML as follows:- axiom_node_t *nameNode = axiom_node_create(env); axutil_string_t* nameString = axutil_string_create (env, Name); axiom_element_create_str(env, parameterNamesNode, nameString, CWMP_EMPTY_PREFIX_NAMESPACE, nameNode); axiom_node_t *tempNode = axiom_node_create(env); axiom_text_create(env, nameNode, tempChar, tempNode); Is this a bug or am I just doing something wrong. Many thanks. Andy
Re: AXIS2C: Unexpected close-tag created
Looks like I'm not doing the right clean-up in the code which is subsequently causing a problem. Please ignore this post/problem. On Thu, Jul 17, 2008 at 2:52 PM, Andy Karseras [EMAIL PROTECTED] wrote: Hi, I am seeing a close tag being created when (I believe) there shouldn't be. The incorrect output is as follows... cwmp:getParameterValues xmlns:cwmp=urn:dslforum-org:cwmp-1-0 ParameterNames *Name/*TempAgent./Name /ParameterNames /cwmp:getParameterValues The code to create the problematic line in the above XML as follows:- axiom_node_t *nameNode = axiom_node_create(env); axutil_string_t* nameString = axutil_string_create (env, Name); axiom_element_create_str(env, parameterNamesNode, nameString, CWMP_EMPTY_PREFIX_NAMESPACE, nameNode); axiom_node_t *tempNode = axiom_node_create(env); axiom_text_create(env, nameNode, tempChar, tempNode); Is this a bug or am I just doing something wrong. Many thanks. Andy
Re: Service Client sending message multiple times to server
Hi, I'll create the JIRA. Concerning eclipse, I'll gladly commit anything back to the community - what exactly would you require ? Andy On Thu, Jul 10, 2008 at 7:57 AM, Supun Kamburugamuva [EMAIL PROTECTED] wrote: Hi Andy, I'm not sure how HTTPS stuff work. But please create a Jira so we won't forget the issue. From your mails it seems that you are using an eclipse project for Axis2/C. We really appreciate if you can commit it back to the community as there were few user requests regarding this. Regards, Supun.. On Wed, Jul 9, 2008 at 11:49 PM, Andy Karseras [EMAIL PROTECTED] wrote: Many thanks. So I was using the axis2_options_set_http_auth_info call (as suggested in Axis2/C Manual 16.2) and had the following commented out in the axis2.ml... parameter name=HTTP-Authentication username=application password=wlyVdZZ05D8 locked=true/ When using the method call, 2 messages are sent to the server. When using the axis2.xml with HTTP Authentication set, only one message is sent (as expected). Are there any known problems with this method call that would prevent it from operating in the same manner as the config settings in the axis2.xml ? If one is not known, should I raise a JIRA ? Andy On Wed, Jul 9, 2008 at 12:59 PM, Manjula Peiris [EMAIL PROTECTED] wrote: On Wed, 2008-07-09 at 11:56 -0400, Andy Karseras wrote: Having stepped through the code, I see the calls to send the message twice being executed. In http_sender_c, the two calls to axis2_http_client_send are made at lines 988 and 1054. This is because you should have specified http authentication in your axis2.xml -Manjula. Andy On Wed, Jul 9, 2008 at 10:43 AM, Andy Karseras [EMAIL PROTECTED] wrote: Thanks for the suggestion. Using the tcpmon tool, I can definitely see 2 messages being sent to the server with one call to axis2_svc_client_send_receive(). Uisng Eclipse, I have stepped in debug mode to prove this. Samisa - would you have any ideas or suggestions why this is happening. Could it be the HTTP client ? Is there any further debugging I can enable to pinpoint in the code where the duplicate messages are being sent ? Andy On Wed, Jul 9, 2008 at 3:59 AM, Supun Kamburugamuva [EMAIL PROTECTED] wrote: Hi, If there is anything I can set to show whether duplicate messages are being sent, please let me know. You can use the TCPmon tool. http://ws.apache.org/commons/tcpmon/. Supun.. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Service Client sending message multiple times to server
Thanks for the suggestion. Using the tcpmon tool, I can definitely see 2 messages being sent to the server with one call to axis2_svc_client_send_receive(). Uisng Eclipse, I have stepped in debug mode to prove this. Samisa - would you have any ideas or suggestions why this is happening. Could it be the HTTP client ? Is there any further debugging I can enable to pinpoint in the code where the duplicate messages are being sent ? Andy On Wed, Jul 9, 2008 at 3:59 AM, Supun Kamburugamuva [EMAIL PROTECTED] wrote: Hi, If there is anything I can set to show whether duplicate messages are being sent, please let me know. You can use the TCPmon tool. http://ws.apache.org/commons/tcpmon/. Supun..
Re: Service Client sending message multiple times to server
Having stepped through the code, I see the calls to send the message twice being executed. In http_sender_c, the two calls to axis2_http_client_send are made at lines 988 and 1054. Andy On Wed, Jul 9, 2008 at 10:43 AM, Andy Karseras [EMAIL PROTECTED] wrote: Thanks for the suggestion. Using the tcpmon tool, I can definitely see 2 messages being sent to the server with one call to axis2_svc_client_send_receive(). Uisng Eclipse, I have stepped in debug mode to prove this. Samisa - would you have any ideas or suggestions why this is happening. Could it be the HTTP client ? Is there any further debugging I can enable to pinpoint in the code where the duplicate messages are being sent ? Andy On Wed, Jul 9, 2008 at 3:59 AM, Supun Kamburugamuva [EMAIL PROTECTED] wrote: Hi, If there is anything I can set to show whether duplicate messages are being sent, please let me know. You can use the TCPmon tool. http://ws.apache.org/commons/tcpmon/. Supun..
Re: Service Client sending message multiple times to server
Many thanks. So I was using the axis2_options_set_http_auth_info call (as suggested in Axis2/C Manual 16.2) and had the following commented out in the axis2.ml... parameter name=HTTP-Authentication username=application password=wlyVdZZ05D8 locked=true/ When using the method call, 2 messages are sent to the server. When using the axis2.xml with HTTP Authentication set, only one message is sent (as expected). Are there any known problems with this method call that would prevent it from operating in the same manner as the config settings in the axis2.xml ? If one is not known, should I raise a JIRA ? Andy On Wed, Jul 9, 2008 at 12:59 PM, Manjula Peiris [EMAIL PROTECTED] wrote: On Wed, 2008-07-09 at 11:56 -0400, Andy Karseras wrote: Having stepped through the code, I see the calls to send the message twice being executed. In http_sender_c, the two calls to axis2_http_client_send are made at lines 988 and 1054. This is because you should have specified http authentication in your axis2.xml -Manjula. Andy On Wed, Jul 9, 2008 at 10:43 AM, Andy Karseras [EMAIL PROTECTED] wrote: Thanks for the suggestion. Using the tcpmon tool, I can definitely see 2 messages being sent to the server with one call to axis2_svc_client_send_receive(). Uisng Eclipse, I have stepped in debug mode to prove this. Samisa - would you have any ideas or suggestions why this is happening. Could it be the HTTP client ? Is there any further debugging I can enable to pinpoint in the code where the duplicate messages are being sent ? Andy On Wed, Jul 9, 2008 at 3:59 AM, Supun Kamburugamuva [EMAIL PROTECTED] wrote: Hi, If there is anything I can set to show whether duplicate messages are being sent, please let me know. You can use the TCPmon tool. http://ws.apache.org/commons/tcpmon/. Supun.. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Changing/Adding SOAP Envelope
On Mon, Jul 7, 2008 at 10:26 AM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Andy Karseras wrote: Hi, I would like to set the SOAP envelope to a particular Namespace. Why do you want to do this at SOAP envelope level? You can do that at Payload level. Samisa... My aim is to change ?xml version='1.0' encoding='utf-8'? *soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;* soapenv:Header to ?xml version='1.0' encoding='utf-8'? *soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ * soapenv:Header Is this possible at the Payload level ? Andy Once created (I used axiom_soap_envelope_create), how is this new envelope used ? Is it added to the ServiceClient ? If so, how ? Many thanks. Andy No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.4.6/1538 - Release Date: 7/7/2008 7:40 AM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Changing/Adding SOAP Envelope
On Mon, Jul 7, 2008 at 11:30 AM, Manjula Peiris [EMAIL PROTECTED] wrote: On Mon, 2008-07-07 at 10:34 -0400, Andy Karseras wrote: My aim is to change ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header to ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header Is this possible at the Payload level ? Seems to me you want set the SOAP version 1.1. This can be done by adding the following line in your client code. axis2_options_set_soap_version(options, env, AXIOM_SOAP11); Thanks, -Manjula. That's it - perfect...many thanks. Andy Once created (I used axiom_soap_envelope_create), how is this new envelope used ? Is it added to the ServiceClient ? If so, how ? Many thanks. Andy No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.4.6/1538 - Release Date: 7/7/2008 7:40 AM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Service Client sending message multiple times to server
Hi, It appears that for some reason, the ServiceClient is sending the message twice to the server in a very short time interval (less than 20 milli-secs). The payload remains the same and it is a a re-send rather than a call being made twice. It may be helpful to note that I am using an AXIS2 Java Server with a AXIS2C client - interaction between the exisiting Java client and Java server are normal and functioning as expected. Therefore, I do not (at this stage) suspect the server. The server is exoected to be slow for the first request so control of the timeout was my initial point of investigation. I have tried setting the axis2_http_client_set_timeoutfile:///D:/axis2c/docs/api/html/group__axis2__http__client.html#g32bb50461fab10fa658ac0d1c659e7dabut to no avail. Would the setting of a socket timeout be necessary and if so, how would this be done ? Any suggestions on why this may be occuring ? For completeness, I have attached my logs (in hope that there is something obvious that I am doing wrong). Andy [Mon Jul 7 15:26:18 2008] [debug] phase.c(121) axis2_handler_t *request_uri_based_dispatcher added to the index 0 of the phase Transport [Mon Jul 7 15:26:18 2008] [debug] phase.c(121) axis2_handler_t *addressing_based_dispatcher added to the index 1 of the phase Transport [Mon Jul 7 15:26:18 2008] [debug] phase.c(121) axis2_handler_t *rest_dispatcher added to the index 0 of the phase Dispatch [Mon Jul 7 15:26:18 2008] [debug] phase.c(121) axis2_handler_t *soap_message_body_based_dispatcher added to the index 1 of the phase Dispatch [Mon Jul 7 15:26:18 2008] [debug] phase.c(121) axis2_handler_t *soap_action_based_dispatcher added to the index 2 of the phase Dispatch [Mon Jul 7 15:26:18 2008] [debug] phase.c(121) axis2_handler_t *dispatch_post_conditions_evaluator added to the index 0 of the phase PostDispatch [Mon Jul 7 15:26:18 2008] [debug] phase.c(121) axis2_handler_t *context_handler added to the index 1 of the phase PostDispatch [Mon Jul 7 15:26:18 2008] [debug] conf_builder.c(233) No custom dispatching order found. Continue with the default dispatching order [Mon Jul 7 15:26:18 2008] [debug] conf_builder.c(378) Module addressing found in axis2.xml [Mon Jul 7 15:26:18 2008] [debug] class_loader.c(141) Object loaded successfully [Mon Jul 7 15:26:18 2008] [debug] class_loader.c(141) Object loaded successfully [Mon Jul 7 15:26:18 2008] [debug] class_loader.c(141) Object loaded successfully [Mon Jul 7 15:26:18 2008] [debug] class_loader.c(141) Object loaded successfully [Mon Jul 7 15:26:18 2008] [error] dir_handler.c(219) No files in the path /home/karseras/axis2c/deploy/services. [Mon Jul 7 15:26:18 2008] [debug] dep_engine.c(1306) axis2_dep_engine_load_module_dll: DLL path is : /home/karseras/axis2c/deploy/modules/addressing/libaxis2_mod_addr.so [Mon Jul 7 15:26:18 2008] [debug] class_loader.c(141) Object loaded successfully [Mon Jul 7 15:26:18 2008] [debug] dep_engine.c(1306) axis2_dep_engine_load_module_dll: DLL path is : /home/karseras/axis2c/deploy/modules/logging/libaxis2_mod_log.so [Mon Jul 7 15:26:18 2008] [debug] class_loader.c(141) Object loaded successfully [Mon Jul 7 15:26:18 2008] [debug] phase_holder.c(139) Add handler AddressingInHandler to phase Transport [Mon Jul 7 15:26:18 2008] [debug] phase_resolver.c(123) Service name is : __ANONYMOUS_SERVICE__ [Mon Jul 7 15:26:18 2008] [debug] phase_resolver.c(259) Module name is:addressing [Mon Jul 7 15:26:18 2008] [debug] phase_resolver.c(375) Trying to add this handler AddressingInHandler to system pre defined phases , but those handlers are already added to global chain which run irrespective of the service [Mon Jul 7 15:26:18 2008] [debug] phase_resolver.c(259) Module name is:addressing [Mon Jul 7 15:26:18 2008] [debug] phase_holder.c(139) Add handler AddressingOutHandler to phase MessageOut [Mon Jul 7 15:26:18 2008] [debug] phase_resolver.c(259) Module name is:addressing [Mon Jul 7 15:26:18 2008] [debug] phase_resolver.c(259) Module name is:addressing [Mon Jul 7 15:26:18 2008] [debug] phase_holder.c(139) Add handler AddressingOutHandler to phase MessageOut [Mon Jul 7 15:26:18 2008] [debug] phase_resolver.c(259) Module name is:addressing [Mon Jul 7 15:26:18 2008] [debug] phase_resolver.c(375) Trying to add this handler AddressingInHandler to system pre defined phases , but those handlers are already added to global chain which run irrespective of the service [Mon Jul 7 15:26:18 2008] [debug] phase_resolver.c(259) Module name is:addressing [Mon Jul 7 15:26:18 2008] [debug] phase_holder.c(139) Add handler AddressingOutHandler to phase MessageOut [Mon Jul 7 15:26:18 2008] [debug] phase_resolver.c(259) Module name is:addressing [Mon Jul 7 15:26:18 2008] [debug] phase_resolver.c(259) Module name is:addressing [Mon Jul 7 15:26:18 2008] [debug] phase_holder.c(139) Add handler AddressingOutHandler to phase MessageOut [Mon Jul 7 15:26:18 2008] [debug] phase_resolver.c(259) Module name is:addressing [Mon
Setting HTTP Headers
Hi, Is there any way of setting the following headers using code ? - SOAPAction: urn:anonOutInOp - Transfer-Encoding: chunked I have tried uncommenting the relevant line in the axis.xml for Transfer-Encoding but this didn't seem to work. Many thanks. Andy
SSL Client Authentication Failure
Hi, I am having trouble using an SSL Client with AXIS2C - basically, authentication appears to fail. I executed the following to obtain the server certificate... echo |\ openssl s_client -connect localhost:7547 21 |\ sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' cert.pem ..and got the following:- -BEGIN CERTIFICATE- MIIDFjCCAtSgAwIBAgIER6H2iDALBgcqhkjOOAQDBQAwbjEPMA0GA1UEBhMGQ2Fu YWRhMRAwDgYDVQQIEwdPbnRhcmlvMQ8wDQYDVQQHEwZPdHRhd2ExGDAWBgNVBAoT D05vcnRlbCBOZXR3b3JrczEMMAoGA1UECxMDSU1TMRAwDgYDVQQDEwdXTUc2MDAw MB4XDTA4MDEzMTE2MjU0NFoXDTA4MDQzMDE2MjU0NFowbjEPMA0GA1UEBhMGQ2Fu YWRhMRAwDgYDVQQIEwdPbnRhcmlvMQ8wDQYDVQQHEwZPdHRhd2ExGDAWBgNVBAoT D05vcnRlbCBOZXR3b3JrczEMMAoGA1UECxMDSU1TMRAwDgYDVQQDEwdXTUc2MDAw MIIBuDCCASwGByqGSM44BAEwggEfAoGBAP1/U4EddRIpUt9KnC7s5Of2EbdSPO9E AMMeP4C2USZpRV1AIlH7WT2NWPq/xfW6MPbLm1Vs14E7gB00b/JmYLdrmVClpJ+f 6AR7ECLCT7up1/63xhv4O1fnxqimFQ8E+4P208UewwI1VBNaFpEy9nXzrith1yrv 8iIDGZ3RSAHHAhUAl2BQjxUjC8yykrmCouuEC/BYHPUCgYEA9+GghdabPd7LvKtc NrhXuXmUr7v6OuqC+VdMCz0HgmdRWVeOutRZT+ZxBxCBgLRJFnEj6EwoFhO3zwky jMim4TwWeotUfI0o4KOuHiuzpnWRbqN/C/ohNWLx+2J6ASQ7zKTxvqhRkImog9/h WuWfBpKLZl6Ae1UlZAFMO/7PSSoDgYUAAoGBAJKVdCfsnmARwlgSMBKRLh4WyyzQ TubhCrNuu3qwZuCILkzmTk/kmH4uCkcFiZx5I7uYphlgkoVW2qHAZ5t17xhz30uD OilLCagWDPygT6wO2uZV1TruKmfEI7zYBGijDazNb2wV8wy1SwON38NC3nKeJf9X BgK6RCCGjcaa75FrMAsGByqGSM44BAMFAAMvADAsAhRWOjxC/Lpp/FGm+3QfLEUU NzoyvQIUfrBKhVVjCHNzuE4NxFb0zhluOMY= -END CERTIFICATE- My axis2.xml contents are... parameter name=SERVER_CERT/etc/nortel/apps/oam/configurationServer/security/cert.pem/parameter !--parameter name=KEY_FILE/path/to/client/certificate/chain/file/parameter-- !--parameter name=SSL_PASSPHRASEpassphrase/parameter-- The relevant logs as follows:- [Thu Jul 3 13:12:57 2008] [debug] http_transport_sender.c(246) ctx_epr: https://localhost:7547/services/ConfigurationServer [Thu Jul 3 13:12:57 2008] [debug] http_transport_sender.c(768) using axis2 native http sender. [Thu Jul 3 13:12:57 2008] [debug] http_sender.c(415) msg_ctx_id:484e90ce-4923-1dd1-20df-00145eecc23a [Thu Jul 3 13:12:57 2008] [info] [ssl client] Client certificate chain filenot specified [Thu Jul 3 13:12:57 2008] [debug] ssl/ssl_utils.c(190) [ssl client] SSL certificate verified against peer [Thu Jul 3 13:12:57 2008] [info] [ssl client] Client certificate chain filenot specified [Thu Jul 3 13:12:57 2008] [debug] ssl/ssl_utils.c(190) [ssl client] SSL certificate verified against peer [Thu Jul 3 13:12:57 2008] [error] http_sender.c(1293) HTTP Authentication failed [Thu Jul 3 13:12:57 2008] [error] http_sender.c(1399) Error occurred in transport [Thu Jul 3 13:12:57 2008] [error] engine.c(179) Transport sender invoke failed Any ideas or suggestions ? Many thanks. Andy
