You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/04/24 08:46:10 UTC
DO NOT REPLY [Bug 17579] -
"port" in "jk_channel_socket_private" should be "int" instead of "short"
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17579>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17579
"port" in "jk_channel_socket_private" should be "int" instead of "short"
ttshiko@sirius.hot.co.jp changed:
What |Removed |Added
----------------------------------------------------------------------------
OS/Version|All |Linux
Version|4.1.18 |4.1.24
------- Additional Comments From ttshiko@sirius.hot.co.jp 2003-04-24 06:46 -------
I did the following test and they seemed to work properly. For example, with a
socket channel's port 49127, Tomcat-4.1.24+Apache-2.0.44+mod_jk2-2.0.2.
1. Search files , each of which includes one or more strings 'short port', from
jk/native2/ recursively.
Then "common/jk_channel_socket.c" and "common/jk_channel_apr_socket.c" are
found. (In "jk_channel_apr_socket.c", type of member "port" in
structure "jk_channel_socket_private" is delared as 'short')
2. Replace 'short port' into 'int port' in those two files and re-compile JK2.
Note that, in the case of replacing to 'unsigned short', they also seemed to
work.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org