[ http://issues.apache.org/jira/browse/AXISCPP-949?page=comments#action_12369618 ]
Adrian Dick commented on AXISCPP-949: ------------------------------------- Hi, I have done some quick testing (thanks also to James) and the described problem doesn't appear to be present on Windows, Linux or AIX. However, looking at the failure point (according to the trace in the original conversation on the mailing list) I noticed some inconsistencies that could potentially cause problems on some platforms: >From HTTPChannel.cpp Line 440: unsigned int uiPort = m_URL.getPort(); // getPort() actually returns unsigned short int but I don't see that being a problem ... ... Line 448: sprintf( szPort, "%hd", uiPort); // we could use "%hu" to be explicit that this is an unsigned int. Perhaps I'm missing a subtlty of C/C++ and this isn't the real problem - and we're just seeing a firewall issue, or somesuch. Adrian > Client call on a great port number (endpoint URL) fails > ------------------------------------------------------- > > Key: AXISCPP-949 > URL: http://issues.apache.org/jira/browse/AXISCPP-949 > Project: Axis-C++ > Type: Bug > Components: Client - Engine, Client - Stub > Versions: 1.6 Alpha > Environment: Solaris 8 > Reporter: Antoine Galataud > > On solaris 8, and maybe other platforms, there is no way of calling an apache > deployed webservice on a great port number (e.g: 63010). The max value seems > to be ~= 32000. > According to Adrian Dick : > "there is an inconsistent mix of signed and unsigned short values when > handling the port number. It is very likely this is the cause of your > problems." -- 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
