eceived the correct results.
>
>JZMQ - 018a38d414af4e689c93e29d4d7a59a1f51fe84e
>libzmq 3.2.2
>
>
>On Mon, May 20, 2013 at 1:45 AM, Mark Sutheran wrote:
>> Hi Pieter,
>>
>> Thanks for the quick response - test case below.
>>
>> Tested it using ipc and tcp transports - no difference
r implements Runnable {
@Override
public void run() {
System.out.println("SubscriptionDataHandler thread starting");
while (true) {
final byte[] rec = subscriber.recv(0);
System.out.println("...received data:\t" + Arrays.toString(rec));
}
}
}
}
Fr
Hi,
I appear to have a issue with PUB/SUB apparently 'dropping' the first byte.
Setup:
* Basic PUB/SUB running on same machine over TCP/localhost.
* Message has first 4 bytes as subscription id, rest payload
Problem:
* On dev box runs fine
* On prod box the subscriber sees no messages
*
Ok, apols - looks like it's my bad!Rebuilt all the libs on the client box (A) to the latest and greatest and the problem went away. So I guess this was a backwards-only compatibility issue between different versions (fits the pattern)Cheers,MarkFrom: Mark Sutheran To: ZeroMQ develo
nnect to and receive data from any valid interface (wlan0, localhost, eth0) when the PUB binds to *.Cheers,MarkFrom: Joshua Foster To: Mark Sutheran ; ZeroMQ development list Sent: Saturday, 7 July 2012, 22:14 Subject:
Re: [zeromq-dev] Asymmetrical PUB-SUB problem
Try binding to * o
I'm having a strange asymmetrical problem with tcp PUB/SUB between two boxes -
it appears to fail one way.
Details:
* zeromq version: 3.2, using the Java wrapper.
* Scenario has two machines A (Ubuntu, x64) and B (Angstrom, arm8)
* Both connected directly via wireless interface (B is acting as
