Version 2.0


Start date not set

Released: 20/Apr/07

Release Notes

Warnings indicate when the status of a JIRA issue doesn't reflect related development activity. For example: an issue marked complete that has an open pull request should be marked as still being in progress.

Unreviewed Code

These issues have been marked complete but the commits are not part of a pull request or review.

CriticalNew FeatureAMQCPP-30Add support to activemq-cpp to support the openwire protocolTimothy BishResolved185 commits
CriticalBugAMQCPP-60message information is lost from stomp message to jmsNathan MittlerClosed1 commit
MajorBugAMQCPP-62Broken CLIENT_ACKNOWLEDGENathan MittlerResolved3 commits
MajorBugAMQCPP-75setCMSReplyTo with null destination segfaults when using Openwire wire formatTimothy BishResolved1 commit
MajorBugAMQCPP-78session tries to destroy already destroyed temporary queueTimothy BishClosed3 commits
MajorBugAMQCPP-80sending with explicit message id hangsNathan MittlerClosed1 commit
MajorBugAMQCPP-92memory leak in openwire session infoNathan MittlerClosed2 commits
MajorBugAMQCPP-98ack handler not set for messagesTimothy BishResolved2 commits
MinorBugAMQCPP-76Integer property not propagated when using OpenwireTimothy BishResolved2 commits
MinorBugAMQCPP-86Valgrind reports memory leaks in unit testsTimothy BishResolved1 commit
MinorBugAMQCPP-87ActiveMQConnectionFactory creates only one unique clientIdTimothy BishClosed2 commits
MinorBugAMQCPP-91A few more Openwire memory leaksTimothy BishResolved2 commits
MinorImprovementAMQCPP-94StompConnector should use Long::toString instead of Integer::toStringNathan MittlerResolved1 commit
MinorBugAMQCPP-96Setting property "JMSXGroupID" on a stomp message yields IllegalArgumentExceptionTimothy BishResolved2 commits
MinorBugAMQCPP-97ThreadPoolTest fails when run under Valgrind 2.4.0 on Fedora Core 4Timothy BishResolved3 commits
TrivialTaskAMQCPP-82Make openwire the default protocolNathan MittlerResolved1 commit
116 of 16