1. Openmama-Dev
  2. Messages

Expanded

Topics Messages Polls
   Date   
Code change(s) just landed on origin/next (Successful)

jenkins@...
 

Some changes have just been added to the origin/next branch! 

[Frank Quinn] MAMA: Fixed race condition deadlock in mamaDispatcher_destroy
	mama/c_cpp/src/c/queue.c
	mama/c_cpp/src/gunittest/c/queuetest.cpp

Results for OpenMAMA_Next_Branch_VS_2015 CI run with latest changes:

  • CI Project Name: OpenMAMA_Next_Branch_VS_2015
  • Build Number: #99
  • Build Status: Successful
  • Build Warnings: 2390
  • Total Amount of Tests:
  • Passed:
  • Failed:
  • Skipped / Disabled:

You may also check CI console output to view the full results.

Code change(s) just landed on origin/OpenMAMA-6.1.0 (Successful)

jenkins@...
 

Some changes have just been added to the origin/OpenMAMA-6.1.0 branch! 

[Frank Quinn] COMMON Failed build and unit test on Mac (#212)
	common/c_cpp/src/c/darwin/wSemaphore.c
	common/c_cpp/src/c/darwin/port.h
	common/c_cpp/src/c/wtable.c
	site_scons/community/command_line.py

[Frank Quinn] PLAT-529: Fixed a bug where mamapublishercpp was adding an extra . to
	mama/c_cpp/src/examples/cpp/mamapublishercpp.cpp

[Frank Quinn] MAMA: Removed mixed declaration in ent-noop (#214)
	mama/c_cpp/src/c/entitlement/noop/noop.c

[Frank Quinn] PLAT-747: Mamalistenc cores on start up when entitlements are not
	mama/c_cpp/src/c/entitlement/oea/oea.c

Results for OpenMAMA_6.1.0_Branch_VS_2015 CI run with latest changes:

  • CI Project Name: OpenMAMA_6.1.0_Branch_VS_2015
  • Build Number: #4
  • Build Status: Successful
  • Build Warnings: 2390
  • Total Amount of Tests:
  • Passed:
  • Failed:
  • Skipped / Disabled:

You may also check CI console output to view the full results.

Re: OpenMAMA-6.1.0-rc1 Now Available

Frank Quinn <fquinn.ni@...>
 

Hi Folks,

Just to keep everyone up to date, we are awaiting on confirmation of one potential bug before this is released.

If that proves to be a non-issue, we can release shortly after confirmation.

If it proves to be a real problem, we will fix, announce another RC, and open up to a further week's testing before release.

Cheers,
Frank

On Wed, Aug 10, 2016 at 5:06 PM, Frank Quinn <fquinn.ni@...> wrote:

Hi Folks,

We are pleased to announce the first release candidate for openMAMA 6.1.0 is now available:

https://github.com/OpenMAMA/OpenMAMA/releases/tag/OpenMAMA-6.1.0-rc1

This release bumps the version of OpenMAMA up to 6.1.0 to bring it into line with Vela's Enterprise MAMA 6 (they will be doing the same) and make it more clear which versions are bridge-compatible.

Key changes and bugfixes included in this release:

  • Removed all known valgrind reported memory leaks from our CI test bed and API
  • Avis now removed (see the mailing list entry)
  • Added Payload and Middleware unit tests on Visual Studio projects
  • Added ability to provide a separate timeout for recaps
  • Fixed issue where book recaps were being ignored duing FT takeover
  • Fixed issue where wildcard subscription OnMsg callback is called with NULL instead of topic
  • Wired up mamamsg vector price and vector datetime field types
  • Qpid support to stop publishing to departed subscribers added

For a complete list of all 62 issues and pull requests included in this release, please see here: https://github.com/OpenMAMA/OpenMAMA/milestone/5?closed=1

Thank you all in advance for your help in testing - if you spot any issues, please follow our guidelines for raising an issue, or even better, follow our guidelines for raising a patch.


As this release is mainly a bugfix release, we're not expecting a large volume of bugs to fall out, so I will be acting on a reasonably brief test window of 2 weeks commencing today. If no issues have been found, we can aim to release on 24th August. If critical issues are found, we will go through weekly release candidates until have a stable release ready.


Cheers,

Frank

Re: mamaBridgeImpl_setProperty is broken

Stuart Beattie
 

Hi Yury,

Thanks for bringing this to our attention - we'll double check the correct behaviour here and making any necessary fixes.

Thanks
Stuart

STUART BEATTIE
Senior Software Engineer

O. +44 28909 93365
M.
sbeattie@...

Adelaide Exchange Building, 2nd Floor, 24-26 Adelaide Street, Belfast, BT2 8GD
velatradingtech.com | @vela_tt

-----Original Message-----
From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Yury Batrakov
Sent: 01 September 2016 14:56
To: openmama-dev@...
Subject: [Openmama-dev] mamaBridgeImpl_setProperty is broken

Classification: Public

Hi everybody,

I found that function mamaBridgeImpl_setProperty (files mama/c_cpp/src/c/bridge.h and mama/c_cpp/src/c/bridge.c) wasn't properly deleted from the codebase - it still exists in header file but was removed from .c file. Thus if some middleware bridge library is using this function it compiles successfully but can't be loaded by OpenMAMA. I suppose it was designed to replace the function with mamaBridgeImpl_setMetaProperty but the latter is not declared in header file and not exported so it won't be usable on Windows.
Could you clarify if clients should use mamaBridgeImpl_setMetaProperty instead and schedule corresponding changes to the next release?

Thanks.


---
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to https://www.db.com/disclosures for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy.
_______________________________________________
Openmama-dev mailing list
Openmama-dev@...
https://lists.openmama.org/mailman/listinfo/openmama-dev

The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. Vela Trading Technologies LLC
Code change(s) just landed on origin/next (Successful)

jenkins@...
 

Some changes have just been added to the origin/next branch! 

[fquinn.ni] PLAT-747: Mamalistenc cores on start up when entitlements are not
	mama/c_cpp/src/c/entitlement/oea/oea.c

Results for OpenMAMA Next Branch with Qpid Proton CI run with latest changes:

  • CI Project Name: OpenMAMA Next Branch with Qpid Proton
  • Build Number: #105
  • Build Status: Successful
  • Build Warnings: 0
  • Total Amount of Tests: 1768
  • Passed: 1768
  • Failed: 0
  • Skipped / Disabled: 0

You may also check CI console output to view the full results.

Code change(s) just landed on origin/next (Successful)

jenkins@...
 

Some changes have just been added to the origin/next branch! 

[fquinn.ni] PLAT-747: Mamalistenc cores on start up when entitlements are not
	mama/c_cpp/src/c/entitlement/oea/oea.c

Results for OpenMAMA_Next_Branch_VS_2015 CI run with latest changes:

  • CI Project Name: OpenMAMA_Next_Branch_VS_2015
  • Build Number: #98
  • Build Status: Successful
  • Build Warnings: 2390
  • Total Amount of Tests:
  • Passed:
  • Failed:
  • Skipped / Disabled:

You may also check CI console output to view the full results.

mamaBridgeImpl_setProperty is broken

Yury Batrakov
 

Classification: Public

Hi everybody,

I found that function mamaBridgeImpl_setProperty (files mama/c_cpp/src/c/bridge.h and mama/c_cpp/src/c/bridge.c) wasn't properly deleted from the codebase - it still exists in header file but was removed from .c file. Thus if some middleware bridge library is using this function it compiles successfully but can't be loaded by OpenMAMA. I suppose it was designed to replace the function with mamaBridgeImpl_setMetaProperty but the latter is not declared in header file and not exported so it won't be usable on Windows.
Could you clarify if clients should use mamaBridgeImpl_setMetaProperty instead and schedule corresponding changes to the next release?

Thanks.


---
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to https://www.db.com/disclosures for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy.
Re: Copy fields from a message of another payload type

Yury Batrakov
 

Classification: Public

Hi Frank,

 

Thank you, this is exactly what I searched for.

 

From: Frank Quinn [mailto:fquinn.ni@...]
Sent: Wednesday, August 24, 2016 11:19 PM
To: Yury Batrakov; openmama-dev@...
Subject: Re: [Openmama-dev] Copy fields from a message of another payload type

 

Hi Yury,

You can still do something similar - it's the enum that is deprecated - payloads are still expected to have their own identifier, you just access it with a private method now, namely  mamaMsgImpl_getPayloadId.

Qpid proton actually has something similar which should provide a working reference for this approach:

https://github.com/OpenMAMA/OpenMAMA/blob/next/mama/c_cpp/src/c/bridge/qpid/codec.c

Cheers,
Frank

 

On Wed, 24 Aug 2016, 16:53 Yury Batrakov, <yury.batrakov@...> wrote:

Classification: Public

Hi everyone,

I'm migrating my middleware and payload bridges to OpenMAMA 2.4.1. What I found is that the number of functions were deprecated in new release, for example mamaMsg_getPayloadType. In my bridge I support sending data of other payload types and this deprecation breaks my code. Could you advise how to port the following pseudo code to 2.4.1?

send_message(msg) {
    if(mamaMsg_getPayloadType(msg) == MY_TYPE) {
        bytes = serialize_fast(msg);
        send(bytes);
    } else {
        // Create a new message of my type and copy all fields from original message to it
        copy = mamaMsg_create();
        mamaMsg_iterateFields(msg, copy_each_field, copy);
        send_message(copy);
    }
}



---
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to https://www.db.com/disclosures for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy.
_______________________________________________
Openmama-dev mailing list
Openmama-dev@...
https://lists.openmama.org/mailman/listinfo/openmama-dev



---
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to https://www.db.com/disclosures for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy.

Re: Copy fields from a message of another payload type

Frank Quinn <fquinn.ni@...>
 

Hi Yury,

You can still do something similar - it's the enum that is deprecated - payloads are still expected to have their own identifier, you just access it with a private method now, namely  mamaMsgImpl_getPayloadId.

Qpid proton actually has something similar which should provide a working reference for this approach:

https://github.com/OpenMAMA/OpenMAMA/blob/next/mama/c_cpp/src/c/bridge/qpid/codec.c

Cheers,
Frank


On Wed, 24 Aug 2016, 16:53 Yury Batrakov, <yury.batrakov@...> wrote:
Classification: Public

Hi everyone,

I'm migrating my middleware and payload bridges to OpenMAMA 2.4.1. What I found is that the number of functions were deprecated in new release, for example mamaMsg_getPayloadType. In my bridge I support sending data of other payload types and this deprecation breaks my code. Could you advise how to port the following pseudo code to 2.4.1?

send_message(msg) {
    if(mamaMsg_getPayloadType(msg) == MY_TYPE) {
        bytes = serialize_fast(msg);
        send(bytes);
    } else {
        // Create a new message of my type and copy all fields from original message to it
        copy = mamaMsg_create();
        mamaMsg_iterateFields(msg, copy_each_field, copy);
        send_message(copy);
    }
}



---
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to https://www.db.com/disclosures for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy.
_______________________________________________
Openmama-dev mailing list
Openmama-dev@...
https://lists.openmama.org/mailman/listinfo/openmama-dev
Re: Java JNI programs not exiting

Frank Quinn <fquinn.ni@...>
 

Thanks Yury / Reed,

Note a fix has already been submitted for this and will be included in the next release: https://github.com/OpenMAMA/OpenMAMA/commit/f917729eea828de4fda0c03600dfe075edd0edbe

Cheers,
Frank


On Wed, 24 Aug 2016, 15:56 Yury Batrakov, <yury.batrakov@...> wrote:
Classification: Public
Hi Reed,

I've just faced the same OpenMAMA behavior with version 2.3.3. Isn't reproducible with C API but 100% reproducible with Java.


From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Alpert, Reed via Openmama-dev
Sent: Thursday, May 12, 2016 9:52 PM
To: openmama-dev@...
Subject: [Openmama-dev] Java JNI programs not exiting

Hi,

Our OpenMAMA Java programs do not exit due to remaining non-daemon threads from the OM JNI.
Even if these native threads have exited the Java threads are still alive and prevent the JVM from exiting.
I tried using AttachCurrentThreadAsDaemon() in mamajniutils.c and this solves the problem, allowing the JVM to exit.

Have other OM users seen the same thing?
I want to make sure this is the issue rather than another problem with our Java apps.

Thanks,

Reed.


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.


---
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to https://www.db.com/disclosures for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy.
_______________________________________________
Openmama-dev mailing list
Openmama-dev@...
https://lists.openmama.org/mailman/listinfo/openmama-dev
Copy fields from a message of another payload type

Yury Batrakov
 

Classification: Public

Hi everyone,

I'm migrating my middleware and payload bridges to OpenMAMA 2.4.1. What I found is that the number of functions were deprecated in new release, for example mamaMsg_getPayloadType. In my bridge I support sending data of other payload types and this deprecation breaks my code. Could you advise how to port the following pseudo code to 2.4.1?

send_message(msg) {
if(mamaMsg_getPayloadType(msg) == MY_TYPE) {
bytes = serialize_fast(msg);
send(bytes);
} else {
// Create a new message of my type and copy all fields from original message to it
copy = mamaMsg_create();
mamaMsg_iterateFields(msg, copy_each_field, copy);
send_message(copy);
}
}



---
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to https://www.db.com/disclosures for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy.

winmail.dat

winmail.dat

Re: Java JNI programs not exiting

Yury Batrakov
 

Classification: Public
Hi Reed,

I've just faced the same OpenMAMA behavior with version 2.3.3. Isn't reproducible with C API but 100% reproducible with Java.


From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Alpert, Reed via Openmama-dev
Sent: Thursday, May 12, 2016 9:52 PM
To: openmama-dev@...
Subject: [Openmama-dev] Java JNI programs not exiting

Hi,

Our OpenMAMA Java programs do not exit due to remaining non-daemon threads from the OM JNI.
Even if these native threads have exited the Java threads are still alive and prevent the JVM from exiting.
I tried using AttachCurrentThreadAsDaemon() in mamajniutils.c and this solves the problem, allowing the JVM to exit.

Have other OM users seen the same thing?
I want to make sure this is the issue rather than another problem with our Java apps.

Thanks,

Reed.


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.


---
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to https://www.db.com/disclosures for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy.

winmail.dat

winmail.dat

Code change(s) just landed on origin/next (Successful)

jenkins@...
 

Some changes have just been added to the origin/next branch! 

[noreply] MAMA: Removed mixed declaration in ent-noop (#214)
	mama/c_cpp/src/c/entitlement/noop/noop.c

Results for OpenMAMA Next Branch with Qpid Proton CI run with latest changes:

  • CI Project Name: OpenMAMA Next Branch with Qpid Proton
  • Build Number: #104
  • Build Status: Successful
  • Build Warnings: 0
  • Total Amount of Tests: 1768
  • Passed: 1768
  • Failed: 0
  • Skipped / Disabled: 0

You may also check CI console output to view the full results.

Code change(s) just landed on origin/next (Successful)

jenkins@...
 

Some changes have just been added to the origin/next branch! 

[noreply] MAMA: Removed mixed declaration in ent-noop (#214)
	mama/c_cpp/src/c/entitlement/noop/noop.c

Results for OpenMAMA_Next_Branch_VS_2015 CI run with latest changes:

  • CI Project Name: OpenMAMA_Next_Branch_VS_2015
  • Build Number: #97
  • Build Status: Successful
  • Build Warnings: 2390
  • Total Amount of Tests:
  • Passed:
  • Failed:
  • Skipped / Disabled:

You may also check CI console output to view the full results.

Code change(s) just landed on origin/next (Successful)

jenkins@...
 

Some changes have just been added to the origin/next branch! 

[fquinn.ni] COMMON Failed build and unit test on Mac (#212)
	site_scons/community/command_line.py
	common/c_cpp/src/c/wtable.c
	common/c_cpp/src/c/darwin/wSemaphore.c
	common/c_cpp/src/c/darwin/port.h

[fquinn.ni] PLAT-529: Fixed a bug where mamapublishercpp was adding an extra . to
	mama/c_cpp/src/examples/cpp/mamapublishercpp.cpp

Results for OpenMAMA Next Branch with Qpid Proton CI run with latest changes:

  • CI Project Name: OpenMAMA Next Branch with Qpid Proton
  • Build Number: #103
  • Build Status: Successful
  • Build Warnings: 0
  • Total Amount of Tests: 1768
  • Passed: 1768
  • Failed: 0
  • Skipped / Disabled: 0

You may also check CI console output to view the full results.

Code change(s) just landed on origin/next (Successful)

jenkins@...
 

Some changes have just been added to the origin/next branch! 

[fquinn.ni] COMMON Failed build and unit test on Mac (#212)
	common/c_cpp/src/c/wtable.c
	site_scons/community/command_line.py
	common/c_cpp/src/c/darwin/port.h
	common/c_cpp/src/c/darwin/wSemaphore.c

[fquinn.ni] PLAT-529: Fixed a bug where mamapublishercpp was adding an extra . to
	mama/c_cpp/src/examples/cpp/mamapublishercpp.cpp

Results for OpenMAMA_Next_Branch_VS_2015 CI run with latest changes:

  • CI Project Name: OpenMAMA_Next_Branch_VS_2015
  • Build Number: #96
  • Build Status: Successful
  • Build Warnings: 2390
  • Total Amount of Tests:
  • Passed:
  • Failed:
  • Skipped / Disabled:

You may also check CI console output to view the full results.

Code change(s) just landed on origin/next (Successful)

jenkins@...
 

Some changes have just been added to the origin/next branch! 

[fquinn.ni] PLAT-687: Make OEA Socket Timeouts Configurable in MAMA (#213)
	mama/c_cpp/src/c/entitlement/oea/oea.c
	mama/c_cpp/src/c/entitlement/oea/oea.h

Results for OpenMAMA Next Branch with Qpid Proton CI run with latest changes:

  • CI Project Name: OpenMAMA Next Branch with Qpid Proton
  • Build Number: #102
  • Build Status: Successful
  • Build Warnings: 0
  • Total Amount of Tests: 1768
  • Passed: 1768
  • Failed: 0
  • Skipped / Disabled: 0

You may also check CI console output to view the full results.

Code change(s) just landed on origin/next (Successful)

jenkins@...
 

Some changes have just been added to the origin/next branch! 

[fquinn.ni] PLAT-687: Make OEA Socket Timeouts Configurable in MAMA (#213)
	mama/c_cpp/src/c/entitlement/oea/oea.c
	mama/c_cpp/src/c/entitlement/oea/oea.h

Results for OpenMAMA_Next_Branch_VS_2015 CI run with latest changes:

  • CI Project Name: OpenMAMA_Next_Branch_VS_2015
  • Build Number: #95
  • Build Status: Successful
  • Build Warnings: 2390
  • Total Amount of Tests:
  • Passed:
  • Failed:
  • Skipped / Disabled:

You may also check CI console output to view the full results.

Solace OpenMAMA Publish/Subscribe tutorial is available

Dmitri Fedorov <dfedorov.solace@...>
 

Hi all,

Solace Systems publishes a series of OpenMAMA tutorials, helping developers to adapt OpenMAMA and get a better understanding of proper configuration of the Solace Middleware Bridge for OpenMAMA.

The posts are meant to complement existing OpenMAMA samples and documentation. 

Publish/Subscribe tutorial has been posted:

http://dev.solacesystems.com/get-started/openmama-tutorials/solace-openmama-publish-subscribe/

If you have any feedback about these posts and/or wishes for the following posts topics, please don't hesitate to email it to me by replying to this email.

Regards,
Dmitri Fedorov
Software Architect
Solace Systems, Inc.
Ottawa, ON Canada

Solace Systems accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Solace Systems.
Code change(s) just landed on origin/OpenMAMA-6.1.0 (Successful)

jenkins@...
 

Some changes have just been added to the origin/OpenMAMA-6.1.0 branch! 

No changes

Results for OpenMAMA_6.1.0_Branch_VS_2015 CI run with latest changes:

  • CI Project Name: OpenMAMA_6.1.0_Branch_VS_2015
  • Build Number: #3
  • Build Status: Successful
  • Build Warnings: 2390
  • Total Amount of Tests:
  • Passed:
  • Failed:
  • Skipped / Disabled:

You may also check CI console output to view the full results.

461 - 480 of 2319