While going over the log thats what showed up (specific section)
2013-01-30 12:41:12 [Protocol] trace SENT [[::1]:5672-[::1]:53052]:
Frame[Ebe; channel=1; content (698 bytes)
\x00\x00\x02\xB6\x00\x00\x00\x01\xA8\x00\x00\x02\xAD\x00\x00\x00%\x06_bTime\x90\x00\x0812:41...]
2013-01-30 12:41:12 [Prot
I have also uploaded my logging file - you can download it from
http://www.filesend.net/download.php?f=12d98ace7fc607dde21e565c356b1735
Any idea on why we get this exception. I am using Qpid Broker 0.18 built
from C++
On Wed, Jan 30, 2013 at 1:35 PM, Jakub Scholz wrote:
> Hi,
>
> My colleagues
Hi,
My colleagues were seeing similar errors when using the MRG-M 2.1 broker:
2012-10-05 10:13:10 error Unexpected exception: Attempted count underflow
on dequeue(313): size: max=100, current=243; count: max=1000,
current=0; type=flow_to_disk (qpid/broker/QueuePolicy.cpp:50)
2012-09-27 19:33:
Hi Gordon , just emailed you the log file at g...@redhat.com
On Wed, Jan 30, 2013 at 12:18 PM, Gordon Sim wrote:
> On 01/30/2013 06:53 PM, Rajesh Khan wrote:
>
>> Hi I am getting this error :
>> framing-error: Attempted size underflow on dequeue(698): size:
>> max=104857600, current=0; count: un
On 01/30/2013 06:53 PM, Rajesh Khan wrote:
Hi I am getting this error :
framing-error: Attempted size underflow on dequeue(698): size:
max=104857600, current=0; count: unlimited; type=reject
(qpid\broker\QueuePolicy.cpp:55) . I do have a logging file however I cant
upload it at this mailing list
Hi I am getting this error :
framing-error: Attempted size underflow on dequeue(698): size:
max=104857600, current=0; count: unlimited; type=reject
(qpid\broker\QueuePolicy.cpp:55) . I do have a logging file however I cant
upload it at this mailing list its size is 902 KB . Any email addresses I
c
No need to apologise, it's all cool.
I think that there's a degree of serendipity in all this in that it
serves as a concrete example in the discussion on user/dev and the fact
that it's sometimes a grey area with some of us users doing crazy things :-)
I think the encoding discussion is a re
Hi Fraser,
sorry for later response, I was in a rush at work.
Yes my patch talks about internal variables "username" and "password".
Your suggestion makes sense - could you please attach it as a comment to the
JIRA?
Thanks,
Pavel
- Original Message -
> From: "Fraser Adams"
> To: user
On 01/29/2013 08:42 PM, Fraser Adams wrote:
I don't know about the
specification document per se, but that JavaDoc for ObjectMessage says:
"An |ObjectMessage| object is used to send a message that contains a
serializable object in the Java programming language ("Java object")".
Being pedantic :-
On 01/30/2013 10:47 AM, yonexw wrote:
try
{
Receiver rcver = session.createReceiver(addr);
..
}
catch (const qpid::messaging::NoMessageAvailable& ex)
{
// No message, ignore exception and keep working
print("Ignore no message available exception, and keep work
try
{
Receiver rcver = session.createReceiver(addr);
..
}
catch (const qpid::messaging::NoMessageAvailable& ex)
{
// No message, ignore exception and keep working
print("Ignore no message available exception, and keep working.");
}
>From our app log, the connect
On 01/30/2013 10:34 AM, yonexw wrote:
Thanks Gordon, I turn off the sending thread, it is still the same.
(Does the sending thread also create another receiver? There are two
concurrent receivers in the log you posted).
I catch the exception qpid::messaging::NoMessageAvailable and just igno
Thanks Gordon, I turn off the sending thread, it is still the same.
I catch the exception qpid::messaging::NoMessageAvailable and just ignore
it.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/connection-is-detached-after-receiver-is-created-tp7587655p7587666.html
Sent fro
On 01/30/2013 10:23 AM, yonexw wrote:
correct, I have two separated thread for sending and receiving.
Can not the session support multiple thread?
It can, but I suspect what might be happening here is that one thread is
triggering the close of the session. What happens for example if a
messag
correct, I have two separated thread for sending and receiving.
Can not the session support multiple thread?
--
View this message in context:
http://qpid.2158936.n2.nabble.com/connection-is-detached-after-receiver-is-created-tp7587655p7587664.html
Sent from the Apache Qpid users mailing list ar
On 01/30/2013 09:22 AM, yonexw wrote:
related my app code for reading broadcast as following:
try
{
Receiver rcver = session.createReceiver(addr);
while(!stopFlag)
{
Message msg = rcver .fetch(Duration::SECOND * 10);
//ProcessBroadcast(msg); message processing
from the bottom line logs, it seems session detached after sync. In what
scenario client will detach session after session sync?
--
View this message in context:
http://qpid.2158936.n2.nabble.com/connection-is-detached-after-receiver-is-created-tp7587655p7587662.html
Sent from the Apache Qpid u
related my app code for reading broadcast as following:
try
{
Receiver rcver = session.createReceiver(addr);
while(!stopFlag)
{
Message msg = rcver .fetch(Duration::SECOND * 10);
//ProcessBroadcast(msg); message processing
session.acknowledge();
}
}
catch() .
I am using qpid c++ client API to connect to broker with SSL connection.
but after I create the receiver I got session detached and connection
closed, can someone shed some light on this? Apid logs as following:
[Security] trace SENT [[33888 192.168.0.1:10170]]: Frame[BEbe; channel=1;
{SessionAtt
19 matches
Mail list logo
