Uploaded image for project: 'ActiveMQ C++ Client'
  1. ActiveMQ C++ Client
  2. AMQCPP-452

Shutdown causing core dump in 3.5.0

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Not A Problem
    • 3.5.0
    • None
    • Decaf
    • HPUX 11.31

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            tabish Timothy A. Bish
            doldrums Jeffrey B
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 24h
                24h
                Remaining:
                Remaining Estimate - 24h
                24h
                Logged:
                Time Spent - Not Specified
                Not Specified

                Slack

                  Issue deployment