You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Dushshantha Chandradasa (JIRA)" <ax...@ws.apache.org> on 2005/06/14 12:46:46 UTC

[jira] Resolved: (AXISCPP-689) SIGSEGV in HTTPTransport::FindTransportPropertyIndex when no SOAPAction set

     [ http://issues.apache.org/jira/browse/AXISCPP-689?page=all ]
     
Dushshantha Chandradasa resolved AXISCPP-689:
---------------------------------------------

    Resolution: Fixed

Fixed.  Made the do.. while loop a while loop with the same condition. 

> SIGSEGV in HTTPTransport::FindTransportPropertyIndex when no SOAPAction set
> ---------------------------------------------------------------------------
>
>          Key: AXISCPP-689
>          URL: http://issues.apache.org/jira/browse/AXISCPP-689
>      Project: Axis-C++
>         Type: Bug
>   Components: Transport (axis3)
>     Reporter: Mark Whitlock
>     Assignee: Dushshantha Chandradasa

>
> 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] <8c...@.>
> [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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira