[ https://issues.apache.org/activemq/browse/AMQ-620?page=all ]
Nathan Mittler closed AMQ-620:
--
Resolution: Duplicate
This issue is being addressed by AMQ 656
> Get openwire-cpp buiding on linux/gcc
> -
>
>
CMS C++ Client - bug handling bytes messages
Key: AMQ-685
URL: https://issues.apache.org/activemq/browse/AMQ-685
Project: ActiveMQ
Type: Bug
Components: JMS client
Versions: 4.0 RC 2
Environment: any
Repo
CMS Client - unassigned value in ActiveMQConnectionFactory constructor
--
Key: AMQ-686
URL: https://issues.apache.org/activemq/browse/AMQ-686
Project: ActiveMQ
Type: Bug
Components: JMS client
[ https://issues.apache.org/activemq/browse/AMQ-686?page=all ]
Nathan Mittler closed AMQ-686:
--
Resolution: Fixed
Host and port were not being parsed properly in the transport - this is fixed
now.
> CMS Client - unassigned value in ActiveMQConnectionF
[ https://issues.apache.org/activemq/browse/AMQ-685?page=all ]
Nathan Mittler closed AMQ-685:
--
Resolution: Fixed
CMS now properly handles bytes messages. Tested against the April 19th
incubator snapshot of the broker. Also updated the test program t
STOMP transport handles JMS type improperly
---
Key: AMQ-739
URL: https://issues.apache.org/activemq/browse/AMQ-739
Project: ActiveMQ
Type: Bug
Components: Transport
Environment: sending from STOMP to JMS
Reporter: Na
[
https://issues.apache.org/activemq/browse/AMQ-664?page=comments#action_36281 ]
Nathan Mittler commented on AMQ-664:
There are a couple ways we could fix this:
1) I guess a quick fix would be to add a timestamp when the broker receives the
message tha
Add request-id and response-id headers to STOMP connect/connected handshake
---
Key: AMQ-748
URL: https://issues.apache.org/activemq/browse/AMQ-748
Project: ActiveMQ
Type: New Feature
Componen
[ https://issues.apache.org/activemq/browse/AMQ-664?page=all ]
Nathan Mittler reassigned AMQ-664:
--
Assign To: Nathan Mittler
> Messages sent via STOMP don't have a correct JMSTimestamp.
> --
>
>
[
https://issues.apache.org/activemq/browse/AMQ-739?page=comments#action_36315 ]
Nathan Mittler commented on AMQ-739:
It isn't possible to reuse the "type" header (JMSType) for the purpose of
sending through the information as to what type of message it
[
https://issues.apache.org/activemq/browse/AMQ-739?page=comments#action_36437 ]
Nathan Mittler commented on AMQ-739:
clients can use bytes and text messages so long as they follow AMQ's scheme for
making the distinction: if content-length is specified,
[
https://issues.apache.org/activemq/browse/AMQ-517?page=comments#action_36505 ]
Nathan Mittler commented on AMQ-517:
We're getting there - I've submitted the activemq-cpp to trunk. Currently it
still only supports stomp, so it is a complete replacemen
[ https://issues.apache.org/activemq/browse/AMQ-778?page=all ]
Nathan Mittler resolved AMQ-778:
Resolution: Fixed
This has been implemented as part of the activemq-cpp patch:
https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-cpp/sr
[ https://issues.apache.org/activemq/browse/AMQ-779?page=all ]
Nathan Mittler reassigned AMQ-779:
--
Assign To: Nathan Mittler
> add createDurableSubscriber() methods to Session.h
> --
>
> Key: AMQ-
[
https://issues.apache.org/activemq/browse/AMQ-779?page=comments#action_36528 ]
Nathan Mittler commented on AMQ-779:
It looks like this has been implemented in activemq-cpp, not sure that it has
been tested yet. We should add an integration test for t
[
https://issues.apache.org/activemq/browse/AMQ-818?page=comments#action_36602 ]
Nathan Mittler commented on AMQ-818:
Patch is applied - thanks Tim!
Check it out and let me know if everything is as it should be.
> Code Drop for Version 0.0.
[ https://issues.apache.org/activemq/browse/AMQ-818?page=all ]
Nathan Mittler resolved AMQ-818.
Resolution: Fixed
patch has been applied to trunk ... not sure if a Fix Version applies - are we
including the activemq-cpp code in releases?
> Code Drop fo
[ https://issues.apache.org/activemq/browse/AMQ-823?page=all ]
Nathan Mittler resolved AMQ-823.
Resolution: Fixed
Patch has been applied ... Thanks!
> Incorect handling of message size in ByteArrayOutputStream::write
> --
[
https://issues.apache.org/activemq/browse/AMQ-707?page=comments#action_36641 ]
Nathan Mittler commented on AMQ-707:
This issue was for the original CMS client, which has since been replaced by
activemq-cpp. I don't think this applies to t
[
https://issues.apache.org/activemq/browse/AMQ-1012?page=comments#action_37349 ]
Nathan Mittler commented on AMQ-1012:
-
I just tried again against the Oct 24th build of 4.0.2 and everything seems to
be working. Could you re-download 4.0.2
[
https://issues.apache.org/activemq/browse/AMQ-1022?page=comments#action_37423 ]
Nathan Mittler commented on AMQ-1022:
-
Please give this test build a try and let me know how it goes ...
http://people.apache.org/~nmittler/apache-activemq-4.2
[
https://issues.apache.org/activemq/browse/AMQ-1022?page=comments#action_37424 ]
Nathan Mittler commented on AMQ-1022:
-
Ignore my previous comment - this build is for a different issue.
> when client is not authorized to write to A_QUEUE, p
Add other versions of send method to CMS MessageProducer
Key: AMQCPP-15
URL: https://issues.apache.org/activemq/browse/AMQCPP-15
Project: ActiveMQ C++ Client
Issue Type: New Feature
[
https://issues.apache.org/activemq/browse/AMQCPP-16?page=comments#action_37557
]
Nathan Mittler commented on AMQCPP-16:
--
Add the following flavors of the send method to MessageProducer:
send(Destination destination, Message message, int
[ https://issues.apache.org/activemq/browse/AMQCPP-15?page=all ]
Nathan Mittler closed AMQCPP-15.
Resolution: Duplicate
This issue is being handled by AMQ-CPP-16
> Add other versions of send method to CMS MessageProducer
> --
[
https://issues.apache.org/activemq/browse/AMQCPP-16?page=comments#action_37559
]
Nathan Mittler commented on AMQCPP-16:
--
I've committed the two extra send methods in the MessageProducer to trunk as
part of my checkin for AMQCPP-14
> CMS
[
https://issues.apache.org/activemq/browse/AMQCPP-14?page=comments#action_37560
]
Nathan Mittler commented on AMQCPP-14:
--
I have committed changes to trunk. I'd like to create a new integration test
to prove that the expiration works pro
[
https://issues.apache.org/activemq/browse/AMQCPP-16?page=comments#action_37570
]
Nathan Mittler commented on AMQCPP-16:
--
I've changed CMS::Message to match the JMS Message property methods. I have
only modified the Stomp implementation.
[
https://issues.apache.org/activemq/browse/AMQCPP-14?page=comments#action_37573
]
Nathan Mittler commented on AMQCPP-14:
--
Another issue was found in that the MessageConsumer's receive() method does not
seem to take message expiration into
Deadlock when in stomp connector close
--
Key: AMQCPP-20
URL: https://issues.apache.org/activemq/browse/AMQCPP-20
Project: ActiveMQ C++ Client
Issue Type: Bug
Affects Versions: 1.0
Reporter
[ 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 nat
[ 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 of the st
[ 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
>
[
https://issues.apache.org/activemq/browse/AMQCPP-16?page=comments#action_37617
]
Nathan Mittler commented on AMQCPP-16:
--
A couple others that deviate from the JMS spec that we may want to consider
1) Bytes message as defined by JMS shoul
[
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.
[
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 by Val
[
https://issues.apache.org/activemq/browse/AMQCPP-28?page=comments#action_37707
]
Nathan Mittler commented on AMQCPP-28:
--
I think the fix that I made to Thread.cpp to fix the unit tests may also fix
this leak. Please try again with the l
[
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 integratio
[ 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
Add support to activemq-cpp to support the openwire protocol
Key: AMQCPP-30
URL: https://issues.apache.org/activemq/browse/AMQCPP-30
Project: ActiveMQ C++ Client
Issue Type: New Fe
[
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, but
[ 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
>
[
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 test
[
https://issues.apache.org/activemq/browse/AMQCPP-28?page=comments#action_37754
]
Nathan Mittler commented on AMQCPP-28:
--
Was this issue resolved by the latest changes?
> Purify and Valgrind warnings when running integration tests
>
[
https://issues.apache.org/activemq/browse/AMQCPP-31?page=comments#action_37758
]
Nathan Mittler commented on AMQCPP-31:
--
Would a better solution be to use the autoconf-style #ifdefs for headers and
methods, like we've done elsewhere in t
[
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
> --
[
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 this behavi
[
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
[
https://issues.apache.org/activemq/browse/AMQCPP-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Mittler closed AMQCPP-28.
Resolution: Fixed
Patch has been applied to trunk.
> Purify and Valgrind warnings when running
[
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
[
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-cpp
[
https://issues.apache.org/activemq/browse/AMQCPP-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Mittler closed AMQCPP-45.
Resolution: Fixed
Fixed in 1.1 tag.
> Update configure.ac with release version
> --
[
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
[
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 -W
[
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 an
[
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 compil
[
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 a samp
[
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 o
[
https://issues.apache.org/activemq/browse/AMQCPP-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Mittler closed AMQCPP-44.
Resolution: Fixed
The documentation on MSDN suggests that using WSAGetLastError is correct (i.e.
[
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
>
>
[
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
>
[
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
[
https://issues.apache.org/activemq/browse/AMQCPP-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37978
]
Nathan Mittler commented on AMQCPP-46:
--
I found some issues with closing a consumer when there is a broken socke
[
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, if it is t
[
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
[
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
[
https://issues.apache.org/activemq/browse/AMQCPP-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38023
]
Nathan Mittler commented on AMQCPP-59:
--
could you include the source code for the application that exhibits this
[
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 th
[
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
>
[
https://issues.apache.org/activemq/browse/AMQ-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38435
]
Nathan Mittler commented on AMQ-1141:
-
the request-id field was added to support doing support the connect/connect
[
https://issues.apache.org/activemq/browse/AMQCPP-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38436
]
Nathan Mittler commented on AMQCPP-60:
--
I've commented the issue. I don't think using correlation-id is the rig
[
https://issues.apache.org/activemq/browse/AMQCPP-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38437
]
Nathan Mittler commented on AMQCPP-60:
--
Kay,
Are you able to send messages from a stomp client to a JMS client (
Refactor transport creation
---
Key: AMQCPP-65
URL: https://issues.apache.org/activemq/browse/AMQCPP-65
Project: ActiveMQ C++ Client
Issue Type: Improvement
Environment: NA
Reporter: Nathan Mittle
[
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 the request
[
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 the la
75 matches
Mail list logo
