On 07/15/2015 08:51 PM, plsph wrote:
it was typo during rewrite. broker settings are fine. i don't know what the
consumer is. i only got producer and broker.
it's hard to argue with statement that it should work. i've used qpid-proton
writen in c and i was able to send messages to jms transformer
On 07/12/2015 08:03 PM, plsph wrote:
it doesn't work with setContentObject, there should be
msg.getContentObject().setEncoding()
but it still doesn't help with my issue.
i use qpid-cpp 0.32, activemq 11.1
code is something like:
Message msg(content);
msg.setContentType() <- i was trying everythi
On 03/28/2015 01:28 PM, Jim Jagielski wrote:
What I don't like, from what I read, is almost virus-like
attempt to make HQ into AMQ. Virus works by invading a cell
and then using the cell itself to reproduce; the original cell
is gone, all that remains is the virus (this is incredibly
simplified,
On 12/18/2014 01:46 PM, Robbie Gemmell wrote:
On 18 December 2014 at 12:29, Gordon Sim wrote:
On 12/17/2014 12:37 PM, Robbie Gemmell wrote:
Hi everyone (please use reply-all to keep both lists on the trail),
I would like to have a discussion around JMS destination handling in
the JMS
On 12/17/2014 12:37 PM, Robbie Gemmell wrote:
Hi everyone (please use reply-all to keep both lists on the trail),
I would like to have a discussion around JMS destination handling in
the JMS Mapping for AMQP 1.0, in particular around how to handle JMS
Destination names via the AMQP "address" fie
[
https://issues.apache.org/jira/browse/AMQ-5490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim closed AMQ-5490.
---
Resolution: Duplicate
> broker does not write out supported version hea
[
https://issues.apache.org/jira/browse/AMQ-5490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249830#comment-14249830
]
Gordon Sim commented on AMQ-5490:
-
Not yet, will do that
> broker does not wr
Gordon Sim created AMQ-5490:
---
Summary: broker does not write out supported version header
Key: AMQ-5490
URL: https://issues.apache.org/jira/browse/AMQ-5490
Project: ActiveMQ
Issue Type: Bug
On 05/19/2014 06:35 PM, uromahn wrote:
Hmm, from the deafening silence I must assume that either of the two things
happened:
1. People didn't read my post for some reason (and hence I am replying to my
own post to refresh this post), or
2. There is no appetite supporting JMS 2.0 in ActiveMQ and h
to send this information to use the same mechanism for
greater interoperability and improved experience to all.
Thanks,
--Gordon Sim.
On 05/14/2014 09:48 PM, Rob Godfrey wrote:
On 14 May 2014 02:23, Robbie Gemmell wrote:
On 13 May 2014 17:31, Gordon Sim wrote:
[...]
For indicating the use of proton I'd suggest we define a
qpid-proton-version property or some such (and then a
qpid-messaging-version / qpid-jms-ve
On 05/14/2014 10:23 AM, Robbie Gemmell wrote:
My interest is mostly around conveying the main component being doing the
messaging (e.g. Qpid Messaging C++ Client, ActiveMQ Broker) rather than the
application, but I can see that could be useful too in some cases.
Yes, and I don't want to overcom
On 05/13/2014 08:25 PM, Robbie Gemmell wrote:
On 13 May 2014 17:59, Justin Ross wrote:
On Tue, May 13, 2014 at 12:31 PM, Gordon Sim wrote:
How about process_name and process_id then?
I like those. I don't think brevity is important in this case, and those
names are very clear
On 05/13/2014 04:47 PM, Robbie Gemmell wrote:
Sounds like a good idea to me. I have been meaning to do the same thing
with some other properties like 'version' and 'product'.
Yeah, my one question there was about distinguishing different 'layers'.
E.g. proton engine version, v. qpid::messaging
The qpid::messaging (c++), qpid.messaging (python) libraries send
connection properties to identify the process by name and pid among
other things. These are then used by the QMF support in qpidd to report
the process details for the connections.
This has proven to be an extremely useful featu
On 05/13/2014 05:12 PM, Chuck Rolke wrote:
I like having registered properties especially for common cases.
'client-pid' and 'client-name' would be my first vote.
The reason I don't like 'client' in there is that its not always
'clients' making the connection and further, 'client' means diffe
[
https://issues.apache.org/jira/browse/AMQ-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865975#comment-13865975
]
Gordon Sim commented on AMQ-4914:
-
I think this may be addressed by h
Gordon Sim created AMQ-4590:
---
Summary: AMQP: Only one connection from a given container is
allowed
Key: AMQ-4590
URL: https://issues.apache.org/jira/browse/AMQ-4590
Project: ActiveMQ
Issue Type
18 matches
Mail list logo
