Trevor Bernard

@sdoeringNew It could be a number of things but first, sockets aren't threadsafe and should be bound to the same thread unless you have a full memory barrier when switching...

@alecz Do you think you are having the same problem as this? http://stackoverflow.com/questions/17209790/zeromq-pull-push-client-crashes-after-upon-connection-of-31-server-on-windows/17222309#17222309

I would check czmq, it's likely this was based of something in there

jeromq is a mashup of both IMHO. Anything prefixed with a Z, the idea/interface most likely came from czmq

I would suggest asking the zeromq mailing list but I would specify more information about your environment like OS, compiler, autoconf version, etc. Best, Trev

This is a known issue. Under the covers in JeroMQ, IPC gets converted to TCP. This was a decision made way before Java supported UNIX Domain Sockets. This issue is...

Is this still an issue? I use ubuntu 12.04 LTS without problems. ``` bash cd /tmp git clone [email protected]:zeromq/jzmq.git ./autogen.sh ./configure --prefix=/tmp make ```

It hasn't been a problem so far but if we fix it, we could potentially break some peoples code. We'll definitely need to bump the major version next release

> I had an NPE with version 0.5.4 at the same line as in the OP, but with a different stack trace. It turned out that due to a race...

This PR added unix domain socket support: https://github.com/zeromq/jeromq/pull/998