What is the normal way of shutting down a reactor in proton-j? I'm trying to
track down a thread leak in a codebase that sets up a new reactor on its own
thread every time a new connection is opened. That part and the subsequent
message traffic all work fine. But when the connection is closed, t
The reason for the definition is that it works in tandem with the gcc
compiler directive "-fvisibility=hidden" to stop exporting symbols that are
not part of the actual API. This second piece of the puzzle is provided in
the CMakeLists.txt files.
Using empty macros as you suggest should "work", at
Hello Robbie,
You are completely right about the way we should proceed and I totally agree.
However, we cannot send into production libraries in snapshot mode because we
want to compile against stable versions(You cannot imagine how quite difficult
it is to compile on Solaris).
We are currently
Hi Adel,
The things I am thinking of that made me look to using 0.15.0 were
more on the proton-j side. I don't have much experience/knowledge on
the C/C++ bits so I'd have a hard time answering with specifics on
that front, thats actually part of what my original mail was about. I
should also note
Hello,
We are trying to compile Proton on Solaris. We have stumbled upon the usage of
macro (__attribute__) which is only available in GCC and not on SunStudio.
In proton-c/bindings/cpp/include/proton/internal/export.hpp:
# define PN_CPP_EXPORT __attribute ((visibility ("default")))
Checki
Hello Robbie,
We are currently trying to compile Proton 0.14.0 on Solaris using SunStudio
compiler. 12.1 We are finding many bugs which we would like to report to the
community in the form of patches.
However, we are not yet able to compile the code entirely.
So I was wondering if there are
