Re: [Firebird-test] [FB-Tracker] Updated: (CORE-2808) XNET classic server client connection process timeout failure blocks subsequent connect attempts.

[Brain D. <bra...@ya...>]

Any idea why I can't get to tracker.firebirdsql.org?  All I get is an empty page when I try.  Figured it was down or something, however you and Dmitry both updated this issue.




--- On Thu, 1/14/10, Pavel Cisar (JIRA) <tr...@fi...> wrote:

> From: Pavel Cisar (JIRA) <tr...@fi...>
> Subject: [FB-Tracker] Updated: (CORE-2808) XNET classic server client connection process timeout failure blocks subsequent connect attempts.
> To: bra...@ya...
> Date: Thursday, January 14, 2010, 4:10 AM
> 
>      [ http://tracker.firebirdsql.org/browse/CORE-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
> 
> Pavel Cisar updated CORE-2808:
> ------------------------------
> 
>     Security:     (was:
> Managers)
>     Reporter: Brenden Walker  (was: Pavel
> Cisar)
> 
> > XNET classic server client connection process timeout
> failure blocks subsequent connect attempts.
> >
> -------------------------------------------------------------------------------------------------
> >
> >             
>    Key: CORE-2808
> >             
>    URL: http://tracker.firebirdsql.org/browse/CORE-2808
> >         
>    Project: Firebird Core
> >          Issue Type: Bug
> >          Components: Engine
> >    Affects Versions: 2.0.5
> >         Environment:
> Windows XP, for me problem only happens on slower machines,
> Pentium 4, 512mb ram, NON hyperthreader/multicore.
> >            Reporter:
> Brenden Walker
> >
> > When the client times out waiting for
> xnet_response_event, the client exits clean.  The
> server however continues on and sets the
> xnet_response_event.  
> > This event sits out there for the next client who
> happily 'grabs' onto it and thinks a connection has been
> established.  The response.map_num is
> XNET_INVALID_MAP_NUM and the client errors out.  Once a
> timeout happens no further XNET connections can be made
> until the server is restarted as each client will grab the
> previous clients event.
> > I've seen similar symptoms on 2.1.3, however the cause
> in the cases I've been able to adequately review has not
> been due to exceeding xnet_connect_timeout.  When I get
> more information on that I'll post a new issue.
> > Workaround for this particular problem is to increase
> the timeout via new config file parameter created in http://tracker.firebirdsql.org/browse/CORE-2769
> 
> -- 
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the
> administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
> 
>         
>