Thanks for the reply...its urgent that we have a workaround/fix for it as
need to release the application by early next week.
Thanks
Abhi
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
it might be detected with "thread sanitizer", I guess.
I'll have a look later
2018-02-22 9:11 GMT+05:00 duttaab :
> Hi,
>
> I am getting the following core/crash dump while using the AcitveMQ-CPP
> (C++) library. What I observe is if I disable the Inactivity Monitor this
> crash occurs, even if m
Thanks Tim, I observed that if we restart the broker, the client was not
getting reconnected to broker once its up again...however when I call the
initialize API only once, there is no such issue. May be this in one of
those that you referred.
Thanks
Abhi
--
Sent from: http://activemq.2283324.n
On 02/20/2018 10:35 AM, duttaab wrote:
What kind of issues do you suspect if its getting called multiple times from
different threads - or we can face undefined behavior.
Thanks
Abhi
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Black holes, unexpected time
What kind of issues do you suspect if its getting called multiple times from
different threads - or we can face undefined behavior.
Thanks
Abhi
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
On 02/20/2018 05:53 AM, duttaab wrote:
Hi,
In a process which is multi-threaded, is it ok to initialize ActiveMQ-CPP
multiple times (by multiple threads) by calling API -->
"activemq::library::ActiveMQCPP::initializeLibrary()". Or should it be
called only once in the process.
Thanks
Abhi
--