OpenMAMA doesn't seem to work with WOMBAT tibrv bridge
Slavomir Kundrik
Hi,
I have finally got around to build the OpenMAMA 2.1 on Windows and all worked great. Perhaps just a small thing. In avis project post-build event I had to change the CommandLine to
copy "$(AVIS_HOME)\Release\avis.dll" "$(OutDir)avis.dll" or it would produce error (copy finished with return code 1). The original copy would fail if AVIS_HOME contains spaces hence quotes.
Anyway,
after getting all the building done I have decided to test it with a tibrv bridge that comes with MAMA4 api from WOMBAT. Unfortunately after launching the mamalistec.exe example that comes with OpenMAMA I got “Entry Point Not Found” error with the following
message
“The procedure entry point mamaMsgImpl_usingPayloadBridge could not be located in the dynamic link library libmamacmd.dll”
Using dependency walker I can see it in the libmamacmd.dll that comes with WOMBAT but not in yours.
Is there something missing in the OpenMAMA implementation?
Thanks,
Slavomir Kundrik
Principal Developer, Futures Front Office IT, EMEA
Nomura
This e-mail (including any attachments) is confidential, may contain
proprietary or privileged information and is intended for the named
recipient(s) only. Unintended recipients are prohibited from taking action
on the basis of information in this e-mail and must delete all copies.
Nomura will not accept responsibility or liability for the accuracy or
completeness of, or the presence of any virus or disabling code in, this
e-mail. If verification is sought please request a hard copy. Any reference
to the terms of executed transactions should be treated as preliminary only
and subject to formal written confirmation by Nomura. Nomura reserves the
right to monitor e-mail communications through its networks (in accordance
with applicable laws). No confidentiality or privilege is waived or lost by
Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is
a reference to any entity in the Nomura Holdings, Inc. group. Please read
our Electronic Communications Legal Notice which forms part of this e-mail:
http://www.Nomura.com/email_disclaimer.htm
|
|
Mike Schonberg <mschonberg@...>
Slavomir,
At this time the commercial bridges for TIBRV, LBM and NYSE Data Fabric supplied by NYSE as part of the MAMA 4.x and 5.x releases are not compatible with OpenMAMA; however, they will be part of the OpenMAMA Enterprise Edition which will be released in the near future.
I will look at the Windows build scripts and fix the problem that you encountered.
Regards, -Mike Schonberg
From: openmama-users-bounces@... [mailto:openmama-users-bounces@...]
On Behalf Of slavomir.kundrik@...
Sent: Wednesday, July 11, 2012 11:27 AM To: openmama-users@... Subject: [Openmama-users] OpenMAMA doesn't seem to work with WOMBAT tibrv bridge
Hi,
I have finally got around to build the OpenMAMA 2.1 on Windows and all worked great. Perhaps just a small thing. In avis project post-build event I had to change the CommandLine
to
or it would produce error (copy finished with return code 1). The original copy would fail if AVIS_HOME contains spaces hence quotes.
Anyway, after getting all the building done I have decided to test it with a tibrv bridge that comes with MAMA4 api from WOMBAT. Unfortunately after launching the mamalistec.exe example that comes with OpenMAMA I got “Entry Point Not Found” error with the following message
“The procedure entry point mamaMsgImpl_usingPayloadBridge could not be located in the dynamic link library libmamacmd.dll”
Using dependency walker I can see it in the libmamacmd.dll that comes with WOMBAT but not in yours.
Is there something missing in the OpenMAMA implementation?
Thanks,
Slavomir Kundrik Principal Developer, Futures Front Office IT, EMEA Nomura
This e-mail (including any attachments) is confidential, may contain proprietary or privileged information and is intended for the named recipient(s) only. Unintended recipients are prohibited from taking action on the basis of information in this e-mail and must delete all copies. Nomura will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in, this e-mail. If verification is sought please request a hard copy. Any reference to the terms of executed transactions should be treated as preliminary only and subject to formal written confirmation by Nomura. Nomura reserves the right to monitor e-mail communications through its networks (in accordance with applicable laws). No confidentiality or privilege is waived or lost by Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is a reference to any entity in the Nomura Holdings, Inc. group. Please read our Electronic Communications Legal Notice which forms part of this e-mail: Please consider the environment before printing this email. Visit our website at http://www.nyse.com |
|
Jacobraj Benet <JBenet@...>
Hi Slavomir,
The OpenMAMA source code doesn't include the bridge implementation of the Tibrv middleware. It only have the bridge implementation of avis and so wouldn't be able to run it on Tibrv.
Thanks,
-- Jacob
From: "slavomir.kundrik@..." <slavomir.kundrik@...>
Date: Wednesday, July 11, 2012 1:27 PM To: "openmama-users@..." <openmama-users@...> Subject: [Openmama-users] OpenMAMA doesn't seem to work with WOMBAT tibrv bridge Hi,
I have finally got around to build the OpenMAMA 2.1 on Windows and all worked great. Perhaps just a small thing. In avis project post-build event I had to change the CommandLine to
copy "$(AVIS_HOME)\Release\avis.dll" "$(OutDir)avis.dll" or it would produce error (copy finished with return code 1). The original copy would fail if AVIS_HOME contains spaces hence quotes.
Anyway,
after getting all the building done I have decided to test it with a tibrv bridge that comes with MAMA4 api from WOMBAT. Unfortunately after launching the mamalistec.exe example that comes with OpenMAMA I got “Entry Point Not Found” error with the following
message
“The procedure entry point mamaMsgImpl_usingPayloadBridge could not be located in the dynamic link library libmamacmd.dll”
Using dependency walker I can see it in the libmamacmd.dll that comes with WOMBAT but not in yours.
Is there something missing in the OpenMAMA implementation?
Thanks,
Slavomir Kundrik
Principal Developer, Futures Front Office IT, EMEA
Nomura
This e-mail (including any attachments) is confidential, may contain
proprietary or privileged information and is intended for the named
recipient(s) only. Unintended recipients are prohibited from taking action
on the basis of information in this e-mail and must delete all copies.
Nomura will not accept responsibility or liability for the accuracy or
completeness of, or the presence of any virus or disabling code in, this
e-mail. If verification is sought please request a hard copy. Any reference
to the terms of executed transactions should be treated as preliminary only
and subject to formal written confirmation by Nomura. Nomura reserves the
right to monitor e-mail communications through its networks (in accordance
with applicable laws). No confidentiality or privilege is waived or lost by
Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is
a reference to any entity in the Nomura Holdings, Inc. group. Please read
our Electronic Communications Legal Notice which forms part of this e-mail:
Please consider the environment before printing this email. Visit our website at http://www.nyse.com |
|
Slavomir Kundrik
Mike,
I forgot 1 more thing with the build.
When building on my VS2010 there is a setting under Tools->Options->Projects and Solutions->Build and Run called “maximum number of parallel builds”. I had this set to 8 and several project builds (about 18 I think) would fail due to “File being used by another process”. After changing this to 1 all seems to work fine.
I’m not sure if you can work around this in the build (I don’t see an obvious easy solution) but it might be worth mentioning in the README file.
Regards, Slavo
From: Mike Schonberg [mailto:mschonberg@...]
Sent: 11 July 2012 19:40 To: Kundrik, Slavomir (IT/UK); openmama-users@... Subject: RE: [Openmama-users] OpenMAMA doesn't seem to work with WOMBAT tibrv bridge
Slavomir,
At this time the commercial bridges for TIBRV, LBM and NYSE Data Fabric supplied by NYSE as part of the MAMA 4.x and 5.x releases are not compatible with OpenMAMA; however, they will be part of the OpenMAMA Enterprise Edition which will be released in the near future.
I will look at the Windows build scripts and fix the problem that you encountered.
Regards, -Mike Schonberg
From:
openmama-users-bounces@...
[mailto:openmama-users-bounces@...]
On Behalf Of slavomir.kundrik@...
Hi,
I have finally got around to build the OpenMAMA 2.1 on Windows and all worked great. Perhaps just a small thing. In avis project post-build event I had to change
the CommandLine to
or it would produce error (copy finished with return code 1). The original copy would fail if AVIS_HOME contains spaces hence quotes.
Anyway, after getting all the building done I have decided to test it with a tibrv bridge that comes with MAMA4 api from WOMBAT. Unfortunately after launching the mamalistec.exe example that comes with OpenMAMA I got “Entry Point Not Found” error with the following message
“The procedure entry point mamaMsgImpl_usingPayloadBridge could not be located in the dynamic link library libmamacmd.dll”
Using dependency walker I can see it in the libmamacmd.dll that comes with WOMBAT but not in yours.
Is there something missing in the OpenMAMA implementation?
Thanks,
Slavomir Kundrik Principal Developer, Futures Front Office IT, EMEA Nomura
This e-mail (including any attachments) is confidential, may contain proprietary or privileged information and is intended for the named recipient(s) only. Unintended recipients are prohibited from taking action on the basis of information in this e-mail and must delete all copies. Nomura will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in, this e-mail. If verification is sought please request a hard copy. Any reference to the terms of executed transactions should be treated as preliminary only and subject to formal written confirmation by Nomura. Nomura reserves the right to monitor e-mail communications through its networks (in accordance with applicable laws). No confidentiality or privilege is waived or lost by Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is a reference to any entity in the Nomura Holdings, Inc. group. Please read our Electronic Communications Legal Notice which forms part of this e-mail: Please consider the environment before printing this email. Visit our website at
http://www.nyse.com This e-mail (including any attachments) is confidential, may contain
proprietary or privileged information and is intended for the named
recipient(s) only. Unintended recipients are prohibited from taking action
on the basis of information in this e-mail and must delete all copies.
Nomura will not accept responsibility or liability for the accuracy or
completeness of, or the presence of any virus or disabling code in, this
e-mail. If verification is sought please request a hard copy. Any reference
to the terms of executed transactions should be treated as preliminary only
and subject to formal written confirmation by Nomura. Nomura reserves the
right to monitor e-mail communications through its networks (in accordance
with applicable laws). No confidentiality or privilege is waived or lost by
Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is
a reference to any entity in the Nomura Holdings, Inc. group. Please read
our Electronic Communications Legal Notice which forms part of this e-mail:
http://www.Nomura.com/email_disclaimer.htm
|
|