[AXISCPP-689] SIGSEGV in HTTPTransport::FindTransportPropertyIndex when no SOAPAction set

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: Transport (axis3)
• Assignee: Marcus Dushshantha Chandradasa
• Reporter: Mark Whitlock
• Created: 14/Jun/05 05:57
• Updated: 14/Jun/05 19:45
• Resolved: 14/Jun/05 19:44

Description

I was using the dynamic client API against a server that did not require SOAPAction to be set. So I did not set SOAPAction in my client application. When I invoked the web service I got a SIGSEGV out of HTTPTransport.FindTransportIndex....

[13/06/2005 21:47:17:000] 1 > Call.invoke() @0012FEE8
[13/06/2005 21:47:17:000] 1 > ClientAxisEngine.process() @003265D8,00326338 [3863320040FFFFFFFF12004CFFFFFFFF1200FFFFFFEC154000] <8c2.@...L....@.>
[13/06/2005 21:47:17:000] 1 > HTTPTransport.getSessionId() @00326338
[13/06/2005 21:47:17:000] 1 < HTTPTransport.getSessionId() @00326338,""
[13/06/2005 21:47:17:000] 1 > HTTPTransport.getServiceName() @00326338
[13/06/2005 21:47:17:000] 1 > HTTPTransport.FindTransportPropertyIndex() "SOAPAction"
[13/06/2005 21:47:17:000] 1 > Call.~Call() @0012FEE8

This is because FindTransportPropertyIndex has a do...while loop that assumes there will always be at least one transport property set, which is true if generated stubs are used, but false when using the dynamic client API.