Bug 4823 - Raw Socket interface failing to accept connections
Summary: Raw Socket interface failing to accept connections
Status: CLOSED WONTFIX
Alias: None
Product: Koha
Classification: Unclassified
Component: SIP2 (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low normal (vote)
Assignee: Colin Campbell
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-27 14:44 UTC by Colin Campbell
Modified: 2014-12-07 20:02 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Colin Campbell 2010-05-27 14:44:16 UTC
This has been reported on 3M self checkouts in both the US and UK.

Sip working ok for days (weeks even) then suddenly the server refuses to accept connections. Restarting sip does not always rectify (immediately) the problem. Suggests the socket gets stuffed (technical term covering a number of possible error conditions). 

A rare occurence and not easily repeatable. May occur intermittently when the symptom is very poor response time (sip messages are not being responded to, are timing out then server responds on second or third retry)
Comment 1 Colin Campbell 2013-09-02 13:02:40 UTC
Closing as resolved. This may have been caused by a configuration issue. If spare servers is set to zero the server will not ensure that a server is available to answer incoming connections. When a unit attempts to reconnect all existing servers may be sitting on old connections they still think are valid (waiting for the next request that never comes), as no spare has started up the connection is refused