Thread: [Quickfix-developers] Acceptor Shutdown Issues
Brought to you by:
orenmnero
From: Jon D. <jd...@wi...> - 2004-10-13 17:40:39
|
I've noticed a problem we're having when our acceptor app is shutdown while clients are connected. It seems as if the sockets are kept in a CLOSE_WAIT state after shutdown when running netstat filtering for our listening port. The reason why I ask this is because we can't restart the acceptor until the OS clears out the sockets in the CLOSE_WAIT state. Could this be a case of not properly shutting down the server? Up unitl now, I thought I was shutting down correctly but now I'm wondering. SocketAcceptor QF 1.9.2 RHAS 2.1 g++ 3.0.4 -jd- |
From: Jon D. <jd...@wi...> - 2004-10-13 17:55:35
|
Sorry, QF 1.9.0 not 1.9.2 > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html QuickFIX FAQ: > http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ QuickFIX > Support: http://www.quickfixengine.org/services.html > > I've noticed a problem we're having when our acceptor app is shutdown > while clients are connected. It seems as if the sockets are kept in a > CLOSE_WAIT state after shutdown when running netstat filtering for our > listening port. > > The reason why I ask this is because we can't restart the acceptor until > the OS clears out the sockets in the CLOSE_WAIT state. > > Could this be a case of not properly shutting down the server? Up unitl > now, I thought I was shutting down correctly but now I'm wondering. > > > SocketAcceptor > QF 1.9.2 > RHAS 2.1 > g++ 3.0.4 > > > -jd- > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give > us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find > out more http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers -- |
From: Jon D. <jd...@wi...> - 2004-10-13 18:03:49
|
gah! ... silly me copied over an older lib ... please disregard. -jd- > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html QuickFIX FAQ: > http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ QuickFIX > Support: http://www.quickfixengine.org/services.html > > Sorry, QF 1.9.0 not 1.9.2 > >> QuickFIX Documentation: >> http://www.quickfixengine.org/quickfix/doc/html/index.html QuickFIX >> FAQ: http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ >> QuickFIX Support: http://www.quickfixengine.org/services.html >> >> I've noticed a problem we're having when our acceptor app is shutdown >> while clients are connected. It seems as if the sockets are kept in a >> CLOSE_WAIT state after shutdown when running netstat filtering for our >> listening port. >> >> The reason why I ask this is because we can't restart the acceptor >> until the OS clears out the sockets in the CLOSE_WAIT state. >> >> Could this be a case of not properly shutting down the server? Up >> unitl now, I thought I was shutting down correctly but now I'm >> wondering. >> >> >> SocketAcceptor >> QF 1.9.2 >> RHAS 2.1 >> g++ 3.0.4 >> >> >> -jd- >> >> >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: IT Product Guide on >> ITManagersJournal Use IT products in your business? Tell us what you >> think of them. Give us Your Opinions, Get Free ThinkGeek Gift >> Certificates! Click to find out more >> http://productguide.itmanagersjournal.com/guidepromo.tmpl >> _______________________________________________ >> Quickfix-developers mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfix-developers > > > -- > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give > us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find > out more http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers -- |
From: Caleb E. <cal...@gm...> - 2004-10-13 18:44:32
|
Have you set SocketReuseAddress=Y in your config file? -- Caleb Epstein cal...@gm... |
From: Andrew S. <ab...@gm...> - 2004-10-13 20:55:52
|
Do you have SocketReuseAddress=Y in your config? On Wed, 13 Oct 2004 12:48:26 -0500 (CDT), Jon Dahl <jd...@wi...> wrote: > QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX FAQ: http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ > QuickFIX Support: http://www.quickfixengine.org/services.html > > Sorry, QF 1.9.0 not 1.9.2 > > > QuickFIX Documentation: > > http://www.quickfixengine.org/quickfix/doc/html/index.html QuickFIX FAQ: > > http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ QuickFIX > > Support: http://www.quickfixengine.org/services.html > > > > I've noticed a problem we're having when our acceptor app is shutdown > > while clients are connected. It seems as if the sockets are kept in a > > CLOSE_WAIT state after shutdown when running netstat filtering for our > > listening port. > > > > The reason why I ask this is because we can't restart the acceptor until > > the OS clears out the sockets in the CLOSE_WAIT state. > > > > Could this be a case of not properly shutting down the server? Up unitl > > now, I thought I was shutting down correctly but now I'm wondering. > > > > > > SocketAcceptor > > QF 1.9.2 > > RHAS 2.1 > > g++ 3.0.4 > > > > > > -jd- > > > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > > Use IT products in your business? Tell us what you think of them. Give > > us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find > > out more http://productguide.itmanagersjournal.com/guidepromo.tmpl > > _______________________________________________ > > Quickfix-developers mailing list > > Qui...@li... > > https://lists.sourceforge.net/lists/listinfo/quickfix-developers > > -- > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers > |
From: Oren M. <or...@qu...> - 2004-10-13 18:03:23
|
Have you tried setting SocketReuseAddress=Y? On Oct 13, 2004, at 12:33 PM, Jon Dahl wrote: > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX FAQ: > http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ > QuickFIX Support: http://www.quickfixengine.org/services.html > > I've noticed a problem we're having when our acceptor app is shutdown > while clients are connected. It seems as if the sockets are kept in a > CLOSE_WAIT state after shutdown when running netstat filtering for our > listening port. > > The reason why I ask this is because we can't restart the acceptor > until > the OS clears out the sockets in the CLOSE_WAIT state. > > Could this be a case of not properly shutting down the server? Up unitl > now, I thought I was shutting down correctly but now I'm wondering. > > > SocketAcceptor > QF 1.9.2 > RHAS 2.1 > g++ 3.0.4 > > > -jd- > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on > ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give > us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out > more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers > |
From: Jon D. <jd...@wi...> - 2004-10-13 18:57:19
|
>Have you tried setting SocketReuseAddress=Y No I have not, but interestingly enough, it did this with an earlier version of the QF library pre 1.9.0. With 1.9.0 it doesn't do it anymore. I'll add this to the config file to be safe. -jd- > Have you tried setting SocketReuseAddress=Y? > > On Oct 13, 2004, at 12:33 PM, Jon Dahl wrote: > >> QuickFIX Documentation: >> http://www.quickfixengine.org/quickfix/doc/html/index.html >> QuickFIX FAQ: >> http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ >> QuickFIX Support: http://www.quickfixengine.org/services.html >> >> I've noticed a problem we're having when our acceptor app is shutdown >> while clients are connected. It seems as if the sockets are kept in a >> CLOSE_WAIT state after shutdown when running netstat filtering for our >> listening port. >> >> The reason why I ask this is because we can't restart the acceptor >> until >> the OS clears out the sockets in the CLOSE_WAIT state. >> >> Could this be a case of not properly shutting down the server? Up >> unitl now, I thought I was shutting down correctly but now I'm >> wondering. >> >> >> SocketAcceptor >> QF 1.9.2 >> RHAS 2.1 >> g++ 3.0.4 >> >> >> -jd- >> >> >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: IT Product Guide on >> ITManagersJournal >> Use IT products in your business? Tell us what you think of them. Give >> us >> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out >> more >> http://productguide.itmanagersjournal.com/guidepromo.tmpl >> _______________________________________________ >> Quickfix-developers mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfix-developers -- |