[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-tabpanel&focusedCommentId=12609472#action_12609472 ] Damitha Kumarage commented on AXIS2C-1213: -- Hi Frederic, To solve your problem Se

[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-tabpanel&focusedCommentId=12609471#action_12609471 ] Damitha Kumarage commented on AXIS2C-1215: -- Also please note that if you don't se

Fwd: Specifying MEP in services.xml for in-only operations should be mandatory

Hi all, Discard the previous mail as its subject is incorrect. Previously it wasn't mandatory to specify the MEP in the services XML for operations. But due to the recent fixes non in-out message patterns are not working properly without the MEP in some scenarios. The need arises in case of fault

[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-tabpanel&focusedCommentId=12609470#action_12609470 ] Damitha Kumarage commented on AXIS2C-1215: -- You can set your mep as an operation

Specifying MEP in services.xml for non in-only operations should be mandatory

Hi all, Previously it wasn't mandatory to specify the MEP in the services XML for operations. But due to the recent fixes non in-out message patterns are not working properly without the MEP in some scenarios. The need arises in case of fault messages. If the service business logic is not implemen

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

[ https://issues.apache.org/jira/browse/AXIS2C-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Kamburugamuva resolved AXIS2C-1216. - Resolution: Fixed Assignee: Supun Kamburugamuva Fixed the issue. Please ch

[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. Now

[jira] Resolved: (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 ] Supun Kamburugamuva resolved AXIS2C-1124. - Resolution: Fixed Patch Applied. Thanks Rajika for fixing the issue and Tommy Od

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

[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 Ve

[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-tabpanel&focusedCommentId=12609351#action_12609351 ] Tommy Odom commented on AXIS2C-1124: The new patch worked for me, thanks! > SOAP acti

[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 this

[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-tabpanel&focusedCommentId=12609307#action_12609307 ] Tommy Odom commented on AXIS2C-1124: I tested out the patch and it almost works, I had

[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-tabpanel&focusedCommentId=12609296#action_12609296 ] Damitha Kumarage commented on AXIS2C-1213: -- According to soap 1.1 specication "T

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

[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 fc

[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) Envir

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

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

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

[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-tabpanel&focusedCommentId=12609260#action_12609260 ] Damitha Kumarage commented on AXIS2C-1211: -- Diluka, Can you show me a specific s

[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] 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: A

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

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

[jira] Resolved: (AXIS2C-1135) MacOS version doesn't compile. Patch provided

[ https://issues.apache.org/jira/browse/AXIS2C-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-1135. Resolution: Fixed Fix Version/s: Current (Nightly) Patch applied. Thanks Mi

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-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-tabpanel&focusedCommentId=12609222#action_12609222 ] Supun Kamburugamuva commented on AXIS2C-1204: - Can you please recheck because

[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, Can

[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

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 identi

[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-tabpanel&focusedCommentId=12609214#action_12609214 ] Damitha Kumarage commented on AXIS2C-1210: -- dual channel samples should work for

[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-tabpanel&focusedCommentId=12609213#action_12609213 ] Supun Kamburugamuva commented on AXIS2C-1204: - I have generated a service and

[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-tabpanel&focusedCommentId=12609212#action_12609212 ] Damitha Kumarage commented on AXIS2C-1209: -- If you are going to do these changes

[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-tabpanel&focusedCommentId=12609208#action_12609208 ] Damitha Kumarage commented on AXIS2C-1209: -- Currently listener manager is started

[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-tabpanel&focusedCommentId=12609198#action_12609198 ] Supun Kamburugamuva commented on AXIS2C-1171: - I'm on Linux. But I didn't get

[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-tabpanel&focusedCommentId=12609196#action_12609196 ] Frederic Heem commented on AXIS2C-1171: --- If your server crashed, that means that you

[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-tabpanel&focusedCommentId=12609195#action_12609195 ] Damitha Kumarage commented on AXIS2C-1188: -- There are following scenarios to cons

[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-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-tabpanel&focusedCommentId=12609193#action_12609193 ] Supun Kamburugamuva commented on AXIS2C-1171: - Hi Fredric, I was trying to re

[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 pion

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

[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-tabpanel&focusedCommentId=12609179#action_12609179 ] Damitha Kumarage commented on AXIS2C-1188: -- I have another question. When service

[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 late