[jira] Created: (AXIS2C-1420) Support to talk to a TLS1 only server

Support to talk to a TLS1 only server - Key: AXIS2C-1420 URL: https://issues.apache.org/jira/browse/AXIS2C-1420 Project: Axis2-C Issue Type: Improvement Reporter: Damitha Kumarage Axis2/C

[jira] Commented: (AXIS2C-1279) A soap fault of No Error return

[ https://issues.apache.org/jira/browse/AXIS2C-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12761210#action_12761210 ] Damitha Kumarage commented on AXIS2C-1279: -- When a service return NULL without

[jira] Created: (AXIS2C-1378) operation name is corruputed by the time it reaches dispatcher

operation name is corruputed by the time it reaches dispatcher -- Key: AXIS2C-1378 URL: https://issues.apache.org/jira/browse/AXIS2C-1378 Project: Axis2-C Issue Type: Bug

[jira] Created: (AXIS2C-1377) switching to global/local pools when used with apache module

switching to global/local pools when used with apache module Key: AXIS2C-1377 URL: https://issues.apache.org/jira/browse/AXIS2C-1377 Project: Axis2-C Issue Type: Improvement

[jira] Resolved: (AXIS2C-1377) switching to global/local pools when used with apache module

[ https://issues.apache.org/jira/browse/AXIS2C-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage resolved AXIS2C-1377. -- Resolution: Fixed Attached patch solve the issue switching to global/local pools

[jira] Created: (AXIS2C-1361) xpath fails when chile elements are prefixed

xpath fails when chile elements are prefixed Key: AXIS2C-1361 URL: https://issues.apache.org/jira/browse/AXIS2C-1361 Project: Axis2-C Issue Type: Bug Components: xml/om

[jira] Commented: (AXIS2C-1355) Changing service client options between messages

[ https://issues.apache.org/jira/browse/AXIS2C-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680766#action_12680766 ] Damitha Kumarage commented on AXIS2C-1355: -- The best thing is take the options

[jira] Created: (AXIS2C-1353) Externally passed configuration context and service should not be freed within service client

Externally passed configuration context and service should not be freed within service client - Key: AXIS2C-1353 URL: https://issues.apache.org/jira/browse/AXIS2C-1353

[jira] Created: (AXIS2C-1354) new function axis2_svc_client_get_conf_ctx() needed.

new function axis2_svc_client_get_conf_ctx() needed. Key: AXIS2C-1354 URL: https://issues.apache.org/jira/browse/AXIS2C-1354 Project: Axis2-C Issue Type: Bug Reporter: Damitha

[jira] Resolved: (AXIS2C-1349) Time Duration related functions does not work

[ https://issues.apache.org/jira/browse/AXIS2C-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage resolved AXIS2C-1349. -- Resolution: Fixed This is fixed Time Duration related functions does not work

[jira] Created: (AXIS2C-1348) Redundancy in Date/Time functions

Redundancy in Date/Time functions - Key: AXIS2C-1348 URL: https://issues.apache.org/jira/browse/AXIS2C-1348 Project: Axis2-C Issue Type: Bug Reporter: Damitha Kumarage In axis2 time handling

[jira] Created: (AXIS2C-1349) Time Duration related functions does not work

Time Duration related functions does not work - Key: AXIS2C-1349 URL: https://issues.apache.org/jira/browse/AXIS2C-1349 Project: Axis2-C Issue Type: Bug Reporter: Damitha Kumarage

[jira] Created: (AXIS2C-1350) Adding hours/mins/secs etc to the duration does not add up correctly

Adding hours/mins/secs etc to the duration does not add up correctly Key: AXIS2C-1350 URL: https://issues.apache.org/jira/browse/AXIS2C-1350 Project: Axis2-C Issue Type:

[jira] Created: (AXIS2C-1328) Implementing new transport to optimize Axis2/C when used in a multi-threading client environment.

Implementing new transport to optimize Axis2/C when used in a multi-threading client environment. - Key: AXIS2C-1328 URL:

[jira] Created: (AXIS2C-1329) There should be a stub creation api function that take axis2 configuration context as parameter

There should be a stub creation api function that take axis2 configuration context as parameter --- Key: AXIS2C-1329 URL:

[jira] Created: (AXIS2C-1326) Improvment to Axis2/C client side thread pool

Improvment to Axis2/C client side thread pool - Key: AXIS2C-1326 URL: https://issues.apache.org/jira/browse/AXIS2C-1326 Project: Axis2-C Issue Type: Improvement Components:

[jira] Created: (AXIS2C-1327) Providing resource free callback in Dual channel non blocking scenarios

Providing resource free callback in Dual channel non blocking scenarios --- Key: AXIS2C-1327 URL: https://issues.apache.org/jira/browse/AXIS2C-1327 Project: Axis2-C Issue

[jira] Resolved: (AXIS2C-1301) Can not change the axis2c logger.

[ https://issues.apache.org/jira/browse/AXIS2C-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage resolved AXIS2C-1301. -- Resolution: Fixed This is fixed Can not change the axis2c logger.

[jira] Commented: (AXIS2C-1301) Can not change the axis2c logger.

[ https://issues.apache.org/jira/browse/AXIS2C-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12652301#action_12652301 ] Damitha Kumarage commented on AXIS2C-1301: -- Please se AXIS2C-1286 is related to

[jira] Resolved: (AXIS2C-1284) Savan/C build fails when --enable-filtering=no

[ https://issues.apache.org/jira/browse/AXIS2C-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage resolved AXIS2C-1284. -- Resolution: Fixed This is fixed now Savan/C build fails when --enable-filtering=no

[jira] Commented: (AXIS2C-1286) Improve the logging facilities to let the client specify their own logging mechanism

[ https://issues.apache.org/jira/browse/AXIS2C-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12646518#action_12646518 ] Damitha Kumarage commented on AXIS2C-1286: -- However my small change to your patch

[jira] Resolved: (AXIS2C-1286) Improve the logging facilities to let the client specify their own logging mechanism

[ https://issues.apache.org/jira/browse/AXIS2C-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage resolved AXIS2C-1286. -- Resolution: Fixed Patch applied. Thanks Dmitry for the patch. I have done only small

[jira] Updated: (AXIS2C-1277) Must use empty header in request

[ https://issues.apache.org/jira/browse/AXIS2C-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage updated AXIS2C-1277: - Attachment: get_version version_client.zip

[jira] Commented: (AXIS2C-1277) Must use empty header in request

[ https://issues.apache.org/jira/browse/AXIS2C-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12641736#action_12641736 ] Damitha Kumarage commented on AXIS2C-1277: -- I could reproduce this. Will fix asap

[jira] Created: (AXIS2C-1279) A soap fault of No Error return

A soap fault of No Error return - Key: AXIS2C-1279 URL: https://issues.apache.org/jira/browse/AXIS2C-1279 Project: Axis2-C Issue Type: Bug Reporter: Damitha Kumarage A soap fault with reason No

[jira] Updated: (AXIS2C-1279) A soap fault of No Error return

[ https://issues.apache.org/jira/browse/AXIS2C-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage updated AXIS2C-1279: - Description: A soap fault with reason No Error return for certain errors at server

[jira] Updated: (AXIS2C-1277) Must use empty header in request

[ https://issues.apache.org/jira/browse/AXIS2C-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage updated AXIS2C-1277: - Attachment: soap_header.c.diff File attached has the desired solution. If there is no

[jira] Created: (AXIS2C-1274) Savan/C seg faults when run with Apache2

Savan/C seg faults when run with Apache2 Key: AXIS2C-1274 URL: https://issues.apache.org/jira/browse/AXIS2C-1274 Project: Axis2-C Issue Type: Bug Reporter: Damitha Kumarage When running

[jira] Created: (AXIS2C-1273) In Savan/C filter template path is hard coded in to the code.

In Savan/C filter template path is hard coded in to the code. - Key: AXIS2C-1273 URL: https://issues.apache.org/jira/browse/AXIS2C-1273 Project: Axis2-C Issue Type: Bug

[jira] Created: (AXIS2C-1261) When several fire and forget sends are done using svc client it segfaults

When several fire and forget sends are done using svc client it segfaults - Key: AXIS2C-1261 URL: https://issues.apache.org/jira/browse/AXIS2C-1261 Project: Axis2-C

[jira] Commented: (AXIS2C-1254) Information set by the Client options axis2_options_set_transport_info function is not used

[ https://issues.apache.org/jira/browse/AXIS2C-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626893#action_12626893 ] Damitha Kumarage commented on AXIS2C-1254: -- I had a look at your patch. Is not it

[jira] Assigned: (AXIS2C-1249) Memory leak in notify client sample

[ https://issues.apache.org/jira/browse/AXIS2C-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage reassigned AXIS2C-1249: Assignee: Damitha Kumarage Memory leak in notify client sample

[jira] Closed: (AXIS2C-1249) Memory leak in notify client sample

[ https://issues.apache.org/jira/browse/AXIS2C-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage closed AXIS2C-1249. Resolution: Fixed This is fixed Memory leak in notify client sample

[jira] Assigned: (AXIS2C-1250) Memory leak in axiom_soap_header_remove_header_block() function

[ https://issues.apache.org/jira/browse/AXIS2C-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage reassigned AXIS2C-1250: Assignee: Damitha Kumarage Memory leak in

[jira] Closed: (AXIS2C-1250) Memory leak in axiom_soap_header_remove_header_block() function

[ https://issues.apache.org/jira/browse/AXIS2C-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage closed AXIS2C-1250. Resolution: Fixed This is fixed now Memory leak in

[jira] Created: (AXIS2C-1250) Memory leak in axiom_soap_header_remove_header_block() function

Memory leak in axiom_soap_header_remove_header_block() function --- Key: AXIS2C-1250 URL: https://issues.apache.org/jira/browse/AXIS2C-1250 Project: Axis2-C Issue Type: Bug

[jira] Updated: (AXIS2C-1250) Memory leak in axiom_soap_header_remove_header_block() function

[ https://issues.apache.org/jira/browse/AXIS2C-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage updated AXIS2C-1250: - Attachment: soap_header.tar.gz Use this sample to reproduce the memory leak Memory

[jira] Created: (AXIS2C-1249) Memory leak in notify client sample

Memory leak in notify client sample --- Key: AXIS2C-1249 URL: https://issues.apache.org/jira/browse/AXIS2C-1249 Project: Axis2-C Issue Type: Bug Reporter: Damitha Kumarage In current svn

[jira] Commented: (AXIS2C-1249) Memory leak in notify client sample

[ https://issues.apache.org/jira/browse/AXIS2C-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12618953#action_12618953 ] Damitha Kumarage commented on AXIS2C-1249: -- The reason is response message

[jira] Commented: (AXIS2C-1236) Memory issues in Axis2/C service client

[ https://issues.apache.org/jira/browse/AXIS2C-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614650#action_12614650 ] Damitha Kumarage commented on AXIS2C-1236: -- Are you using libxml2 parser?. If so

[jira] Commented: (AXIS2C-1156) memory leak in savanc

[ https://issues.apache.org/jira/browse/AXIS2C-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12613110#action_12613110 ] Damitha Kumarage commented on AXIS2C-1156: -- I found that leak details for server

[jira] Assigned: (AXIS2C-1223) Ws-Addressing Module, extracting information from EPR

[ https://issues.apache.org/jira/browse/AXIS2C-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage reassigned AXIS2C-1223: Assignee: Damitha Kumarage Ws-Addressing Module, extracting information from EPR

[jira] Assigned: (AXIS2C-1227) engine not freed when server return an error

[ https://issues.apache.org/jira/browse/AXIS2C-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage reassigned AXIS2C-1227: Assignee: Damitha Kumarage engine not freed when server return an error

[jira] Commented: (AXIS2C-1156) memory leak in savanc

[ https://issues.apache.org/jira/browse/AXIS2C-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12613039#action_12613039 ] Damitha Kumarage commented on AXIS2C-1156: -- Hi Diluka, Applied your patch. But

[jira] Resolved: (AXIS2C-1219) Savan remote subs_mgr gives an internal server error

[ https://issues.apache.org/jira/browse/AXIS2C-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage resolved AXIS2C-1219. -- Resolution: Fixed Patch applied. Thanks Diluka Savan remote subs_mgr gives an

[jira] Assigned: (AXIS2C-1219) Savan remote subs_mgr gives an internal server error

[ https://issues.apache.org/jira/browse/AXIS2C-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage reassigned AXIS2C-1219: Assignee: Damitha Kumarage Savan remote subs_mgr gives an internal server error

[jira] Commented: (AXIS2C-1215) incorrect MEP on the server side

[ https://issues.apache.org/jira/browse/AXIS2C-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609470#action_12609470 ] Damitha Kumarage commented on AXIS2C-1215: -- You can set your mep as an operation

[jira] Commented: (AXIS2C-1215) incorrect MEP on the server side

[ https://issues.apache.org/jira/browse/AXIS2C-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609471#action_12609471 ] Damitha Kumarage commented on AXIS2C-1215: -- Also please note that if you don't

[jira] Commented: (AXIS2C-1213) server returns HTTP/1.1 500 Internal Server Error for In-Only message

[ https://issues.apache.org/jira/browse/AXIS2C-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609472#action_12609472 ] Damitha Kumarage commented on AXIS2C-1213: -- Hi Frederic, To solve your problem

[jira] Resolved: (AXIS2C-1211) Improving the AXIS2_SVC_SKELETON_INIT_WITH_CONF

[ https://issues.apache.org/jira/browse/AXIS2C-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage resolved AXIS2C-1211. -- Resolution: Fixed Diluka, I applied the patch and it seems ok. Thanks for the patch.

[jira] Commented: (AXIS2C-1188) SOAP fault not working with axis2c latest revision(663886) from code generated from axis2/java using adb

[ https://issues.apache.org/jira/browse/AXIS2C-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609168#action_12609168 ] Damitha Kumarage commented on AXIS2C-1188: -- I reviewd the patch and it is good to

[jira] Commented: (AXIS2C-1188) SOAP fault not working with axis2c latest revision(663886) from code generated from axis2/java using adb

[ https://issues.apache.org/jira/browse/AXIS2C-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609179#action_12609179 ] Damitha Kumarage commented on AXIS2C-1188: -- I have another question. When service

[jira] Commented: (AXIS2C-1188) SOAP fault not working with axis2c latest revision(663886) from code generated from axis2/java using adb

[ https://issues.apache.org/jira/browse/AXIS2C-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609195#action_12609195 ] Damitha Kumarage commented on AXIS2C-1188: -- There are following scenarios to

[jira] Commented: (AXIS2C-1209) Current Dual-channel Implementation can never Support Certain Transports

[ https://issues.apache.org/jira/browse/AXIS2C-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609208#action_12609208 ] Damitha Kumarage commented on AXIS2C-1209: -- Currently listener manager is started

[jira] Commented: (AXIS2C-1209) Current Dual-channel Implementation can never Support Certain Transports

[ https://issues.apache.org/jira/browse/AXIS2C-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609212#action_12609212 ] Damitha Kumarage commented on AXIS2C-1209: -- If you are going to do these changes

[jira] Commented: (AXIS2C-1210) Service Client does not Pick the Correct Transport Receiver

[ https://issues.apache.org/jira/browse/AXIS2C-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609214#action_12609214 ] Damitha Kumarage commented on AXIS2C-1210: -- dual channel samples should work for

[jira] Commented: (AXIS2C-1211) Improving the AXIS2_SVC_SKELETON_INIT_WITH_CONF

[ https://issues.apache.org/jira/browse/AXIS2C-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609260#action_12609260 ] Damitha Kumarage commented on AXIS2C-1211: -- Diluka, Can you show me a specific

[jira] Resolved: (AXIS2C-1212) incorrect debug message in axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync

[ https://issues.apache.org/jira/browse/AXIS2C-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage resolved AXIS2C-1212. -- Resolution: Fixed This is fixed by calling and printing the fault details base nodes

[jira] Commented: (AXIS2C-1213) server returns HTTP/1.1 500 Internal Server Error for In-Only message

[ https://issues.apache.org/jira/browse/AXIS2C-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609296#action_12609296 ] Damitha Kumarage commented on AXIS2C-1213: -- According to soap 1.1 specication

[jira] Commented: (AXIS2C-723) add new transport in Axis2/C

[ https://issues.apache.org/jira/browse/AXIS2C-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608663#action_12608663 ] Damitha Kumarage commented on AXIS2C-723: - I am thinking whether there is

[jira] Commented: (AXIS2C-1154) multiple Invalid read of size 4 for client In-Only message

[ https://issues.apache.org/jira/browse/AXIS2C-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608689#action_12608689 ] Damitha Kumarage commented on AXIS2C-1154: -- Supun, Your fix makes sense to me.

[jira] Closed: (AXIS2C-832) When a axis2c client executed all the modules in the client repository are initialized even when then client does not engage them

[ https://issues.apache.org/jira/browse/AXIS2C-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage closed AXIS2C-832. --- Resolution: Fixed If the problem is fixed as explained by me then the problem arise when the

[jira] Updated: (AXIS2C-740) Definition of type axis2_bool_t based on an enumeration

[ https://issues.apache.org/jira/browse/AXIS2C-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage updated AXIS2C-740: Fix Version/s: 1.4.1 Definition of type axis2_bool_t based on an enumeration

[jira] Updated: (AXIS2C-1190) Non blocking samples could be improved by the use of axis2_callback_get_complete function.

[ https://issues.apache.org/jira/browse/AXIS2C-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage updated AXIS2C-1190: - Fix Version/s: 1.4.1 Fixed version is updated 1.4.1 Non blocking samples could be

[jira] Updated: (AXIS2C-1143) Implement CGI deployment support for Axis2/C

[ https://issues.apache.org/jira/browse/AXIS2C-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage updated AXIS2C-1143: - Fix Version/s: 1.4.1 Updating the fixed version to 1.4.1 Implement CGI deployment

[jira] Assigned: (AXIS2C-1205) Redundant adding of handlers into execution chains.

[ https://issues.apache.org/jira/browse/AXIS2C-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage reassigned AXIS2C-1205: Assignee: Damitha Kumarage Redundant adding of handlers into execution chains.

[jira] Updated: (AXIS2C-1156) memory leak in savanc

[ https://issues.apache.org/jira/browse/AXIS2C-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage updated AXIS2C-1156: - Fix Version/s: 1.4.1 Updating the fixed version to 1.4.1 memory leak in savanc

[jira] Updated: (AXIS2C-1128) New enumeration type called axis2_invocation_response_t. needed.

[ https://issues.apache.org/jira/browse/AXIS2C-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage updated AXIS2C-1128: - Updating the fixed version to 1.4.1 New enumeration type called

[jira] Updated: (AXIS2C-645) Need to pass configuration context to axis2_module_shutdown()

[ https://issues.apache.org/jira/browse/AXIS2C-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage updated AXIS2C-645: Fix Version/s: 1.4.1 I think it seems that we need to fix this as the point is not

[jira] Closed: (AXIS2C-1189) svc_client_send_receive could be improved significantly in blocking dual channel case.

[ https://issues.apache.org/jira/browse/AXIS2C-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage closed AXIS2C-1189. Resolution: Fixed I have fixed this some time back. No issure is reported so far. So

[jira] Resolved: (AXIS2C-1205) Redundant adding of handlers into execution chains.

[ https://issues.apache.org/jira/browse/AXIS2C-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage resolved AXIS2C-1205. -- Resolution: Fixed I have fixed this and so far no problem reported. Redundant

[jira] Commented: (AXIS2C-1190) Non blocking samples could be improved by the use of axis2_callback_get_complete function.

[ https://issues.apache.org/jira/browse/AXIS2C-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608975#action_12608975 ] Damitha Kumarage commented on AXIS2C-1190: -- Senaka, This is about non-blocking

[jira] Closed: (AXIS2C-1177) op_ctx_map in conf_ctx is not used.

[ https://issues.apache.org/jira/browse/AXIS2C-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage closed AXIS2C-1177. Resolution: Fixed On an after thought I think that these context maps could be useful

[jira] Closed: (AXIS2C-1176) When axis2_op_register_op_ctx function is called from htttp_worker it return failure with warning.

[ https://issues.apache.org/jira/browse/AXIS2C-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage closed AXIS2C-1176. Resolution: Fixed This is fixed some time back and no problems reported. So closing the

[jira] Resolved: (AXIS2C-1202) Loading modules in alphabetical order has a problem when using module operation level module ref

[ https://issues.apache.org/jira/browse/AXIS2C-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage resolved AXIS2C-1202. -- Resolution: Fixed Assignee: Damitha Kumarage (was: S.Uthaiyashankar) This

[jira] Commented: (AXIS2C-1203) More readable LOG Macros.

[ https://issues.apache.org/jira/browse/AXIS2C-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608309#action_12608309 ] Damitha Kumarage commented on AXIS2C-1203: -- It seems to me that the patch has a

[jira] Commented: (AXIS2C-1201) When same operation is defined in Service level as well as module level, service level operation should be used.

[ https://issues.apache.org/jira/browse/AXIS2C-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608322#action_12608322 ] Damitha Kumarage commented on AXIS2C-1201: -- Module is a way of extention to the

[jira] Commented: (AXIS2C-723) add new transport in Axis2/C

[ https://issues.apache.org/jira/browse/AXIS2C-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608416#action_12608416 ] Damitha Kumarage commented on AXIS2C-723: - We can solve this problem as following.

[jira] Created: (AXIS2C-1205) Redundant adding of handlers into execution chains.

Redundant adding of handlers into execution chains. --- Key: AXIS2C-1205 URL: https://issues.apache.org/jira/browse/AXIS2C-1205 Project: Axis2-C Issue Type: Bug Environment: all

[jira] Assigned: (AXIS2C-1190) Non blocking samples could be improved by the use of axis2_callback_get_complete function.

[ https://issues.apache.org/jira/browse/AXIS2C-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage reassigned AXIS2C-1190: Assignee: Damitha Kumarage Non blocking samples could be improved by the use of

[jira] Closed: (AXIS2C-1162) Axis2/C does not invoke the phases correctly when there are module defined phases.

[ https://issues.apache.org/jira/browse/AXIS2C-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage closed AXIS2C-1162. Resolution: Fixed This is not an issue as this is the designed behaviour. Use can add

[jira] Commented: (AXIS2C-1177) op_ctx_map in conf_ctx is not used.

[ https://issues.apache.org/jira/browse/AXIS2C-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604153#action_12604153 ] Damitha Kumarage commented on AXIS2C-1177: -- I can see that in addressing

[jira] Closed: (AXIS2C-1161) In echo sample client wrong addressing headers passed in the second message.

[ https://issues.apache.org/jira/browse/AXIS2C-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage closed AXIS2C-1161. Resolution: Fixed The reason for this issue is in op_client_two_way_send function we take

[jira] Assigned: (AXIS2C-1189) svc_client_send_receive could be improved significantly in blocking dual channel case.

[ https://issues.apache.org/jira/browse/AXIS2C-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage reassigned AXIS2C-1189: Assignee: Damitha Kumarage svc_client_send_receive could be improved

[jira] Created: (AXIS2C-1189) svc_client_send_receive could be improved significantly in blocking dual channel case.

svc_client_send_receive could be improved significantly in blocking dual channel case. -- Key: AXIS2C-1189 URL: https://issues.apache.org/jira/browse/AXIS2C-1189

[jira] Created: (AXIS2C-1190) Non blocking samples could be improved by the use of axis2_callback_get_complete function.

Non blocking samples could be improved by the use of axis2_callback_get_complete function. -- Key: AXIS2C-1190 URL: https://issues.apache.org/jira/browse/AXIS2C-1190

[jira] Closed: (AXIS2C-1077) axis2_phase_resolver_engage_module_to_svc_from_global should be a local function to phase_resolver.c

[ https://issues.apache.org/jira/browse/AXIS2C-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage closed AXIS2C-1077. Resolution: Fixed Move the above function to phase_resolved.c as a static function

[jira] Closed: (AXIS2C-1084) Retrieving wrong object in the conf.c code

[ https://issues.apache.org/jira/browse/AXIS2C-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage closed AXIS2C-1084. Resolution: Fixed This is fixed now Retrieving wrong object in the conf.c code

[jira] Closed: (AXIS2C-1102) is_in_use property is not checked when freeing operation context

[ https://issues.apache.org/jira/browse/AXIS2C-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage closed AXIS2C-1102. Resolution: Fixed This is fixed is_in_use property is not checked when freeing

[jira] Resolved: (AXIS2C-1160) axis2_svc_client_send_robust_with_op_qname doesn't return AXIS2_FAILURE when the server returns HTTP/1.1 500 Internal Server Error

[ https://issues.apache.org/jira/browse/AXIS2C-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage resolved AXIS2C-1160. -- Resolution: Fixed I tested with server sending HTTP/1.1 500 Interval Server Error.

[jira] Created: (AXIS2C-1176) When axis2_op_register_op_ctx function is called from htttp_worker it return failure with warning.

When axis2_op_register_op_ctx function is called from htttp_worker it return failure with warning. -- Key: AXIS2C-1176 URL:

[jira] Updated: (AXIS2C-1176) When axis2_op_register_op_ctx function is called from htttp_worker it return failure with warning.

[ https://issues.apache.org/jira/browse/AXIS2C-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage updated AXIS2C-1176: - Attachment: op.c.diff When axis2_op_register_op_ctx function is called from

[jira] Created: (AXIS2C-1177) op_ctx_map in conf_ctx is not used.

op_ctx_map in conf_ctx is not used. --- Key: AXIS2C-1177 URL: https://issues.apache.org/jira/browse/AXIS2C-1177 Project: Axis2-C Issue Type: Bug Reporter: Damitha Kumarage I can not see any use

[jira] Created: (AXIS2C-1173) In op_client.c when response envelope is immediately received without waiting, handler already visited case not handled.

In op_client.c when response envelope is immediately received without waiting, handler already visited case not handled. Key: AXIS2C-1173

[jira] Resolved: (AXIS2C-1164) savan_publishing_client_publish() crashes when trying to publish message when more then 1 subscription to this event source exists at moment.

[ https://issues.apache.org/jira/browse/AXIS2C-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage resolved AXIS2C-1164. -- Resolution: Fixed Patch applied savan_publishing_client_publish() crashes when

[jira] Resolved: (AXIS2C-1173) In op_client.c when response envelope is immediately received without waiting, handler already visited case not handled.

[ https://issues.apache.org/jira/browse/AXIS2C-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage resolved AXIS2C-1173. -- Resolution: Fixed This is fixed now In op_client.c when response envelope is

[jira] Created: (AXIS2C-1161) In echo sample client wrong addressing headers passed in the second message.

In echo sample client wrong addressing headers passed in the second message. Key: AXIS2C-1161 URL: https://issues.apache.org/jira/browse/AXIS2C-1161 Project: Axis2-C

[jira] Assigned: (AXIS2C-1156) memory leak in savanc

[ https://issues.apache.org/jira/browse/AXIS2C-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage reassigned AXIS2C-1156: Assignee: Damitha Kumarage memory leak in savanc -

[jira] Created: (AXIS2C-1136) Wrong parameter type doc commented for the function axis2_op_ctx_get_msg_ctx()

Wrong parameter type doc commented for the function axis2_op_ctx_get_msg_ctx() -- Key: AXIS2C-1136 URL: https://issues.apache.org/jira/browse/AXIS2C-1136 Project: Axis2-C

[jira] Commented: (AXIS2C-1129) Processing requests by modules, handlers

[ https://issues.apache.org/jira/browse/AXIS2C-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594528#action_12594528 ] Damitha Kumarage commented on AXIS2C-1129: -- Hi, We have a Axis2/C module called

  1   2   3   4   >