Afternoon all, Following a few weeks of testing and some feedback from the community, we've decided to merge the field cache code into the next branch in advance of the 2.3.1 release. There are a few

[Note: This is a cross-post from the Library Manager Working Group - If you're not familiar with the goals of the working group or the library manager project, please refer to the links within the rel

Previously, sub messages were considered when calculating the correct number of fields. This patch ignores the sub messages and instead counts only the number of top level fields to conform with other

Added support for compiling and running on Mac OS X. Excludes support for setting the scheduler and malloc options which are put behind macros for Mac. Tested on * Mac OS X 10.9.2 x86_64 * Ubuntu 12.0

Mac OS X does not support the clock_gettime function that is used in a number of the performance testing applications, but does have equivalient fucntions. This change wraps the time functions from th

Fix for some error logging which is being truncated Signed-off-by: Phil Preston <philippreston@...> --- mama/c_cpp/src/c/bridge/qpid/queue.c | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 de

http://www.openmama.org/downloads has a link to the quick start guide - it is broken: http://wiki.openmama.org/Quick_start_guide should be http://wiki.openmama.org/index.php/Quick_start_guide

This is requested code hygiene improvements requested by Damian for re-submission from original commit. This would be covered under general regression testing. From 09adac845a2742c5571ccf1f304d26e5e4e

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Michael, Thanks for this bug report - as it appears to be an upstream issue, I'm putting it on the OpenMAMA mailing list for discussion Regards, Dani

Hello, Few weeks ago I found a crash (see below) happening for our Java Publisher - which we upgraded to use the latest version of OpenMAMA 2.3.0. We were using for the test the Qpid bridge for the Pu

TESTING – I have attached modified versions of mamapublisherc & secstatuslisten.cpp for testing of this issue. The publisher has been modified to now include commandline parameters for both the securi

Morning all, I'm sure many of you are aware, but a number of mailing lists have recently been impacted by problems as a result of Yahoo (and potentially others) enforcing stricter DMARC policies. The

Hello, I have an issue compiling the common, commoncpp, mamac, mamacpp. The issue is repeating in Visual Studio for all of them, so I'll use only the commonc issue. Basically compiling commonc project

TESTING - Attached test app will show memory leak on windows with old version and none in new version. Running mamalisten with stats enabled will show multiple queues with same name on old version. Af

TESTING - Using attached test application the previous verison will log errors, and now the new version will log at level finest. From cddfb49afd15897c529f7f882ae4feb196dd69c4 Mon Sep 17 00:00:00 2001

TESTING - To test this simply try taking a new build and in the <install>/examples/mama/c try setting a different compiler in your environment and then try recompiling something like mamalistenc. To u

TESTING – Test by putting activate call in the onError callback. A timeout event will cause an error in the activate. Putting deactivate / activate call in the onMsg will give also cause an error. Aft

Hi, I have an issue building the mamacpp project using Visual Studio 2010 and 2012. The configuration is in Win32 Debug and Release. In both cases I compile commonc, commoncpp, mamac and then mamacpp.

Debian/Ubuntu try to follow recent JVMs. OpenMAMA wiki suggests JDK 1.6 and above. The next stable releases of Debian and Ubuntu (end of 2014/early 2015) may have OpenJDK 1.8, the previous OpenMAMA re

SCons also doesn't seem to understand DESTDIR. prefix is only half the story. When building a package, the tools set DESTDIR to have the "install" file-set deployed to some temporary tree. E.g. with a