[jira] Commented: (AMQCPP-60) message information is lost from stomp message to jms

[ https://issues.apache.org/activemq/browse/AMQCPP-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38443 ] Nathan Mittler commented on AMQCPP-60: -- I think I found it ... as you had indicated, we were sending

[jira] Commented: (AMQCPP-62) Broken CLIENT_ACKNOWLEDGE

[ https://issues.apache.org/activemq/browse/AMQCPP-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38444 ] Nathan Mittler commented on AMQCPP-62: -- I've made a fix to the validation of received ack messages. Give

[jira] Updated: (AMQCPP-64) Inconsistency in topic names when creating topics

[ https://issues.apache.org/activemq/browse/AMQCPP-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler updated AMQCPP-64: - Description: Hi I am using the activemq-cpp cms api 1.0 release. The problem I am facing

[jira] Resolved: (AMQCPP-64) Inconsistency in topic names when creating topics

[ https://issues.apache.org/activemq/browse/AMQCPP-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler resolved AMQCPP-64. -- Resolution: Won't Fix Looking closer at you sample code, it looks like the problem is how

[jira] Closed: (AMQCPP-61) CMSException::what returns c_str of temporary std::string

[ https://issues.apache.org/activemq/browse/AMQCPP-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-61. Resolution: Fixed fixed in trunk CMSException::what returns c_str of temporary std::string

[jira] Commented: (AMQCPP-60) message information is lost from stomp message to jms

[ https://issues.apache.org/activemq/browse/AMQCPP-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38039 ] Nathan Mittler commented on AMQCPP-60: -- Many bugs have been fixed since 1.0 - I would recommend trying

[jira] Closed: (AMQCPP-59) Exception is thrown when destroying consumer after connection failure

[ https://issues.apache.org/activemq/browse/AMQCPP-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-59. Resolution: Fixed Since it sounds like it's working now, I'm closing this issue. Exception

[jira] Commented: (AMQCPP-58) Possible memory leak when reestablishing connection

[ https://issues.apache.org/activemq/browse/AMQCPP-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38022 ] Nathan Mittler commented on AMQCPP-58: -- I've done a bit of clean up to catch various error conditions and clean

[jira] Commented: (AMQCPP-59) Exception is thrown when destroying consumer after connection failure

[ https://issues.apache.org/activemq/browse/AMQCPP-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38024 ] Nathan Mittler commented on AMQCPP-59: -- Albert, I think the issue was your main module. It wasn't destroying

Re: wiki access

so, I'll try to get this fix for you ASAP in the mean time. On 1/27/07, Nathan Mittler [EMAIL PROTECTED] wrote: Hey guys, I've apparently lost my privileges to change our wiki. Was just trying to update the AMQCPP 1.1 release page ( http://www.activemq.org/site/activemq-cpp-11-release.html

[jira] Commented: (AMQCPP-56) GCC warnings and possible SocketFactory bug on 64-bit Linux

[ https://issues.apache.org/activemq/browse/AMQCPP-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38021 ] Nathan Mittler commented on AMQCPP-56: -- Albert, I think you were trying out trunk while I was in the middle

Re: Doxample: Can we ship it with our code?

Hey Hiram, Is the resolution on this that we can just add a new header to his file in our distro? On 1/19/07, Hiram Chirino [EMAIL PROTECTED] wrote: Thanks Oren! On Jan 18, 2007, at 6:49 PM, Oren Ben-Kiki wrote: On Thu, 2007-01-18 at 18:09 -0500, Hiram Chirino wrote: ... Yeah the

wiki access

Hey guys, I've apparently lost my privileges to change our wiki. Was just trying to update the AMQCPP 1.1 release page ( http://www.activemq.org/site/activemq-cpp-11-release.html) and was denied. Thanks, Nate

[jira] Commented: (AMQCPP-46) ActiveMQConnection doesn't propagate exception listener to underlying connector

[ https://issues.apache.org/activemq/browse/AMQCPP-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38006 ] Nathan Mittler commented on AMQCPP-46: -- The destructor of the consumer should not throw an exception

[jira] Closed: (AMQCPP-46) ActiveMQConnection doesn't propagate exception listener to underlying connector

[ https://issues.apache.org/activemq/browse/AMQCPP-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-46. Resolution: Fixed This has been fixed in trunk ActiveMQConnection doesn't propagate exception

[jira] Commented: (AMQCPP-57) Typo in names of delivery modes

[ https://issues.apache.org/activemq/browse/AMQCPP-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38009 ] Nathan Mittler commented on AMQCPP-57: -- Oops - good find :) While changing it to -TENT would cause

[jira] Closed: (AMQCPP-56) GCC warnings and possible SocketFactory bug on 64-bit Linux

[ https://issues.apache.org/activemq/browse/AMQCPP-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-56. Resolution: Fixed fixed in trunk. Tested in msvc with warning level at 3 GCC warnings

[jira] Closed: (AMQCPP-57) Typo in names of delivery modes

[ https://issues.apache.org/activemq/browse/AMQCPP-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-57. Resolution: Fixed fixed in trunk Typo in names of delivery modes

[jira] Reopened: (AMQCPP-56) GCC warnings and possible SocketFactory bug on 64-bit Linux

[ https://issues.apache.org/activemq/browse/AMQCPP-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler reopened AMQCPP-56: -- still a few issues on os x GCC warnings and possible SocketFactory bug on 64-bit Linux

[jira] Closed: (AMQCPP-56) GCC warnings and possible SocketFactory bug on 64-bit Linux

[ https://issues.apache.org/activemq/browse/AMQCPP-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-56. Resolution: Fixed gcc problems fixed in trunk. GCC warnings and possible SocketFactory bug

[jira] Commented: (AMQCPP-46) ActiveMQConnection doesn't propagate exception listener to underlying connector

[ https://issues.apache.org/activemq/browse/AMQCPP-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37998 ] Nathan Mittler commented on AMQCPP-46: -- hm ... I'm not getting that same stack trace in msvc, but I did find

[jira] Closed: (AMQCPP-55) Need close() to propagate to child resources

[ https://issues.apache.org/activemq/browse/AMQCPP-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-55. Resolution: Duplicate This is being fixed along with issue AMQCPP-46 Need close

[jira] Closed: (AMQCPP-53) Declaration of extern int errno after including errno.h doesn't compile

[ https://issues.apache.org/activemq/browse/AMQCPP-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-53. Resolution: Fixed fixed in trunk Declaration of extern int errno after including errno.h

[jira] Commented: (AMQCPP-49) Add -W -Wall compile options

[ https://issues.apache.org/activemq/browse/AMQCPP-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37977 ] Nathan Mittler commented on AMQCPP-49: -- patches are always welcome :) Add -W -Wall compile options

[jira] Commented: (AMQCPP-46) ActiveMQConnection doesn't propagate exception listener to underlying connector

[ https://issues.apache.org/activemq/browse/AMQCPP-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37982 ] Nathan Mittler commented on AMQCPP-46: -- at first glance it looks like the problem is in your main

[jira] Commented: (AMQCPP-46) ActiveMQConnection doesn't propagate exception listener to underlying connector

[ https://issues.apache.org/activemq/browse/AMQCPP-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37983 ] Nathan Mittler commented on AMQCPP-46: -- I've cleaned up a couple of items that you might want to grab from

[jira] Commented: (AMQCPP-46) ActiveMQConnection doesn't propagate exception listener to underlying connector

[ https://issues.apache.org/activemq/browse/AMQCPP-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37986 ] Nathan Mittler commented on AMQCPP-46: -- Albert - you are correct. Looking at the JMS 1.1 spec, it specifically

[jira] Commented: (AMQCPP-46) ActiveMQConnection doesn't propagate exception listener to underlying connector

[ https://issues.apache.org/activemq/browse/AMQCPP-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37989 ] Nathan Mittler commented on AMQCPP-46: -- Albert, I've made some updates to trunk to do the automatic closing

[jira] Updated: (AMQCPP-54) Build broken due to autoconf problem?

[ https://issues.apache.org/activemq/browse/AMQCPP-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler updated AMQCPP-54: - Priority: Trivial (was: Major) Fix Version/s: 2.0 Build broken due to autoconf

[jira] Commented: (AMQCPP-54) Build broken due to autoconf problem?

[ https://issues.apache.org/activemq/browse/AMQCPP-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37993 ] Nathan Mittler commented on AMQCPP-54: -- The build is not broken ... it's just a warning from autogen.sh. You

[jira] Commented: (AMQCPP-46) ActiveMQConnection doesn't propagate exception listener to underlying connector

[ https://issues.apache.org/activemq/browse/AMQCPP-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37994 ] Nathan Mittler commented on AMQCPP-46: -- sure thing - grab trunk! ActiveMQConnection doesn't propagate

[jira] Closed: (AMQCPP-54) Build broken due to autoconf problem?

[ https://issues.apache.org/activemq/browse/AMQCPP-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-54. Resolution: Fixed Since the build works, I'm considering it fixed. Build broken due

[jira] Closed: (AMQCPP-46) ActiveMQConnection doesn't propagate exception listener to underlying connector

[ https://issues.apache.org/activemq/browse/AMQCPP-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-46. Resolution: Fixed The example seems to be working fine now on OS X. ActiveMQConnection

[jira] Created: (AMQCPP-55) Need close() to propagate to child resources

Affects Versions: 1.1 Environment: All Reporter: Nathan Mittler Assigned To: Nathan Mittler Priority: Minor Fix For: 2.0 Currently, the user is required to close CMS resources in the following order: consumer/producer session connection We

[jira] Work started: (AMQCPP-55) Need close() to propagate to child resources

[ https://issues.apache.org/activemq/browse/AMQCPP-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQCPP-55 started by Nathan Mittler. Need close() to propagate to child resources Key: AMQCPP

[jira] Updated: (AMQCPP-51) Autoconf is not properly setting CXXFLAGS on Linux

[ https://issues.apache.org/activemq/browse/AMQCPP-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler updated AMQCPP-51: - Fix Version/s: 2.0 Autoconf is not properly setting CXXFLAGS on Linux

[jira] Closed: (AMQCPP-51) Autoconf is not properly setting CXXFLAGS on Linux

[ https://issues.apache.org/activemq/browse/AMQCPP-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-51. Resolution: Duplicate This is a duplicate of AMQCPP-49. I have re-opened that issue to address

[jira] Assigned: (AMQCPP-30) Add support to activemq-cpp to support the openwire protocol

[ https://issues.apache.org/activemq/browse/AMQCPP-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler reassigned AMQCPP-30: Assignee: Timothy Bish (was: Nathan Mittler) Add support to activemq-cpp to support

[jira] Closed: (AMQCPP-49) Add -W -Wall compile options

[ https://issues.apache.org/activemq/browse/AMQCPP-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-49. Resolution: Fixed The compiler options are working correctly now. Due to some problems

[jira] Closed: (AMQCPP-38) Async error on broker when running integration tests

[ https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-38. Resolution: Fixed I believe this to be a broker side issue captured in AMQ-1077 Async error

[jira] Reopened: (AMQCPP-49) Add -W -Wall compile options

[ https://issues.apache.org/activemq/browse/AMQCPP-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler reopened AMQCPP-49: -- Accidentally disabled -W -Wall Add -W -Wall compile options

[jira] Closed: (AMQCPP-40) A few stray unix and sun defines

[ https://issues.apache.org/activemq/browse/AMQCPP-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-40. Resolution: Fixed fixed in trunk A few stray unix and sun defines

[jira] Closed: (AMQCPP-50) Derive cms::CMSException from std::exception

[ https://issues.apache.org/activemq/browse/AMQCPP-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-50. Resolution: Fixed Applied to trunk Derive cms::CMSException from std::exception

[jira] Commented: (AMQCPP-44) Reason for socket errors not reported correctly on Windows

[ https://issues.apache.org/activemq/browse/AMQCPP-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37963 ] Nathan Mittler commented on AMQCPP-44: -- I've updated trunk to log all socket errors as is appropriate

[jira] Closed: (AMQCPP-49) Add -W -Wall compile options

[ https://issues.apache.org/activemq/browse/AMQCPP-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-49. Resolution: Fixed Finally got cygwin happy. Removed use of -ansi -pedantic on cygwin, as well

[jira] Closed: (AMQCPP-48) Fix compilation with Visual Studio .NET 2003

[ https://issues.apache.org/activemq/browse/AMQCPP-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-48. Resolution: Fixed Patch applied to trunk Fix compilation with Visual Studio .NET 2003

[jira] Closed: (AMQCPP-47) MapMessage getters should be const

[ https://issues.apache.org/activemq/browse/AMQCPP-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-47. Resolution: Fixed Patch applied to trunk MapMessage getters should be const

[jira] Commented: (AMQCPP-49) Add -W -Wall compile options

[ https://issues.apache.org/activemq/browse/AMQCPP-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37940 ] Nathan Mittler commented on AMQCPP-49: -- Unfortunately, without it - many warnings that are important don't show

[jira] Commented: (AMQCPP-49) Add -W -Wall compile options

[ https://issues.apache.org/activemq/browse/AMQCPP-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37942 ] Nathan Mittler commented on AMQCPP-49: -- I'd rather not have to get that specific. Looking at the output from

[jira] Commented: (AMQCPP-49) Add -W -Wall compile options

[ https://issues.apache.org/activemq/browse/AMQCPP-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37943 ] Nathan Mittler commented on AMQCPP-49: -- Also, I'd prefer to go with the approach of exposing all the warnings

[jira] Closed: (AMQCPP-49) Add -W -Wall compile options

[ https://issues.apache.org/activemq/browse/AMQCPP-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-49. Resolution: Fixed Made changes throughout the source to support -W -Wall Add -W -Wall

[jira] Commented: (AMQCPP-49) Add -W -Wall compile options

[ https://issues.apache.org/activemq/browse/AMQCPP-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37946 ] Nathan Mittler commented on AMQCPP-49: -- You need to grab the latest makefile.am for main. Please provide

[jira] Created: (AMQCPP-49) Add -W -Wall compile options

Mittler Assigned To: Nathan Mittler Priority: Trivial Fix For: 2.0 Add -W -Wall compile options and clean up resulting warnings -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https

Re: activemq-cpp compilation warnings

At this point, the vote for 1.1 has already gone to the incubator PMC, so unfortunately it's to late to get it into 1.1. Why don't you capture that in an issue targeted for 2.0 http://issues.apache.org/activemq/browse/AMQCPP ... if there are enough issues, we may cut an patched 1.1.1 release

Re: [VOTE] Release ActiveMQ-CPP 1.1

. And ask folks to install it manually as part of the build procedure... or we could just remove all the doxygen bits out of the autoconf stuff so that it's not a dependency. On 1/16/07, Nathan Mittler [EMAIL PROTECTED] wrote: It appears that the Autoconf macros are under the GPL (as expected) http

Re: [VOTE] Release ActiveMQ-CPP 1.1

Miller [EMAIL PROTECTED] wrote: On Jan 17, 2007, at 9:36 AM, Mittler, Nathan wrote: Hi Kevan, With the current changes, can I call you a +1? Thanks, Nate -Original Message- From: Nathan Mittler [mailto: [EMAIL PROTECTED] Sent: Wednesday, January 17, 2007 6:42 AM To: activemq

[jira] Commented: (AMQCPP-46) ActiveMQConnection doesn't propagate exception listener to underlying connector

[ https://issues.apache.org/activemq/browse/AMQCPP-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37932 ] Nathan Mittler commented on AMQCPP-46: -- Committed a fix for the exception listener to trunk and added unit

Re: [VOTE] Release ActiveMQ-CPP 1.1

It appears that the Autoconf macros are under the GPL (as expected) http://sourceforge.net/projects/ac-archive/. What is the typical way we deal with this at the ASF? On 1/16/07, Nathan Mittler [EMAIL PROTECTED] wrote: Great - thanks! On 1/15/07, Hiram Chirino [EMAIL PROTECTED] wrote: Hi

Re: [VOTE] Release ActiveMQ-CPP 1.1

, 2007, at 11:07 AM, Nathan Mittler wrote: Hi everyone, Several bug fixes as well as a few new features have been incorporated into ActiveMQ-CPP - worthy of a 1.1 release, before we go for full openwire support in 2.0. The source bundle for the release candidate can be found here: http

[VOTE] Release ActiveMQ-CPP 1.1

Hi everyone, Several bug fixes as well as a few new features have been incorporated into ActiveMQ-CPP - worthy of a 1.1 release, before we go for full openwire support in 2.0. The source bundle for the release candidate can be found here:

[jira] Commented: (AMQCPP-25) Bus error on Solaris OS from DataInput and DataOutput streams

[ https://issues.apache.org/activemq/browse/AMQCPP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37883 ] Nathan Mittler commented on AMQCPP-25: -- Hi Albert, Great work! Looks like you might be onto something here

[jira] Commented: (AMQCPP-25) Bus error on Solaris OS from DataInput and DataOutput streams

[ https://issues.apache.org/activemq/browse/AMQCPP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37884 ] Nathan Mittler commented on AMQCPP-25: -- As indicated in the links Albert provided, we should add the following

[jira] Updated: (AMQCPP-38) Async error on broker when running integration tests

[ https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler updated AMQCPP-38: - Fix Version/s: (was: 1.1) 2.0 Moving to release 2.0 - the current

[jira] Updated: (AMQCPP-42) A few more strict aliasing warnings

[ https://issues.apache.org/activemq/browse/AMQCPP-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler updated AMQCPP-42: - Fix Version/s: (was: 2.0) 1.1 A few more strict aliasing warnings

[jira] Closed: (AMQCPP-42) A few more strict aliasing warnings

[ https://issues.apache.org/activemq/browse/AMQCPP-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-42. Resolution: Fixed Assignee: Nathan Mittler (was: Timothy Bish) Patches have been applied

[jira] Closed: (AMQCPP-32) Stomp messages don't preserve property types: please document this behaviour

[ https://issues.apache.org/activemq/browse/AMQCPP-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-32. Resolution: Fixed I have documented the behavior here http://www.activemq.org/site/activemq

[jira] Commented: (AMQCPP-32) Stomp messages don't preserve property types: please document this behaviour

[ https://issues.apache.org/activemq/browse/AMQCPP-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37832 ] Nathan Mittler commented on AMQCPP-32: -- I agree with Tim - this really should be commented on the wiki page

[jira] Updated: (AMQCPP-38) Async error on broker when running integration tests

[ https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler updated AMQCPP-38: - Fix Version/s: 1.1 Async error on broker when running integration tests

[jira] Updated: (AMQCPP-32) Stomp messages don't preserve property types: please document this behaviour

[ https://issues.apache.org/activemq/browse/AMQCPP-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler updated AMQCPP-32: - Fix Version/s: 1.1 Stomp messages don't preserve property types: please document

[jira] Closed: (AMQCPP-27) Issues reported by Valgrind when running unit tests

[ https://issues.apache.org/activemq/browse/AMQCPP-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-27. Resolution: Fixed If the leaks shown by valgrind end up being real leaks or if more leaks pop

[jira] Commented: (AMQCPP-38) Async error on broker when running integration tests

[ https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37827 ] Nathan Mittler commented on AMQCPP-38: -- Running the integration tests several times in a row against the latest

[jira] Commented: (AMQCPP-27) Issues reported by Valgrind when running unit tests

[ https://issues.apache.org/activemq/browse/AMQCPP-27?page=comments#action_37753 ] Nathan Mittler commented on AMQCPP-27: -- I haven't heard back - was this resolved by my latest changes? Issues reported by Valgrind when running unit

[jira] Updated: (AMQCPP-31) Consider giving the unix #define a more unique name

[ https://issues.apache.org/activemq/browse/AMQCPP-31?page=all ] Nathan Mittler updated AMQCPP-31: - Fix Version/s: 1.1 Consider giving the unix #define a more unique name --- Key

Re: Undocumented stomp header?

Ok, that clears it up. Thnx! On 12/19/06, Brian McCallister [EMAIL PROTECTED] wrote: On Dec 17, 2006, at 9:58 AM, Nathan Mittler wrote: Hey guys, I was just looking at the stomp transport and noticed what appears to be an undocumented extension to stomp adding a header for subscription

[jira] Commented: (AMQCPP-27) Issues reported by Valgrind when running unit tests

[ https://issues.apache.org/activemq/browse/AMQCPP-27?page=comments#action_37706 ] Nathan Mittler commented on AMQCPP-27: -- Ok, I think I got it. Grab the latest activemq/concurrent/Thread.cpp and give that a try. Issues reported

[jira] Commented: (AMQCPP-28) Purify and Valgrind warnings when running integration tests

[ https://issues.apache.org/activemq/browse/AMQCPP-28?page=comments#action_37708 ] Nathan Mittler commented on AMQCPP-28: -- ... also, what version of the broker are you running against? Purify and Valgrind warnings when running

[jira] Resolved: (AMQ-517) Create a C++ client for ActiveMQ that can work with STOMP and OpenWire

[ https://issues.apache.org/activemq/browse/AMQ-517?page=all ] Nathan Mittler resolved AMQ-517. Resolution: Fixed Since activemq-cpp can support both stomp and openwire, I think it's safe to say this issue has been resolved. I will open another issue

[jira] Created: (AMQCPP-30) Add support to activemq-cpp to support the openwire protocol

Feature Components: Openwire Environment: All Reporter: Nathan Mittler Assigned To: Nathan Mittler Priority: Critical Fix For: 2.0 Need to complete the first cut at the implementation of the openwire transport -- This message

[jira] Commented: (AMQCPP-28) Purify and Valgrind warnings when running integration tests

[ https://issues.apache.org/activemq/browse/AMQCPP-28?page=comments#action_37715 ] Nathan Mittler commented on AMQCPP-28: -- We've just recently discovered this same problem. It seems that the integration tests work fine against 4.0.2

[jira] Assigned: (AMQCPP-29) Projects in MSVC build building on top of one another

[ https://issues.apache.org/activemq/browse/AMQCPP-29?page=all ] Nathan Mittler reassigned AMQCPP-29: Assignee: Timothy Bish (was: Nathan Mittler) Projects in MSVC build building on top of one another

[jira] Closed: (AMQCPP-16) CMS API needs updates to more closely follow JMS API

[ https://issues.apache.org/activemq/browse/AMQCPP-16?page=all ] Nathan Mittler closed AMQCPP-16. Resolution: Fixed Assignee: Nathan Mittler (was: Timothy Bish) At this point, we have implemented 3 of the 4 changes. We're going to push out

[jira] Commented: (AMQCPP-29) Projects in MSVC build building on top of one another

[ https://issues.apache.org/activemq/browse/AMQCPP-29?page=comments#action_37710 ] Nathan Mittler commented on AMQCPP-29: -- It sounds like you know what needs to be done - would you fancy providing us with a patch? Projects in MSVC build

[jira] Updated: (AMQCPP-27) Issues reported by Valgrind when running unit tests

[ https://issues.apache.org/activemq/browse/AMQCPP-27?page=all ] Nathan Mittler updated AMQCPP-27: - Fix Version/s: 1.1 Issues reported by Valgrind when running unit tests --- Key

[jira] Updated: (AMQCPP-28) Purify and Valgrind warnings when running integration tests

[ https://issues.apache.org/activemq/browse/AMQCPP-28?page=all ] Nathan Mittler updated AMQCPP-28: - Fix Version/s: 1.1 Purify and Valgrind warnings when running integration tests

[jira] Updated: (AMQCPP-29) Projects in MSVC build building on top of one another

[ https://issues.apache.org/activemq/browse/AMQCPP-29?page=all ] Nathan Mittler updated AMQCPP-29: - Fix Version/s: 1.1 Projects in MSVC build building on top of one another - Key

Undocumented stomp header?

Hey guys, I was just looking at the stomp transport and noticed what appears to be an undocumented extension to stomp adding a header for subscription ID (literally the string id on the wire) to the subscribe and unsubscribe frames. I have just a few questions: 1) Is this equivalent to a

[jira] Commented: (AMQCPP-28) Purify and Valgrind warnings when running integration tests

[ https://issues.apache.org/activemq/browse/AMQCPP-28?page=comments#action_37718 ] Nathan Mittler commented on AMQCPP-28: -- For now, let's stick this under AMQCPP until we are sure that it's not a bug on the client side. If we determine

[jira] Commented: (AMQCPP-27) Issues reported by Valgrind when running unit tests

[ https://issues.apache.org/activemq/browse/AMQCPP-27?page=comments#action_37702 ] Nathan Mittler commented on AMQCPP-27: -- I've added a couple of tweaks to trunk. If this doesn't work I think Valgrind is giving us a phantom memory leak

[jira] Commented: (AMQCPP-27) Issues reported by Valgrind when running unit tests

[ https://issues.apache.org/activemq/browse/AMQCPP-27?page=comments#action_37694 ] Nathan Mittler commented on AMQCPP-27: -- Patch applied to trunk - Thanks! I will look at the Valgrind output a bit later. Issues reported by Valgrind when

[jira] Commented: (AMQCPP-26) Memory leaks reported by Rational Purify when running unit tests

[ https://issues.apache.org/activemq/browse/AMQCPP-26?page=comments#action_37695 ] Nathan Mittler commented on AMQCPP-26: -- I've made some changes in trunk that I'd like you to try when you get a chance. Thanks for the help! Memory

[jira] Commented: (AMQCPP-27) Issues reported by Valgrind when running unit tests

[ https://issues.apache.org/activemq/browse/AMQCPP-27?page=comments#action_37697 ] Nathan Mittler commented on AMQCPP-27: -- I think I may have located the last leak listed in the file ... but it will only occur on win32 - I'm assuming

[jira] Commented: (AMQCPP-27) Issues reported by Valgrind when running unit tests

[ https://issues.apache.org/activemq/browse/AMQCPP-27?page=comments#action_37698 ] Nathan Mittler commented on AMQCPP-27: -- I've fixed a couple other leaks that I've found related to the leak in activemq::connector::stomp

[jira] Commented: (AMQCPP-28) Purify and Valgrind warnings when running integration tests

[ https://issues.apache.org/activemq/browse/AMQCPP-28?page=comments#action_37700 ] Nathan Mittler commented on AMQCPP-28: -- please reuse the issues when they're all related to the same problem (e.g. memory leaks). At this point, let's

[jira] Commented: (AMQCPP-28) Purify and Valgrind warnings when running integration tests

[ https://issues.apache.org/activemq/browse/AMQCPP-28?page=comments#action_37701 ] Nathan Mittler commented on AMQCPP-28: -- Updates have been applied to trunk. Purify and Valgrind warnings when running integration tests

[jira] Commented: (AMQCPP-16) CMS API needs updates to more closely follow JMS API

[ https://issues.apache.org/activemq/browse/AMQCPP-16?page=comments#action_37685 ] Nathan Mittler commented on AMQCPP-16: -- 1) has been implemented in trunk. This required changes to DataInput/OutputStreams and ByteArrayInput

[jira] Created: (AMQCPP-20) Deadlock when in stomp connector close

Reporter: Nathan Mittler Assigned To: Nathan Mittler Fix For: 1.1 When a broken socket occurs, the stomp connector attempts to asynchronously close itself. This can cause a deadlock if the main thread is in the close method and is performing a join on the transport thread

[jira] Closed: (AMQCPP-20) Deadlock when in stomp connector close

[ https://issues.apache.org/activemq/browse/AMQCPP-20?page=all ] Nathan Mittler closed AMQCPP-20. Resolution: Fixed Fixed in trunk Removed the call to close from the asynchronous thread. The user will eventually close it anyway ... that's the more

[jira] Reopened: (AMQCPP-20) Deadlock when in stomp connector close

[ https://issues.apache.org/activemq/browse/AMQCPP-20?page=all ] Nathan Mittler reopened AMQCPP-20: -- Need to add better handling of close, so that we don't log an error or notify the client if the broken socket was due to the sending

[jira] Closed: (AMQCPP-20) Deadlock when in stomp connector close

[ https://issues.apache.org/activemq/browse/AMQCPP-20?page=all ] Nathan Mittler closed AMQCPP-20. Resolution: Fixed fixed in trunk Deadlock when in stomp connector close -- Key: AMQCPP-20

[jira] Created: (AMQCPP-18) ActiveMQConnection.close() causes app to crash

Environment: All platforms Reporter: Nathan Mittler Assigned To: Nathan Mittler Fix For: 1.1 We currently have a flawed exception handling model in StompCommandReader. It propagates different exceptions than the ones that are advertised, which causes

  1   2   3   >