Squid - ftp & SSL: resource temporarily unavailable error

Hello

I am having a problem with Squid Version 2.2.STABLE4, running on
Solaris 2.6
(with latest recommended patches). What may be the cause of the
problem (and
why I am cross-posting to the SOCKS list) is that I am running squid
SOCKSified with socks5 v1.0r10. The socks server is running on Solaris
2.6 in
threaded mode. I have had problems a couple of years ago with SOCKS &
squid
fighting, and was wondering if they were tickling boundary conditions
in
either set of code.

I am running squid with "runsocks squid", and I am the only user
currently using the 2.2 stable4 squid. All works fine, the only issue
is that I get a lot of messages in cache.log when doing ftp and SSL
sessions. Since these are
"temporary" errors, I still get the relevant pages. Note that I am
currently
running squid 1.1.20 with SOCKS and hundreds of users with no
problems.

ftp

---
1999/08/20 14:43:31| ftpReadControlReply: read error: (11) Resource
temporarily unavailable
1999/08/20 14:43:50| ftpReadControlReply: read error: (11) Resource
temporarily unavailable
1999/08/20 14:43:53| ftpDataRead: read error: (11) Resource
temporarily unavailable
1999/08/20 14:44:01| ftpReadControlReply: read error: (11) Resource
temporarily unavailable
1999/08/20 14:44:04| ftpDataRead: read error: (11) Resource
temporarily unavailable
1999/08/20 14:44:37| ftpReadControlReply: read error: (11) Resource
temporarily unavailable
1999/08/20 14:44:39| ftpReadControlReply: read error: (11) Resource
temporarily unavailable
SSL
---
1999/08/20 12:58:23| sslWriteServer: FD 27: write failure: (11)
Resource temporarily unavailable.
1999/08/20 12:58:23| sslWriteServer: FD 27: write failure: (11)
Resource temporarily unavailable.
1999/08/20 12:58:23| sslReadServer: FD 27: read failure: (11) Resource
temporarily unavailable
1999/08/20 12:59:43| sslWriteServer: FD 19: write failure: (11)
Resource temporarily unavailable.
1999/08/20 12:59:43| sslWriteServer: FD 19: write failure: (11)
Resource temporarily unavailable.
I get no other errors from SOCKS or Squid. I am not having problems or
errors with file descriptors, semaphores, threads or the like.
My question is - what would be causing this and should I be worried?
Can I
release the new version of squid into production with these errors?
Thanks
John