[jira] Commented: (QPID-2216) Error for missing ssl-cert-db option reports wrong option name

2009-12-10 Thread Gordon Sim (JIRA)

[ 
https://issues.apache.org/jira/browse/QPID-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788696#action_12788696
 ] 

Gordon Sim commented on QPID-2216:
--

I've fixed the second point. I'm not sure about the first point, I don't think 
we have a consistently agreed and understood approach to log levels. On one 
hand (as the module will always be loaded in a default installation), always 
having that message reported adds noise and confusion, on the other hand when 
someone is trying to configure it they may not think to turn on info level 
logging for ssl.

 Error for missing ssl-cert-db option reports wrong option name
 --

 Key: QPID-2216
 URL: https://issues.apache.org/jira/browse/QPID-2216
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
Affects Versions: 0.6
 Environment: Linux
Reporter: Steve Huston
Priority: Minor

 On Linux, trying to run the broker with the ssl module, but forgetting the 
 ssl-cert-db option, yields:
 2009-11-24 18:48:18 info SSL plugin not enabled, you must set 
 --qpid-ssl-cert-db to enable it.
 Two problems:
 1. It's an 'info' message, so is not visible with default logging level set; 
 I added -t to see this.
 2. the option that must be set is --ssl-cert-db, not --qpid-ssl-cert-db 
 (--help reports it correctly)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org



[jira] Commented: (QPID-2216) Error for missing ssl-cert-db option reports wrong option name

2009-12-10 Thread Steve Huston (JIRA)

[ 
https://issues.apache.org/jira/browse/QPID-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789098#action_12789098
 ] 

Steve Huston commented on QPID-2216:


I see your point, Gordon, but if a module is loading but can't do anything 
useful, I think it's a good idea to let the user know that. If there's a 
problem logged, the user can decide to a) fix it, b) avoid loading a module 
they won't use, c) ignore it.

 Error for missing ssl-cert-db option reports wrong option name
 --

 Key: QPID-2216
 URL: https://issues.apache.org/jira/browse/QPID-2216
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
Affects Versions: 0.6
 Environment: Linux
Reporter: Steve Huston
Priority: Minor

 On Linux, trying to run the broker with the ssl module, but forgetting the 
 ssl-cert-db option, yields:
 2009-11-24 18:48:18 info SSL plugin not enabled, you must set 
 --qpid-ssl-cert-db to enable it.
 Two problems:
 1. It's an 'info' message, so is not visible with default logging level set; 
 I added -t to see this.
 2. the option that must be set is --ssl-cert-db, not --qpid-ssl-cert-db 
 (--help reports it correctly)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org