|
Home > Archive > SQL Anywhere for Linux > April 2006 > tcpip listener stuck
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
tcpip listener stuck
|
|
|
| x64 linux asa 9.0.2.3249.
just found asa tcp/ip listener on my production box has
stoped to accept connection.
already opened connection is functional. shmem is ok.
numer of opened connections is 6, no locks, no high cpu
utilization .
application that works over 6 connections continues to work
without any problem.
smth wrong in x64 tcp/ip internals, similar problem i found
using built-in http.
has any picularities/settings in using tcp/ip connection on
x64 that can affect in this way? for instance application
open/close many connections.
| |
| Mark Culp 2006-04-06, 1:24 pm |
| If you have started the http server in the engine (i.e. -xs ...),
check the number of file handles that are open by the process
(i.e. ls /proc/<pid_of_engine> ) - if this looks like there are
a lot of handles (sockets) open, then you need to get the latest
9.0.2 EBF (build 3264 or higher) - there was a handle leak in the
http server, and this could result in it appearing that no new
connections could be established.
Also check your sysv semaphore settings on your computer.
(run ipcs and see how many semaphores are open)
--
Mark Culp
SQLAnywhere Research and Development
-------------------------------------------------------------------------
** Whitepapers, TechDocs, bug fixes are all available through the **
** iAnywhere Developer Community at http://www.ianywhere.com/developer **
-------------------------------------------------------------------------
Alex wrote:
>
> x64 linux asa 9.0.2.3249.
>
> just found asa tcp/ip listener on my production box has
> stoped to accept connection.
> already opened connection is functional. shmem is ok.
> numer of opened connections is 6, no locks, no high cpu
> utilization .
> application that works over 6 connections continues to work
> without any problem.
>
> smth wrong in x64 tcp/ip internals, similar problem i found
> using built-in http.
>
> has any picularities/settings in using tcp/ip connection on
> x64 that can affect in this way? for instance application
> open/close many connections.
|
|
|
|
|