On 07/01/2015 03:27 PM, Gordon Sim wrote:
On 06/30/2015 10:17 AM, Michael Ivanov wrote:
Ok it crashed again and here are the backtrace and protocol trace:
The error occurs when draining events on the collector as part of
freeing it. The connection has already been 'freed' by the application,
On 06/30/2015 10:17 AM, Michael Ivanov wrote:
Ok it crashed again and here are the backtrace and protocol trace:
The error occurs when draining events on the collector as part of
freeing it. The connection has already been 'freed' by the application,
but is referenced by an event in the colle
Ok it crashed again and here are the backtrace and protocol trace:
Program received signal SIGSEGV, Segmentation fault.
0x0115bc00 in ?? ()
(gdb) bt
#0 0x0115bc00 in ?? ()
#1 0x7fb7c6afc74d in pn_connection_finalize (object=0xda2c90) at
/usr/src/debug/qpid-proton-0.9/proton-c
On 06/29/2015 05:09 PM, Michael Ivanov wrote:
I have built it myself but I packed them in rpm package. I have used rpm
spec file frrom epel as a template.
Are you able to reproduce that crash easily? If so would you mind
getting a protocol trace from the broker?
The error appears to be some
I have built it myself but I packed them in rpm package. I have used rpm
spec file frrom epel as a template.
29.06.2015 18:59, Gordon Sim пишет:
> On 06/29/2015 03:41 PM, Michael Ivanov wrote:
>> I have started qpidd under debugger and I got the following backtrace:
>>
>> #0 0x0030 in
On 06/29/2015 03:41 PM, Michael Ivanov wrote:
I have started qpidd under debugger and I got the following backtrace:
#0 0x0030 in ?? ()
#1 0x73a1a74d in pn_connection_finalize (object=0xb1d450) at
/usr/src/debug/qpid-proton-0.9/proton-c/src/engine/engine.c:467
#2 0x7ff
I have started qpidd under debugger and I got the following backtrace:
#0 0x0030 in ?? ()
#1 0x73a1a74d in pn_connection_finalize (object=0xb1d450) at
/usr/src/debug/qpid-proton-0.9/proton-c/src/engine/engine.c:467
#2 0x73a0f5c8 in pn_class_decref (clazz=0x73c434
On 06/29/2015 11:27 AM, Michael Ivanov wrote:
Hallo,
I am using qpidd 0.32 Sometimes during operation the following diagnostics
appears:
Detected two management objects with the same identifier:
0-40-1--128(org.apache.qpid.broker:incoming:92bd6cc8-400a-4a81-8770-85d038a3d179,sender-xxx)
That
Hallo,
I am using qpidd 0.32 Sometimes during operation the following diagnostics
appears:
Detected two management objects with the same identifier:
0-40-1--128(org.apache.qpid.broker:incoming:92bd6cc8-400a-4a81-8770-85d038a3d179,sender-xxx)
Is this a real problem or can these messages be ignor
