[
https://issues.apache.org/jira/browse/AMQCPP-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQCPP-449.
---------------------------------
Resolution: Fixed
Fix Version/s: 3.6.0
Resolved on trunk and the 3.5.x fixes branch.
> activemq::library::ActiveMQCPP::shutdownLibrary(); causing runtime exception
> ----------------------------------------------------------------------------
>
> Key: AMQCPP-449
> URL: https://issues.apache.org/jira/browse/AMQCPP-449
> 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
> Labels: HPUX, crash, destructor, exception, runtime, thread
> Fix For: 3.5.1, 3.6.0
>
> Attachments: amqdriver.cpp, amqdriver.cpp
>
>
> Whenever my simple driver application or my receiver application call the
> shutdownLibrary() method at the end, as the program is going through
> desctuctors for threads it prints and causes a core dump
> aCC runtime: Unexpected exception of type
> "decaf::lang::exceptions::RuntimeException".
> aCC runtime: what(): Failed to Lock OS Mutex
> Abort(coredump)
> I added another catch and print in decaf/lang/Thread.cpp about line 133 and
> on decaf/internal/util/concurrent/unix/PlatformThread.cpp about line 76 i
> printed out ther error number return from pthread_mutex_lock()
> Now i get:
> Failed to Lock OS Mutex, Error num: 22
> FILE: decaf/internal/util/concurrent/unix/PlatformThread.cpp, LINE: 78
> aCC runtime: Unexpected exception of type
> "decaf::lang::exceptions::RuntimeException".
> aCC runtime: what(): Failed to Lock OS Mutex, Error num: 22
> Abort(coredump)
> Error 22 is EINVAL and can have two meanings on my system:
> mutex is a PTHREAD_PRIO_PROTECT mutex and the caller's priority is
> higher than mutex's priority ceiling.
> mutex is not an initialized mutex.
> I'll try and upload my code to see if this happens on other systems as well.
--
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
