Alex and Sinisa,
>Sinisa,
>SM> There is no thread 4 because may be it has died.
>SM> If your daemon is multithreaded, then some of it's thread has may be
>SM> died, thus causing timeout.
>SM> I hate myself for saying this, as logically there could be no
>SM> connection, but Just out of curiosity if you build without Innobase
>SM> yourself (explained as above) would you still get timeouts ??
>SM> Sorry for troubling you , but experimentation is one of the items that
>SM> has remained.
> You don't trouble me at all ! I really appreciate your help in
> trying to solve that problem.
> I will try to rebuild on my own without Innobase and create MyIsam
> tables form my application. I'll let you know.
from the debug log Alex sent some time ago I see that it is a real
thread calling thr_alarm and sending the signal 14 (in the log below
it is thread 11).
Maybe the Solaris debugger does not show the connection thread if
it has called for thr-alarm, or if it is cached.
From the discussion I have got the impression that there is a
phantom connection left hanging in Solaris: the MySQL server
detects this connection and tries to answer to it, but there is
no client process behind the connection.
Regards,
Heikki
...... Debug log .................
T@1 : | | info: Thread 2 created
T@1 : | <create_new_thread
T@11 : <end_thread
T@11 : info: check_connections called by thread 2
T@11 : general: New connection received on socket (9)
T@11 : general: Host: localhost
T@11 : >vio_keepalive
T@11 : | enter: sd=9, set_keep_alive=1
T@11 : <vio_keepalive
T@11 : >net_flush
T@11 : | >vio_is_blocking
T@11 : | | exit: 0
T@11 : | <vio_is_blocking
T@11 : | >net_real_write
T@11 : | | >vio_write
T@11 : | | | enter: sd=9, buf=d4860b8, size=54
T@11 : | | | exit: 54
T@11 : | | <vio_write
T@11 : | <net_real_write
T@11 : <net_flush
T@11 : >vio_is_blocking
T@11 : | exit: 0
T@11 : <vio_is_blocking
T@11 : >vio_read
T@11 : | enter: sd=9, buf=d4860b8, size=4
T@11 : | error: Got error 11 during read
T@11 : | exit: -1
T@11 : <vio_read
T@11 : info: vio_read returned -1, errno: 11
T@11 : >thr_alarm
T@11 : | enter: thread: T@11 sec: 5
T@11 : | info: reschedule
T@11 : <thr_alarm
T@11 : >vio_is_blocking
T@11 : | exit: 0
T@10 : | >process_alarm
T@10 : | | info: sig: 14 active alarms: 1
T@11 : <vio_is_blocking
T@11 : >vio_blocking
> Regards,
> Alex.
