Re: content-type & interoperability between Java/JMS & Cpp/amqp

2018-10-26 Thread Olivier Mallassi 
Robbie,

Sorry and just in case. Is this decision "included decision to remove those
and leave it as implementation detail " definitive? :)

cheers

On Thu, Oct 25, 2018 at 9:37 PM Olivier Mallassi 
wrote:

> Thanks Robbie.
> I understand "leave it as implementation detail since the concepts " as I
> should use my own custom header like myContentTypeHeader
>
> Am I right?
> What would you advice then?
>
> On Thu, Oct 25, 2018 at 6:11 PM Robbie Gemmell 
> wrote:
>
>> The JMS client does not currently allow (outside of perhaps using
>> reflection to access implementation details) manipulating or accessing
>> the content type and encoding fields. It doesnt support the
>> vendor-property you refer to below, and discussion since that old
>> mapping draft was written (by me) actually included decision to remove
>> those and leave it as implementation detail since the concepts are not
>> part of JMS.
>>
>> On Thu, 25 Oct 2018 at 16:45, Olivier Mallassi
>>  wrote:
>> >
>> > All,
>> >
>> > I am facing the following context and would need your help as I am not
>> able
>> > to fully understand it from specification & code perspectives.
>> >
>> > I need
>> > - to send/consume messages using JMS and consume/send messages using
>> > proton-c.
>> > and
>> > - my message can be of multiple types : application/json,
>> application/xml
>> > and binary based on protocolbuffer (so something like
>> application/protobuf
>> > but to be defined).
>> > I was expecting to use the amqp content-type (and content-encoding)
>> > headers. but I cannot see how to set them in JMS.
>> >
>> > My understanding of the "specification" (
>> >
>> https://www.oasis-open.org/committees/download.php/56418/amqp-bindmap-jms-v1.0-wd06.pdf
>> )
>> > is that (1) there is a default mapping based on the java.jms.Message
>> type
>> > and (2) we can use JMS AMQP CONTENT TYPE vendor specific properties to
>> > specify our content type.
>> > Am I right?
>> > My understanding from the JMS code (
>> >
>> https://github.com/apache/qpid-jms/blob/master/qpid-jms-client/src/main/java/org/apache/qpid/jms/provider/amqp/message/AmqpCodec.java#L414
>> )
>> > is that I cannot do (2). in fact I will fallback to ByteMessage with no
>> way
>> > of being able to distinguish between the potential content-types.
>> >
>> > What am I missing? Do you have any guidelines about how to do this?
>> >
>> > Thanks a lot for your help and apologies if I missed something obvious.
>> >
>> > Regards.
>> >
>> > olivier.
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>>
>>

Re: qpid-cpp-0.35 errors

2018-10-26 Thread Gordon Sim 

On 26/10/18 00:44, rammohan ganapavarapu wrote:

Any idea when do we see this error?


In AMQP 0-10, the connection-close frame allows an informational message 
(replyText) to be included. This must be less than 256 bytes. It sounds 
like something is either trying to exceed that, or succeeding and 
violating the protocol.


If you can reproduce with a protocol trace, that will speed up resolution.



On Tue, Oct 23, 2018 at 10:42 AM rammohan ganapavarapu <
rammohanga...@gmail.com> wrote:


That error i get it but what is this error i am seeing in client ?


2018-10-23 17:10:57,997  IoReceiver - /10.68.94.134:5672 ERROR
o.a.q.c.AMQConnectionDelegate_0_10 - AMQConnectionDelegate_0_10.closed() :
connection exception: conn:5668fdd1
org.apache.qpid.transport.ConnectionException: illegal-argument: Value for
replyText is too large
at org.apache.qpid.transport.Connection.closeCode(Connection.java:556)
~[qpid-common-0.28.jar:na]
at
org.apache.qpid.transport.ConnectionDelegate.connectionClose(ConnectionDelegate.java:75)
~[qpid-common-0.28.jar:na]
at
org.apache.qpid.transport.ConnectionDelegate.connectionClose(ConnectionDelegate.java:40)
~[qpid-common-0.28.jar:na]
at
org.apache.qpid.transport.ConnectionClose.dispatch(ConnectionClose.java:91)
~[qpid-common-0.28.jar:na]
at
org.apache.qpid.transport.ConnectionDelegate.control(ConnectionDelegate.java:49)
~[qpid-common-0.28.jar:na]
at
org.apache.qpid.transport.ConnectionDelegate.control(ConnectionDelegate.java:40)
~[qpid-common-0.28.jar:na]
at org.apache.qpid.transport.Method.delegate(Method.java:163)
~[qpid-common-0.28.jar:na]
at org.apache.qpid.transport.Connection.received(Connection.java:392)
~[qpid-common-0.28.jar:na]
at org.apache.qpid.transport.Connection.received(Connection.java:62)
~[qpid-common-0.28.jar:na]
at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:97)
~[qpid-common-0.28.jar:na]
at
org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:183)
~[qpid-common-0.28.jar:na]
at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:131)
~[qpid-common-0.28.jar:na]
at org.apache.qpid.transport.network.Frame.delegate(Frame.java:128)
~[qpid-common-0.28.jar:na]
at
org.apache.qpid.transport.network.Assembler.received(Assembler.java:102)
~[qpid-common-0.28.jar:na]
at org.apache.qpid.transport.network.Assembler.received(Assembler.java:44)
~[qpid-common-0.28.jar:na]
at
org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:189)
~[qpid-common-0.28.jar:na]
at
org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:105)
~[qpid-common-0.28.jar:na]
at
org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:44)
~[qpid-common-0.28.jar:na]
at
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161)
~[qpid-common-0.28.jar:na]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_112]

Ram

On Mon, Oct 22, 2018 at 3:41 PM Chester  wrote:


2018-10-22 07:39:02 [Broker] warning Exchange ex-group-1 cannot deliver to

queue prod-queue-01: resource-limit-exceeded: Maximum depth exceeded on

prod-queue-01: current=[count: 12567, size: 1073741816], max=[count:

100, size: 1073741824]

(/builddir/build/BUILD/qpid-cpp-1.35.0/src/qpid/broker/Queue.cpp:1662)


Looks like you're hitting a queue size (bytes) limit of ~1GB. See the
Broker Book for the configuration option that sets this limit [1].

[1]

https://qpid.apache.org/releases/qpid-cpp-1.38.0/cpp-broker/book/ch01s02.html#CheatSheetforconfiguringQueueOptions-ApplyingQueueSizingConstraints


On Mon, Oct 22, 2018 at 5:21 PM rammohan ganapavarapu <
rammohanga...@gmail.com> wrote:


Hi,

I am seeing lot of these messages in my qpidd logs and i am not sure

why am

i seeing these, can some one explain?

2018-10-22 07:39:02 [Broker] warning Exchange ex-group-1 cannot deliver

to

queue prod-queue-01: resource-limit-exceeded: Maximum depth exceeded on
prod-queue-01: current=[count: 12567, size: 1073741816], max=[count:
100, size: 1073741824]
(/builddir/build/BUILD/qpid-cpp-1.35.0/src/qpid/broker/Queue.cpp:1662)

2018-10-22 07:39:02 [Broker] error Execution exception:
resource-limit-exceeded: Maximum depth exceeded on prod-queue-01:
current=[count: 12567, size: 1073741816], max=[count: 100, size:
1073741824]
(/builddir/build/BUILD/qpid-cpp-1.35.0/src/qpid/broker/Queue.cpp:1662)

2018-10-22 08:05:30 [Broker] error Channel exception: not-attached:

Channel

0 is not attached



(/builddir/build/BUILD/qpid-cpp-1.35.0/src/qpid/amqp_0_10/SessionHandler.cpp:39)



2018-10-22 07:37:02 [Broker] error Connection exception: framing-error:
Queue prod-queue-01: MessageStoreImpl::store() failed: jexception 0x0803
wmgr::enqueue() threw JERR_WMGR_ENQDISCONT: Enqueued new dtok when

previous

enqueue returned partly completed (state ENQ_PART). (This data_tok:
id=4682049 state=NONE)



(/home/rganapavarapu/rpmbuild/BUILD/qpid-cpp-1.35.0/src/qpid/linearstore/MessageStoreImpl.cpp:1211)

2018-10-22 07:37:02 [Protocol] error Connection
qpid.10.68.94

[RESULT] [VOTE] Release Apache Qpid C++ 1.39.0

2018-10-26 Thread Justin Ross 
The release is approved with 5 votes in favor and none against.

I'll move the artifacts to the release dist location.  On Monday, I'll push
the site update and send the announcement.

On Mon, Oct 22, 2018 at 5:47 AM Justin Ross  wrote:

> Hi, everyone.  Please test this release candidate and vote based on what
> you find.
>
> Source archive and signatures:
> https://dist.apache.org/repos/dist/dev/qpid/cpp/1.39.0-rc1/
>
> Issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12342978
>
> Tag:
> 1.39.0-rc1
>