[zeromq-dev] Broken pipe, WAS Java/Windows issues

Conrad Steenberg conrad.steenberg at gmail.com
Tue Sep 8 19:05:39 CEST 2009


Hi Pavol,

Sorry for the late reply: I don't see the "broken pipe" error anymore.

Thanks!
Conrad

On Thu, 2009-09-03 at 11:04 +0200, Pavol Malosek wrote:
> Hello,
> 
> We have found one minor bug in zmq_server which could cause problem you are
> describing (solved in commit 031d371)
> Please update your source code and give us some feedback.
> 
> malo
> 
> 
> ----- Original Message -----
> From: "Conrad Steenberg" <conrad.steenberg at gmail.com>
> To: "Robin Weisberg" <robin at scout-trading.com>
> Cc: "Pavol Malosek" <malosek at fastmq.com>; <zeromq-dev at lists.zeromq.org>
> Sent: Tuesday, August 25, 2009 10:16 PM
> Subject: Re: [zeromq-dev] Java/Windows issues
> 
> 
> > FWIW I'm running into the same problem...
> >
> > On Tue, 2009-08-25 at 16:04 -0400, Robin Weisberg wrote:
> > > So we tried pulling out from Git and we ran into some issues w/ this
> > > version and TCP (probably not TCP related though).
> > >
> > > First on Java/Windows we previously ran into an issue where when using
> > > one Zmq object soon as you started publishing, receiving stopped
> > > working. We solved this by separating out listening and sending into 2
> > > different Zmq objects.
> > > Secondly, this workaround doesn't appear to work in the new version.
> > > Using 2 different zmq objects causes a crash. The crash occurs in
> > > locator.cpp line 108.
> > >
> > > Also code that previously worked on Linux/C crashes now when binding
> > > to a remote exchange after binding a global queue (the bindings are
> > > using different dispatchers/locators because we had issues w/ sending
> > > and receiving using the same dispathers/locators). The crash was:
> > >
> > >   Broken pipe
> > > nbytes != -1 (tcp_socket.cpp:306)
> > > Aborted (core dumped)
> > >
> > > Changing the code to share locators across multiple dispatchers caused
> > > the code not to crash.
> > >
> > > How stable should we expect head to be at this point? Is there more
> > > than just 1.0.1 bug fixes going into it? Is there a way to get only
> > > bug fixes (a branch or similar). It really would be nice to get a
> > > 1.0.1 version w/ just bug fixes. At this point I'm going to go through
> > > the mail list archives and try applying some of the key patches to the
> > > 1.0.0 version to get something usable.
> > >
> > > Thanks,
> > > Robin
> 




More information about the zeromq-dev mailing list