You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by sivasnp <si...@rockwellcollins.com> on 2017/03/29 16:20:30 UTC
qpid-cpp-1.35 - Cannot sent large message (320K)
Hi,
qpid-client is unable to send a message of size 320K. But a small size
message (10K) is sent without any problem
Following are the options, I set while connecting to the broker.
options["reconnect"] = true;
options["max_frame_size"] = 1370;
options["bounds"] = 330000;
Initially I did not have the bounds option set. Without bounds option set,
when I try to send this message, the send() function hangs and never
returns.
After bounds options is set, the sender returns immediately, but the actual
message is not send to the receiver.
Packet capture shows that the first frame( 1490 bytes) is sent, but
remaining is not sent.
Please help. I am using qpid on ubuntu xenial.
Please let me know, if I am missing something. I can update the logs if
necessary.
Thanks,
Siva.
--
View this message in context: http://qpid.2158936.n2.nabble.com/qpid-cpp-1-35-Cannot-sent-large-message-320K-tp7661623.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpid-cpp-1.35 - Cannot sent large message (320K)
Posted by Gordon Sim <gs...@redhat.com>.
On 30/03/17 13:01, sivasnp wrote:
> Hi Gordon,
> I think I found the problem and it's not related to qpid. I am sending
> data encrypted over IPSec tunnel. I think that is causing theissue. I
> disabled don't fragment bit and it is working now.
Excellent! That is what I was beginning to suspect also.
> Sorry for the trouble. I appreciate all your help
Most welcome! Appreciate you using Qpid!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpid-cpp-1.35 - Cannot sent large message (320K)
Posted by sivasnp <si...@rockwellcollins.com>.
Hi Gordon,
I think I found the problem and it's not related to qpid. I am sending
data encrypted over IPSec tunnel. I think that is causing theissue. I
disabled don't fragment bit and it is working now. I am sorry I suspected
qpid
Sorry for the trouble. I appreciate all your help
The broker log was huge and it contained proprietary information, so I have
to filter the relevant messages before sending it to you. I searched for
"172.21.0.4|amq.fanout" and that resulted in two repeated lines, one for
each match
Thanks,
Siva.
On Thu, Mar 30, 2017 at 6:48 AM Gordon Sim [via Qpid] <
ml-node+s2158936n7661690h73@n2.nabble.com> wrote:
> On 30/03/17 00:07, sivasnp wrote:
> > Hi Gordon,
> > Please see the broker log attached.
>
> There are some odd duplicate lines in that log. However the broker
> doesn't seem to be getting any of the data through. My suspicion would
> be on something odd going on at the TCP level from this log. Maybe get a
> wireshark capture?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> <http:///user/SendEmail.jtp?type=node&node=7661690&i=0>
> For additional commands, e-mail: [hidden email]
> <http:///user/SendEmail.jtp?type=node&node=7661690&i=1>
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://qpid.2158936.n2.nabble.com/qpid-cpp-1-35-Cannot-sent-large-message-320K-tp7661623p7661690.html
> To unsubscribe from qpid-cpp-1.35 - Cannot sent large message (320K), click
> here
> <http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7661623&code=c2l2YS5rdW1hci5zaXZhLnNhbmthcmFuQHJvY2t3ZWxsY29sbGlucy5jb218NzY2MTYyM3wxNjk5ODU5MTQ3>
> .
> NAML
> <http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://qpid.2158936.n2.nabble.com/qpid-cpp-1-35-Cannot-sent-large-message-320K-tp7661623p7661691.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
Re: qpid-cpp-1.35 - Cannot sent large message (320K)
Posted by Gordon Sim <gs...@redhat.com>.
On 30/03/17 00:07, sivasnp wrote:
> Hi Gordon,
> Please see the broker log attached.
There are some odd duplicate lines in that log. However the broker
doesn't seem to be getting any of the data through. My suspicion would
be on something odd going on at the TCP level from this log. Maybe get a
wireshark capture?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpid-cpp-1.35 - Cannot sent large message (320K)
Posted by sivasnp <si...@rockwellcollins.com>.
Hi Gordon,
Please see the broker log attached.
Thanks,
Siva.
On Wed, Mar 29, 2017 at 4:36 PM, Siva Kumar Siva Sankaran <
siva.kumar.siva.sankaran@rockwellcollins.com> wrote:
> The qpid-send just hangs. I have to terminate it.
>
> I did a qpid-stat -q on the queue at the broker and did not see any new
> messages
>
> I did not enable the qpid-broker logs. I will enable it and sent that to
> you in an hour.
>
> Thanks,
> Siva
>
> On Wed, Mar 29, 2017 at 4:32 PM Gordon Sim [via Qpid] <
> ml-node+s2158936n7661650h33@n2.nabble.com> wrote:
>
>> On 29/03/17 22:10, sivasnp wrote:
>> > Please see the output of
>> >
>> > qpid-send -b 172.21.0.254 --address amq.fanout --content-size 500000
>> > --log-enable trace+
>>
>> [...]
>>
>> > 2017-03-29 21:07:06 [Network] trace RECV [[10.0.3.219:51830
>> > -172.21.0.254:5672]]: Frame[BEbe; channel=1; {SessionCompletedBody:
>> > commands={ [0,2] }; }]
>> > 2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
>> > -172.21.0.254:5672]]: Frame[Bbe; channel=1; {MessageTransferBody:
>> > destination=amq.fanout; accept-mode=1; acquire-mode=0; }]
>> > 2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
>> > -172.21.0.254:5672]]: Frame[be; channel=1; header (66 bytes);
>> > properties={{MessageProperties: content-length=500000;
>> > content-type=text/plain; user-id=;
>> > application-headers={sn:F4:uint32(1),ts:F8:int64(1490821626691555779)};
>>
>> > }{DeliveryProperties: routing-key=; }}]
>> > 2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
>> > -172.21.0.254:5672]]: Frame[Eb; channel=1; content (65523 bytes)
>> > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...]
>> > 2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
>> > -172.21.0.254:5672]]: Frame[E; channel=1; content (65523 bytes)
>> > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...]
>>
>> Is that all the output? Does qpid-send terminate or just hangs? Is there
>> anything on the broker logs?
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> <http:///user/SendEmail.jtp?type=node&node=7661650&i=0>
>> For additional commands, e-mail: [hidden email]
>> <http:///user/SendEmail.jtp?type=node&node=7661650&i=1>
>>
>>
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://qpid.2158936.n2.nabble.com/qpid-cpp-1-35-Cannot-sent-
>> large-message-320K-tp7661623p7661650.html
>> To unsubscribe from qpid-cpp-1.35 - Cannot sent large message (320K), click
>> here
>> <http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7661623&code=c2l2YS5rdW1hci5zaXZhLnNhbmthcmFuQHJvY2t3ZWxsY29sbGlucy5jb218NzY2MTYyM3wxNjk5ODU5MTQ3>
>> .
>> NAML
>> <http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
broker.log (16K) <http://qpid.2158936.n2.nabble.com/attachment/7661662/0/broker.log>
--
View this message in context: http://qpid.2158936.n2.nabble.com/qpid-cpp-1-35-Cannot-sent-large-message-320K-tp7661623p7661662.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
Re: qpid-cpp-1.35 - Cannot sent large message (320K)
Posted by sivasnp <si...@rockwellcollins.com>.
The qpid-send just hangs. I have to terminate it.
I did a qpid-stat -q on the queue at the broker and did not see any new
messages
I did not enable the qpid-broker logs. I will enable it and sent that to
you in an hour.
Thanks,
Siva
On Wed, Mar 29, 2017 at 4:32 PM Gordon Sim [via Qpid] <
ml-node+s2158936n7661650h33@n2.nabble.com> wrote:
> On 29/03/17 22:10, sivasnp wrote:
> > Please see the output of
> >
> > qpid-send -b 172.21.0.254 --address amq.fanout --content-size 500000
> > --log-enable trace+
>
> [...]
>
> > 2017-03-29 21:07:06 [Network] trace RECV [[10.0.3.219:51830
> > -172.21.0.254:5672]]: Frame[BEbe; channel=1; {SessionCompletedBody:
> > commands={ [0,2] }; }]
> > 2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
> > -172.21.0.254:5672]]: Frame[Bbe; channel=1; {MessageTransferBody:
> > destination=amq.fanout; accept-mode=1; acquire-mode=0; }]
> > 2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
> > -172.21.0.254:5672]]: Frame[be; channel=1; header (66 bytes);
> > properties={{MessageProperties: content-length=500000;
> > content-type=text/plain; user-id=;
> > application-headers={sn:F4:uint32(1),ts:F8:int64(1490821626691555779)};
> > }{DeliveryProperties: routing-key=; }}]
> > 2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
> > -172.21.0.254:5672]]: Frame[Eb; channel=1; content (65523 bytes)
> > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...]
> > 2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
> > -172.21.0.254:5672]]: Frame[E; channel=1; content (65523 bytes)
> > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...]
>
> Is that all the output? Does qpid-send terminate or just hangs? Is there
> anything on the broker logs?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> <http:///user/SendEmail.jtp?type=node&node=7661650&i=0>
> For additional commands, e-mail: [hidden email]
> <http:///user/SendEmail.jtp?type=node&node=7661650&i=1>
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://qpid.2158936.n2.nabble.com/qpid-cpp-1-35-Cannot-sent-large-message-320K-tp7661623p7661650.html
> To unsubscribe from qpid-cpp-1.35 - Cannot sent large message (320K), click
> here
> <http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7661623&code=c2l2YS5rdW1hci5zaXZhLnNhbmthcmFuQHJvY2t3ZWxsY29sbGlucy5jb218NzY2MTYyM3wxNjk5ODU5MTQ3>
> .
> NAML
> <http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://qpid.2158936.n2.nabble.com/qpid-cpp-1-35-Cannot-sent-large-message-320K-tp7661623p7661651.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
Re: qpid-cpp-1.35 - Cannot sent large message (320K)
Posted by Gordon Sim <gs...@redhat.com>.
On 29/03/17 22:10, sivasnp wrote:
> Please see the output of
>
> qpid-send -b 172.21.0.254 --address amq.fanout --content-size 500000
> --log-enable trace+
[...]
> 2017-03-29 21:07:06 [Network] trace RECV [[10.0.3.219:51830
> -172.21.0.254:5672]]: Frame[BEbe; channel=1; {SessionCompletedBody:
> commands={ [0,2] }; }]
> 2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
> -172.21.0.254:5672]]: Frame[Bbe; channel=1; {MessageTransferBody:
> destination=amq.fanout; accept-mode=1; acquire-mode=0; }]
> 2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
> -172.21.0.254:5672]]: Frame[be; channel=1; header (66 bytes);
> properties={{MessageProperties: content-length=500000;
> content-type=text/plain; user-id=;
> application-headers={sn:F4:uint32(1),ts:F8:int64(1490821626691555779)};
> }{DeliveryProperties: routing-key=; }}]
> 2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
> -172.21.0.254:5672]]: Frame[Eb; channel=1; content (65523 bytes)
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...]
> 2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
> -172.21.0.254:5672]]: Frame[E; channel=1; content (65523 bytes)
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...]
Is that all the output? Does qpid-send terminate or just hangs? Is there
anything on the broker logs?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpid-cpp-1.35 - Cannot sent large message (320K)
Posted by sivasnp <si...@rockwellcollins.com>.
Please see the output of
qpid-send -b 172.21.0.254 --address amq.fanout --content-size 500000
--log-enable trace+
2017-03-29 21:07:06 [Messaging] debug Trying versions amqp0-10, amqp1.0
2017-03-29 21:07:06 [Client] debug Starting connection, urls=[172.21.0.254]
2017-03-29 21:07:06 [Client] info Trying to connect to 172.21.0.254...
2017-03-29 21:07:06 [Client] debug Created IO thread: 0
2017-03-29 21:07:06 [Network] debug TCPConnector created for 0-10
2017-03-29 21:07:06 [Client] debug Set TCP_NODELAY
2017-03-29 21:07:06 [System] info Connecting: 172.21.0.254:5672
2017-03-29 21:07:06 [Client] debug RECV [[10.0.3.219:51830-172.21.0.254:5672]]:
INIT(0-10)
2017-03-29 21:07:06 [Network] trace RECV [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=0; {ConnectionStartBody:
server-properties={qpid.federation_tag:V2:36:str16(40671cbf-c4e3-4eab-a740-2f1ae110ca63)};
mechanisms=str16{V2:9:str16(ANONYMOUS), V2:5:str16(PLAIN)};
locales=str16{V2:5:str16(en_US)}; }]
2017-03-29 21:07:06 [Security] debug CyrusSasl::start(ANONYMOUS PLAIN)
2017-03-29 21:07:06 [Security] debug min_ssf: 0, max_ssf: 256
2017-03-29 21:07:06 [Security] debug CyrusSasl::start(ANONYMOUS PLAIN):
selected ANONYMOUS response: 'anonymous@S-001'
2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=0; {ConnectionStartOkBody:
client-properties={qpid.client_pid:F4:int32(2031),qpid.client_ppid:F4:int32(339),qpid.client_process:V2:9:str16(qpid-send),qpid.session_flow:F4:int32(1)};
mechanism=ANONYMOUS; response=xxxxxx; locale=en_US; }]
2017-03-29 21:07:06 [Network] trace RECV [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=0; {ConnectionTuneBody:
channel-max=32767; max-frame-size=65535; heartbeat-min=0;
heartbeat-max=120; }]
2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=0; {ConnectionTuneOkBody:
channel-max=32767; max-frame-size=65535; heartbeat=0; }]
2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=0; {ConnectionOpenBody:
virtual-host=; capabilities=void{}; insist=1; }]
2017-03-29 21:07:06 [Network] trace RECV [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=0; {ConnectionOpenOkBody:
known-hosts=str16{}; }]
2017-03-29 21:07:06 [Client] info Connection [10.0.3.219:51830-
172.21.0.254:5672] connected to tcp:172.21.0.254:5672
2017-03-29 21:07:06 [Client] debug Connection [10.0.3.219:51830-
172.21.0.254:5672] no security layer in place
2017-03-29 21:07:06 [Client] info Connected to 172.21.0.254
2017-03-29 21:07:06 [Client] debug Added known-hosts,
reconnect-urls=[172.21.0.254]
2017-03-29 21:07:06 [Client] debug Connection successful,
urls=[172.21.0.254]
2017-03-29 21:07:06 [Broker] debug SessionState::SessionState .: 0xcefe38
2017-03-29 21:07:06 [Client] debug Known-brokers for connection:
2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=1; {SessionAttachBody:
name=c7a09332-6d50-49db-b9e8-4ea9b90afbec; }]
2017-03-29 21:07:06 [Network] trace RECV [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=1; {SessionAttachedBody:
name=c7a09332-6d50-49db-b9e8-4ea9b90afbec; }]
2017-03-29 21:07:06 [Network] trace RECV [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=1; {SessionCommandPointBody:
command-id=0; command-offset=0; }]
2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=1; {SessionRequestTimeoutBody:
timeout=0; }]
2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=1; {SessionCommandPointBody:
command-id=0; command-offset=0; }]
2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=1; {ExecutionSyncBody: }]
2017-03-29 21:07:06 [Network] trace RECV [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=1; {SessionTimeoutBody:
timeout=0; }]
2017-03-29 21:07:06 [Network] trace RECV [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=1; {SessionCompletedBody:
commands={ [0,0] }; }]
2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=1; {ExchangeBoundBody:
exchange=amq.fanout; queue=amq.fanout; binding-key=; arguments={}; }]
2017-03-29 21:07:06 [Network] trace RECV [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=1; {ExecutionResultBody:
command-id=1; value=\x07\x02\x02\x00; }]
2017-03-29 21:07:06 [Client] debug treating target address as topic:
amq.fanout
2017-03-29 21:07:06 [Network] trace RECV [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=1; {SessionCompletedBody:
commands={ [0,1] }; }]
2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=1; {ExchangeDeclareBody:
exchange=amq.fanout; type=; alternate-exchange=; passive=1; arguments={}; }]
2017-03-29 21:07:06 [Network] trace RECV [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[BEbe; channel=1; {SessionCompletedBody:
commands={ [0,2] }; }]
2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[Bbe; channel=1; {MessageTransferBody:
destination=amq.fanout; accept-mode=1; acquire-mode=0; }]
2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[be; channel=1; header (66 bytes);
properties={{MessageProperties: content-length=500000;
content-type=text/plain; user-id=;
application-headers={sn:F4:uint32(1),ts:F8:int64(1490821626691555779)};
}{DeliveryProperties: routing-key=; }}]
2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[Eb; channel=1; content (65523 bytes)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...]
2017-03-29 21:07:06 [Network] trace SENT [[10.0.3.219:51830
-172.21.0.254:5672]]: Frame[E; channel=1; content (65523 bytes)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...]
Thanks for all the help,
Siva.
On Wed, Mar 29, 2017 at 3:58 PM, Gordon Sim [via Qpid] <
ml-node+s2158936n7661647h40@n2.nabble.com> wrote:
> On 29/03/17 20:34, sivasnp wrote:
> > Hi Gordon,
> > Thank you for the response.
> >
> > What broker are you sending to?
> > I am trying to sent to a remote broker (version 0.24,
> unfortunately,
> > I cannot update the version).
> > Have you tried with a larger frame size?
> > Yes, I have, the result is same.
>
> Does your qpid-cpp package include qpid-send? If so could you get a
> protocol trace for:
>
> qpid-send -b <hostname-of-broker> --address amq.fanout --content-size
> 500000 --log-enable trace+
>
> (You can use a different address if needed for any reason).
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> <http:///user/SendEmail.jtp?type=node&node=7661647&i=0>
> For additional commands, e-mail: [hidden email]
> <http:///user/SendEmail.jtp?type=node&node=7661647&i=1>
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://qpid.2158936.n2.nabble.com/qpid-cpp-1-35-Cannot-sent-
> large-message-320K-tp7661623p7661647.html
> To unsubscribe from qpid-cpp-1.35 - Cannot sent large message (320K), click
> here
> <http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7661623&code=c2l2YS5rdW1hci5zaXZhLnNhbmthcmFuQHJvY2t3ZWxsY29sbGlucy5jb218NzY2MTYyM3wxNjk5ODU5MTQ3>
> .
> NAML
> <http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://qpid.2158936.n2.nabble.com/qpid-cpp-1-35-Cannot-sent-large-message-320K-tp7661623p7661648.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
Re: qpid-cpp-1.35 - Cannot sent large message (320K)
Posted by Gordon Sim <gs...@redhat.com>.
On 29/03/17 20:34, sivasnp wrote:
> Hi Gordon,
> Thank you for the response.
>
> What broker are you sending to?
> I am trying to sent to a remote broker (version 0.24, unfortunately,
> I cannot update the version).
> Have you tried with a larger frame size?
> Yes, I have, the result is same.
Does your qpid-cpp package include qpid-send? If so could you get a
protocol trace for:
qpid-send -b <hostname-of-broker> --address amq.fanout --content-size
500000 --log-enable trace+
(You can use a different address if needed for any reason).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpid-cpp-1.35 - Cannot sent large message (320K)
Posted by sivasnp <si...@rockwellcollins.com>.
Hi Gordon,
Thank you for the response.
What broker are you sending to?
I am trying to sent to a remote broker (version 0.24, unfortunately,
I cannot update the version).
Have you tried with a larger frame size?
Yes, I have, the result is same.
Thanks again for your help
Siva
On Wed, Mar 29, 2017 at 2:25 PM, Gordon Sim [via Qpid] <
ml-node+s2158936n7661639h92@n2.nabble.com> wrote:
> On 29/03/17 17:20, sivasnp wrote:
>
> > Hi,
> > qpid-client is unable to send a message of size 320K. But a small size
> > message (10K) is sent without any problem
> >
> > Following are the options, I set while connecting to the broker.
> >
> > options["reconnect"] = true;
> > options["max_frame_size"] = 1370;
> > options["bounds"] = 330000;
> >
> > Initially I did not have the bounds option set. Without bounds option
> set,
> > when I try to send this message, the send() function hangs and never
> > returns.
>
> What broker are you sending to? It seems to work for me (even for much
> larger messages) against qpidd.
>
> Have you tried with a larger frame size?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> <http:///user/SendEmail.jtp?type=node&node=7661639&i=0>
> For additional commands, e-mail: [hidden email]
> <http:///user/SendEmail.jtp?type=node&node=7661639&i=1>
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://qpid.2158936.n2.nabble.com/qpid-cpp-1-35-Cannot-sent-
> large-message-320K-tp7661623p7661639.html
> To unsubscribe from qpid-cpp-1.35 - Cannot sent large message (320K), click
> here
> <http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7661623&code=c2l2YS5rdW1hci5zaXZhLnNhbmthcmFuQHJvY2t3ZWxsY29sbGlucy5jb218NzY2MTYyM3wxNjk5ODU5MTQ3>
> .
> NAML
> <http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://qpid.2158936.n2.nabble.com/qpid-cpp-1-35-Cannot-sent-large-message-320K-tp7661623p7661641.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
Re: qpid-cpp-1.35 - Cannot sent large message (320K)
Posted by sivasnp <si...@rockwellcollins.com>.
I don't know, if it helps... The client application is running inside
lxc-container (ubuntu xenial 16.04) and the broker runs in CentOS.
Thanks,
Siva.
On Wed, Mar 29, 2017 at 2:25 PM, Gordon Sim [via Qpid] <
ml-node+s2158936n7661639h92@n2.nabble.com> wrote:
> On 29/03/17 17:20, sivasnp wrote:
>
> > Hi,
> > qpid-client is unable to send a message of size 320K. But a small size
> > message (10K) is sent without any problem
> >
> > Following are the options, I set while connecting to the broker.
> >
> > options["reconnect"] = true;
> > options["max_frame_size"] = 1370;
> > options["bounds"] = 330000;
> >
> > Initially I did not have the bounds option set. Without bounds option
> set,
> > when I try to send this message, the send() function hangs and never
> > returns.
>
> What broker are you sending to? It seems to work for me (even for much
> larger messages) against qpidd.
>
> Have you tried with a larger frame size?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> <http:///user/SendEmail.jtp?type=node&node=7661639&i=0>
> For additional commands, e-mail: [hidden email]
> <http:///user/SendEmail.jtp?type=node&node=7661639&i=1>
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://qpid.2158936.n2.nabble.com/qpid-cpp-1-35-Cannot-sent-
> large-message-320K-tp7661623p7661639.html
> To unsubscribe from qpid-cpp-1.35 - Cannot sent large message (320K), click
> here
> <http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7661623&code=c2l2YS5rdW1hci5zaXZhLnNhbmthcmFuQHJvY2t3ZWxsY29sbGlucy5jb218NzY2MTYyM3wxNjk5ODU5MTQ3>
> .
> NAML
> <http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://qpid.2158936.n2.nabble.com/qpid-cpp-1-35-Cannot-sent-large-message-320K-tp7661623p7661642.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
Re: qpid-cpp-1.35 - Cannot sent large message (320K)
Posted by Gordon Sim <gs...@redhat.com>.
On 29/03/17 17:20, sivasnp wrote:
> Hi,
> qpid-client is unable to send a message of size 320K. But a small size
> message (10K) is sent without any problem
>
> Following are the options, I set while connecting to the broker.
>
> options["reconnect"] = true;
> options["max_frame_size"] = 1370;
> options["bounds"] = 330000;
>
> Initially I did not have the bounds option set. Without bounds option set,
> when I try to send this message, the send() function hangs and never
> returns.
What broker are you sending to? It seems to work for me (even for much
larger messages) against qpidd.
Have you tried with a larger frame size?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org