[ https://issues.apache.org/activemq/browse/AMQCPP-28?page=all ]
Albert Strasheim updated AMQCPP-28:
---
Attachment: ExpirationTest-leak.diff
I'm attaching a patch for the leak in ExpirationTest. With this patch the
integration tests run clean through Va
Async error on broker when running integration tests
Key: AMQCPP-38
URL: https://issues.apache.org/activemq/browse/AMQCPP-38
Project: ActiveMQ C++ Client
Issue Type: Bug
Affects Versio
[
https://issues.apache.org/activemq/browse/AMQCPP-27?page=comments#action_37772
]
Albert Strasheim commented on AMQCPP-27:
Still get the same "leak" with the latest trunk. I'm beginning to think that is
is probably leak in my glibc or
[ https://issues.apache.org/activemq/browse/AMQCPP-37?page=all ]
Attachment: readwriteutfv2.diff
> readUTF and writeUTF for BytesMessage
> -
>
> Key: AMQCPP-37
> URL: https://issues.apache.org/activemq/browse/AMQCPP-37
readUTF and writeUTF for BytesMessage
-
Key: AMQCPP-37
URL: https://issues.apache.org/activemq/browse/AMQCPP-37
Project: ActiveMQ C++ Client
Issue Type: New Feature
Components: CMS Impl
[
https://issues.apache.org/activemq/browse/AMQCPP-36?page=comments#action_37771
]
Albert Strasheim commented on AMQCPP-36:
Fair enough. I'll leave the headers alone and let you clean up the trailing
whitespace if it becomes a problem f
[
https://issues.apache.org/activemq/browse/AMQCPP-36?page=comments#action_37770
]
Timothy Bish commented on AMQCPP-36:
Yes, I do mind. I prefer to leave small functions in the headers of little
classes like this, if they get inlined by th
[ https://issues.apache.org/activemq/browse/AMQCPP-36?page=all ]
Albert Strasheim updated AMQCPP-36:
---
Attachment: StompFrame-signmismatch.diff
> Cleanup whitespace and member function definitions in header files
> --
[
https://issues.apache.org/activemq/browse/AMQCPP-36?page=comments#action_37769
]
Albert Strasheim commented on AMQCPP-36:
> I don't follow this rule.
Do you mind if the patches move member functions to .cpp files? As I see it,
header