n if this occurs just as the virtual host is stopping (once
>> it has been stopped the connection is closed by the broker without it
>> attempting to move thread pools).
>>
>> Thanks for the detailed bug report, and apologies that you have run
>> into this.
>
documentation:
>
> http://qpid.apache.org/releases/qpid-jms-0.8.0/docs/index.html#connect
> ion-uri
>
> Robbie
>
> On 21 March 2016 at 07:58, Julien Charon
> wrote:
> > Hi Robbie,
> >
> >
> > Thanks for the hint. But how can I manipulate t
our system.
-Ursprüngliche Nachricht-
Von: Julien Charon [mailto:julien.cha...@avitech.aero]
Gesendet: Montag, 21. März 2016 08:59
An: users@qpid.apache.org
Betreff: AW: java broker queue flow control
Hi Robbie,
Thanks for the hint. But how can I manipulate the link credit for a JMS client
a
> In terms of queue flow control, governing ability to send works
>> differently in AMQP 1.0 than in AMQP 0.x did, and I'm not sure what
>> the broker does there, it may be that feature isnt yet functional for
>> AMQP 1.0 producers.
>>
>> Robbie
&g
t;
>> In terms of queue flow control, governing ability to send works
>> differently in AMQP 1.0 than in AMQP 0.x did, and I'm not sure what
>> the broker does there, it may be that feature isnt yet functional for
>> AMQP 1.0 producers.
>>
>> Robbie
&g
system.
-Ursprüngliche Nachricht-
Von: Julien Charon [mailto:julien.cha...@avitech.aero]
Gesendet: Freitag, 18. März 2016 07:59
An: users@qpid.apache.org
Betreff: Java broker crashes after stopping vhost
Hi,
I ran into a strange behaviour of the java broker I'd like to report.
I di
Hi,
I'm currently trying to configure flow control on queue level as described in
[1].
I tried the following:
- Create a queue, set flow control settings: capacity = 1024, resume capacity =
512 (I also tried with capacity = 10240, resume capacity = 5120 and capacity =
102400, resume capacity
ently
which would cause the sends to break.
On 03/16/2016 06:02 AM, Julien Charon wrote:
>Hi,
>
>
> I'm currently doing some testing on a client that uses the JMS client
> internally to send messages to an AMQP queue.
> Now I wanted to test what happens when the broker is n
Hi,
I ran into a strange behaviour of the java broker I'd like to report.
I did the following:
- Change the flow control of a queue in the web management console. An info
tells me that I have to restart the vhost so that changes will have effect
- Stop the vhost (default) in the web management
Hi,
I'm currently doing some testing on a client that uses the JMS client
internally to send messages to an AMQP queue.
Now I wanted to test what happens when the broker is not reachable and I try to
send a message. I configured the connection with failover(...) so that the
connection will b
P JMS mapping and implement it, I have raised
https://issues.apache.org/jira/browse/QPIDJMS-153 to track things from the
client side.
Robbie
On 8 March 2016 at 11:04, Julien Charon wrote:
> Hi Robbie,
>
>
> Will that be added in future?
>
>
> Best regards,
>
> Julien
&g
sure whether there is an equivalent mechanism in the
> newer Proton-based Qpid JMS client.
>
> -- Rob
>
> On 8 March 2016 at 09:11, Julien Charon wrote:
>
>> Hi,
>>
>>
>> I have a short question regarding the JMS client. How can I set
>> headers and
ied in the 0.32 release of that... I'm not
sure whether there is an equivalent mechanism in the newer Proton-based Qpid
JMS client.
-- Rob
On 8 March 2016 at 09:11, Julien Charon wrote:
> Hi,
>
>
> I have a short question regarding the JMS client. How can I set
> headers
Hi,
I have a short question regarding the JMS client. How can I set headers and
delivery / message annotations on a JMS message?
I found a jira issue [1] regarding this, but it's quite old and doesn't seem to
be valid anymore.
Is there some documentation in how to do this?
[1] https://issues
en the origin server MUST send
either a 200 (OK) or a
204 (No Content) response to indicate successful completion of the request."
So I believe we do follow the spec and returning 4xx would violate it.
Kind regards,
Lorenz
[1] https://tools.ietf.org/html/rfc7231#section-4.3.4
On 07/03/16 08:3
odfrey [mailto:rob.j.godf...@gmail.com]
Gesendet: Montag, 7. März 2016 09:14
An: users@qpid.apache.org
Betreff: Re: potential java broker REST API bug
On 7 March 2016 at 07:06, Julien Charon wrote:
>
> Indeed, copy paste error on this, sorry. I observed the behaviour not
> only for DELETE,
: potential java broker REST API bug
Raised JIRAs https://issues.apache.org/jira/browse/QPID-7124 and
https://issues.apache.org/jira/browse/QPID-7125 to cover the issues brought up
here.
-- Rob
On 4 March 2016 at 14:06, Rob Godfrey wrote:
>
>
> On 4 March 2016 at 13:49, Julien Charon
> wrot
Hi,
I'm currently doing some tests with the java broker's REST API (6.0.1), mainly
queue management, i.e. GET, PUT, DELETE and ran into something strange.
Assuming the broker is running on localhost and on port 8080, I can perform
following requests:
GET: http://localhost:8080/api/latest/queu
owse/QPID-7103)
-- Rob
On 4 March 2016 at 11:47, Julien Charon wrote:
> Hi,
>
>
> I'm currently developing a java client that accesses the java broker's
> REST API, mainly to manage queues. Now I'm wondering if there already
> are some java classes that can be
Hi,
I'm currently developing a java client that accesses the java broker's REST
API, mainly to manage queues. Now I'm wondering if there already are some java
classes that can be used to serialise / deserialise the json configuration e.g.
with jackson. If so, it would be nice to be able to r
As to simply exposing the information through REST (JMX is being removed in the
next release), that would be easier to add - I'll look at those later this
morning and if it is simple I'll make a change on trunk for this.
-- Rob
On 15 January 2016 at 08:34, Julien Charon
wrote:
&g
Hi,
I was just experimenting a little bit with the REST API of the java broker
(Release 6.0.0)and ran into 2 errors when using paths /api/latest/consumer and
/api/latest/publisher.
In the broker logs, I can see following stack trace (pretty much the same for
both paths):
2016-01-15 08:05:30
Hi,
Is there any possibility to configure the java broker so that it adds some
additional information on AMQP messages?
My concrete use case is that I'd need the java broker to add the clientId and
the userId of the client that sent/published a message, e.g. the message
annotations or appl
ember 2015 at 14:24, Julien Charon wrote:
> Hi Rob,
>
>
> Thank you very much for the implementation. I just tested it with a very
> similar configuration as described in QPID-6954 (merely modified the pattern)
> and it seems to work pretty well.
> However, I noticed 2 t
Hi Rob,
Thank you very much for the implementation. I just tested it with a very
similar configuration as described in QPID-6954 (merely modified the pattern)
and it seems to work pretty well.
However, I noticed 2 things:
1. After a broker restart, an automatically created queue has disappear
it instead concentrated on getting messages from A to B rather than
> defining an explicit broker model that must be implemented. There is
> an effort at the OASIS AMQP TC to define a layered AMQP Management
> specification that uses AMQP messaging to support implementing such
>
Hi,
I'd like to know if it's possible to dynamically / automatically have queues
created using AMQP 1.0 and the java broker. I'd like to avoid to use the REST
or JMX interface to create queues manually before a client can make a
connection. I need this for some publish/subscribe scenario.
An
27 matches
Mail list logo
