Re: [Quickfix-developers] Logging of socket function failures

[<OM...@th...>]

This has been brought up before and we are adding additional logging
capabilities.  Part of the reason was that the logging was originally done
on a per session basis (each session has its own log files).  Some of these
calls fail before any session is associated with them.

connect we can easily associate with a session, but bind, listen and accept
arn't associated with any session (or with multiple sessions, depending on
how you look at it).

I guess I would like some input on how people would like to see those.  If
accept fails for instance, should it show up in a global log, or should the
failure show up in each associated session log.  I think that I favor the
latter.  The reason is if a client calls because they are having a problem
connecting, I would want to have all available information inside their log
file.

Any other thoughts?

I do not know if anyone has run QF through purify.  We havn't had any
reports of resource leaks with the C++ API, and many users keep it up 24
hours/day with heavy usage.  There were some reported leaks in the JAVA/JNI
layer, but they have since been resolved.  If you would like to run it
through yourself, I think it would interesting to see the results reported
in this list.

--oren



|---------+----------------------------------------------->
|         |           Chris Patmore                       |
|         |           <Chr...@BT...>            |
|         |           Sent by:                            |
|         |           qui...@li...|
|         |           ceforge.net                         |
|         |                                               |
|         |                                               |
|         |           02/05/2003 10:49 AM                 |
|         |                                               |
|---------+----------------------------------------------->
  >----------------------------------------------------------------------------------------------|
  |                                                                                              |
  |       To:       "'qui...@li...'"                                |
  |        <qui...@li...>                                           |
  |       cc:                                                                                    |
  |       Subject:  [Quickfix-developers] Logging of socket function failures                    |
  >----------------------------------------------------------------------------------------------|




Is there any reason why Utility.c does not report errors from low level
socket calls?

For example if my ThreadedSocketInitiator's call to socket_createConnector
fails in the connect() call, the function silently returns.  The
ThreadedSocketInitiator then sleeps and retries but, again, nothing is
logged.  Failed calls to bind, listen, accept, etc. are also silent.

Regards
                                                 Chris Patmore

PS Has anyone run the library under Purify?
****************************************************************************

This message is confidential to the sender and addressee, and may contain
proprietary or legally privileged information. If you are not the intended
recipient, please delete it from your system, destroy any copies, and
notify
the sender immediately. Opinions stated herein are not necessarily those of
BrokerTec. BrokerTec reserves the right to monitor messages that pass
through it's networks. BrokerTec Europe Ltd is regulated by FSA.


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers