saves having to specify env vars for the dbs etc
The cert db is opened in NSSInit() and is therefore a process wide option, not per connection. The same applies for the password file. Only the cert-name is a connection level option - making that configurable through the connection options would indeed be valuable but will require more work than justified for 1.3. Note the ssl options can also be set in /etc/qpid/qpidc.conf.
Resolved upstream in revision 1066508. https://issues.apache.org/jira/browse/QPID-3031
VERIFIED on rhel5.6 rhel6.1 (i686/x86_64) # rpm -qa | grep qpid qpid-java-common-0.10-4.el6.noarch qpid-java-jca-0.10-4.el6.noarch qpid-cpp-client-0.10-3.el6.i686 qpid-cpp-client-ssl-0.10-3.el6.i686 qpid-cpp-client-devel-0.10-3.el6.i686 qpid-cpp-server-rdma-0.10-3.el6.i686 ruby-qpid-qmf-0.10-6.el6.i686 qpid-qmf-devel-0.10-6.el6.i686 qpid-tools-0.10-3.el6.noarch qpid-java-client-0.10-4.el6.noarch qpid-cpp-server-0.10-3.el6.i686 qpid-cpp-server-xml-0.10-3.el6.i686 qpid-cpp-server-cluster-0.10-3.el6.i686 qpid-cpp-server-devel-0.10-3.el6.i686 python-qpid-0.10-1.el6.noarch qpid-java-example-0.10-4.el6.noarch qpid-qmf-0.10-6.el6.i686 python-qpid-qmf-0.10-6.el6.i686 qpid-cpp-server-store-0.10-3.el6.i686 qpid-cpp-client-devel-docs-0.10-3.el6.noarch qpid-cpp-client-rdma-0.10-3.el6.i686 qpid-cpp-server-ssl-0.10-3.el6.i686 rh-qpid-cpp-tests-0.10-3.el6.i686 qpid-tests-0.10-1.el6.noarch --> VERIFIED
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2011-0890.html