You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Venkat Nani <sw...@gmail.com> on 2018/03/28 09:26:13 UTC

Issue in connecting qpid broker j from qpid proton java libraries

Hi Team,
I am facing issue in connecting qpid broker j from qpid java client.
I using the libraries and code which is apache.org which is also in git hub.
https://github.com/apache/qpid-proton-j/tree/master/examples

I could see the connection established in qpid broker j but not able to
post the message and connection is not closed. Could you please help in
configuring the broker or client programming or procedure to do working
sample with qpid broker j from a proton java client libraries.
below are the broker screen shot and broker logs. Please let me know if
anything required to sort out the issue.








Broker logs:
2018-03-28 13:32:38,535 INFO  [Broker-Config] (q.m.b.ready) - [Broker]
BRK-1004 : Qpid Broker Ready
2018-03-28 13:32:53,348 INFO  [FileSystemSpaceChecker[default]]
(q.m.v.filesystem_full) - [FileSystemSpaceChecker[default]]
[vh(/default)/ms(BDBMessageStore)] VHT-1006 : Filesystem is over 90 per
cent full, enforcing flow control.
2018-03-28 13:32:58,143 INFO  [qtp150440100-125] (q.m.m.open) -
[mng:lDQpBoQc(admin@/0:0:0:0:0:0:0:1:60805)] MNG-1007 : Open : User admin
2018-03-28 13:33:17,226 INFO  [Broker-Config] (q.m.c.open) - [con:0(/
127.0.0.1:60817)] CON-1001 : Open : Destination : AMQP(127.0.0.1:5672) :
Protocol Version : 1.0
2018-03-28 13:33:17,353 INFO  [IO-/127.0.0.1:60817] (q.m.c.open) -
[con:0(ANONYMOUS@/127.0.0.1:60817/default)] CON-1001 : Open : Destination :
AMQP(127.0.0.1:5672) : Protocol Version : 1.0 : Client ID :
1acc401b-9c26-46b9-9f9f-decfb71ec374
2018-03-28 13:33:17,415 INFO  [IO-/127.0.0.1:60817] (q.m.c.create) -
[con:0(ANONYMOUS@/127.0.0.1:60817/default)/ch:0] CHN-1001 : Create
2018-03-28 13:33:17,431 INFO  [IO-/127.0.0.1:60817] (q.m.c.flow_enforced) -
[con:0(ANONYMOUS@/127.0.0.1:60817/default)] [con:0(ANONYMOUS@/
127.0.0.1:60817/default)/ch:0] CHN-1005 : Flow Control Enforced (Queue **
All Queues **)
2018-03-28 13:36:15,232 INFO  [Broker-Config] (q.m.c.open) - [con:1(/
127.0.0.1:60843)] CON-1001 : Open : Destination : AMQP(127.0.0.1:5672) :
Protocol Version : 1.0
2018-03-28 13:36:15,279 INFO  [IO-/127.0.0.1:60843] (q.m.c.open) -
[con:1(ANONYMOUS@/127.0.0.1:60843/default)] CON-1001 : Open : Destination :
AMQP(127.0.0.1:5672) : Protocol Version : 1.0 : Client ID :
e2aacb0e-1834-4627-ab09-49a9f4540403
2018-03-28 13:36:15,295 INFO  [IO-/127.0.0.1:60843] (q.m.c.create) -
[con:1(ANONYMOUS@/127.0.0.1:60843/default)/ch:0] CHN-1001 : Create
2018-03-28 13:36:15,295 INFO  [IO-/127.0.0.1:60843] (q.m.c.flow_enforced) -
[con:1(ANONYMOUS@/127.0.0.1:60843/default)] [con:1(ANONYMOUS@/
127.0.0.1:60843/default)/ch:0] CHN-1005 : Flow Control Enforced (Queue **
All Queues **)


Regards
Venkat
+919164256688

Re: Issue in connecting qpid broker j from qpid proton java libraries

Posted by Robbie Gemmell <ro...@gmail.com>.
First, it seems from your logs that you are running low on disk space and
so the broker is flow controlling the virtualhost / its queues. I expect
that means it wont grant new credit to a new sender, and so wont accept new
messages. The example I think you are using closes its connection after
successfully sending, which it presumably thus wont yet be able to do.

Beyond that, the next main issue is going to be that those examples arent
very good. I'd guess you ran 'engine' Spout example, as I'm not sure the
'reactor' Send example would actually work against most real servers (they
demonstrate some basics and work with each other, but omit details that
might be required against real servers).

Proton was originally envisaged as purely a protocol engine others could
use in creating AMQP 1.0 clients/servers/others, and thats how proton-j
continues to see most of its use, e.g within Qpid JMS, the ActiveMQ
brokers, and Vert.x, amongst others. I don't expect thats what you are
looking to do here, but rather just use a client to send and recieve
messages? The 'reactor' was added later as an expansion of that but is
fairly low level and not a very good fit for most end users.

If the JMS client doesnt fit your needs, I'd suggest you might want to look
at
https://github.com/vert-x3/vertx-proton/blob/3.5.1/src/main/asciidoc/java/index.adoc#using-vertx-proton
for an simpler alternative 'client' experience. Theres a HelloWorld example
at
https://github.com/vert-x3/vertx-proton/blob/3.5.1/src/test/java/io/vertx/proton/example/HelloWorld.java
you could look at.

Robbie

(dropped proton@ since it is no longer used and now only an alias for users@
)

On 28 March 2018 at 10:26, Venkat Nani <sw...@gmail.com> wrote:

> Hi Team,
> I am facing issue in connecting qpid broker j from qpid java client.
> I using the libraries and code which is apache.org which is also in git
> hub.
> https://github.com/apache/qpid-proton-j/tree/master/examples
>
> I could see the connection established in qpid broker j but not able to
> post the message and connection is not closed. Could you please help in
> configuring the broker or client programming or procedure to do working
> sample with qpid broker j from a proton java client libraries.
> below are the broker screen shot and broker logs. Please let me know if
> anything required to sort out the issue.
>
>
>
>
>
>
>
>
> Broker logs:
> 2018-03-28 13:32:38,535 INFO  [Broker-Config] (q.m.b.ready) - [Broker]
> BRK-1004 : Qpid Broker Ready
> 2018-03-28 13:32:53,348 INFO  [FileSystemSpaceChecker[default]]
> (q.m.v.filesystem_full) - [FileSystemSpaceChecker[default]]
> [vh(/default)/ms(BDBMessageStore)] VHT-1006 : Filesystem is over 90 per
> cent full, enforcing flow control.
> 2018-03-28 13:32:58,143 INFO  [qtp150440100-125] (q.m.m.open) -
> [mng:lDQpBoQc(admin@/0:0:0:0:0:0:0:1:60805)] MNG-1007 : Open : User admin
> 2018-03-28 13:33:17,226 INFO  [Broker-Config] (q.m.c.open) - [con:0(/
> 127.0.0.1:60817)] CON-1001 : Open : Destination : AMQP(127.0.0.1:5672) :
> Protocol Version : 1.0
> 2018-03-28 13:33:17,353 INFO  [IO-/127.0.0.1:60817] (q.m.c.open) -
> [con:0(ANONYMOUS@/127.0.0.1:60817/default)] CON-1001 : Open : Destination
> : AMQP(127.0.0.1:5672) : Protocol Version : 1.0 : Client ID :
> 1acc401b-9c26-46b9-9f9f-decfb71ec374
> 2018-03-28 13:33:17,415 INFO  [IO-/127.0.0.1:60817] (q.m.c.create) -
> [con:0(ANONYMOUS@/127.0.0.1:60817/default)/ch:0] CHN-1001 : Create
> 2018-03-28 13:33:17,431 INFO  [IO-/127.0.0.1:60817] (q.m.c.flow_enforced)
> - [con:0(ANONYMOUS@/127.0.0.1:60817/default)] [con:0(ANONYMOUS@/127.0.0.1:
> 60817/default)/ch:0] CHN-1005 : Flow Control Enforced (Queue ** All
> Queues **)
> 2018-03-28 13:36:15,232 INFO  [Broker-Config] (q.m.c.open) - [con:1(/
> 127.0.0.1:60843)] CON-1001 : Open : Destination : AMQP(127.0.0.1:5672) :
> Protocol Version : 1.0
> 2018-03-28 13:36:15,279 INFO  [IO-/127.0.0.1:60843] (q.m.c.open) -
> [con:1(ANONYMOUS@/127.0.0.1:60843/default)] CON-1001 : Open : Destination
> : AMQP(127.0.0.1:5672) : Protocol Version : 1.0 : Client ID :
> e2aacb0e-1834-4627-ab09-49a9f4540403
> 2018-03-28 13:36:15,295 INFO  [IO-/127.0.0.1:60843] (q.m.c.create) -
> [con:1(ANONYMOUS@/127.0.0.1:60843/default)/ch:0] CHN-1001 : Create
> 2018-03-28 13:36:15,295 INFO  [IO-/127.0.0.1:60843] (q.m.c.flow_enforced)
> - [con:1(ANONYMOUS@/127.0.0.1:60843/default)] [con:1(ANONYMOUS@/127.0.0.1:
> 60843/default)/ch:0] CHN-1005 : Flow Control Enforced (Queue ** All
> Queues **)
>
>
> Regards
> Venkat
> +919164256688 <+91%2091642%2056688>
>

Re: Issue in connecting qpid broker j from qpid proton java libraries

Posted by Robbie Gemmell <ro...@gmail.com>.
First, it seems from your logs that you are running low on disk space and
so the broker is flow controlling the virtualhost / its queues. I expect
that means it wont grant new credit to a new sender, and so wont accept new
messages. The example I think you are using closes its connection after
successfully sending, which it presumably thus wont yet be able to do.

Beyond that, the next main issue is going to be that those examples arent
very good. I'd guess you ran 'engine' Spout example, as I'm not sure the
'reactor' Send example would actually work against most real servers (they
demonstrate some basics and work with each other, but omit details that
might be required against real servers).

Proton was originally envisaged as purely a protocol engine others could
use in creating AMQP 1.0 clients/servers/others, and thats how proton-j
continues to see most of its use, e.g within Qpid JMS, the ActiveMQ
brokers, and Vert.x, amongst others. I don't expect thats what you are
looking to do here, but rather just use a client to send and recieve
messages? The 'reactor' was added later as an expansion of that but is
fairly low level and not a very good fit for most end users.

If the JMS client doesnt fit your needs, I'd suggest you might want to look
at
https://github.com/vert-x3/vertx-proton/blob/3.5.1/src/main/asciidoc/java/index.adoc#using-vertx-proton
for an simpler alternative 'client' experience. Theres a HelloWorld example
at
https://github.com/vert-x3/vertx-proton/blob/3.5.1/src/test/java/io/vertx/proton/example/HelloWorld.java
you could look at.

Robbie

(dropped proton@ since it is no longer used and now only an alias for users@
)

On 28 March 2018 at 10:26, Venkat Nani <sw...@gmail.com> wrote:

> Hi Team,
> I am facing issue in connecting qpid broker j from qpid java client.
> I using the libraries and code which is apache.org which is also in git
> hub.
> https://github.com/apache/qpid-proton-j/tree/master/examples
>
> I could see the connection established in qpid broker j but not able to
> post the message and connection is not closed. Could you please help in
> configuring the broker or client programming or procedure to do working
> sample with qpid broker j from a proton java client libraries.
> below are the broker screen shot and broker logs. Please let me know if
> anything required to sort out the issue.
>
>
>
>
>
>
>
>
> Broker logs:
> 2018-03-28 13:32:38,535 INFO  [Broker-Config] (q.m.b.ready) - [Broker]
> BRK-1004 : Qpid Broker Ready
> 2018-03-28 13:32:53,348 INFO  [FileSystemSpaceChecker[default]]
> (q.m.v.filesystem_full) - [FileSystemSpaceChecker[default]]
> [vh(/default)/ms(BDBMessageStore)] VHT-1006 : Filesystem is over 90 per
> cent full, enforcing flow control.
> 2018-03-28 13:32:58,143 INFO  [qtp150440100-125] (q.m.m.open) -
> [mng:lDQpBoQc(admin@/0:0:0:0:0:0:0:1:60805)] MNG-1007 : Open : User admin
> 2018-03-28 13:33:17,226 INFO  [Broker-Config] (q.m.c.open) - [con:0(/
> 127.0.0.1:60817)] CON-1001 : Open : Destination : AMQP(127.0.0.1:5672) :
> Protocol Version : 1.0
> 2018-03-28 13:33:17,353 INFO  [IO-/127.0.0.1:60817] (q.m.c.open) -
> [con:0(ANONYMOUS@/127.0.0.1:60817/default)] CON-1001 : Open : Destination
> : AMQP(127.0.0.1:5672) : Protocol Version : 1.0 : Client ID :
> 1acc401b-9c26-46b9-9f9f-decfb71ec374
> 2018-03-28 13:33:17,415 INFO  [IO-/127.0.0.1:60817] (q.m.c.create) -
> [con:0(ANONYMOUS@/127.0.0.1:60817/default)/ch:0] CHN-1001 : Create
> 2018-03-28 13:33:17,431 INFO  [IO-/127.0.0.1:60817] (q.m.c.flow_enforced)
> - [con:0(ANONYMOUS@/127.0.0.1:60817/default)] [con:0(ANONYMOUS@/127.0.0.1:
> 60817/default)/ch:0] CHN-1005 : Flow Control Enforced (Queue ** All
> Queues **)
> 2018-03-28 13:36:15,232 INFO  [Broker-Config] (q.m.c.open) - [con:1(/
> 127.0.0.1:60843)] CON-1001 : Open : Destination : AMQP(127.0.0.1:5672) :
> Protocol Version : 1.0
> 2018-03-28 13:36:15,279 INFO  [IO-/127.0.0.1:60843] (q.m.c.open) -
> [con:1(ANONYMOUS@/127.0.0.1:60843/default)] CON-1001 : Open : Destination
> : AMQP(127.0.0.1:5672) : Protocol Version : 1.0 : Client ID :
> e2aacb0e-1834-4627-ab09-49a9f4540403
> 2018-03-28 13:36:15,295 INFO  [IO-/127.0.0.1:60843] (q.m.c.create) -
> [con:1(ANONYMOUS@/127.0.0.1:60843/default)/ch:0] CHN-1001 : Create
> 2018-03-28 13:36:15,295 INFO  [IO-/127.0.0.1:60843] (q.m.c.flow_enforced)
> - [con:1(ANONYMOUS@/127.0.0.1:60843/default)] [con:1(ANONYMOUS@/127.0.0.1:
> 60843/default)/ch:0] CHN-1005 : Flow Control Enforced (Queue ** All
> Queues **)
>
>
> Regards
> Venkat
> +919164256688 <+91%2091642%2056688>
>