tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric J. Pinnell" <e...@iCky.org>
Subject RE: mod jk2 problem, segmetation fault
Date Wed, 02 Jul 2003 03:10:41 GMT
Hi,

For anyone that cares I changed the 'long's to 'unsigned short's with some
advice from Jeff Trawick.

Still looks good after a some load.  It's not being hammered but it looks
ok.

-e

On Tue, 1 Jul 2003, Eric J. Pinnell wrote:

> Hi,
>
> This tweak on
> jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2/common/jk_channel_socket.c
>
> seems to fix the high TCP port issue.
>
> Alhtough I haven't found any trouble with it yet I have never written
> anything for JK2 and am unfamiliar with it's inner workings.  So I
> wouldn't bet the farm on it.
>
>
> bash-2.04$ diff jk_channel_socket.c.old jk_channel_socket.c.new
>
> 94c94
> <     short port;
> ---
> >     long port;
> 110c110
> <                                                short port,
> ---
> >                                                long port,
> 204c204
> < static int JK_METHOD jk2_channel_socket_resolve(jk_env_t *env, char
> *host, short port,
> ---
> > static int JK_METHOD jk2_channel_socket_resolve(jk_env_t *env, char
> *host, long port,
>
>
> -e
>
>
>
>
>
> On Tue, 1 Jul 2003, Shapira, Yoav wrote:
>
> >
> > Howdy,
> > Well, that provided a bit of amusement for today ;) ;)
> >
> > You can put in an enhancement request to use 32bits for the port number.
> > It's a low-priority item, not sure it will be done any time soon.
> >
> > Yoav Shapira
> >
> > >> >14009 works
> > >> >48009 doesn't.  The apache error log says that it can't connect.
> > >> >According to tomcat the Connector is listening and a netstat shows
> > the
> > >> >port in a LISTEN state.
> > >>
> > >> I have a random guess harkening back to my C days: > 32767 won't
> > work.
> > >> Give it a shot.  Has to do with 2^16 int size bytes used to store the
> > >> port number.
> > >>
> > >
> > >
> > >You got it.  :)  32767 yes, 32768 no.
> > >
> > >So is this still a bug?  or is this a "workaround"?
> >
> >
> >
> > This e-mail, including any attachments, is a confidential business communication,
and may contain information that is confidential, proprietary and/or privileged.  This e-mail
is intended only for the individual(s) to whom it is addressed, and may not be saved, copied,
printed, disclosed or used by anyone else.  If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and notify the sender.  Thank you.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message