You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Mikhail Melamud (JIRA)" <ji...@apache.org> on 2012/08/13 21:24:37 UTC
[jira] [Created] (AMQCPP-421) cms crashing when SSL certificate's
subject alternative name doesn't match the specified in failover URI
Mikhail Melamud created AMQCPP-421:
--------------------------------------
Summary: cms crashing when SSL certificate's subject alternative name doesn't match the specified in failover URI
Key: AMQCPP-421
URL: https://issues.apache.org/jira/browse/AMQCPP-421
Project: ActiveMQ C++ Client
Issue Type: Bug
Components: CMS Impl, Decaf
Affects Versions: 3.4.2, 3.4.0
Environment: Windows 7, self-signed SSL certificate. Broker version is 5.6.0
Reporter: Mikhail Melamud
Assignee: Timothy Bish
When we specify self-signed certificate in PEM-formatted file as value of the "decaf.net.ssl.trustStore" property and SAN that does't match any name in failover URI, cms is crashing on "R6025 Pure Virtual Function Call" run-time error. I think, the issue can be attributed to multithreading... After ??Server Certificate Name doesn't match the URI Host Name value.?? exception is thrown, CMS is trying to fire an exception using listener pointer that is not instantiated properly in _void TransportFilter::fire( const decaf::lang::Exception& ex )_ method... It is not happening all the time, so a simple unit test won't do... I'm attaching a bit re-factored _HelloWorldProducer_ app and the certificate file that I used... There is possibility that it has something to with InactivityMonitor injected into transport filter chain... When I tried {color:blue}"failover://(ssl://dev1467:61618?transport.useInactivityMonitor=false){color} instead of {color:blue}"failover://(ssl://dev1467:61618)"{color} it behaves much more stable, i.e. client app can be re-run many more times without a crash, still crashing though in OpenFormatNegotiator
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (AMQCPP-421) cms crashing when SSL certificate's
subject alternative name doesn't match the specified in failover URI
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQCPP-421.
-------------------------------
Resolution: Duplicate
Duplicates the issue described in AMQCPP-422
> cms crashing when SSL certificate's subject alternative name doesn't match the specified in failover URI
> --------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-421
> URL: https://issues.apache.org/jira/browse/AMQCPP-421
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2
> Environment: Windows 7, self-signed SSL certificate. Broker version is 5.6.0
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
>
> When we specify self-signed certificate in PEM-formatted file as value of the "decaf.net.ssl.trustStore" property and SAN that does't match any name in failover URI, cms is crashing on "R6025 Pure Virtual Function Call" run-time error. I think, the issue can be attributed to multithreading... After ??Server Certificate Name doesn't match the URI Host Name value.?? exception is thrown, CMS is trying to fire an exception using listener pointer that is not instantiated properly in _void TransportFilter::fire( const decaf::lang::Exception& ex )_ method... It is not happening all the time, so a simple unit test won't do... I'm attaching a bit re-factored _HelloWorldProducer_ app and the certificate file that I used... There is possibility that it has something to with InactivityMonitor injected into transport filter chain... When I tried {color:blue}"failover://(ssl://dev1467:61618?transport.useInactivityMonitor=false){color} instead of {color:blue}"failover://(ssl://dev1467:61618)"{color} it behaves much more stable, i.e. client app can be re-run many more times without a crash, still crashing though in OpenFormatNegotiator
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-421) cms crashing when SSL certificate's
subject alternative name doesn't match the specified in failover URI
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433542#comment-13433542 ]
Timothy Bish commented on AMQCPP-421:
-------------------------------------
Have you tested this using the latest release v3.4.4 ?
> cms crashing when SSL certificate's subject alternative name doesn't match the specified in failover URI
> --------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-421
> URL: https://issues.apache.org/jira/browse/AMQCPP-421
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2
> Environment: Windows 7, self-signed SSL certificate. Broker version is 5.6.0
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
>
> When we specify self-signed certificate in PEM-formatted file as value of the "decaf.net.ssl.trustStore" property and SAN that does't match any name in failover URI, cms is crashing on "R6025 Pure Virtual Function Call" run-time error. I think, the issue can be attributed to multithreading... After ??Server Certificate Name doesn't match the URI Host Name value.?? exception is thrown, CMS is trying to fire an exception using listener pointer that is not instantiated properly in _void TransportFilter::fire( const decaf::lang::Exception& ex )_ method... It is not happening all the time, so a simple unit test won't do... I'm attaching a bit re-factored _HelloWorldProducer_ app and the certificate file that I used... There is possibility that it has something to with InactivityMonitor injected into transport filter chain... When I tried {color:blue}"failover://(ssl://dev1467:61618?transport.useInactivityMonitor=false){color} instead of {color:blue}"failover://(ssl://dev1467:61618)"{color} it behaves much more stable, i.e. client app can be re-run many more times without a crash, still crashing though in OpenFormatNegotiator
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira