On Fri, 2013-01-11 at 06:50 -0800, Alex1 wrote:
> Tried 3.5.0.
>
> It behaved the same.
>
>
> pure virtual method called
> terminate called after throwing an instance of
> 'decaf::internal::net::ssl::openssl::OpenSSLSocketException'
>
> But with 3.5.0, when I removed "failover" URI and added
>
Tried 3.5.0.
It behaved the same.
pure virtual method called
terminate called after throwing an instance of
'decaf::internal::net::ssl::openssl::OpenSSLSocketException'
But with 3.5.0, when I removed "failover" URI and added
"useInactivityMonitor"=false, the frequency of crash is much lower.
On Thu, 2013-01-10 at 12:37 -0800, Alex1 wrote:
> Look at the open issue db, and also the stack trace, it looks like very much
> the case AMQCPP-422.
>
> It traced back from IOTransport->fire
> Transportfilter::fire
> InactivivtyMonitor::OnException
> InactivivtyMonitor::stopMonitorThread
> synch
Look at the open issue db, and also the stack trace, it looks like very much
the case AMQCPP-422.
It traced back from IOTransport->fire
Transportfilter::fire
InactivivtyMonitor::OnException
InactivivtyMonitor::stopMonitorThread
synchronized()
decaf::util::concurrent::Lock
The pure virtual happens
On Wed, 2013-01-09 at 18:49 -0800, Alex1 wrote:
> activemq-cpp, version 3.4.0
> REdhat LInux
>
> Built activemq-cpp with openssl enabled.
>
> The server is configured with openssl enabled. The broker's certificate is
> set on client side
> with setSystemProperty(). Client test seems working fine