the commiter of the patch is my workmate, we found the bug, and he fixed it
finally~~
2013/1/11 肖康(KangXiao)
> 陈竞 gmail.com> writes:
>
> >
> >
> > thank you for reply, we dont run word count topology in our storm, we
> will
> try it later. and the phenomenon is that, at one moment, all the
陈竞 gmail.com> writes:
>
>
> thank you for reply, we dont run word count topology in our storm, we will
try it later. and the phenomenon is that, at one moment, all the workers in
the
topology will core, and we don't know why
> .
> and also that
> 4 0x2aaab36cf2ab in Java_org_zeromq_
thank you for reply, we dont run word count topology in our storm, we
will try it later. and the phenomenon is that, at one moment, all the
workers in the topology will core, and we don't know why
.
and also that
4 0x2aaab36cf2ab in Java_org_zeromq_ZMQ_00024Socket_send (env=0x162a,
obj=0x17
Ok,
The exception occurs when the pointer of c++ bound socket is null. If we use
ZMQ.Socket after ZMQ.Socket.close is called, this exception could occur.
I know how it the storm works. The storm doesn't do complex stuffs with the
zeromq. So I don't think it misuse the zeromq.
Does the word co
we use a distributed system called storm which use zeromq, and we use storm
run my job, but it always core, so we gdb the core, found it cores in jzmq,
so i cant give the code, i just wander if any one met the same problem, so
that we can locate the problem, it seems not to be zeromq bug according
Could you please show us the java code which you tested with ?
This might help to look into the problem.
Thanks
Min
On Nov 16, 2012, at 12:52 PM, 陈竞 wrote:
> hi, i use jzmq in my project, i use jzmq 2.10, zeromq 2.1.7, but i get a
> problem: i get assertion error in zeromq. i get the core
hi, i use jzmq in my project, i use jzmq 2.10, zeromq 2.1.7, but i get a
problem: i get assertion error in zeromq. i get the core dump, and the
backstrace blows:
#0 0x003eb9a30265 in raise () from /lib64/libc.so.6
#1 0x003eb9a31d10 in abort () from /lib64/libc.so.6
#2 0x003eb9a296e6 in
