[ https://issues.apache.org/jira/browse/QPID-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646795#comment-13646795 ]
Chuck Rolke commented on QPID-4801: ----------------------------------- Be careful adding QPID_LOG statements in the Options processing. Depending on where you are in configuring the logging itself QPID_LOG may produce core files. Maybe Alan can recall more specific restrictions or suggest another way out like writing to stderr. It's a circular issue when you can't read the file that describes where you want the logs written. > No error reported on failure to open a configuration file > --------------------------------------------------------- > > Key: QPID-4801 > URL: https://issues.apache.org/jira/browse/QPID-4801 > Project: Qpid > Issue Type: Bug > Components: C++ Client > Affects Versions: 0.20 > Reporter: Darryl L. Pierce > Assignee: Darryl L. Pierce > Priority: Minor > Fix For: 0.23 > > > A critical example of this is when a client app attempts to connect to the > broker using SSL. If the qpidc.conf file is unreadable (the file permissions > deny reading) then the Connection attempts to connect and fails. But rather > than reporting the cause of the failure (that it was unable to load the > connection configuration) it just repeatedly attempts to establish the > connection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org