Date   

Re: QPID Proton bridge: multiple subscribers, one publisher

Frank Quinn <fquinn.ni@...>
 

Hi Nestor,

If you modify each new subscriber to use a different incoming URL and reply URL, you can actually do this today, though as you can imagine it becomes a bit of a brute to configure very quickly.

The better solution though is probably the currently experimental feature-qpid-broker branch that I'm hoping will make it into OpenMAMA 2.3.4. It allows for a much easier to manage pub / sub infrastructure where in terms of transport configuration, all you do is point it to the broker - there's an example mama.properties on that branch to give you an idea: http://git.openmama.org/?p=OpenMAMA.git;a=blob;f=mama/c_cpp/src/examples/mama.properties;h=86c7b1ce3933a10b0022b89837094bdb5904b974;hb=feature-qpid-broker

Cheers,
Frank


On Tue, 21 Jul 2015 16:23 Macrux <kmacrux@...> wrote:
Hi guys,

I'd like to know if there was or there will be some change to the Qpid Proton Bridge such that I can have a publish/subscribe connection in which only one advanced publisher can have multiple subscribers, because according to the wiki, "the current QPID Proton bridge is a point-to-point implementation" and I've had to run multiple publishers (always the same) each one with a different transport, and to subscribe each client with only one publisher.

Maybe, if someone knows some technique to achieve this behavior, it would be very helpful for me.

Thanks in advance.

Kind regards,


Nestor.
_______________________________________________
Openmama-dev mailing list
Openmama-dev@...
https://lists.openmama.org/mailman/listinfo/openmama-dev


QPID Proton bridge: multiple subscribers, one publisher

macrux
 

Hi guys,

I'd like to know if there was or there will be some change to the Qpid Proton Bridge such that I can have a publish/subscribe connection in which only one advanced publisher can have multiple subscribers, because according to the wiki, "the current QPID Proton bridge is a point-to-point implementation" and I've had to run multiple publishers (always the same) each one with a different transport, and to subscribe each client with only one publisher.

Maybe, if someone knows some technique to achieve this behavior, it would be very helpful for me.

Thanks in advance.

Kind regards,


Nestor.


[PATCH] AVIS: Made some basic changes to eliminate crashes on CI tests

Frank Quinn <fquinn.ni@...>
 

Pushed this change earlier on but sending around for transparency. Avis tests still fail but at least they finish running (and a lot of the failures are expected due to lack of support in the avis bridge / middleware for certain functionality).

This was mostly just NULL checking and changing an EXPECT to an
ASSERT in the unit tests inside msgvectortests.cpp.

Signed-off-by: Frank Quinn <fquinn.ni@...>
---
 mama/c_cpp/src/c/payload/avismsg/avispayload.c     | 79 ++++++++++++++--------
 .../src/gunittest/c/mamamsg/msgvectortests.cpp     |  2 +-
 2 files changed, 53 insertions(+), 28 deletions(-)

diff --git a/mama/c_cpp/src/c/payload/avismsg/avispayload.c b/mama/c_cpp/src/c/payload/avismsg/avispayload.c
index 5a92b43..6da49f5 100644
--- a/mama/c_cpp/src/c/payload/avismsg/avispayload.c
+++ b/mama/c_cpp/src/c/payload/avismsg/avispayload.c
@@ -102,7 +102,7 @@ avismsgPayload_createImpl (mamaPayloadBridge* result, char* identifier)
     mamaPayloadBridgeImpl*       impl    = NULL;
     mama_status             resultStatus = MAMA_STATUS_OK;
 
-    CHECK_NULL (result);
+    CHECK_NULL(result);
 
     impl = (mamaPayloadBridgeImpl*)calloc (1, sizeof (mamaPayloadBridgeImpl));
     if (!impl)
@@ -164,9 +164,9 @@ avismsgPayload_createForTemplate (msgPayload*         msg,
 mama_status
 avismsgPayload_createFromByteBuffer(msgPayload* msg, mamaPayloadBridge bridge, const void* buffer, mama_size_t bufferLength)
 {
-    CHECK_NULL (msg);
-    CHECK_NULL (bridge);
-    CHECK_NULL (buffer);
+    CHECK_NULL(msg);
+    CHECK_NULL(bridge);
+    CHECK_NULL(buffer);
    
     avisPayloadImpl* newPayload = (avisPayloadImpl*)calloc (1, sizeof(avisPayloadImpl));
 
@@ -217,7 +217,7 @@ avismsgPayload_setParent (msgPayload          msg,
                        const mamaMsg       parent)
 {
     avisPayloadImpl* impl = (avisPayloadImpl*) msg;
-    CHECK_NULL (impl);
+    CHECK_NULL(impl);
 
     impl->mParent = parent;
    
@@ -250,7 +250,7 @@ avismsgPayload_unSerialize (const msgPayload    msg,
     uint8_t *    buffPos = (void*)buffer;
 
     CHECK_PAYLOAD (msg);
-    CHECK_NULL (buffer);
+    CHECK_NULL(buffer);
 
     if (!impl->mAvisMsg)
         impl->mAvisMsg = attributes_create();
@@ -326,8 +326,8 @@ avismsgPayload_serialize     (const msgPayload    msg,
     avisFieldPayload*    currField    = NULL;
 
     CHECK_PAYLOAD (msg);
-    CHECK_NULL (buffer);
-    CHECK_NULL (bufferLength);
+    CHECK_NULL(buffer);
+    CHECK_NULL(bufferLength);
 
     if (!impl->mIterator)
     {
@@ -445,8 +445,8 @@ avismsgPayload_getByteBuffer     (const msgPayload    msg,
 {
     avisPayloadImpl* impl = (avisPayloadImpl*)msg;
     CHECK_PAYLOAD(msg);
-    CHECK_NULL (buffer);
-    CHECK_NULL (bufferLength);
+    CHECK_NULL(buffer);
+    CHECK_NULL(bufferLength);
 
     *buffer = impl->mAvisMsg;
 
@@ -659,7 +659,7 @@ avismsgPayload_getNativeMsg     (const msgPayload    msg,
                                void**              nativeMsg)
 {
     CHECK_PAYLOAD(msg);
-    CHECK_NULL (nativeMsg);
+    CHECK_NULL(nativeMsg);
     *nativeMsg = msg;
     return MAMA_STATUS_OK;
 }
@@ -832,7 +832,7 @@ avismsgPayload_addString         (msgPayload          msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
-    CHECK_NULL (value);
+    CHECK_NULL(value);
     return avisMsg_setString(avisPayload(msg), name, fid, value);
 }
 
@@ -845,7 +845,7 @@ avismsgPayload_addOpaque         (msgPayload          msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
-    CHECK_NULL (value);
+    CHECK_NULL(value);
     return avisMsg_setOpaque(avisPayload(msg), name, fid, value, size);
 }
 
@@ -1221,7 +1221,7 @@ avismsgPayload_updateString      (msgPayload          msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
-    CHECK_NULL (value);
+    CHECK_NULL(value);
     return avisMsg_setString(avisPayload(msg), name, fid, value);
 }
 
@@ -1234,7 +1234,7 @@ avismsgPayload_updateOpaque      (msgPayload          msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
-    CHECK_NULL (value);
+    CHECK_NULL(value);
     return avisMsg_setOpaque(avisPayload(msg), name, fid, value, size);
 }
 
@@ -1266,8 +1266,6 @@ avismsgPayload_updateSubMsg      (msgPayload          msg,
                                 mama_fid_t          fid,
                                 const msgPayload    value)
 {
-    CHECK_PAYLOAD(msg);
-    CHECK_NAME(name,fid);
     return MAMA_STATUS_NOT_IMPLEMENTED;
 }
 
@@ -1480,6 +1478,7 @@ avismsgPayload_getBool           (const msgPayload    msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
+    CHECK_NULL(mamaResult);
     return avisMsg_getBool(avisPayload(msg), name, fid, mamaResult);
 }
 
@@ -1491,6 +1490,7 @@ avismsgPayload_getChar           (const msgPayload    msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
+    CHECK_NULL(result);
     return avisMsg_getChar(avisPayload(msg), name, fid, result);
 }
 
@@ -1502,6 +1502,7 @@ avismsgPayload_getI8             (const msgPayload    msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
+    CHECK_NULL(result);
     return avisMsg_getI8(avisPayload(msg), name, fid, result);
 }
 
@@ -1513,6 +1514,7 @@ avismsgPayload_getU8             (const msgPayload    msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
+    CHECK_NULL(result);
     return avisMsg_getU8(avisPayload(msg), name, fid, result);
 }
 
@@ -1524,6 +1526,7 @@ avismsgPayload_getI16            (const msgPayload    msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
+    CHECK_NULL(result);
     return avisMsg_getI16(avisPayload(msg), name, fid, result);
 }
 
@@ -1535,6 +1538,7 @@ avismsgPayload_getU16            (const msgPayload    msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
+    CHECK_NULL(result);
     return avisMsg_getU16(avisPayload(msg), name, fid, result);
 }
 
@@ -1546,6 +1550,7 @@ avismsgPayload_getI32            (const msgPayload    msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
+    CHECK_NULL(result);
     return avisMsg_getI32(avisPayload(msg), name, fid, result);
 }
 
@@ -1557,6 +1562,7 @@ avismsgPayload_getU32            (const msgPayload    msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
+    CHECK_NULL(result);
     return avisMsg_getU32(avisPayload(msg), name, fid, result);
 }
 
@@ -1568,6 +1574,7 @@ avismsgPayload_getI64            (const msgPayload    msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
+    CHECK_NULL(mamaResult);
     return avisMsg_getI64(avisPayload(msg), name, fid, mamaResult);
 }
 
@@ -1579,6 +1586,7 @@ avismsgPayload_getU64            (const msgPayload    msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
+    CHECK_NULL(mamaResult);
     return avisMsg_getU64(avisPayload(msg), name, fid, mamaResult);
 }
 
@@ -1590,6 +1598,7 @@ avismsgPayload_getF32            (const msgPayload    msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
+    CHECK_NULL(result);
     return avisMsg_getF32(avisPayload(msg), name, fid, result);
 }
 
@@ -1601,6 +1610,7 @@ avismsgPayload_getF64            (const msgPayload    msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
+    CHECK_NULL(result);
     return avisMsg_getF64(avisPayload(msg), name, fid, result);
 }
 
@@ -1612,7 +1622,7 @@ avismsgPayload_getString         (const msgPayload    msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
-    CHECK_NULL (result);
+    CHECK_NULL(result);
     return avisMsg_getString(avisPayload(msg), name, fid, result);
 }
 
@@ -1625,7 +1635,7 @@ avismsgPayload_getOpaque         (const msgPayload    msg,
 {
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name,fid);
-    CHECK_NULL (result);
+    CHECK_NULL(result);
     return avisMsg_getOpaque(avisPayload(msg), name, fid, result, size);
 }
 
@@ -1641,7 +1651,7 @@ avismsgPayload_getField          (const msgPayload    msg,
     Value* pValue = NULL;
     CHECK_PAYLOAD(msg);
     CHECK_NAME(name, fid);
-    CHECK_NULL (result);
+    CHECK_NULL(result);
 
     if ( (!impl->mAvisField) && (avismsgFieldPayload_create((msgFieldPayload*) &impl->mAvisField) != MAMA_STATUS_OK) ) {
         return MAMA_STATUS_PLATFORM;
@@ -1910,7 +1920,7 @@ avismsgPayloadIter_create        (msgPayloadIter* iter,
     mama_status status = MAMA_STATUS_OK;
     avisIterator* impl = NULL;
     CHECK_PAYLOAD(msg);
-    CHECK_NULL (iter);
+    CHECK_NULL(iter);
 
     impl = calloc (1, sizeof (avisIterator));
     if (!impl) return (MAMA_STATUS_NOMEM);
@@ -2012,7 +2022,7 @@ avismsgPayloadIter_associate      (msgPayloadIter iter,
     avisIterator* impl = (avisIterator*) iter;
     CHECK_PAYLOAD(msg);
 
-    CHECK_NULL (impl);
+    CHECK_NULL(impl);
 
     attributes_iter_init(impl->mMsgIterator, avisPayload(msg));
     impl->mAvisMsg = avisPayload(msg);
@@ -2023,7 +2033,7 @@ mama_status
 avismsgPayloadIter_destroy       (msgPayloadIter iter)
 {
     avisIterator* impl = (avisIterator*) iter;
-    CHECK_NULL (impl);
+    CHECK_NULL(impl);
 
     if (impl->mMsgIterator)
        attributes_iter_destroy(impl->mMsgIterator);
@@ -2068,6 +2078,7 @@ avismsgFieldPayload_getName      (const msgFieldPayload   field,
                                 const char**            result)
 {
     uint16_t fid =0;
+    CHECK_NULL(result);
     CHECK_FIELD(field);
 
     fid = atoi(avisField(field)->mName);
@@ -2113,6 +2124,7 @@ avismsgFieldPayload_getFid       (const msgFieldPayload   field,
 {
     uint16_t fid =0;
     CHECK_FIELD(field);
+    CHECK_NULL(result);
 
     fid = atoi(avisField(field)->mName);
     if (fid==0)
@@ -2170,6 +2182,7 @@ mama_status
 avismsgFieldPayload_getType      (msgFieldPayload         field,
                                 mamaFieldType*          result)
 {
+    CHECK_NULL(result);
     CHECK_FIELD(field);
     if (avisField(field)->mValue == 0)
         return MAMA_STATUS_INVALID_ARG;
@@ -2331,7 +2344,7 @@ avismsgFieldPayload_updateString  (msgFieldPayload         field,
 {
     CHECK_FIELD(field);
     CHECK_PAYLOAD(msg);
-    CHECK_NULL (value);
+    CHECK_NULL(value);
     return avisMsg_setString(avisPayload(msg), avisField(field)->mName, 0, value);
 }
 
@@ -2343,6 +2356,7 @@ avismsgFieldPayload_getBool      (const msgFieldPayload   field,
                                 mama_bool_t*            result)
 {
     CHECK_FIELD(field);
+    CHECK_NULL(result);
     return avisValue_getBool(avisField(field)->mValue, result);
 }
 
@@ -2351,6 +2365,7 @@ avismsgFieldPayload_getChar      (const msgFieldPayload   field,
                                 char*                   result)
 {
     CHECK_FIELD(field);
+    CHECK_NULL(result);
     return avisValue_getChar(avisField(field)->mValue, result);
 }
 
@@ -2359,6 +2374,7 @@ avismsgFieldPayload_getI8        (const msgFieldPayload   field,
                                 mama_i8_t*              result)
 {
     CHECK_FIELD(field);
+    CHECK_NULL(result);
     return avisValue_getI8(avisField(field)->mValue, result);
 }
 
@@ -2367,6 +2383,7 @@ avismsgFieldPayload_getU8        (const msgFieldPayload   field,
                                 mama_u8_t*              result)
 {
     CHECK_FIELD(field);
+    CHECK_NULL(result);
     return avisValue_getU8(avisField(field)->mValue, result);
 }
 
@@ -2375,6 +2392,7 @@ avismsgFieldPayload_getI16       (const msgFieldPayload   field,
                                 mama_i16_t*             result)
 {
     CHECK_FIELD(field);
+    CHECK_NULL(result);
     return avisValue_getI16(avisField(field)->mValue, result);
 }
 
@@ -2383,6 +2401,7 @@ avismsgFieldPayload_getU16       (const msgFieldPayload   field,
                                 mama_u16_t*             result)
 {
     CHECK_FIELD(field);
+    CHECK_NULL(result);
     return avisValue_getU16(avisField(field)->mValue, result);
 }
 
@@ -2391,6 +2410,7 @@ avismsgFieldPayload_getI32       (const msgFieldPayload   field,
                                 mama_i32_t*             result)
 {
     CHECK_FIELD(field);
+    CHECK_NULL(result);
     return avisValue_getI32(avisField(field)->mValue, result);
 }
 
@@ -2399,6 +2419,7 @@ avismsgFieldPayload_getU32       (const msgFieldPayload   field,
                                 mama_u32_t*             result)
 {
     CHECK_FIELD(field);
+    CHECK_NULL(result);
     return avisValue_getU32(avisField(field)->mValue, result);
 }
 
@@ -2407,6 +2428,7 @@ avismsgFieldPayload_getI64       (const msgFieldPayload   field,
                                 mama_i64_t*             result)
 {
     CHECK_FIELD(field);
+    CHECK_NULL(result);
     return avisValue_getI64(avisField(field)->mValue, result);
 }
 
@@ -2415,6 +2437,7 @@ avismsgFieldPayload_getU64       (const msgFieldPayload   field,
                                 mama_u64_t*             result)
 {
     CHECK_FIELD(field);
+    CHECK_NULL(result);
     return avisValue_getU64(avisField(field)->mValue, result);
 }
 
@@ -2423,6 +2446,7 @@ avismsgFieldPayload_getF32       (const msgFieldPayload   field,
                                 mama_f32_t*             result)
 {
     CHECK_FIELD(field);
+    CHECK_NULL(result);
     return avisValue_getF32(avisField(field)->mValue, result);
 }
 
@@ -2431,6 +2455,7 @@ avismsgFieldPayload_getF64       (const msgFieldPayload   field,
                                 mama_f64_t*             result)
 {
     CHECK_FIELD(field);
+    CHECK_NULL(result);
     return avisValue_getF64(avisField(field)->mValue, result);
 }
 
@@ -2439,7 +2464,7 @@ avismsgFieldPayload_getString    (const msgFieldPayload   field,
                                 const char**            result)
 {
     CHECK_FIELD(field);
-    CHECK_NULL (result);
+    CHECK_NULL(result);
     return avisValue_getString(avisField(field)->mValue, result);
 }
 
@@ -2449,8 +2474,8 @@ avismsgFieldPayload_getOpaque    (const msgFieldPayload   field,
                                 mama_size_t*            size)
 {
     CHECK_FIELD(field);
-    CHECK_NULL (result);
-    CHECK_NULL (size);
+    CHECK_NULL(result);
+    CHECK_NULL(size);
     return avisValue_getOpaque(avisField(field)->mValue, result, size);
 }
 
diff --git a/mama/c_cpp/src/gunittest/c/mamamsg/msgvectortests.cpp b/mama/c_cpp/src/gunittest/c/mamamsg/msgvectortests.cpp
index b72fa68..c291e44 100644
--- a/mama/c_cpp/src/gunittest/c/mamamsg/msgvectortests.cpp
+++ b/mama/c_cpp/src/gunittest/c/mamamsg/msgvectortests.cpp
@@ -116,7 +116,7 @@ TEST_F(MsgVectorBoolTestsC, AddVectorBool)
                                      mIn,
                                      VECTOR_SIZE);
 
-    EXPECT_EQ(mStatus, MAMA_STATUS_OK);
+    ASSERT_EQ(mStatus, MAMA_STATUS_OK);
 
     mStatus = mamaMsg_getVectorBool (mMsg,
                                      NULL,
--
2.4.3


OpenMAMA 2.3.3 Released

Frank Quinn <fquinn.ni@...>
 

Hi Folks,

It is with great pleasure that we can announce the release of OpenMAMA 2.3.3. The latest release contains several minor bugfixes since 2.3.2 and the following new features:

* Support added for Qpid Proton > 0.8
* Deferred entitlements now supported to allow middleware bridges to manage entitlements
* Basic MAMA Plugin implementation added
* Fedora 21, 22 and CentOS 7 RPMs now supported

Note that due to deadlocking issues encountered with Qpid Proton, you are recommended to avoid 0.9.x releases of Qpid Proton and instead either stick to 0.8, or else try out their 0.10.x beta versions ahead of their official 0.10 release which contains a fix for the deadlock issue which we hit during testing. See https://issues.apache.org/jira/browse/PROTON-907 for more details.

We've also updated our continuous integration over at http://ci.openmama.org to help us support the multiple versions of qpid proton which people seem to be using at the moment (though we will need to start dropping support for some of those older versions soon).

Full details of the release including binary and package downloads can be found on the releases page of the website over at http://www.openmama.org/downloads/releases.

You can also as usual view everything included in this release over on the source control browser: http://git.openmama.org/?p=OpenMAMA.git;a=shortlog;h=refs/tags/OpenMAMA-2.3.3-release

Any problems with the release, please let us know through the usual channels - mailing list / IRC etc.

Cheers,
Frank


[PATCH 2/2] RPM: Added RPM builds for CentOS 7, FC21, FC22

Frank Quinn <fquinn.ni@...>
 

Also deprecated support for EOL distros FC19 and FC20.

Signed-off-by: Frank Quinn <fquinn.ni@...>
---
 release_scripts/openmama-rpm.sh | 15 ++++++++-------
 release_scripts/openmama.spec   |  4 ++--
 2 files changed, 10 insertions(+), 9 deletions(-)

diff --git a/release_scripts/openmama-rpm.sh b/release_scripts/openmama-rpm.sh
index 191678c..96054f8 100755
--- a/release_scripts/openmama-rpm.sh
+++ b/release_scripts/openmama-rpm.sh
@@ -260,8 +260,9 @@ if [ $MOCK_BUILD -eq 1 ] && [ $RETURN_CODE -eq 0 ]; then
     try cd ${BUILD_DIR}/SRPMS
     try /usr/bin/mock -r epel-6-i386 --define 'BUILD_VERSION '${VERSION} --define 'BUILD_NUMBER '${BUILD_NUMBER} openmama-${VERSION}-${BUILD_NUMBER}.*.src.rpm > ${BUILD_DIR}/mock-el6-i386.log 2>&1
     try /usr/bin/mock -r epel-6-x86_64 --define 'BUILD_VERSION '${VERSION} --define 'BUILD_NUMBER '${BUILD_NUMBER} openmama-${VERSION}-${BUILD_NUMBER}.*.src.rpm > ${BUILD_DIR}/mock-el6-x64.log 2>&1
-    try /usr/bin/mock -r fedora-19-x86_64 --define 'BUILD_VERSION '${VERSION} --define 'BUILD_NUMBER '${BUILD_NUMBER} openmama-${VERSION}-${BUILD_NUMBER}.*.src.rpm > ${BUILD_DIR}/mock-f19-x64.log 2>&1
-    try /usr/bin/mock -r fedora-20-x86_64 --define 'BUILD_VERSION '${VERSION} --define 'BUILD_NUMBER '${BUILD_NUMBER} openmama-${VERSION}-${BUILD_NUMBER}.*.src.rpm > ${BUILD_DIR}/mock-f20-x64.log 2>&1
+    try /usr/bin/mock -r epel-7-x86_64 --define 'BUILD_VERSION '${VERSION} --define 'BUILD_NUMBER '${BUILD_NUMBER} openmama-${VERSION}-${BUILD_NUMBER}.*.src.rpm > ${BUILD_DIR}/mock-el7-x64.log 2>&1
+    try /usr/bin/mock -r fedora-21-x86_64 --define 'BUILD_VERSION '${VERSION} --define 'BUILD_NUMBER '${BUILD_NUMBER} openmama-${VERSION}-${BUILD_NUMBER}.*.src.rpm > ${BUILD_DIR}/mock-f21-x64.log 2>&1
+    try /usr/bin/mock -r fedora-22-x86_64 --define 'BUILD_VERSION '${VERSION} --define 'BUILD_NUMBER '${BUILD_NUMBER} openmama-${VERSION}-${BUILD_NUMBER}.*.src.rpm > ${BUILD_DIR}/mock-f22-x64.log 2>&1
     next
     RETURN_CODE=$?
 fi
@@ -281,13 +282,13 @@ if [ $PACKAGE_RELEASE -eq 1 ] && [ $RETURN_CODE -eq 0 ]; then
     # Copy in the Source RPM
     try cp ${BUILD_DIR}/SRPMS/openmama-${VERSION}-${BUILD_NUMBER}.*.src.rpm ${RELEASE_DIR}
 
-    # These paths are hard coded, since they should always remain there. We may
-    # want to update them periodically, especially with EL7, and newer Fedora
-    # versions.
+    # These paths are hard coded, since they should always remain there. We need
+    # to update these periodically.
     try cp /var/lib/mock/epel-6-i386/result/openmama-${VERSION}-${BUILD_NUMBER}.el6.i686.rpm ${RELEASE_DIR}
     try cp /var/lib/mock/epel-6-x86_64/result/openmama-${VERSION}-${BUILD_NUMBER}.el6.x86_64.rpm ${RELEASE_DIR}
-    try cp /var/lib/mock/fedora-19-x86_64/result/openmama-${VERSION}-${BUILD_NUMBER}.fc19.x86_64.rpm ${RELEASE_DIR}
-    try cp /var/lib/mock/fedora-20-x86_64/result/openmama-${VERSION}-${BUILD_NUMBER}.fc20.x86_64.rpm ${RELEASE_DIR}
+    try cp /var/lib/mock/epel-7-x86_64/result/openmama-${VERSION}-${BUILD_NUMBER}.el7.*.x86_64.rpm ${RELEASE_DIR}
+    try cp /var/lib/mock/fedora-21-x86_64/result/openmama-${VERSION}-${BUILD_NUMBER}.fc21.x86_64.rpm ${RELEASE_DIR}
+    try cp /var/lib/mock/fedora-22-x86_64/result/openmama-${VERSION}-${BUILD_NUMBER}.fc22.x86_64.rpm ${RELEASE_DIR}
 
     # Build and tar the binary release
     if [ -d ${BUILD_DIR}/binary ]; then
diff --git a/release_scripts/openmama.spec b/release_scripts/openmama.spec
index d5ec35d..40ae53b 100644
--- a/release_scripts/openmama.spec
+++ b/release_scripts/openmama.spec
@@ -12,8 +12,8 @@ BuildRequires: libtool autoconf automake ant libuuid-devel flex doxygen qpid-pro
 Requires: libuuid qpid-proton-c libevent ncurses
 
 %if 0%{?fedora}
-BuildRequires: java-1.7.0-openjdk-devel
-Requires: java-1.7.0-openjdk
+BuildRequires: java-1.8.0-openjdk-devel
+Requires: java-1.8.0-openjdk
 %define java_home /usr/lib/jvm/java/
 %endif
 
--
2.4.3


[PATCH 1/2] SCONS: Fixed issue with builds not working on 32 bit Linux

Frank Quinn <fquinn.ni@...>
 

Added i686 and a few other similar ancestors for good measure.

Signed-off-by: Frank Quinn <fquinn.ni@...>
---
 site_scons/community/command_line.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site_scons/community/command_line.py b/site_scons/community/command_line.py
index 4bbacc5..1f7f278 100644
--- a/site_scons/community/command_line.py
+++ b/site_scons/community/command_line.py
@@ -65,7 +65,7 @@ def get_command_line_opts( host, products, VERSIONS ):
                          #mamda all is a windows only build
                          allowed_values=( [ x for x in products if x != "mamdaall" ] )),
             EnumVariable('target_arch', 'Specifies if the build should target 32 or 64 bit architectures.',
-                          host['arch'], allowed_values=['x86', 'x86_64']),
+                          host['arch'], allowed_values=['i386', 'i586', 'i686', 'x86', 'x86_64']),
             EnumVariable( 'compiler', 'Compiler to use for building OpenMAMA',
                          'default', allowed_values=('default', 'gcc', 'clang', 'clang-analyzer')),
         )
--
2.4.3


[PATCH 2/2] QPID: Fixed build error introduced in proton 0.9

fquinn.ni@...
 

From: Frank Quinn <fquinn.ni@gmail.com>

---
mama/c_cpp/src/c/bridge/qpid/qpiddefs.h | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/mama/c_cpp/src/c/bridge/qpid/qpiddefs.h b/mama/c_cpp/src/c/bridge/qpid/qpiddefs.h
index cd52e96..79ddbc4 100644
--- a/mama/c_cpp/src/c/bridge/qpid/qpiddefs.h
+++ b/mama/c_cpp/src/c/bridge/qpid/qpiddefs.h
@@ -32,7 +32,6 @@
#include <list.h>

/* Qpid include files */
-#include <proton/driver.h>
#include <proton/message.h>
#include <proton/messenger.h>

@@ -87,6 +86,10 @@ typedef enum qpidMsgType_
#if (PN_VERSION_MAJOR == 0 && PN_VERSION_MINOR <= 7)
#include <proton/util.h>
#endif
+#if (PN_VERSION_MAJOR == 0 && PN_VERSION_MINOR <= 8)
+/* The proton header driver.h was removed in version 0.9 */
+#include <proton/driver.h>
+#endif

/* Place other version specific macros here */

--
1.7.1


[PATCH 1/2] QPID: Fixed warnings introduced since proton 0.8

fquinn.ni@...
 

From: Frank Quinn <fquinn.ni@gmail.com>

---
mama/c_cpp/src/c/bridge/qpid/transport.c | 2 +-
mama/c_cpp/src/c/payload/qpidmsg/qpidcommon.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/mama/c_cpp/src/c/bridge/qpid/transport.c b/mama/c_cpp/src/c/bridge/qpid/transport.c
index 8ca9550..aa84fd7 100644
--- a/mama/c_cpp/src/c/bridge/qpid/transport.c
+++ b/mama/c_cpp/src/c/bridge/qpid/transport.c
@@ -1433,7 +1433,7 @@ void* qpidBridgeMamaTransportImpl_dispatchThread (void* closure)
case QPID_MSG_SUB_REQUEST:
{
pn_data_t* data = pn_message_body (msgNode->mMsg);
- char* topic = NULL;
+ const char* topic = NULL;
const char* replyTo = NULL;

/* Move to the content which will contain the topic */
diff --git a/mama/c_cpp/src/c/payload/qpidmsg/qpidcommon.c b/mama/c_cpp/src/c/payload/qpidmsg/qpidcommon.c
index 8e91c2d..78d5123 100644
--- a/mama/c_cpp/src/c/payload/qpidmsg/qpidcommon.c
+++ b/mama/c_cpp/src/c/payload/qpidmsg/qpidcommon.c
@@ -210,7 +210,7 @@ qpidmsgPayloadInternal_elementToString (pn_data_t* payload,
case PN_BINARY:
{
mama_size_t i = 0;
- char* bytePos = NULL;
+ const char* bytePos = NULL;
pn_bytes_t bytes;

bytes = atom.u.as_bytes;
--
1.7.1


Re: Java MamaPublisher destroy

Adrienne Ambrose <a.ambrose@...>
 

Hi Reed,

 

I have raised Bugzilla Bug-203 for tracking of this issue, if you wish to submit a patch for this.

 

Thanks,

Adrienne

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Stuart Beattie
Sent: 10 July 2015 16:33
To: Alpert, Reed; openmama-dev@...
Subject: Re: [Openmama-dev] Java MamaPublisher destroy

 

We are now tracking this internally in order to investigate further and schedule it for a future release.  If you like, you can raise a Bugzilla ticket to track it there too.

 

Thanks

Stuart

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Stuart Beattie
Sent: 10 July 2015 16:24
To: Alpert, Reed; openmama-dev@...
Subject: Re: [Openmama-dev] Java MamaPublisher destroy

 

Hi Reed,

 

No, the missing destroy call looks like a bug.

 

Thanks

Stuart

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Alpert, Reed
Sent: 10 July 2015 13:58
To:
openmama-dev@...
Subject: [Openmama-dev] Java MamaPublisher destroy

 

Hi,

 

For Java MamaPublisher I don’t see a destroy or finalize method, are the C resources being freed in another way I don’t see?

 

Thanks,

 

Reed.

 


Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198  | M: 917.414.4613 | reed.alpert@...

Alternate Contact:  CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...

 

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.


Re: Java MamaPublisher destroy

Stuart Beattie <s.beattie@...>
 

We are now tracking this internally in order to investigate further and schedule it for a future release.  If you like, you can raise a Bugzilla ticket to track it there too.

 

Thanks

Stuart

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Stuart Beattie
Sent: 10 July 2015 16:24
To: Alpert, Reed; openmama-dev@...
Subject: Re: [Openmama-dev] Java MamaPublisher destroy

 

Hi Reed,

 

No, the missing destroy call looks like a bug.

 

Thanks

Stuart

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Alpert, Reed
Sent: 10 July 2015 13:58
To:
openmama-dev@...
Subject: [Openmama-dev] Java MamaPublisher destroy

 

Hi,

 

For Java MamaPublisher I don’t see a destroy or finalize method, are the C resources being freed in another way I don’t see?

 

Thanks,

 

Reed.

 


Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198  | M: 917.414.4613 | reed.alpert@...

Alternate Contact:  CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...

 

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.


Re: Help with bookpublisher

Stuart Beattie <s.beattie@...>
 

Hi Nestor,

 

The key command line arguments for MamdaBookPublisherJava are:

 

-SP – the source name on which book data is published.

-s Symbol to publish (can be passed multiple times)

-p Participant ID (optional)

 

As well as standard options like –tport, -m etc.

 

Any market data subscriber example application, eg MamaListen, can be used to listen to the dummy orderbook data that MamdaBookPublisherJava publishes.

 

Example command line for MamdaBookPublisherJava:

 

java -cp com.wombat.mamda.examples.MamdaBookPublisher -SP STUARTB2 -s STUBOOK -m wmw -tport pub

 

Corresponding MamaListen command:

 

java com.wombat.mama.examples.MamaListen -S STUARTB2 -s STUBOOK -m wmw -tport sub

 

MamaListen output:

 

STUBOOK Type: BOOK_INITIAL Status: OK

   MdMsgType            | 1    | U8         | 16

    wNumLevels           | 651  | I16        | 0

    MamaSenderId         | 20   | U64        | 5841862551486352289

    MdSeqNum             | 10   | U32        | 1

    MdMsgStatus          | 2    | U8         | 0

TRANSPORT CONNECTED!

STUBOOK Type: BOOK_UPDATE Status: OK

   MdMsgType            | 1    | U8         | 17

    wPriceLevels         | 699  | VECTOR_MSG |

   {

      wPlPrice             | 653  | F64        | 100.0

       wPlSize              | 655  | U32        | 1000

       wPlSizeChange        | 656  | U32        | 1000

       wPlTime              | 658  | TIME       | 2015-07-10 15:49:27.208294

       wPlNumAttach         | 659  | U32        | 0

    }

   {

      wPlPrice             | 653  | F64        | 101.0

       wPlSize              | 655  | U32        | 2000

       wPlSizeChange        | 656  | U32        | 2000

       wPlTime              | 658  | TIME       | 2015-07-10 15:49:27.212162

       wPlNumAttach         | 659  | U32        | 0

    }

   wNumLevels           | 651  | U32        | 2

    MdMsgStatus          | 2    | U8         | 0

    MdSeqNum             | 10   | U32        | 2

    MamaSenderId         | 20   | U64        | 5841862551486352289

 

Note that for MamaBookPublisherJava to work, it will also need to subscribe to another source which is publishing a MAMA dictionary.

 

Thanks

Stuart

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Macrux
Sent: 02 July 2015 15:59
To: openmama-dev@...
Subject: [Openmama-dev] Help with bookpublisher

 

Hi there,

Could someone, please, give me a hand with the MamdaBookPublisher.java example, I haven't been able to run it, I mean, I don't know which are the arguments I've to pass. Thank you all.

kind regards,

Nestor


Re: Java MamaPublisher destroy

Stuart Beattie <s.beattie@...>
 

Hi Reed,

 

No, the missing destroy call looks like a bug.

 

Thanks

Stuart

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Alpert, Reed
Sent: 10 July 2015 13:58
To: openmama-dev@...
Subject: [Openmama-dev] Java MamaPublisher destroy

 

Hi,

 

For Java MamaPublisher I don’t see a destroy or finalize method, are the C resources being freed in another way I don’t see?

 

Thanks,

 

Reed.

 


Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198  | M: 917.414.4613 | reed.alpert@...

Alternate Contact:  CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...

 

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.


Java MamaPublisher destroy

Alpert, Reed <reed.alpert@...>
 

Hi,

 

For Java MamaPublisher I don’t see a destroy or finalize method, are the C resources being freed in another way I don’t see?

 

Thanks,

 

Reed.

 


Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198  | M: 917.414.4613 | reed.alpert@...

Alternate Contact:  CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...

 

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.


Re: OpenMAMA-2.3.3-rc1

Frank Quinn <fquinn.ni@...>
 

Looks like they fixed this issue today and the fix will be in Proton 0.10 which I expect will be out in a couple of weeks (they move pretty fast). I haven't tried the fix yet but assuming it works, we can then look towards completing testing for the open source messaging stack / OpenMAMA 2.3.3.

Cheers,
Frank


On Wed, 1 Jul 2015 15:30 Frank Quinn <f.quinn@...> wrote:

Just to add some context on the issue in question, it is pretty serious for Qpid Proton users as it effectively deadlocks OpenMAMA on RHEL (works fine on Fedora though). This has blocked testing as it means we can’t test the small changes that we needed to make to get it to compile in the first place. Proton 0.9.x is the default version that gets installed if you use EPEL repositories for RHEL 6 or CentOS 6.

 

We can recreate this in isolation with just the qpid proton provided test applications and we have reported this to the proton folks at the start of June and after chasing it up, it’s not yet resolved: http://qpid.2158936.n2.nabble.com/Strange-behaviour-for-pn-messenger-send-on-CentOS-6-td7625846.html#a7626144 / http://qpid.2158936.n2.nabble.com/PROTON-907-Issue-td7627337.html / https://issues.apache.org/jira/browse/PROTON-907. We’re continuing to chase though.

 

Cheers,

Frank

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Adrienne Ambrose
Sent: 01 July 2015 15:18


To: Alpert, Reed; Gary Molloy; openmama-dev@...

Subject: Re: [Openmama-dev] OpenMAMA-2.3.3-rc1

 

Hi Reed,

 

Apologies for the delay on this release, we hit an issue while running tests, present in the Qpid Proton 0.9.x and we had hoped this would be resolved by now.

Frank has been chasing this up, so I will let him explain the actual problem.

 

We can still release if needs be, but we really wanted to bring OpenMAMA up to date with the latest versions of the relevant open source messaging stacks before dubbing it fit for release.

 

Thanks,

Adrienne

 

Adrienne Ambrose, Software Engineer

Tel: +4428 9099 7580 |

Adelaide Exchange | 24-26 Adelaide Street | Belfast | UK | BT2 8GD

www.srtechlabs.com

 

SR.LABS Proven High Speed Electronic Trading Solutions

 

 

 

From: Alpert, Reed [mailto:reed.alpert@...]
Sent: 30 June 2015 19:50
To: Adrienne Ambrose; Gary Molloy; openmama-dev@...
Cc: Phelan, Nigel
Subject: RE: OpenMAMA-2.3.3-rc1

 

Hi,

 

Is 2.3.3 being released soon?

We have some dependencies on that/etc.

 

Thanks,

 

Reed.

 


Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198  | M: 917.414.4613 | reed.alpert@...

Alternate Contact:  CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...

 

From: Adrienne Ambrose [mailto:a.ambrose@...]
Sent: Wednesday, May 27, 2015 10:42 AM
To: Alpert, Reed; Gary Molloy; openmama-dev@...
Subject: RE: OpenMAMA-2.3.3-rc1

 

Hi Reed,

 

Thanks for the feedback, it is greatly appreciated.

Please keep us informed on the outcome of any further testing.

 

Thanks,

Adrienne

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Alpert, Reed
Sent: 27 May 2015 15:29
To: Gary Molloy; openmama-dev@...
Subject: Re: [Openmama-dev] OpenMAMA-2.3.3-rc1

 

We’ve been testing with this release and have no issues so far.

Testing C++ and Java clients.

Publish and subscribe.

Solace and Tick42 bridges.

 


Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198  | M: 917.414.4613 | reed.alpert@...

Alternate Contact:  CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Gary Molloy
Sent: Tuesday, May 05, 2015 10:31 AM
To: openmama-dev@...
Subject: [Openmama-dev] OpenMAMA-2.3.3-rc1

 

Hi Guys,

 

I have cut the new OpenMAMA-2.3.3 branch and created the OpenMAMA-2.3.3-rc1 tag, this is now available for testing.  I would anticipate a test period of around 2-3 weeks with a view to making the release official by the end of the month.

 

This release has been cut from the next branch.

 

The following list of issues/features have been added for this release:

 

BZ-166 Wombat: wInterlocked_set inconsistent return value

BZ-164 MAMAJNI: MamaPublisher: Overloaded MamaPublisher create method

BZ-169  Wombat queue has no separate deallocate method

BZ-176  Missing actions for snapshot subscriptions transition to deactivate state

BZ-168 Complete support for Vector Bool and Vector Char field types

BZ-156 No value expansion of last property line in mama.properties

BZ-178 Problem with mamaDictionary_getDictionaryMessage when multiple bridges are loaded

BZ-182 MAMAJAVA: Add java MamaDateTime::getAsFormattedString() method

BZ-181 MAMAJAVA: Java subscription setup fix - it loses the closure

BZ-183 SCons: OpenMAMA will not build on windows

BZ-189 [MAMAC] mamaPlugin Feature

BZ-190 [MAMAC] Add ability to turn on/off entitlements on a per bridge basis

BZ-191 [MAMAC] mamaPublisherImpl_getTransportImpl() accessor

BZ-179 OpenMAMA mock RPM's fail to build

BZ-187 SCons: Include stdout for build commands using site scons logger

BZ-188 Scons: fixes for Windows and Linux

BZ-192 OpenMAMA RPM Release Scripts

 

 

Thanks,

Gary

 

 

Gary Molloy – SR Labs

Adelaide Exchange | 24-26 Adelaide Street | Belfast | BT2 8GD

g.molloy@...

 

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.

_______________________________________________
Openmama-dev mailing list
Openmama-dev@...
https://lists.openmama.org/mailman/listinfo/openmama-dev


Help with bookpublisher

macrux
 

Hi there,

Could someone, please, give me a hand with the MamdaBookPublisher.java example, I haven't been able to run it, I mean, I don't know which are the arguments I've to pass. Thank you all.

kind regards,

Nestor


Re: OpenMAMA-2.3.3-rc1

Frank Quinn <f.quinn@...>
 

Just to add some context on the issue in question, it is pretty serious for Qpid Proton users as it effectively deadlocks OpenMAMA on RHEL (works fine on Fedora though). This has blocked testing as it means we can’t test the small changes that we needed to make to get it to compile in the first place. Proton 0.9.x is the default version that gets installed if you use EPEL repositories for RHEL 6 or CentOS 6.

 

We can recreate this in isolation with just the qpid proton provided test applications and we have reported this to the proton folks at the start of June and after chasing it up, it’s not yet resolved: http://qpid.2158936.n2.nabble.com/Strange-behaviour-for-pn-messenger-send-on-CentOS-6-td7625846.html#a7626144 / http://qpid.2158936.n2.nabble.com/PROTON-907-Issue-td7627337.html / https://issues.apache.org/jira/browse/PROTON-907. We’re continuing to chase though.

 

Cheers,

Frank

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Adrienne Ambrose
Sent: 01 July 2015 15:18
To: Alpert, Reed; Gary Molloy; openmama-dev@...
Subject: Re: [Openmama-dev] OpenMAMA-2.3.3-rc1

 

Hi Reed,

 

Apologies for the delay on this release, we hit an issue while running tests, present in the Qpid Proton 0.9.x and we had hoped this would be resolved by now.

Frank has been chasing this up, so I will let him explain the actual problem.

 

We can still release if needs be, but we really wanted to bring OpenMAMA up to date with the latest versions of the relevant open source messaging stacks before dubbing it fit for release.

 

Thanks,

Adrienne

 

Adrienne Ambrose, Software Engineer

Tel: +4428 9099 7580 |

Adelaide Exchange | 24-26 Adelaide Street | Belfast | UK | BT2 8GD

www.srtechlabs.com

 

SR.LABS Proven High Speed Electronic Trading Solutions

 

 

 

From: Alpert, Reed [mailto:reed.alpert@...]
Sent: 30 June 2015 19:50
To: Adrienne Ambrose; Gary Molloy; openmama-dev@...
Cc: Phelan, Nigel
Subject: RE: OpenMAMA-2.3.3-rc1

 

Hi,

 

Is 2.3.3 being released soon?

We have some dependencies on that/etc.

 

Thanks,

 

Reed.

 


Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198  | M: 917.414.4613 | reed.alpert@...

Alternate Contact:  CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...

 

From: Adrienne Ambrose [mailto:a.ambrose@...]
Sent: Wednesday, May 27, 2015 10:42 AM
To: Alpert, Reed; Gary Molloy; openmama-dev@...
Subject: RE: OpenMAMA-2.3.3-rc1

 

Hi Reed,

 

Thanks for the feedback, it is greatly appreciated.

Please keep us informed on the outcome of any further testing.

 

Thanks,

Adrienne

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Alpert, Reed
Sent: 27 May 2015 15:29
To: Gary Molloy; openmama-dev@...
Subject: Re: [Openmama-dev] OpenMAMA-2.3.3-rc1

 

We’ve been testing with this release and have no issues so far.

Testing C++ and Java clients.

Publish and subscribe.

Solace and Tick42 bridges.

 


Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198  | M: 917.414.4613 | reed.alpert@...

Alternate Contact:  CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Gary Molloy
Sent: Tuesday, May 05, 2015 10:31 AM
To: openmama-dev@...
Subject: [Openmama-dev] OpenMAMA-2.3.3-rc1

 

Hi Guys,

 

I have cut the new OpenMAMA-2.3.3 branch and created the OpenMAMA-2.3.3-rc1 tag, this is now available for testing.  I would anticipate a test period of around 2-3 weeks with a view to making the release official by the end of the month.

 

This release has been cut from the next branch.

 

The following list of issues/features have been added for this release:

 

BZ-166 Wombat: wInterlocked_set inconsistent return value

BZ-164 MAMAJNI: MamaPublisher: Overloaded MamaPublisher create method

BZ-169  Wombat queue has no separate deallocate method

BZ-176  Missing actions for snapshot subscriptions transition to deactivate state

BZ-168 Complete support for Vector Bool and Vector Char field types

BZ-156 No value expansion of last property line in mama.properties

BZ-178 Problem with mamaDictionary_getDictionaryMessage when multiple bridges are loaded

BZ-182 MAMAJAVA: Add java MamaDateTime::getAsFormattedString() method

BZ-181 MAMAJAVA: Java subscription setup fix - it loses the closure

BZ-183 SCons: OpenMAMA will not build on windows

BZ-189 [MAMAC] mamaPlugin Feature

BZ-190 [MAMAC] Add ability to turn on/off entitlements on a per bridge basis

BZ-191 [MAMAC] mamaPublisherImpl_getTransportImpl() accessor

BZ-179 OpenMAMA mock RPM's fail to build

BZ-187 SCons: Include stdout for build commands using site scons logger

BZ-188 Scons: fixes for Windows and Linux

BZ-192 OpenMAMA RPM Release Scripts

 

 

Thanks,

Gary

 

 

Gary Molloy – SR Labs

Adelaide Exchange | 24-26 Adelaide Street | Belfast | BT2 8GD

g.molloy@...

 

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.


Re: OpenMAMA-2.3.3-rc1

Adrienne Ambrose <a.ambrose@...>
 

Hi Reed,

 

Apologies for the delay on this release, we hit an issue while running tests, present in the Qpid Proton 0.9.x and we had hoped this would be resolved by now.

Frank has been chasing this up, so I will let him explain the actual problem.

 

We can still release if needs be, but we really wanted to bring OpenMAMA up to date with the latest versions of the relevant open source messaging stacks before dubbing it fit for release.

 

Thanks,

Adrienne

 

Adrienne Ambrose, Software Engineer

Tel: +4428 9099 7580 |

Adelaide Exchange | 24-26 Adelaide Street | Belfast | UK | BT2 8GD

www.srtechlabs.com

 

SR.LABS Proven High Speed Electronic Trading Solutions

 

 

 

From: Alpert, Reed [mailto:reed.alpert@...]
Sent: 30 June 2015 19:50
To: Adrienne Ambrose; Gary Molloy; openmama-dev@...
Cc: Phelan, Nigel
Subject: RE: OpenMAMA-2.3.3-rc1

 

Hi,

 

Is 2.3.3 being released soon?

We have some dependencies on that/etc.

 

Thanks,

 

Reed.

 


Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198  | M: 917.414.4613 | reed.alpert@...

Alternate Contact:  CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...

 

From: Adrienne Ambrose [mailto:a.ambrose@...]
Sent: Wednesday, May 27, 2015 10:42 AM
To: Alpert, Reed; Gary Molloy; openmama-dev@...
Subject: RE: OpenMAMA-2.3.3-rc1

 

Hi Reed,

 

Thanks for the feedback, it is greatly appreciated.

Please keep us informed on the outcome of any further testing.

 

Thanks,

Adrienne

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Alpert, Reed
Sent: 27 May 2015 15:29
To: Gary Molloy; openmama-dev@...
Subject: Re: [Openmama-dev] OpenMAMA-2.3.3-rc1

 

We’ve been testing with this release and have no issues so far.

Testing C++ and Java clients.

Publish and subscribe.

Solace and Tick42 bridges.

 


Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198  | M: 917.414.4613 | reed.alpert@...

Alternate Contact:  CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Gary Molloy
Sent: Tuesday, May 05, 2015 10:31 AM
To: openmama-dev@...
Subject: [Openmama-dev] OpenMAMA-2.3.3-rc1

 

Hi Guys,

 

I have cut the new OpenMAMA-2.3.3 branch and created the OpenMAMA-2.3.3-rc1 tag, this is now available for testing.  I would anticipate a test period of around 2-3 weeks with a view to making the release official by the end of the month.

 

This release has been cut from the next branch.

 

The following list of issues/features have been added for this release:

 

BZ-166 Wombat: wInterlocked_set inconsistent return value

BZ-164 MAMAJNI: MamaPublisher: Overloaded MamaPublisher create method

BZ-169  Wombat queue has no separate deallocate method

BZ-176  Missing actions for snapshot subscriptions transition to deactivate state

BZ-168 Complete support for Vector Bool and Vector Char field types

BZ-156 No value expansion of last property line in mama.properties

BZ-178 Problem with mamaDictionary_getDictionaryMessage when multiple bridges are loaded

BZ-182 MAMAJAVA: Add java MamaDateTime::getAsFormattedString() method

BZ-181 MAMAJAVA: Java subscription setup fix - it loses the closure

BZ-183 SCons: OpenMAMA will not build on windows

BZ-189 [MAMAC] mamaPlugin Feature

BZ-190 [MAMAC] Add ability to turn on/off entitlements on a per bridge basis

BZ-191 [MAMAC] mamaPublisherImpl_getTransportImpl() accessor

BZ-179 OpenMAMA mock RPM's fail to build

BZ-187 SCons: Include stdout for build commands using site scons logger

BZ-188 Scons: fixes for Windows and Linux

BZ-192 OpenMAMA RPM Release Scripts

 

 

Thanks,

Gary

 

 

Gary Molloy – SR Labs

Adelaide Exchange | 24-26 Adelaide Street | Belfast | BT2 8GD

g.molloy@...

 

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.


Re: [PATCH 2.3.3-rc1] NULL Symbol causes crash

Adrienne Ambrose <a.ambrose@...>
 

Hi Reed,

 

Thank you for the attached patch. I have opened a Bugzilla ticket [Bug 202] for tracking of this issue :-

http://bugs.openmama.org/show_bug.cgi?id=202

 

We will review this patch, but if you could update the ticket when the unit tests are available that would be greatly appreciated.

 

Thank you,

Adrienne

 

Adrienne Ambrose, Software Engineer

Tel: +4428 9099 7580 |

Adelaide Exchange | 24-26 Adelaide Street | Belfast | UK | BT2 8GD

www.srtechlabs.com

 

SR.LABS Proven High Speed Electronic Trading Solutions

 

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Reed Alpert
Sent: 01 July 2015 01:58
To: openmama-dev@...
Subject: [Openmama-dev] [PATCH 2.3.3-rc1] NULL Symbol causes crash

 

Patch for NULL symbol in subscribe causing crash.

Test is modified mamalistencpp.

 

I am working on the unit tests but they need more changes to make then work with any bridge/transport. Will send those when ready, but wanted to get this patch sent.

 

Thanks,

 

Reed.

 


[PATCH 2.3.3-rc1] NULL Symbol causes crash

Reed Alpert <reed.alpert@...>
 

Patch for NULL symbol in subscribe causing crash.
Test is modified mamalistencpp.

I am working on the unit tests but they need more changes to make then work with any bridge/transport. Will send those when ready, but wanted to get this patch sent.

Thanks,

Reed.


Re: OpenMAMA-2.3.3-rc1

Alpert, Reed <reed.alpert@...>
 

Hi,

 

Is 2.3.3 being released soon?

We have some dependencies on that/etc.

 

Thanks,

 

Reed.

 


Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198  | M: 917.414.4613 | reed.alpert@...

Alternate Contact:  CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...

 

From: Adrienne Ambrose [mailto:a.ambrose@...]
Sent: Wednesday, May 27, 2015 10:42 AM
To: Alpert, Reed; Gary Molloy; openmama-dev@...
Subject: RE: OpenMAMA-2.3.3-rc1

 

Hi Reed,

 

Thanks for the feedback, it is greatly appreciated.

Please keep us informed on the outcome of any further testing.

 

Thanks,

Adrienne

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Alpert, Reed
Sent: 27 May 2015 15:29
To: Gary Molloy; openmama-dev@...
Subject: Re: [Openmama-dev] OpenMAMA-2.3.3-rc1

 

We’ve been testing with this release and have no issues so far.

Testing C++ and Java clients.

Publish and subscribe.

Solace and Tick42 bridges.

 


Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198  | M: 917.414.4613 | reed.alpert@...

Alternate Contact:  CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Gary Molloy
Sent: Tuesday, May 05, 2015 10:31 AM
To: openmama-dev@...
Subject: [Openmama-dev] OpenMAMA-2.3.3-rc1

 

Hi Guys,

 

I have cut the new OpenMAMA-2.3.3 branch and created the OpenMAMA-2.3.3-rc1 tag, this is now available for testing.  I would anticipate a test period of around 2-3 weeks with a view to making the release official by the end of the month.

 

This release has been cut from the next branch.

 

The following list of issues/features have been added for this release:

 

BZ-166 Wombat: wInterlocked_set inconsistent return value

BZ-164 MAMAJNI: MamaPublisher: Overloaded MamaPublisher create method

BZ-169  Wombat queue has no separate deallocate method

BZ-176  Missing actions for snapshot subscriptions transition to deactivate state

BZ-168 Complete support for Vector Bool and Vector Char field types

BZ-156 No value expansion of last property line in mama.properties

BZ-178 Problem with mamaDictionary_getDictionaryMessage when multiple bridges are loaded

BZ-182 MAMAJAVA: Add java MamaDateTime::getAsFormattedString() method

BZ-181 MAMAJAVA: Java subscription setup fix - it loses the closure

BZ-183 SCons: OpenMAMA will not build on windows

BZ-189 [MAMAC] mamaPlugin Feature

BZ-190 [MAMAC] Add ability to turn on/off entitlements on a per bridge basis

BZ-191 [MAMAC] mamaPublisherImpl_getTransportImpl() accessor

BZ-179 OpenMAMA mock RPM's fail to build

BZ-187 SCons: Include stdout for build commands using site scons logger

BZ-188 Scons: fixes for Windows and Linux

BZ-192 OpenMAMA RPM Release Scripts

 

 

Thanks,

Gary

 

 

Gary Molloy – SR Labs

Adelaide Exchange | 24-26 Adelaide Street | Belfast | BT2 8GD

g.molloy@...

 

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.

761 - 780 of 2305