Hi Team,
We found that to install zero MQ on linux GCC compiler is must but, in our
production environment we cannot install GCC due to some reason.
Will zero MQ work if we install it in development machine and copy necessary
folders to production?
Thanks
Santosh
Hi,
I have pattern as below and there are multiple REP. How can I send a msg to a
specific REP? And is there any work to send a msg to all REP
which looks like broad?
REQ ---ROUTERDEALERREP
Regards,
Kira___
zeromq-dev mailing list
On 08/01/13 23:25, Ian Barber wrote:
What is the actual address you're passing which triggers the assert?
This is the pure string: epgm://192.168.2.113;239.192.1.1:5678\\n
But it must be something else because that's exactly what I was passing
when the subscriber was being created in the main
On 8 January 2013 16:51, Claudio Carbone erup...@libero.it wrote:
I see ZMQ examples were addresses such as
ipc://home/address
are used, but in my case they don't.
I can use addresses as
ipc://home
but no matter what I add after that, it stops working.
What does this depend on?
This
On 9 January 2013 06:30, Gadkari, Santosh santosh.gadk...@citi.com wrote:
Hi Team,
We found that to install zero MQ on linux GCC compiler is must but, in our
production environment we cannot install GCC due to some reason.
Will zero MQ work if we install it in development machine and copy
On Wed, Jan 9, 2013 at 7:30 AM, Gadkari, Santosh
santosh.gadk...@citi.com wrote:
Hi Team,
We found that to install zero MQ on linux GCC compiler is must but, in our
production environment we cannot install GCC due to some reason.
Will zero MQ work if we install it in development machine and
On 09/01/13 12:14, Ben Gray wrote:
This won't have any effect on the epgm problems you talk about later
but the ipc examples use triple / not double, so ipc:///home/address,
for it to be valid. Which is probably why it stopped working.
As I said in the first email in this thread, I wrote a
To build 0MQ you need gcc, make, gcc-c++, libstdc++-devel on a RHEL system.
However, once you've built the package it can be installed without gcc. If you
are on RHEL then simply build an RPM with the latest spec file and you should
be just fine.
Cheers,
--
Justin Cook
On Wednesday, 9
As I said in the first email in this thread, I wrote a simple program to
test just that.
The only addresses the work are of the type
ipc://whatever
Addresses as the following
ipc:///whatever
ipc:///whatever/whatever
don't work.
And in fact I don't know why that is.
Something strange
On 09/01/13 12:32, Ben Gray wrote:
Something strange going on there then, which version of zmq are you using?
I was testing, in response to your first post, with the
test_delay_connection.cpp code from the 3.2.2 build and had
ipc://whatever
ipc:///whatever
ipc:///whatever/whatever
On 9 January 2013 11:40, Claudio Carbone erup...@libero.it wrote:
On 09/01/13 12:32, Ben Gray wrote:
I'm using 3.2.2 and the only address that works for me is the first.
Would you mind telling me how can I conduct the same test you did?
I don't have any test_delay_connection anywhere, not even
On 09/01/13 12:52, Ben Gray wrote:
On 9 January 2013 11:40, Claudio Carbone erup...@libero.it wrote:
On 09/01/13 12:32, Ben Gray wrote:
I'm using 3.2.2 and the only address that works for me is the first.
Would you mind telling me how can I conduct the same test you did?
I don't have any
In an ipc address the ipc:// defines the address type,
and the remainder defines the path to the socket. So you are defining
a file system path on your system.
ipc://test
would be test in the current working directory, all processes need to
run in the same directory.
ipc:///test
would be
There is a gotcha with ipc endpoints on Unixes.
ipc_endpoint = ipc://*address*
*address* is actually a file path where zeromq will create the file
representing your ipc communication channel. Consequently, *address* should
point to a file where you have read/write access.
ipc://whatever is
Ben which part did you modify to test the ipc address?
There are a lot of sockets and I'm unsure which ones are control sockets
and which one are transport sockets.
lines 49, 74 and 112 are the ones I used, these are for the client -
server link up.
Thank you to both Stephen and Michael (don't have the umlaut on my
keyboard).
It's a lot more clear now.
Claudio
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
I've been having this problem the past couple of days: whenever I try to
debug a program of mine I get an assert fail on a socket address.
There are a few curious facts about this problem:
-the program works perfectly when run normally
-the problem appears if the very same lines are in a child
On 9 January 2013 08:44, Claudio Carbone erup...@libero.it wrote:
ss epgm:// _local_ip_address ; MULTICAST_ADDRESS
: MULTICAST_PORT std::endl;
Why the newline at the end? It makes the declaration invalid.
--
Steve-o
___
zeromq-dev
I have been adding more event monitoring into a fork of 3.2.2 for
auditing at where I work and so far I've been unable to find how the
socket::monitor_event calls are thread safe.
As far as I can tell they are called via the socket::event_* functions
from a number of different io_objects which
On 09/01/13 15:15, Steven McCoy wrote:
On 9 January 2013 08:44, Claudio Carbone erup...@libero.it
mailto:erup...@libero.it wrote:
ss epgm:// _local_ip_address ;
MULTICAST_ADDRESS : MULTICAST_PORT std::endl;
Why the newline at the end? It makes the declaration invalid.
Hi Santosh,
Do you mean this? http://www.zeromq.org/community (go the
Distributions Builds :-)
On Wed, Jan 9, 2013 at 7:26 PM, Justin Cook jhc...@gmail.com wrote:
To build 0MQ you need gcc, make, gcc-c++, libstdc++-devel on a RHEL system.
However, once you've built the package it can be
I traced my program through all the function
zmq::socket_base_t::connect
and it goes through it flawlessly until line 556
add_endpoint (addr_, (own_t *) session);
which translates to
launch_child (endpoint_);
endpoints.insert (endpoints_t::value_type (std::string (addr_),
endpoint_));
On 09/01/13 17:25, Claudio Carbone wrote:
I traced my program through all the function
zmq::socket_base_t::connect
and it goes through it flawlessly until line 556
add_endpoint (addr_, (own_t *) session);
which translates to
launch_child (endpoint_);
endpoints.insert
Here is what happens
int rc = pgm_receiver-init (udp_encapsulation,
addr-address.c_str ());
errno_assert (rc == 0);
udp_encapsulation is true
addr-address is 192.168.2.113;239.192.1.1:5678
This is all exactly the same if the socket isn't created in a child
thread but
This seems to be a semi-reproducible case (randomness due to scheduler
and ordering of events):
https://gist.github.com/4496344
We start 3 threads here:
(1) Low priority -- allocate messages in a loop, send messages in another loop
(2) Medium priority -- dumb primality test (just burns CPU)
(3)
I am seeing an assertion failure when shutting down my application:
Assertion failed: fd_table [handle_].valid (devpoll.cpp:91)
The frequency of the assertion is about once every few hundred to few thousand
executions (so it appears sometimes in our automated testing).
I have created a minimal
Although I don't like shipping Visual C++ redistributable, it seems
inevitable.
On Wed, Jan 9, 2013 at 10:49 AM, Steven McCoy steven.mc...@miru.hk wrote:
On 8 January 2013 20:30, crocket crockabisc...@gmail.com wrote:
It seems that v90, v100, and v110 mean the versions of Visual C++ Runtime.
https://github.com/zeromq/filemq/pull/17
Ditto, as the subject states.
--d
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
You can probably make a zeromq dll with the CRT library statically linked.
But if you need MSVCRT.DLL (system one) compiled zmq.dll, you can grab
form here:
https://github.com/malkia/ufo/tree/master/bin/Windows
check the x86 and x64 folders.
you would need zmq.dll and pgm.dll
On 1/8/2013 4:11
29 matches
Mail list logo
