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:26:37 UTC
[jira] [Created] (AMQCPP-422) 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.
Mikhail Melamud created AMQCPP-422:
--------------------------------------
Summary: 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.
Key: AMQCPP-422
URL: https://issues.apache.org/jira/browse/AMQCPP-422
Project: ActiveMQ C++ Client
Issue Type: Bug
Components: CMS Impl, Decaf
Affects Versions: 3.4.2, 3.4.0
Environment: Broker: 5.6.0,
CMS 3.4.2
Windows
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] [Updated] (AMQCPP-422) 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.
Posted by "Mikhail Melamud (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Melamud updated AMQCPP-422:
-----------------------------------
Attachment: AMQTest.cpp
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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-422) 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.
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433547#comment-13433547 ]
Timothy Bish commented on AMQCPP-422:
-------------------------------------
Have you tested this using the latest release v3.4.4 ?
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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-422) 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.
Posted by "Mikhail Melamud (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433450#comment-13433450 ]
Mikhail Melamud commented on AMQCPP-422:
----------------------------------------
As I mentioned, it takes several re-tries to reproduce the issue. I've used simple shell loop to do it: FOR /L %G IN (0 1 15) DO TestApp.exe
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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-422) 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.
Posted by "Jeffrey B (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435219#comment-13435219 ]
Jeffrey B commented on AMQCPP-422:
----------------------------------
I finally got it to work.
It doesnt seem to be written anywhere, but the CN field for the certificate has to match the actual resolved hostname, and possibly the broker name too, (probably not that though becuase you can have more than one).
so CN cant be your first and last name like java asks for or anything else, and not your IP either i guess, so if youre working internally, somthing like machxx1223, externally something like www.myserver.com
Also when i didnt specify an algorithm for keytool, it did SHA1withDSA, and I dont think this was supported by openssl, if you say -keyalg RSA, you get SHA1withRSA, which works.
Last thing, whenever you make changes to your certificates, you probably need to shut down the broker, rerun setSSLOpts.bat, or whatever you have, and then start the server again.
After all this, mine finally started working.
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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] [Updated] (AMQCPP-422) 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.
Posted by "Mikhail Melamud (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Melamud updated AMQCPP-422:
-----------------------------------
Attachment: (was: AMQTest.cpp)
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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] [Updated] (AMQCPP-422) 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.
Posted by "Mikhail Melamud (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Melamud updated AMQCPP-422:
-----------------------------------
Attachment: AMQTest.cpp
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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-422) 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.
Posted by "Jeffrey B (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435118#comment-13435118 ]
Jeffrey B commented on AMQCPP-422:
----------------------------------
I am having this or a very similar issue in 3.4.4 running on HPUX 11.31
When I start my client with ssl connector, one of two things happens.
1) It instantly says:
Server Certificate Name doesn't match the URI Host Name value.
FILE: decaf/internal/net/ssl/openssl/OpenSSLSocket.cpp, LINE: 708
FILE: decaf/internal/net/ssl/openssl/OpenSSLSocket.cpp, LINE: 421
FILE: decaf/internal/net/ssl/openssl/OpenSSLSocket.cpp, LINE: 595
FILE: decaf/internal/net/ssl/openssl/OpenSSLSocketOutputStream.cpp, LINE: 93
FILE: decaf/io/OutputStream.cpp, LINE: 93
FILE: decaf/io/OutputStream.cpp, LINE: 69
FILE: decaf/io/BufferedOutputStream.cpp, LINE: 110
FILE: decaf/io/FilterOutputStream.cpp, LINE: 139
FILE: activemq/transport/IOTransport.cpp, LINE: 132
FILE: activemq/transport/inactivity/InactivityMonitor.cpp, LINE: 381
FILE: activemq/transport/inactivity/InactivityMonitor.cpp, LINE: 388
FILE: activemq/wireformat/openwire/OpenWireFormatNegotiator.cpp, LINE: 233
FILE: activemq/transport/correlator/ResponseCorrelator.cpp, LINE: 245
FILE: activemq/core/ActiveMQConnectionFactory.cpp, LINE: 325
Memory fault(coredump)
this causes it to crash and coredump
2)It waits a few seconds and then says:
OpenWireFormatNegotiator::onewayWire format negotiation timeout: peer did not send his wire format.
FILE: activemq/wireformat/openwire/OpenWireFormatNegotiator.cpp, LINE: 73
FILE: activemq/wireformat/openwire/OpenWireFormatNegotiator.cpp, LINE: 82
FILE: activemq/transport/correlator/ResponseCorrelator.cpp, LINE: 132
FILE: activemq/core/ActiveMQConnection.cpp, LINE: 916
FILE: activemq/core/ActiveMQConnection.cpp, LINE: 968
FILE: activemq/core/ActiveMQConnection.cpp, LINE: 544
Server Certificate Name doesn't match the URI Host Name value.
FILE: decaf/internal/net/ssl/openssl/OpenSSLSocket.cpp, LINE: 708
FILE: decaf/internal/net/ssl/openssl/OpenSSLSocket.cpp, LINE: 421
FILE: decaf/internal/net/ssl/openssl/OpenSSLSocket.cpp, LINE: 524
FILE: decaf/internal/net/ssl/openssl/OpenSSLSocketInputStream.cpp, LINE: 106
FILE: decaf/io/InputStream.cpp, LINE: 140
FILE: decaf/io/InputStream.cpp, LINE: 74
FILE: decaf/io/BufferedInputStream.cpp, LINE: 370
FILE: decaf/io/BufferedInputStream.cpp, LINE: 258
FILE: decaf/io/InputStream.cpp, LINE: 86
FILE: decaf/io/DataInputStream.cpp, LINE: 502
FILE: decaf/io/DataInputStream.cpp, LINE: 130
FILE: activemq/wireformat/openwire/OpenWireFormat.cpp, LINE: 265
FILE: activemq/transport/IOTransport.cpp, LINE: 258
FILE: activemq/core/ActiveMQConnection.cpp, LINE: 299
This doesnt cause a crash, but it still fails.
I am able to use ssl easily and properly in a java client. And my CPP client works well with regular tcp,
I have my keystore set up with decaf::lang::System::setProperty to a pem file containing my public and private keys and the password,
And then truststore set up to the self signed cert in ASCII .pem format of my broker and the password.
I may be doing something wrong with my certificates, but I've been working on this for a few days and cant get it working at all.
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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] [Updated] (AMQCPP-422) 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.
Posted by "Mikhail Melamud (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Melamud updated AMQCPP-422:
-----------------------------------
Attachment: brokerkeystore.pem
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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] [Updated] (AMQCPP-422) 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.
Posted by "Mikhail Melamud (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Melamud updated AMQCPP-422:
-----------------------------------
Affects Version/s: 3.4.4
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2, 3.4.4
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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-422) 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.
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444532#comment-13444532 ]
Timothy Bish commented on AMQCPP-422:
-------------------------------------
CMS has no internal tracing, you are free to instrument the code using whichever tracing tool your particular organization uses.
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2, 3.4.4
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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 do 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-422) 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.
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433543#comment-13433543 ]
Timothy Bish commented on AMQCPP-422:
-------------------------------------
This appears to be a dup of AMQCPP-421
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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-422) 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.
Posted by "Mikhail Melamud (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435438#comment-13435438 ]
Mikhail Melamud commented on AMQCPP-422:
----------------------------------------
Confirmed. The same exactly crash with v3.4.4.
{code}
R6025
- pure virtual function call
CMS Exception occurred 276.
Server Certificate Name doesn't match the URI Host Name value.
FILE: ..\src\main\decaf\internal\net\ssl\openssl\OpenSSLSocket.cpp, LINE: 708
FILE: ..\src\main\decaf\internal\net\ssl\ope
{code}
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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-422) 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.
Posted by "Mikhail Melamud (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444481#comment-13444481 ]
Mikhail Melamud commented on AMQCPP-422:
----------------------------------------
What would be a recommended way to enable tracing in CMS?
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2, 3.4.4
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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 do 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (AMQCPP-422) 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.
Posted by "Mikhail Melamud (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435438#comment-13435438 ]
Mikhail Melamud edited comment on AMQCPP-422 at 8/16/12 6:27 AM:
-----------------------------------------------------------------
Confirmed. The same exactly crash with v3.4.4. Out of 15 sequential runs it crashed 3 times... :-)
{code}
R6025
- pure virtual function call
CMS Exception occurred 276.
Server Certificate Name doesn't match the URI Host Name value.
FILE: ..\src\main\decaf\internal\net\ssl\openssl\OpenSSLSocket.cpp, LINE: 708
FILE: ..\src\main\decaf\internal\net\ssl\ope
{code}
was (Author: mikmela):
Confirmed. The same exactly crash with v3.4.4.
{code}
R6025
- pure virtual function call
CMS Exception occurred 276.
Server Certificate Name doesn't match the URI Host Name value.
FILE: ..\src\main\decaf\internal\net\ssl\openssl\OpenSSLSocket.cpp, LINE: 708
FILE: ..\src\main\decaf\internal\net\ssl\ope
{code}
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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-422) 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.
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437076#comment-13437076 ]
Timothy Bish commented on AMQCPP-422:
-------------------------------------
I updated the SSL transport page to include the info about matching the host name to the certificates common name.
You should attempt to get a back-trace of all threads when the segfault happens so it can be analyzed here.
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2, 3.4.4
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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 do 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] [Updated] (AMQCPP-422) 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.
Posted by "Mikhail Melamud (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Melamud updated AMQCPP-422:
-----------------------------------
Description: 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 do 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 (was: 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)
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-422
> URL: https://issues.apache.org/jira/browse/AMQCPP-422
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl, Decaf
> Affects Versions: 3.4.0, 3.4.2, 3.4.4
> Environment: Broker: 5.6.0,
> CMS 3.4.2
> Windows
> Reporter: Mikhail Melamud
> Assignee: Timothy Bish
> Attachments: AMQTest.cpp, brokerkeystore.pem
>
>
> 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 do 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