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

Service Client does not Pick the Correct Transport Receiver --- Key: AXIS2C-1210 URL: https://issues.apache.org/jira/browse/AXIS2C-1210 Project: Axis2-C Issue Type: Bug

[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=12609164#action_12609164 ] Supun Kamburugamuva commented on AXIS2C-1210: - I think this prevents dual

[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=12609167#action_12609167 ] Danushka Menikkumbura commented on AXIS2C-1210: --- Even TCP dual-channel

[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] Resolved: (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:all-tabpanel ] Supun Kamburugamuva resolved AXIS2C-1188. - Resolution: Fixed Fixed in the trunk. SOAP fault not working with axis2c

[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=12609181#action_12609181 ] Supun Kamburugamuva commented on AXIS2C-1188: - In in-out MEP we are supposed

[jira] Assigned: (AXIS2C-610) Null pionter exception on complex schema code gen

[ https://issues.apache.org/jira/browse/AXIS2C-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milinda Lakmal Pathirage reassigned AXIS2C-610: --- Assignee: Milinda Lakmal Pathirage (was: Dimuthu Gamage) Null

[jira] Commented: (AXIS2C-1171) axis2_http_server remote crash, invalid read in axutil_stream_peek_socket

[ https://issues.apache.org/jira/browse/AXIS2C-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609193#action_12609193 ] Supun Kamburugamuva commented on AXIS2C-1171: - Hi Fredric, I was trying to

[jira] Resolved: (AXIS2C-610) Null pionter exception on complex schema code gen

[ https://issues.apache.org/jira/browse/AXIS2C-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milinda Lakmal Pathirage resolved AXIS2C-610. - Resolution: Later Fix Version/s: Current (Nightly)

[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-1171) axis2_http_server remote crash, invalid read in axutil_stream_peek_socket

[ https://issues.apache.org/jira/browse/AXIS2C-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609196#action_12609196 ] Frederic Heem commented on AXIS2C-1171: --- If your server crashed, that means that you

[jira] Commented: (AXIS2C-1171) axis2_http_server remote crash, invalid read in axutil_stream_peek_socket

[ https://issues.apache.org/jira/browse/AXIS2C-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609198#action_12609198 ] Supun Kamburugamuva commented on AXIS2C-1171: - I'm on Linux. But I didn't get

[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-1204) memory leak for In-Only message with no parameter

[ https://issues.apache.org/jira/browse/AXIS2C-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609213#action_12609213 ] Supun Kamburugamuva commented on AXIS2C-1204: - I have generated a service and

[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

Problem Reading chunk streams in mod_axis2

Hi devs, When a chunked stream comes to Axis2/C we create a axutil_http_chunked_stream which wraps an axutil_stream. So we use functions defined in util/src/http_chunked_stream.c to deal with the stream. At the beginning calling axutil_http_chunked_stream_start_chunk() function is called to

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

Improving the AXIS2_SVC_SKELETON_INIT_WITH_CONF --- Key: AXIS2C-1211 URL: https://issues.apache.org/jira/browse/AXIS2C-1211 Project: Axis2-C Issue Type: Bug Environment: Ubuntu 7.04

[jira] Updated: (AXIS2C-1124) SOAP action not parsed correctly when it is contained in the content type from a MTOM message

[ https://issues.apache.org/jira/browse/AXIS2C-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajika Kumarasiri updated AXIS2C-1124: -- Attachment: http_transport_utils.c.patch This patch contains a fix to the problem,

[jira] Commented: (AXIS2C-1204) memory leak for In-Only message with no parameter

[ https://issues.apache.org/jira/browse/AXIS2C-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609222#action_12609222 ] Supun Kamburugamuva commented on AXIS2C-1204: - Can you please recheck because

Memory leak woes

Hi All, I have attached couple of small test programs. I am trying to reuse svc_client and I can't figure out the cause of memory leaks in the loop. Any insight will be greatly appreciated. I am using AXIS2/C 1.4.0 on Win32 with Visual Studio 2003 Thank you, Hatim

[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=12609245#action_12609245 ] Frederic Heem commented on AXIS2C-1154: --- The patch doesn't work when used with the

[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=12609246#action_12609246 ] Frederic Heem commented on AXIS2C-1154: --- Actually, there is a cosmetic issue with

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

incorrect debug message in axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync --- Key: AXIS2C-1212 URL: https://issues.apache.org/jira/browse/AXIS2C-1212 Project:

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

server returns HTTP/1.1 500 Internal Server Error for In-Only message - Key: AXIS2C-1213 URL: https://issues.apache.org/jira/browse/AXIS2C-1213 Project: Axis2-C Issue Type:

[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] 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=12609264#action_12609264 ] Frederic Heem commented on AXIS2C-1213: --- Please note that the nofity client works.

[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=12609265#action_12609265 ] Frederic Heem commented on AXIS2C-1213: --- When it fails, here is the server output :

[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-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:comment-tabpanelfocusedCommentId=12609284#action_12609284 ] Frederic Heem commented on AXIS2C-1212: --- Would it be possible to print the

[jira] Created: (AXIS2C-1214) memory leak when server returns an error

memory leak when server returns an error Key: AXIS2C-1214 URL: https://issues.apache.org/jira/browse/AXIS2C-1214 Project: Axis2-C Issue Type: Bug Affects Versions: Current (Nightly)

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

incorrect MEP on the server side Key: AXIS2C-1215 URL: https://issues.apache.org/jira/browse/AXIS2C-1215 Project: Axis2-C Issue Type: Bug Affects Versions: Current (Nightly) Environment: linux

[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=12609294#action_12609294 ] Frederic Heem commented on AXIS2C-1215: --- I was wrong by saying that the MEP is set

[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-1124) SOAP action not parsed correctly when it is contained in the content type from a MTOM message

[ https://issues.apache.org/jira/browse/AXIS2C-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609307#action_12609307 ] Tommy Odom commented on AXIS2C-1124: I tested out the patch and it almost works, I had

[jira] Updated: (AXIS2C-1124) SOAP action not parsed correctly when it is contained in the content type from a MTOM message

[ https://issues.apache.org/jira/browse/AXIS2C-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajika Kumarasiri updated AXIS2C-1124: -- Attachment: http_transport_utils.c_v2.patch The proposed changes are available in

[jira] Commented: (AXIS2C-1124) SOAP action not parsed correctly when it is contained in the content type from a MTOM message

[ https://issues.apache.org/jira/browse/AXIS2C-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609351#action_12609351 ] Tommy Odom commented on AXIS2C-1124: The new patch worked for me, thanks! SOAP

[jira] Created: (AXIS2C-1216) axiom_node_sub_tree_to_string serialize the sub tree wrongly

axiom_node_sub_tree_to_string serialize the sub tree wrongly Key: AXIS2C-1216 URL: https://issues.apache.org/jira/browse/AXIS2C-1216 Project: Axis2-C Issue Type: Bug Affects

[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=12609440#action_12609440 ] Supun Kamburugamuva commented on AXIS2C-1215: - AFAIK the MEP is specified in

[jira] Resolved: (AXIS2C-1184) add http_transport_utils_process_request method which can be used by all modules implementing the http transport

[ https://issues.apache.org/jira/browse/AXIS2C-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Kamburugamuva resolved AXIS2C-1184. - Resolution: Fixed Assignee: Supun Kamburugamuva Method is implemented.