Tks. I actually tried to hard code the port number using:
ip4addr.sin_port = htons(5566);
And the following output from netstat indicates that I have a socket
listening at port 5566.
tcp0 0 0.0.0.0:55660.0.0.0:* LISTEN
It looks quite strange. TCPDump canno
Right. So the situation is that the existing design dates from a time when
threads and scheduling for Unix were primitive. It was not uncommon in
those
days for threads to "go away" for half a second, a second or more in a
loaded system.
To deal with this, the current design is non-blocking all
On 09/11/2011 07:47 PM, steven liu wrote:
It is 32-bit. Tks.
Ok, confirmed, on 32-bit debug builds this triggers the assert. :/ Did
you file a bug ?
-- Leif
While I think this is not an ideal solution, but for the reasons you
mentioned (re invasiveness/ease), I'd be willing to accept it.
I think I would prefer to fix the queuing so that it can't leave an
unserviced request. But if the "fix" of waking a thread every now and
again is well documented it
Monday, September 12, 2011, 10:28:17 AM, you wrote:
> The server port comes from a URL, e.g. http://10.44.10.1:80, and I just atoi
> the port. I have checked with a network trace that the correct port is being
> connected to. With previous versions of Traffic Server I never had to
> use ntohs and
The server port comes from a URL, e.g. http://10.44.10.1:80, and I just atoi
the port. I have checked with a network trace that the correct port is being
connected to. With previous versions of Traffic Server I never had to
use ntohs and
just passed in the atoied number.
On 12 September 2011 15:57
Actually, Chris, you should use htons since this is going from host to network
order. However on all modern systems htons() and ntohs() are the same function.
Some of us old timers remember systems where that wasn't the case but those
have long since faded to memories.
I think TSNetConnect gets
On 3.1 I have to use the ntohs function for the port number when using
TsNetConnect. Have you tried this?
On 12 September 2011 02:33, steven liu wrote:
> Thanks. Yes. I am setting port using hons() using following codes.
>
> struct sockaddr_in ip4addr;
> ip4addr.sin_family = AF_INET;
> ip4addr.s