activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeffrey B (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMQCPP-452) Shutdown causing core dump in 3.5.0
Date Mon, 04 Feb 2013 18:06:13 GMT
Jeffrey B created AMQCPP-452:
--------------------------------

             Summary: Shutdown causing core dump in 3.5.0
                 Key: AMQCPP-452
                 URL: https://issues.apache.org/jira/browse/AMQCPP-452
             Project: ActiveMQ C++ Client
          Issue Type: Bug
          Components: Decaf
    Affects Versions: 3.5.0
         Environment: HPUX 11.31
            Reporter: Jeffrey B
            Assignee: Timothy Bish
            Priority: Critical


Whenever a thread is created in my receiver program, The use of the activemq::library::ActiveMQCPP::shutdownLibrary();
causes a core dump after my return 0; statement

It does not happen on my sender after applying patch for a similar issue, and this is almost
identical, so I can not find the difference.

The cause is trying to lock a null mutex in the function Threading.cpp::attachToCurrentThread().
 This gets called only once in my sender program, during the activemq::library::ActiveMQCPP::initializeLibrary();
call, but it gets called twice in my receiver program, once in the same place and then after
the return 0; line.  At that point library->globalLock is NULL.

Will attach my source in a moment, but I have literally taken it down to the bare minimum
so that it has no function.

--
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

Mime
View raw message