1. Openmama-users@lists.openmama.org
  2. Messages
   Date   
Re: Data Dictionary Developer Questions [I]

Matthew Mulhern <MMulhern@...>
 

Addressing each of your points in turn:

0. The default OpenMama topic model is the concatenation of
'namespace'##'symbol'. Can OpenMama support multiple symbols published
over a single topic? Would there be any complications (on the caching
mechanism, for example) if a group topic model were followed?

OpenMAMA has the concept of group subscriptions, where multiple symbols
are sent down a single subscription. It¹s a different subscription type
on the client side.
The publisher needs to send an initial for each symbol within the group
before the 10 second timeout elapses.
The specific symbol within the group is communicated using the
wIssueSymbol reserved field.
Each symbol has a separate context and has its own sequence numbers and
gap detection.


1. Data Dictionary API: Can one enrish the standard field description with
user-defined fields? Example custom fields would be: custom data-types,
and byte-offset?

Yes, there is a dedicated range for adding your own custom fields.
However the types available in the dictionary may be a lot less strict
than the payload. Generally the dictionary is used for
Name/fid mapping.


2. Data Dictionary API: Is there java support? Is there a plan for
supporting java?

There is a MamaDIctionary in JAVA currently. However it relies on
populating from a file or a msg.



Rgds,
Matt Mulhern


On 04/02/2013 19:30, "Joseph Sarbak" <joseph.sarbak@db.com> wrote:

Classification: For internal use only

Dear openmama-users@lists.openmama.org,

For my employer, I am investigating the work required to publish market
data to internal consumers over the OpenMama API. I have a couple
questions regarding the default mama topic model and the data dictionary
api. I would be very grateful if someone could either answer these
questions or indicate whether I should be asking another mailing list.


0. The default OpenMama topic model is the concatenation of
'namespace'##'symbol'. Can OpenMama support multiple symbols published
over a single topic? Would there be any complications (on the caching
mechanism, for example) if a group topic model were followed?

1. Data Dictionary API: Can one enrish the standard field description
with user-defined fields? Example custom fields would be: custom
data-types, and byte-offset?

2. Data Dictionary API: Is there java support? Is there a plan for
supporting java?

Thank you.

Joseph Sarbak


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

Deutsche Bank does not render legal or tax advice, and the information
contained in this communication should not be regarded as such.
_______________________________________________
Openmama-users mailing list
Openmama-users@lists.openmama.org
https://lists.openmama.org/mailman/listinfo/openmama-users

________________________________

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Data Dictionary Developer Questions [I]

Joseph Sarbak
 

Classification: For internal use only

Dear openmama-users@lists.openmama.org,

For my employer, I am investigating the work required to publish market data to internal consumers over the OpenMama API. I have a couple questions regarding the default mama topic model and the data dictionary api. I would be very grateful if someone could either answer these questions or indicate whether I should be asking another mailing list.


0. The default OpenMama topic model is the concatenation of 'namespace'##'symbol'. Can OpenMama support multiple symbols published over a single topic? Would there be any complications (on the caching mechanism, for example) if a group topic model were followed?

1. Data Dictionary API: Can one enrish the standard field description with user-defined fields? Example custom fields would be: custom data-types, and byte-offset?

2. Data Dictionary API: Is there java support? Is there a plan for supporting java?

Thank you.

Joseph Sarbak


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

Deutsche Bank does not render legal or tax advice, and the information contained in this communication should not be regarded as such.
(No subject)

Glenn McClements <gmcclements@...>
 

Hi,
If you're using Linux then the steps include the commands to use from a
terminal:

WOMBAT_PATH
export WOMBAT_PATH=/var/userspace/mama/config


LD_LIBRARY_PATH:
export LD_LIBRARY_PATH=/var/userspace/mama/lib:$LD_LIBRARY_PATH


Glenn


From: Shoyaib Hossain <shoyaib0088@yahoo.com>
Reply-To: Shoyaib Hossain <shoyaib0088@yahoo.com>
Date: Sat, 26 Jan 2013 08:38:44 -0800
To: "Openmama-users@lists.openmama.org"
<Openmama-users@lists.openmama.org>
Subject: [Openmama-users] (no subject)


Dear Sir/Madam,


I have
completed the first three steps however i have stuck in step - 4 and 5.
I do not know how to set it WOMBAT_PATH and use the
following command line $ export
WOMBAT_PATH=/var/userspace/mama/config.WOMBAT_PAT. Also i am having same
problem in step - 5.



1. Unzip the file to a convenient directory. For illustration, we use the
directory /var/userspace/
mama. The following directories are created:
2. Create a config directory:
$ mkdir /var/userspace/mama/config
3. Copy mama.properties from examples/mama to the config directory. This
file should have
transport settings.
4. Set the WOMBAT_PATH variable to include config:
$ export WOMBAT_PATH=/var/userspace/mama/config
5. Set the LD_LIBRARY_PATH variable to include lib:
$ export LD_LIBRARY_PATH=/var/userspace/mama/lib:$LD_LIBRARY_PATH
6. For the Java and JNI versions of MAMA, set the CLASSPATH variable to
include the .jar files in the
lib directory:
$ export CLASSPATH=/var/userspace/mama/lib/mamajni.jar:$CLASSPATH


Can you kindly help me out please.

Thanks





_______________________________________________
Openmama-users mailing list
Openmama-users@lists.openmama.orghttps://lists.openmama.org/mailman/listinf
o/openmama-users


________________________________

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
(No subject)

shoyaib
 

Dear Sir/Madam,

I have completed the first three steps however i have stuck in step - 4 and 5.  I do not know how to set it WOMBAT_PATH and use the following command line $ export WOMBAT_PATH=/var/userspace/mama/config.WOMBAT_PAT.   Also i am having same problem in step - 5.


1. Unzip the file to a convenient directory. For illustration, we use the directory /var/userspace/
mama. The following directories are created:
2. Create a config directory:
$ mkdir /var/userspace/mama/config
3. Copy mama.properties from examples/mama to the config directory. This file should have
transport settings.
4. Set the WOMBAT_PATH variable to include config:
$ export WOMBAT_PATH=/var/userspace/mama/config
5. Set the LD_LIBRARY_PATH variable to include lib:
$ export LD_LIBRARY_PATH=/var/userspace/mama/lib:$LD_LIBRARY_PATH
6. For the Java and JNI versions of MAMA, set the CLASSPATH variable to include the .jar files in the
lib directory:
$ export CLASSPATH=/var/userspace/mama/lib/mamajni.jar:$CLASSPATH


Can you kindly help me out please.

Thanks
(No subject)

Glenn McClements <gmcclements@...>
 

Hi Shoyaib,
Have you set the LD_LIBRARY_PATH correctly to point to the lib directory? 

Section 2.1 of the Developer's Guide has some more details on running the examples on Linux: 

Regards,
Glenn 

From: Shoyaib Hossain <shoyaib0088@...>
Reply-To: Shoyaib Hossain <shoyaib0088@...>
Date: Wed, 23 Jan 2013 12:09:47 -0800
To: "Openmama-users@..." <Openmama-users@...>
Subject: [Openmama-users] (no subject)

Dear Sir/Madam

When i use the following command then i am getting an error.  Can you kindly help me out please.

/opt/openmama/bin$ ./mamapublisherc -m avis -tport sub

Starting Publisher With:

topic                           MAMA_TOPIC
inbound topic             MAMA_INBOUND_TOPIC
interval                       0.500000
transport                     sub

mama_loadmamaPayload(): Could not open middleawre bridge [mamaavismlp] [libmamaavisimpl.so: cannot open shared object file: No such file or directory]

Error loading bridge: NO_BRIDGE_IMPL



I am looking forward to your response.

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

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

(No subject)

Jacobraj Benet <JBenet@...>
 

Hi Shoyaib,

It seems that mamapublisherc is unable to load the libmamaavisimp.so shared object.

Can you verify the following:- 

Check to see where libmamaavisimpl.so exist in the lib folder of the install
Make sure that the LD_LIBRARY_PATH is pointing the the lib folder of the install

Could you also run the mamapublisherc in verbose mode and send out the output
Mamapublisherc –m avis –tport sub –v –v –v –v 

-- 

Jacob


From: Shoyaib Hossain <shoyaib0088@...>
Reply-To: Shoyaib Hossain <shoyaib0088@...>
Date: Wednesday, January 23, 2013 2:09 PM
To: "Openmama-users@..." <Openmama-users@...>
Subject: [Openmama-users] (no subject)

Dear Sir/Madam

When i use the following command then i am getting an error.  Can you kindly help me out please.

/opt/openmama/bin$ ./mamapublisherc -m avis -tport sub

Starting Publisher With:

topic                           MAMA_TOPIC
inbound topic             MAMA_INBOUND_TOPIC
interval                       0.500000
transport                     sub

mama_loadmamaPayload(): Could not open middleawre bridge [mamaavismlp] [libmamaavisimpl.so: cannot open shared object file: No such file or directory]

Error loading bridge: NO_BRIDGE_IMPL



I am looking forward to your response.

Thanks

Please consider the environment before printing this email.

Visit our website at http://www.nyse.com
*****************************************************************************
Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to 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 the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Euronext.

(No subject)

shoyaib
 

Dear Sir/Madam

When i use the following command then i am getting an error.  Can you kindly help me out please.

/opt/openmama/bin$ ./mamapublisherc -m avis -tport sub

Starting Publisher With:

topic                           MAMA_TOPIC
inbound topic             MAMA_INBOUND_TOPIC
interval                       0.500000
transport                     sub
mama_loadmamaPayload(): Could not open middleawre bridge [mamaavismlp] [libmamaavisimpl.so: cannot open shared object file: No such file or directory]
Error loading bridge: NO_BRIDGE_IMPL



I am looking forward to your response.

Thanks
Re: Times in the AVIS bridge

Glenn McClements <gmcclements@...>
 

Hi Mark,
There are some know issues with the Avis support, some architectural, some issues in the bridge and some within Avis itself, all of which which is not good it has to be said. The two biggest problem areas are: 

- timers
- lack of vector support in Avis

Rather than spend time fixing the Avis implementation I'm currently working with Red Hat and concentrating on making the AMQP Qpid bridges a "best practice" open source implementation. Avis will then be deprecated. 

Qpid does support vectors and overall ia a far better middleware, so in the long term this will be better for everyone but please do bear with us as we make the transition. 

Glenn 

From: Mark Perkin <mark@...>
Date: Thu, 17 Jan 2013 13:01:39 +0000
To: <openmama-users@...>
Subject: [Openmama-users] Times in the AVIS bridge

Hi All,

I recently grabbed the latest openmama and built it on CentOS 6.3. When I run the C unit tests using AVIS:

./UnitTestMamaC -m avis -p avismsg

It core dumps.

I've looked at the avis timer code and its clear that there are some serious threading problems - impl objects shared across threads without any synchronization, impl objects getting freed  in one thread then  later dereferenced, multiple frees of the same impl, etc.

Are these known issues and if so, is anyone working to fix the avis bridge code? I was thinking of starting to fix these but my concern is that the whole avis bridge code base my be in a poor state and I'd be diving down a rats nest.

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

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Times in the AVIS bridge

Mark Perkin <mark@...>
 

Hi All,

I recently grabbed the latest openmama and built it on CentOS 6.3. When I run the C unit tests using AVIS:

./UnitTestMamaC -m avis -p avismsg

It core dumps.

I've looked at the avis timer code and its clear that there are some serious threading problems - impl objects shared across threads without any synchronization, impl objects getting freed  in one thread then  later dereferenced, multiple frees of the same impl, etc.

Are these known issues and if so, is anyone working to fix the avis bridge code? I was thinking of starting to fix these but my concern is that the whole avis bridge code base my be in a poor state and I'd be diving down a rats nest.

Mark
Re: Algorithm (OpenMAMA)

Glenn McClements <gmcclements@...>
 

Hi Shoyaib,
That is quite an open ended question, and one that is probably beyond the scope of this list. 

Can you give any more detail on what exactly you are trying to do and I'll try to answer your question?

Glenn 

From: Shoyaib Hossain <shoyaib0088@...>
Reply-To: Shoyaib Hossain <shoyaib0088@...>
Date: Fri, 11 Jan 2013 19:46:34 -0800
To: "Openmama-users@..." <Openmama-users@...>
Subject: [Openmama-users] Algorithm (OpenMAMA)

Dear Sir/Madam

I am going to implement a software (data entry/routing) using OpenMAMA and Avis software.  Can you kindly tell me what type of software algorithm will be the best to implement the software (data entry/routing).

Thanks

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

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Algorithm (OpenMAMA)

shoyaib
 

Dear Sir/Madam

I am going to implement a software (data entry/routing) using OpenMAMA and Avis software.  Can you kindly tell me what type of software algorithm will be the best to implement the software (data entry/routing).

Thanks
Re: Fw: OpenMAMA and Avis building problem

Jacobraj Benet <JBenet@...>
 

Hi Shoyaib,

Can you make sure that you have the JAVA_HOME set to the home folder of the Java install, as the error seem to be around the missing jni.h header file.

mamajniutils.h:25:17: fatal error: jni.h: No such file or directory

I am also assuming that you are executing the generateBuildFile.sh script before running the configure.

./generateBuildFiles.sh
./configure —prefix= --avis-path=
make mamajni
make mamajni-install

The above should build mamajni libraries.

Hope this helps,

Thanks,

-- 

Jacob


From: Shoyaib Hossain <shoyaib0088@...>
Reply-To: Shoyaib Hossain <shoyaib0088@...>
Date: Thursday, January 10, 2013 9:56 PM
To: "Openmama-users@..." <Openmama-users@...>
Subject: [Openmama-users] Fw: OpenMAMA and Avis building problem


----- Forwarded Message -----

From: Shoyaib Hossain <shoyaib0088@...>
To: "Openmama-users@..." <Openmama-users@...>
Sent: Friday, 11 January 2013, 2:10
Subject: OpenMAMA and Avis building problem

Dear Sir/Madam

I am trying to build OpenMAMA and Avis on Ubuntu.  However when i try to compile OpenMAMA and execute the following commands then i found some problems such as "mamajni" and "mamadajni" are not found.

>./configure
>make
>sudo make install

Therefore i have installed Java JDK 7 and Avis client and router library.
I have attached the errors that i have found from the terminal.

I am looking forward to your response.


Thanks


Please consider the environment before printing this email.

Visit our website at http://www.nyse.com
*****************************************************************************
Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to 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 the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Euronext.

Market Data dictionary and Market Data publisher for OpenMAMDA

Hien Nguyen <hien.nguyen@...>
 

Hi,

 

I’m doing some studies on OpenMAMA and OpenMAMDA.

So far, I have configured OpenMAMA with Avis successfully. I can send and receive normal data with OpenMAMA now.

 

For the next step, I want to explore OpenMAMDA but I cannot figure out by myself which format market data dictionary is required by OpenMAMDA and how to publish market data.

Could you please point me to some documents to read for more details or give me some examples on that (I have finished OpenMAMA & OpenMAMDA developer guide but it doesn’t help me much in working with market data dictionary & market data publishing)

 

Thank you very much.

 

Best Regards,

Hien

 

Nguyen Hong Hien

Consultant

+65 8220 2751

hien.nguyen@...

 
Fw: OpenMAMA and Avis building problem

shoyaib
 


----- Forwarded Message -----

From: Shoyaib Hossain <shoyaib0088@...>
To: "Openmama-users@..." <Openmama-users@...>
Sent: Friday, 11 January 2013, 2:10
Subject: OpenMAMA and Avis building problem

Dear Sir/Madam

I am trying to build OpenMAMA and Avis on Ubuntu.  However when i try to compile OpenMAMA and execute the following commands then i found some problems such as "mamajni" and "mamadajni" are not found.

>./configure
>make
>sudo make install

Therefore i have installed Java JDK 7 and Avis client and router library.
I have attached the errors that i have found from the terminal.

I am looking forward to your response.


Thanks


?
OpenMAMA .odt

OpenMAMA and Avis building problem

shoyaib
 

Dear Sir/Madam

I am trying to build OpenMAMA and Avis on Ubuntu.  However when i try to compile OpenMAMA and execute the following commands then i found some problems such as "mamajni" and "mamadajni" are not found.

>./configure
>make
>sudo make install

Therefore i have installed Java JDK 7 and Avis client and router library.
I have attached the errors that i have found from the terminal.

I am looking forward to your response.


Thanks

?
OpenMAMA .odt

Re: NO_BRIDGE_IMPL() issue (avis is compiled/linked properly)

Gagan Sidhu <gagan@...>
 

On 2012-11-29, at 12:31 PM, Philip Preston <PPreston@nyx.com> wrote:

Ah if you have that semaphore sorted then it may just be the LIB_EXTENSION. That's in port.h in the environment specific folders in wombatcommon. Its set to .so for linux so I'd created a mac specific folder with its own port.h setting the LIB_EXTENSION to dylib.
worked like a charm! Thanks Phil. My gosh, that's all it was :)

now to figure out how to use this and take over the world mwahahahahahha :)



Philip Preston
NYSE Technologies

Adelaide Exchange
24-26 Adelaide St
Belfast, BT2 8GD
United Kingdom

t: +44 (0) 2890 822 091
m: +44 (0) 7903 300307
e: ppreston@nyx.com

NYSE Euronext
Powering the Exchanging World
www.nyse.com/technologies
_

----- Original Message -----
From: Gagan Sidhu [mailto:gagan@g-a.ca]
Sent: Thursday, November 29, 2012 07:24 PM
To: openmama-users@lists.openmama.org <openmama-users@lists.openmama.org>
Subject: Re: [Openmama-users] NO_BRIDGE_IMPL() issue (avis is compiled/linked properly)


Hi Phil,

On 2012-11-29, at 12:17 PM, Philip Preston <PPreston@nyx.com> wrote:

Gagan

It will compile - but the programs won't work because mac os x does not fully implement posix semaphores, and as such it silently fails. Also it won't load the bridge in the example apps unless you change the LIB_EXTENSION to .dylib (if you haven't already).
which library? Right now they look like this:

GagansMacPro:c Gagan$ ls -lh /usr/local/lib/libavis.*
lrwxr-xr-x 1 root wheel 15B 25 Nov 17:40 /usr/local/lib/libavis.0.0.0.dylib -> libavis.0.dylib
-rwxr-xr-x 1 root wheel 86K 25 Nov 17:40 /usr/local/lib/libavis.0.dylib
-rw-r--r-- 1 root wheel 298K 25 Nov 17:40 /usr/local/lib/libavis.a
lrwxr-xr-x 1 root wheel 15B 25 Nov 17:40 /usr/local/lib/libavis.dylib -> libavis.0.dylib
-rwxr-xr-x 1 root wheel 932B 25 Nov 17:40 /usr/local/lib/libavis.la


GagansMacPro:c Gagan$ ls -lh /opt/openmama/lib
total 41976
-rwxr-xr-x 1 root admin 591K 26 Nov 16:28 libmama.0.0.0.dylib
lrwxr-xr-x 1 root admin 19B 26 Nov 16:28 libmama.0.dylib -> libmama.0.0.0.dylib
-rw-r--r-- 1 root admin 2.0M 26 Nov 16:28 libmama.a
lrwxr-xr-x 1 root admin 19B 26 Nov 16:28 libmama.dylib -> libmama.0.0.0.dylib
-rwxr-xr-x 1 root admin 917B 26 Nov 16:28 libmama.la
-rwxr-xr-x 1 root admin 63K 26 Nov 16:28 libmamaavisimpl.0.0.0.dylib
lrwxr-xr-x 1 root admin 27B 26 Nov 16:28 libmamaavisimpl.0.dylib -> libmamaavisimpl.0.0.0.dylib
-rw-r--r-- 1 root admin 183K 26 Nov 16:28 libmamaavisimpl.a
lrwxr-xr-x 1 root admin 27B 26 Nov 16:28 libmamaavisimpl.dylib -> libmamaavisimpl.0.0.0.dylib
-rwxr-xr-x 1 root admin 1.1K 26 Nov 16:28 libmamaavisimpl.la
-rwxr-xr-x 1 root admin 101K 26 Nov 16:28 libmamaavismsgimpl.0.0.0.dylib
lrwxr-xr-x 1 root admin 30B 26 Nov 16:28 libmamaavismsgimpl.0.dylib -> libmamaavismsgimpl.0.0.0.dylib
-rw-r--r-- 1 root admin 294K 26 Nov 16:28 libmamaavismsgimpl.a
lrwxr-xr-x 1 root admin 30B 26 Nov 16:28 libmamaavismsgimpl.dylib -> libmamaavismsgimpl.0.0.0.dylib
-rwxr-xr-x 1 root admin 1.1K 26 Nov 16:28 libmamaavismsgimpl.la
-rwxr-xr-x 1 root admin 696K 26 Nov 16:28 libmamacpp.0.0.0.dylib
lrwxr-xr-x 1 root admin 22B 26 Nov 16:28 libmamacpp.0.dylib -> libmamacpp.0.0.0.dylib
-rw-r--r-- 1 root admin 3.9M 26 Nov 16:28 libmamacpp.a
lrwxr-xr-x 1 root admin 22B 26 Nov 16:28 libmamacpp.dylib -> libmamacpp.0.0.0.dylib
-rwxr-xr-x 1 root admin 891B 26 Nov 16:28 libmamacpp.la
-rwxr-xr-x 1 root admin 1.6M 26 Nov 16:29 libmamda.0.0.0.dylib
lrwxr-xr-x 1 root admin 20B 26 Nov 16:29 libmamda.0.dylib -> libmamda.0.0.0.dylib
-rw-r--r-- 1 root admin 5.7M 26 Nov 16:29 libmamda.a
lrwxr-xr-x 1 root admin 20B 26 Nov 16:29 libmamda.dylib -> libmamda.0.0.0.dylib
-rwxr-xr-x 1 root admin 865B 26 Nov 16:29 libmamda.la
-rwxr-xr-x 1 root admin 164K 26 Nov 16:30 libmamdanews.0.0.0.dylib
lrwxr-xr-x 1 root admin 24B 26 Nov 16:30 libmamdanews.0.dylib -> libmamdanews.0.0.0.dylib
-rw-r--r-- 1 root admin 879K 26 Nov 16:30 libmamdanews.a
lrwxr-xr-x 1 root admin 24B 26 Nov 16:30 libmamdanews.dylib -> libmamdanews.0.0.0.dylib
-rwxr-xr-x 1 root admin 893B 26 Nov 16:30 libmamdanews.la
-rwxr-xr-x 1 root admin 192K 26 Nov 16:30 libmamdaoptions.0.0.0.dylib
lrwxr-xr-x 1 root admin 27B 26 Nov 16:30 libmamdaoptions.0.dylib -> libmamdaoptions.0.0.0.dylib
-rw-r--r-- 1 root admin 1.8M 26 Nov 16:30 libmamdaoptions.a
lrwxr-xr-x 1 root admin 27B 26 Nov 16:30 libmamdaoptions.dylib -> libmamdaoptions.0.0.0.dylib
-rwxr-xr-x 1 root admin 914B 26 Nov 16:30 libmamdaoptions.la
-rw-r--r-- 1 root admin 387K 26 Nov 16:28 libwombatcommon.a
-rwxr-xr-x 1 root admin 798B 26 Nov 16:28 libwombatcommon.la
-rw-r--r-- 1 root admin 11K 26 Nov 16:28 libwombatcommoncpp.a
-rwxr-xr-x 1 root admin 801B 26 Nov 16:28 libwombatcommoncpp.la
-rw-r--r-- 1 root admin 161K 26 Nov 16:29 mamajni.jar
-rw-r--r-- 1 root admin 161K 26 Nov 16:29 mamajni_2.2.1.1.jar
-rw-r--r-- 1 root admin 352K 26 Nov 16:30 mamda.jar
-rw-r--r-- 1 root admin 352K 26 Nov 16:30 mamda_2.2.1.1_jdk1.7.0_07.jar
-rw-r--r-- 1 root admin 207K 26 Nov 16:30 mamda_2.2.1.1_jdk1.7.0_07_book.jar
-rw-r--r-- 1 root admin 245K 26 Nov 16:30 mamda_2.2.1.1_jdk1.7.0_07_options.jar
-rw-r--r-- 1 root admin 207K 26 Nov 16:30 mamda_book.jar
-rw-r--r-- 1 root admin 245K 26 Nov 16:30 mamda_options.jar


The function calls exist for posix unnamed semaphores on mac but return error codes indicate they are not implemented - mama doesn't log the failure cause its not an issue on any of the officially supported os. This stops any of the queues working. You can work around this by implementing named semaphores. I'd made some changes to do this for openmama1 and have got most of moved to a local openmama2, following the breakout of platforms in wombatcommon. Have added a darwin folder with appropriate changes.
this is correct. usually it would then compile with -DNO_SEM_TIMEDWAIT, however I found someone who wrote code that mimics sem_timedwait for OSX, so I included that header file in wSemaphore.c and that made the issue wrt semaphores and timedwait go away.

Happy to pass it on once I get time to finish / tidy it up. Also had it setup in xcode.
Cool. But *if* that code I'm using is working correctly, then the queue issue wouldn't be the root cause of the errors below, no?

Do I need to edit the source files of mama to ensure it's trying to use .dylibs instead of the unix suffix?

Cheers

Phil

Philip Preston
NYSE Technologies

Adelaide Exchange
24-26 Adelaide St
Belfast, BT2 8GD
United Kingdom

t: +44 (0) 2890 822 091
m: +44 (0) 7903 300307
e: ppreston@nyx.com

NYSE Euronext
Powering the Exchanging World
www.nyse.com/technologies
_

----- Original Message -----
From: Gagan Sidhu [mailto:gagan@g-a.ca]
Sent: Thursday, November 29, 2012 06:08 PM
To: openmama-users@lists.openmama.org <openmama-users@lists.openmama.org>
Subject: Re: [Openmama-users] NO_BRIDGE_IMPL() issue (avis is compiled/linked properly)

Hey Glen,

On 2012-11-29, at 10:58 AM, Glenn McClements <gmcclements@nyx.com> wrote:

Hi Gigan,
This looks like the avis bridge lib isn't in being loaded for some reason
(FYI bridge libraries are dynamical *loaded* using dlopen() not
dynamically linked). Is the bridge library and the AVIS in your
DYLD_LIBRARY_PATH? Also putting mamalistenc in full verbose mode may give
more info, i.e:

./mamalistenc -m avis -v -v -v -v

As you said, OSX isn't currently supported but I do know of some people
who have tried in the past and did manage to get something up and running.
yeah, theoretically speaking there is not much of a difference in the required libs.
I installed avis in /usr/local so /usr/local/include contains the avis folder, and /usr/local/lib contains libavis
I didn't export DYLD_LIBRARY_PATH till now, but it looks like this:

GagansMacPro:c Gagan$ echo $DYLD_LIBRARY_PATH
/opt/openmama/lib:/usr/local/lib:

and changing -lmamaavisimpl to -lavis and re-compiling with Makefile -f sMakefile.sample still gets the same sort of issue.
I've tried -v -v -v -v before because will henry suggested it, but that didn't work:

GagansMacPro:c Gagan$ ./mamalistenc -m avis -v -v -v -v
Enter one symbol per line and terminate with a .
Symbol> .
Could not open MAMA avis bridge.

Given that the verbose output doesn't work, I'm really puzzled as to what is causing the issue.

Is there a way to check that the compiled libraries have everything?

FYI: I am new to the whole "trading" thing. I do not have any avis servers or anything like that setup, just the client installed.

I'm wondering why the examples say tiprv/elvin/one other oen, but do not mention avis? I assume elvin is avis but just slightly different.

In any case, is there a way to check the "integrity" of the libraries first? They must be the issue, as the programs compile fine but are failing to load the bridge.



Did you make any other changes to get it building on OSX? If so, and
provided other platforms aren't affected of course, then I'd be happy to
apply them. I can't see NYSE ever supporting this in their commercial
distribution as there isn't a demand for it with their customers, but for
the open source project additional platform support can only be a good
thing.
I agree, but I want to hold off on sharing those changes until we can ensure the build works properly.
They are small changes here and there, but most definitely should not be the reason for the error.

-gAgan ;)

Glenn


On 29/11/2012 17:13, "Gagan Sidhu" <gagan@g-a.ca> wrote:

Hi guys,

Currently I'm on OSX and trying to build the openMAMA libs for my system.

I understand that OSX is not officially supported, but the issue I'm
experiencing is not specific to this platform.

Specifically, I build and install the avis client, copy the config_h to
the suggested directories, and proceed to build mama.

The build and linking goes fine, from what I can see, however the example
programs do *not* work.

I have compiled each one using a slightly modified Makefile.sample (no
-lrt flag or -Xlinker before the -Bstatic/-Bdynamic).

This issue is very strange, because I saw someone else had a bridge issue
but the linked library spit out an error. All I see is:

here's the dump:

GagansMacPro:c Gagan$ make -f Makefile.sample
gcc -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamapublisherc mamapublisherc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamasubscriberc.o mamasubscriberc.c
mamasubscriberc.c: In function ŒwildCardMsgCb¹:
mamasubscriberc.c:280:56: warning: cast to pointer from integer of
different size [-Wint-to-pointer-cast]
mamasubscriberc.c:285:13: warning: cast from pointer to integer of
different size [-Wpointer-to-int-cast]
gcc -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamasubscriberc mamasubscriberc.o -Bstatic -lmamaavisimpl -lmama
-Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamasymbollistsubscriberc.o
mamasymbollistsubscriberc.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamasymbollistsubscriberc mamasymbollistsubscriberc.o -Bstatic
-lmamaavisimpl -lmama -Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamaproxyc.o mamaproxyc.c
mamaproxyc.c: In function ŒsubscribeToSymbols¹:
mamaproxyc.c:230:34: warning: cast to pointer from integer of different
size [-Wint-to-pointer-cast]
mamaproxyc.c: In function ŒsubscriptionHandlerOnNewRequestCb¹:
mamaproxyc.c:354:62: warning: cast to pointer from integer of different
size [-Wint-to-pointer-cast]
mamaproxyc.c: In function ŒsubscriptionHandlerOnRequestCb¹:
mamaproxyc.c:422:26: warning: cast from pointer to integer of different
size [-Wpointer-to-int-cast]
mamaproxyc.c:435:26: warning: cast from pointer to integer of different
size [-Wpointer-to-int-cast]
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamaproxyc mamaproxyc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamaio.o mamaio.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o mamaio
mamaio.o -Bstatic -lmamaavisimpl -lmama -Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamamultisubscriberc.o
mamamultisubscriberc.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamamultisubscriberc mamamultisubscriberc.o -Bstatic -lmamaavisimpl
-lmama -Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamaftmemberc.o mamaftmemberc.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamaftmemberc mamaftmemberc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
GagansMacPro:c Gagan$ ./mamalistenc
Enter one symbol per line and terminate with a .
Symbol> ,
Symbol> .
Could not open MAMA wmw bridge.
GagansMacPro:c Gagan$ ./mamalistenc -m avis
Enter one symbol per line and terminate with a .
Symbol> .
Could not open MAMA avis bridge.
Thanks,
Gagan Sidhu,
Director, General Analytics (GA) Inc.

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

________________________________

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
_______________________________________________
Openmama-users mailing list
Openmama-users@lists.openmama.org
https://lists.openmama.org/mailman/listinfo/openmama-users

________________________________

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
_______________________________________________
Openmama-users mailing list
Openmama-users@lists.openmama.org
https://lists.openmama.org/mailman/listinfo/openmama-users

________________________________

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Re: NO_BRIDGE_IMPL() issue (avis is compiled/linked properly)

Philip Preston <PPreston@...>
 

Ah if you have that semaphore sorted then it may just be the LIB_EXTENSION. That's in port.h in the environment specific folders in wombatcommon. Its set to .so for linux so I'd created a mac specific folder with its own port.h setting the LIB_EXTENSION to dylib.



Philip Preston
NYSE Technologies

Adelaide Exchange
24-26 Adelaide St
Belfast, BT2 8GD
United Kingdom

t: +44 (0) 2890 822 091
m: +44 (0) 7903 300307
e: ppreston@nyx.com

NYSE Euronext
Powering the Exchanging World
www.nyse.com/technologies
_

----- Original Message -----
From: Gagan Sidhu [mailto:gagan@g-a.ca]
Sent: Thursday, November 29, 2012 07:24 PM
To: openmama-users@lists.openmama.org <openmama-users@lists.openmama.org>
Subject: Re: [Openmama-users] NO_BRIDGE_IMPL() issue (avis is compiled/linked properly)


Hi Phil,

On 2012-11-29, at 12:17 PM, Philip Preston <PPreston@nyx.com> wrote:

Gagan

It will compile - but the programs won't work because mac os x does not fully implement posix semaphores, and as such it silently fails. Also it won't load the bridge in the example apps unless you change the LIB_EXTENSION to .dylib (if you haven't already).
which library? Right now they look like this:

GagansMacPro:c Gagan$ ls -lh /usr/local/lib/libavis.*
lrwxr-xr-x 1 root wheel 15B 25 Nov 17:40 /usr/local/lib/libavis.0.0.0.dylib -> libavis.0.dylib
-rwxr-xr-x 1 root wheel 86K 25 Nov 17:40 /usr/local/lib/libavis.0.dylib
-rw-r--r-- 1 root wheel 298K 25 Nov 17:40 /usr/local/lib/libavis.a
lrwxr-xr-x 1 root wheel 15B 25 Nov 17:40 /usr/local/lib/libavis.dylib -> libavis.0.dylib
-rwxr-xr-x 1 root wheel 932B 25 Nov 17:40 /usr/local/lib/libavis.la


GagansMacPro:c Gagan$ ls -lh /opt/openmama/lib
total 41976
-rwxr-xr-x 1 root admin 591K 26 Nov 16:28 libmama.0.0.0.dylib
lrwxr-xr-x 1 root admin 19B 26 Nov 16:28 libmama.0.dylib -> libmama.0.0.0.dylib
-rw-r--r-- 1 root admin 2.0M 26 Nov 16:28 libmama.a
lrwxr-xr-x 1 root admin 19B 26 Nov 16:28 libmama.dylib -> libmama.0.0.0.dylib
-rwxr-xr-x 1 root admin 917B 26 Nov 16:28 libmama.la
-rwxr-xr-x 1 root admin 63K 26 Nov 16:28 libmamaavisimpl.0.0.0.dylib
lrwxr-xr-x 1 root admin 27B 26 Nov 16:28 libmamaavisimpl.0.dylib -> libmamaavisimpl.0.0.0.dylib
-rw-r--r-- 1 root admin 183K 26 Nov 16:28 libmamaavisimpl.a
lrwxr-xr-x 1 root admin 27B 26 Nov 16:28 libmamaavisimpl.dylib -> libmamaavisimpl.0.0.0.dylib
-rwxr-xr-x 1 root admin 1.1K 26 Nov 16:28 libmamaavisimpl.la
-rwxr-xr-x 1 root admin 101K 26 Nov 16:28 libmamaavismsgimpl.0.0.0.dylib
lrwxr-xr-x 1 root admin 30B 26 Nov 16:28 libmamaavismsgimpl.0.dylib -> libmamaavismsgimpl.0.0.0.dylib
-rw-r--r-- 1 root admin 294K 26 Nov 16:28 libmamaavismsgimpl.a
lrwxr-xr-x 1 root admin 30B 26 Nov 16:28 libmamaavismsgimpl.dylib -> libmamaavismsgimpl.0.0.0.dylib
-rwxr-xr-x 1 root admin 1.1K 26 Nov 16:28 libmamaavismsgimpl.la
-rwxr-xr-x 1 root admin 696K 26 Nov 16:28 libmamacpp.0.0.0.dylib
lrwxr-xr-x 1 root admin 22B 26 Nov 16:28 libmamacpp.0.dylib -> libmamacpp.0.0.0.dylib
-rw-r--r-- 1 root admin 3.9M 26 Nov 16:28 libmamacpp.a
lrwxr-xr-x 1 root admin 22B 26 Nov 16:28 libmamacpp.dylib -> libmamacpp.0.0.0.dylib
-rwxr-xr-x 1 root admin 891B 26 Nov 16:28 libmamacpp.la
-rwxr-xr-x 1 root admin 1.6M 26 Nov 16:29 libmamda.0.0.0.dylib
lrwxr-xr-x 1 root admin 20B 26 Nov 16:29 libmamda.0.dylib -> libmamda.0.0.0.dylib
-rw-r--r-- 1 root admin 5.7M 26 Nov 16:29 libmamda.a
lrwxr-xr-x 1 root admin 20B 26 Nov 16:29 libmamda.dylib -> libmamda.0.0.0.dylib
-rwxr-xr-x 1 root admin 865B 26 Nov 16:29 libmamda.la
-rwxr-xr-x 1 root admin 164K 26 Nov 16:30 libmamdanews.0.0.0.dylib
lrwxr-xr-x 1 root admin 24B 26 Nov 16:30 libmamdanews.0.dylib -> libmamdanews.0.0.0.dylib
-rw-r--r-- 1 root admin 879K 26 Nov 16:30 libmamdanews.a
lrwxr-xr-x 1 root admin 24B 26 Nov 16:30 libmamdanews.dylib -> libmamdanews.0.0.0.dylib
-rwxr-xr-x 1 root admin 893B 26 Nov 16:30 libmamdanews.la
-rwxr-xr-x 1 root admin 192K 26 Nov 16:30 libmamdaoptions.0.0.0.dylib
lrwxr-xr-x 1 root admin 27B 26 Nov 16:30 libmamdaoptions.0.dylib -> libmamdaoptions.0.0.0.dylib
-rw-r--r-- 1 root admin 1.8M 26 Nov 16:30 libmamdaoptions.a
lrwxr-xr-x 1 root admin 27B 26 Nov 16:30 libmamdaoptions.dylib -> libmamdaoptions.0.0.0.dylib
-rwxr-xr-x 1 root admin 914B 26 Nov 16:30 libmamdaoptions.la
-rw-r--r-- 1 root admin 387K 26 Nov 16:28 libwombatcommon.a
-rwxr-xr-x 1 root admin 798B 26 Nov 16:28 libwombatcommon.la
-rw-r--r-- 1 root admin 11K 26 Nov 16:28 libwombatcommoncpp.a
-rwxr-xr-x 1 root admin 801B 26 Nov 16:28 libwombatcommoncpp.la
-rw-r--r-- 1 root admin 161K 26 Nov 16:29 mamajni.jar
-rw-r--r-- 1 root admin 161K 26 Nov 16:29 mamajni_2.2.1.1.jar
-rw-r--r-- 1 root admin 352K 26 Nov 16:30 mamda.jar
-rw-r--r-- 1 root admin 352K 26 Nov 16:30 mamda_2.2.1.1_jdk1.7.0_07.jar
-rw-r--r-- 1 root admin 207K 26 Nov 16:30 mamda_2.2.1.1_jdk1.7.0_07_book.jar
-rw-r--r-- 1 root admin 245K 26 Nov 16:30 mamda_2.2.1.1_jdk1.7.0_07_options.jar
-rw-r--r-- 1 root admin 207K 26 Nov 16:30 mamda_book.jar
-rw-r--r-- 1 root admin 245K 26 Nov 16:30 mamda_options.jar


The function calls exist for posix unnamed semaphores on mac but return error codes indicate they are not implemented - mama doesn't log the failure cause its not an issue on any of the officially supported os. This stops any of the queues working. You can work around this by implementing named semaphores. I'd made some changes to do this for openmama1 and have got most of moved to a local openmama2, following the breakout of platforms in wombatcommon. Have added a darwin folder with appropriate changes.
this is correct. usually it would then compile with -DNO_SEM_TIMEDWAIT, however I found someone who wrote code that mimics sem_timedwait for OSX, so I included that header file in wSemaphore.c and that made the issue wrt semaphores and timedwait go away.

Happy to pass it on once I get time to finish / tidy it up. Also had it setup in xcode.
Cool. But *if* that code I'm using is working correctly, then the queue issue wouldn't be the root cause of the errors below, no?

Do I need to edit the source files of mama to ensure it's trying to use .dylibs instead of the unix suffix?

Cheers

Phil

Philip Preston
NYSE Technologies

Adelaide Exchange
24-26 Adelaide St
Belfast, BT2 8GD
United Kingdom

t: +44 (0) 2890 822 091
m: +44 (0) 7903 300307
e: ppreston@nyx.com

NYSE Euronext
Powering the Exchanging World
www.nyse.com/technologies
_

----- Original Message -----
From: Gagan Sidhu [mailto:gagan@g-a.ca]
Sent: Thursday, November 29, 2012 06:08 PM
To: openmama-users@lists.openmama.org <openmama-users@lists.openmama.org>
Subject: Re: [Openmama-users] NO_BRIDGE_IMPL() issue (avis is compiled/linked properly)

Hey Glen,

On 2012-11-29, at 10:58 AM, Glenn McClements <gmcclements@nyx.com> wrote:

Hi Gigan,
This looks like the avis bridge lib isn't in being loaded for some reason
(FYI bridge libraries are dynamical *loaded* using dlopen() not
dynamically linked). Is the bridge library and the AVIS in your
DYLD_LIBRARY_PATH? Also putting mamalistenc in full verbose mode may give
more info, i.e:

./mamalistenc -m avis -v -v -v -v

As you said, OSX isn't currently supported but I do know of some people
who have tried in the past and did manage to get something up and running.
yeah, theoretically speaking there is not much of a difference in the required libs.
I installed avis in /usr/local so /usr/local/include contains the avis folder, and /usr/local/lib contains libavis
I didn't export DYLD_LIBRARY_PATH till now, but it looks like this:

GagansMacPro:c Gagan$ echo $DYLD_LIBRARY_PATH
/opt/openmama/lib:/usr/local/lib:

and changing -lmamaavisimpl to -lavis and re-compiling with Makefile -f sMakefile.sample still gets the same sort of issue.
I've tried -v -v -v -v before because will henry suggested it, but that didn't work:

GagansMacPro:c Gagan$ ./mamalistenc -m avis -v -v -v -v
Enter one symbol per line and terminate with a .
Symbol> .
Could not open MAMA avis bridge.

Given that the verbose output doesn't work, I'm really puzzled as to what is causing the issue.

Is there a way to check that the compiled libraries have everything?

FYI: I am new to the whole "trading" thing. I do not have any avis servers or anything like that setup, just the client installed.

I'm wondering why the examples say tiprv/elvin/one other oen, but do not mention avis? I assume elvin is avis but just slightly different.

In any case, is there a way to check the "integrity" of the libraries first? They must be the issue, as the programs compile fine but are failing to load the bridge.



Did you make any other changes to get it building on OSX? If so, and
provided other platforms aren't affected of course, then I'd be happy to
apply them. I can't see NYSE ever supporting this in their commercial
distribution as there isn't a demand for it with their customers, but for
the open source project additional platform support can only be a good
thing.
I agree, but I want to hold off on sharing those changes until we can ensure the build works properly.
They are small changes here and there, but most definitely should not be the reason for the error.

-gAgan ;)

Glenn


On 29/11/2012 17:13, "Gagan Sidhu" <gagan@g-a.ca> wrote:

Hi guys,

Currently I'm on OSX and trying to build the openMAMA libs for my system.

I understand that OSX is not officially supported, but the issue I'm
experiencing is not specific to this platform.

Specifically, I build and install the avis client, copy the config_h to
the suggested directories, and proceed to build mama.

The build and linking goes fine, from what I can see, however the example
programs do *not* work.

I have compiled each one using a slightly modified Makefile.sample (no
-lrt flag or -Xlinker before the -Bstatic/-Bdynamic).

This issue is very strange, because I saw someone else had a bridge issue
but the linked library spit out an error. All I see is:

here's the dump:

GagansMacPro:c Gagan$ make -f Makefile.sample
gcc -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamapublisherc mamapublisherc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamasubscriberc.o mamasubscriberc.c
mamasubscriberc.c: In function ŒwildCardMsgCb¹:
mamasubscriberc.c:280:56: warning: cast to pointer from integer of
different size [-Wint-to-pointer-cast]
mamasubscriberc.c:285:13: warning: cast from pointer to integer of
different size [-Wpointer-to-int-cast]
gcc -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamasubscriberc mamasubscriberc.o -Bstatic -lmamaavisimpl -lmama
-Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamasymbollistsubscriberc.o
mamasymbollistsubscriberc.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamasymbollistsubscriberc mamasymbollistsubscriberc.o -Bstatic
-lmamaavisimpl -lmama -Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamaproxyc.o mamaproxyc.c
mamaproxyc.c: In function ŒsubscribeToSymbols¹:
mamaproxyc.c:230:34: warning: cast to pointer from integer of different
size [-Wint-to-pointer-cast]
mamaproxyc.c: In function ŒsubscriptionHandlerOnNewRequestCb¹:
mamaproxyc.c:354:62: warning: cast to pointer from integer of different
size [-Wint-to-pointer-cast]
mamaproxyc.c: In function ŒsubscriptionHandlerOnRequestCb¹:
mamaproxyc.c:422:26: warning: cast from pointer to integer of different
size [-Wpointer-to-int-cast]
mamaproxyc.c:435:26: warning: cast from pointer to integer of different
size [-Wpointer-to-int-cast]
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamaproxyc mamaproxyc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamaio.o mamaio.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o mamaio
mamaio.o -Bstatic -lmamaavisimpl -lmama -Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamamultisubscriberc.o
mamamultisubscriberc.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamamultisubscriberc mamamultisubscriberc.o -Bstatic -lmamaavisimpl
-lmama -Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamaftmemberc.o mamaftmemberc.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamaftmemberc mamaftmemberc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
GagansMacPro:c Gagan$ ./mamalistenc
Enter one symbol per line and terminate with a .
Symbol> ,
Symbol> .
Could not open MAMA wmw bridge.
GagansMacPro:c Gagan$ ./mamalistenc -m avis
Enter one symbol per line and terminate with a .
Symbol> .
Could not open MAMA avis bridge.
Thanks,
Gagan Sidhu,
Director, General Analytics (GA) Inc.

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

________________________________

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
_______________________________________________
Openmama-users mailing list
Openmama-users@lists.openmama.org
https://lists.openmama.org/mailman/listinfo/openmama-users

________________________________

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
_______________________________________________
Openmama-users mailing list
Openmama-users@lists.openmama.org
https://lists.openmama.org/mailman/listinfo/openmama-users

________________________________

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Re: NO_BRIDGE_IMPL() issue (avis is compiled/linked properly)

Gagan Sidhu <gagan@...>
 

Hi Phil,

On 2012-11-29, at 12:17 PM, Philip Preston <PPreston@nyx.com> wrote:

Gagan

It will compile - but the programs won't work because mac os x does not fully implement posix semaphores, and as such it silently fails. Also it won't load the bridge in the example apps unless you change the LIB_EXTENSION to .dylib (if you haven't already).
which library? Right now they look like this:

GagansMacPro:c Gagan$ ls -lh /usr/local/lib/libavis.*
lrwxr-xr-x 1 root wheel 15B 25 Nov 17:40 /usr/local/lib/libavis.0.0.0.dylib -> libavis.0.dylib
-rwxr-xr-x 1 root wheel 86K 25 Nov 17:40 /usr/local/lib/libavis.0.dylib
-rw-r--r-- 1 root wheel 298K 25 Nov 17:40 /usr/local/lib/libavis.a
lrwxr-xr-x 1 root wheel 15B 25 Nov 17:40 /usr/local/lib/libavis.dylib -> libavis.0.dylib
-rwxr-xr-x 1 root wheel 932B 25 Nov 17:40 /usr/local/lib/libavis.la


GagansMacPro:c Gagan$ ls -lh /opt/openmama/lib
total 41976
-rwxr-xr-x 1 root admin 591K 26 Nov 16:28 libmama.0.0.0.dylib
lrwxr-xr-x 1 root admin 19B 26 Nov 16:28 libmama.0.dylib -> libmama.0.0.0.dylib
-rw-r--r-- 1 root admin 2.0M 26 Nov 16:28 libmama.a
lrwxr-xr-x 1 root admin 19B 26 Nov 16:28 libmama.dylib -> libmama.0.0.0.dylib
-rwxr-xr-x 1 root admin 917B 26 Nov 16:28 libmama.la
-rwxr-xr-x 1 root admin 63K 26 Nov 16:28 libmamaavisimpl.0.0.0.dylib
lrwxr-xr-x 1 root admin 27B 26 Nov 16:28 libmamaavisimpl.0.dylib -> libmamaavisimpl.0.0.0.dylib
-rw-r--r-- 1 root admin 183K 26 Nov 16:28 libmamaavisimpl.a
lrwxr-xr-x 1 root admin 27B 26 Nov 16:28 libmamaavisimpl.dylib -> libmamaavisimpl.0.0.0.dylib
-rwxr-xr-x 1 root admin 1.1K 26 Nov 16:28 libmamaavisimpl.la
-rwxr-xr-x 1 root admin 101K 26 Nov 16:28 libmamaavismsgimpl.0.0.0.dylib
lrwxr-xr-x 1 root admin 30B 26 Nov 16:28 libmamaavismsgimpl.0.dylib -> libmamaavismsgimpl.0.0.0.dylib
-rw-r--r-- 1 root admin 294K 26 Nov 16:28 libmamaavismsgimpl.a
lrwxr-xr-x 1 root admin 30B 26 Nov 16:28 libmamaavismsgimpl.dylib -> libmamaavismsgimpl.0.0.0.dylib
-rwxr-xr-x 1 root admin 1.1K 26 Nov 16:28 libmamaavismsgimpl.la
-rwxr-xr-x 1 root admin 696K 26 Nov 16:28 libmamacpp.0.0.0.dylib
lrwxr-xr-x 1 root admin 22B 26 Nov 16:28 libmamacpp.0.dylib -> libmamacpp.0.0.0.dylib
-rw-r--r-- 1 root admin 3.9M 26 Nov 16:28 libmamacpp.a
lrwxr-xr-x 1 root admin 22B 26 Nov 16:28 libmamacpp.dylib -> libmamacpp.0.0.0.dylib
-rwxr-xr-x 1 root admin 891B 26 Nov 16:28 libmamacpp.la
-rwxr-xr-x 1 root admin 1.6M 26 Nov 16:29 libmamda.0.0.0.dylib
lrwxr-xr-x 1 root admin 20B 26 Nov 16:29 libmamda.0.dylib -> libmamda.0.0.0.dylib
-rw-r--r-- 1 root admin 5.7M 26 Nov 16:29 libmamda.a
lrwxr-xr-x 1 root admin 20B 26 Nov 16:29 libmamda.dylib -> libmamda.0.0.0.dylib
-rwxr-xr-x 1 root admin 865B 26 Nov 16:29 libmamda.la
-rwxr-xr-x 1 root admin 164K 26 Nov 16:30 libmamdanews.0.0.0.dylib
lrwxr-xr-x 1 root admin 24B 26 Nov 16:30 libmamdanews.0.dylib -> libmamdanews.0.0.0.dylib
-rw-r--r-- 1 root admin 879K 26 Nov 16:30 libmamdanews.a
lrwxr-xr-x 1 root admin 24B 26 Nov 16:30 libmamdanews.dylib -> libmamdanews.0.0.0.dylib
-rwxr-xr-x 1 root admin 893B 26 Nov 16:30 libmamdanews.la
-rwxr-xr-x 1 root admin 192K 26 Nov 16:30 libmamdaoptions.0.0.0.dylib
lrwxr-xr-x 1 root admin 27B 26 Nov 16:30 libmamdaoptions.0.dylib -> libmamdaoptions.0.0.0.dylib
-rw-r--r-- 1 root admin 1.8M 26 Nov 16:30 libmamdaoptions.a
lrwxr-xr-x 1 root admin 27B 26 Nov 16:30 libmamdaoptions.dylib -> libmamdaoptions.0.0.0.dylib
-rwxr-xr-x 1 root admin 914B 26 Nov 16:30 libmamdaoptions.la
-rw-r--r-- 1 root admin 387K 26 Nov 16:28 libwombatcommon.a
-rwxr-xr-x 1 root admin 798B 26 Nov 16:28 libwombatcommon.la
-rw-r--r-- 1 root admin 11K 26 Nov 16:28 libwombatcommoncpp.a
-rwxr-xr-x 1 root admin 801B 26 Nov 16:28 libwombatcommoncpp.la
-rw-r--r-- 1 root admin 161K 26 Nov 16:29 mamajni.jar
-rw-r--r-- 1 root admin 161K 26 Nov 16:29 mamajni_2.2.1.1.jar
-rw-r--r-- 1 root admin 352K 26 Nov 16:30 mamda.jar
-rw-r--r-- 1 root admin 352K 26 Nov 16:30 mamda_2.2.1.1_jdk1.7.0_07.jar
-rw-r--r-- 1 root admin 207K 26 Nov 16:30 mamda_2.2.1.1_jdk1.7.0_07_book.jar
-rw-r--r-- 1 root admin 245K 26 Nov 16:30 mamda_2.2.1.1_jdk1.7.0_07_options.jar
-rw-r--r-- 1 root admin 207K 26 Nov 16:30 mamda_book.jar
-rw-r--r-- 1 root admin 245K 26 Nov 16:30 mamda_options.jar


The function calls exist for posix unnamed semaphores on mac but return error codes indicate they are not implemented - mama doesn't log the failure cause its not an issue on any of the officially supported os. This stops any of the queues working. You can work around this by implementing named semaphores. I'd made some changes to do this for openmama1 and have got most of moved to a local openmama2, following the breakout of platforms in wombatcommon. Have added a darwin folder with appropriate changes.
this is correct. usually it would then compile with -DNO_SEM_TIMEDWAIT, however I found someone who wrote code that mimics sem_timedwait for OSX, so I included that header file in wSemaphore.c and that made the issue wrt semaphores and timedwait go away.

Happy to pass it on once I get time to finish / tidy it up. Also had it setup in xcode.
Cool. But *if* that code I'm using is working correctly, then the queue issue wouldn't be the root cause of the errors below, no?

Do I need to edit the source files of mama to ensure it's trying to use .dylibs instead of the unix suffix?

Cheers

Phil

Philip Preston
NYSE Technologies

Adelaide Exchange
24-26 Adelaide St
Belfast, BT2 8GD
United Kingdom

t: +44 (0) 2890 822 091
m: +44 (0) 7903 300307
e: ppreston@nyx.com

NYSE Euronext
Powering the Exchanging World
www.nyse.com/technologies
_

----- Original Message -----
From: Gagan Sidhu [mailto:gagan@g-a.ca]
Sent: Thursday, November 29, 2012 06:08 PM
To: openmama-users@lists.openmama.org <openmama-users@lists.openmama.org>
Subject: Re: [Openmama-users] NO_BRIDGE_IMPL() issue (avis is compiled/linked properly)

Hey Glen,

On 2012-11-29, at 10:58 AM, Glenn McClements <gmcclements@nyx.com> wrote:

Hi Gigan,
This looks like the avis bridge lib isn't in being loaded for some reason
(FYI bridge libraries are dynamical *loaded* using dlopen() not
dynamically linked). Is the bridge library and the AVIS in your
DYLD_LIBRARY_PATH? Also putting mamalistenc in full verbose mode may give
more info, i.e:

./mamalistenc -m avis -v -v -v -v

As you said, OSX isn't currently supported but I do know of some people
who have tried in the past and did manage to get something up and running.
yeah, theoretically speaking there is not much of a difference in the required libs.
I installed avis in /usr/local so /usr/local/include contains the avis folder, and /usr/local/lib contains libavis
I didn't export DYLD_LIBRARY_PATH till now, but it looks like this:

GagansMacPro:c Gagan$ echo $DYLD_LIBRARY_PATH
/opt/openmama/lib:/usr/local/lib:

and changing -lmamaavisimpl to -lavis and re-compiling with Makefile -f sMakefile.sample still gets the same sort of issue.
I've tried -v -v -v -v before because will henry suggested it, but that didn't work:

GagansMacPro:c Gagan$ ./mamalistenc -m avis -v -v -v -v
Enter one symbol per line and terminate with a .
Symbol> .
Could not open MAMA avis bridge.

Given that the verbose output doesn't work, I'm really puzzled as to what is causing the issue.

Is there a way to check that the compiled libraries have everything?

FYI: I am new to the whole "trading" thing. I do not have any avis servers or anything like that setup, just the client installed.

I'm wondering why the examples say tiprv/elvin/one other oen, but do not mention avis? I assume elvin is avis but just slightly different.

In any case, is there a way to check the "integrity" of the libraries first? They must be the issue, as the programs compile fine but are failing to load the bridge.



Did you make any other changes to get it building on OSX? If so, and
provided other platforms aren't affected of course, then I'd be happy to
apply them. I can't see NYSE ever supporting this in their commercial
distribution as there isn't a demand for it with their customers, but for
the open source project additional platform support can only be a good
thing.
I agree, but I want to hold off on sharing those changes until we can ensure the build works properly.
They are small changes here and there, but most definitely should not be the reason for the error.

-gAgan ;)

Glenn


On 29/11/2012 17:13, "Gagan Sidhu" <gagan@g-a.ca> wrote:

Hi guys,

Currently I'm on OSX and trying to build the openMAMA libs for my system.

I understand that OSX is not officially supported, but the issue I'm
experiencing is not specific to this platform.

Specifically, I build and install the avis client, copy the config_h to
the suggested directories, and proceed to build mama.

The build and linking goes fine, from what I can see, however the example
programs do *not* work.

I have compiled each one using a slightly modified Makefile.sample (no
-lrt flag or -Xlinker before the -Bstatic/-Bdynamic).

This issue is very strange, because I saw someone else had a bridge issue
but the linked library spit out an error. All I see is:

here's the dump:

GagansMacPro:c Gagan$ make -f Makefile.sample
gcc -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamapublisherc mamapublisherc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamasubscriberc.o mamasubscriberc.c
mamasubscriberc.c: In function ŒwildCardMsgCb¹:
mamasubscriberc.c:280:56: warning: cast to pointer from integer of
different size [-Wint-to-pointer-cast]
mamasubscriberc.c:285:13: warning: cast from pointer to integer of
different size [-Wpointer-to-int-cast]
gcc -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamasubscriberc mamasubscriberc.o -Bstatic -lmamaavisimpl -lmama
-Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamasymbollistsubscriberc.o
mamasymbollistsubscriberc.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamasymbollistsubscriberc mamasymbollistsubscriberc.o -Bstatic
-lmamaavisimpl -lmama -Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamaproxyc.o mamaproxyc.c
mamaproxyc.c: In function ŒsubscribeToSymbols¹:
mamaproxyc.c:230:34: warning: cast to pointer from integer of different
size [-Wint-to-pointer-cast]
mamaproxyc.c: In function ŒsubscriptionHandlerOnNewRequestCb¹:
mamaproxyc.c:354:62: warning: cast to pointer from integer of different
size [-Wint-to-pointer-cast]
mamaproxyc.c: In function ŒsubscriptionHandlerOnRequestCb¹:
mamaproxyc.c:422:26: warning: cast from pointer to integer of different
size [-Wpointer-to-int-cast]
mamaproxyc.c:435:26: warning: cast from pointer to integer of different
size [-Wpointer-to-int-cast]
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamaproxyc mamaproxyc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamaio.o mamaio.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o mamaio
mamaio.o -Bstatic -lmamaavisimpl -lmama -Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamamultisubscriberc.o
mamamultisubscriberc.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamamultisubscriberc mamamultisubscriberc.o -Bstatic -lmamaavisimpl
-lmama -Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamaftmemberc.o mamaftmemberc.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamaftmemberc mamaftmemberc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
GagansMacPro:c Gagan$ ./mamalistenc
Enter one symbol per line and terminate with a .
Symbol> ,
Symbol> .
Could not open MAMA wmw bridge.
GagansMacPro:c Gagan$ ./mamalistenc -m avis
Enter one symbol per line and terminate with a .
Symbol> .
Could not open MAMA avis bridge.
Thanks,
Gagan Sidhu,
Director, General Analytics (GA) Inc.

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

________________________________

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
_______________________________________________
Openmama-users mailing list
Openmama-users@lists.openmama.org
https://lists.openmama.org/mailman/listinfo/openmama-users

________________________________

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Re: NO_BRIDGE_IMPL() issue (avis is compiled/linked properly)

Philip Preston <PPreston@...>
 

Gagan

It will compile - but the programs won't work because mac os x does not fully implement posix semaphores, and as such it silently fails. Also it won't load the bridge in the example apps unless you change the LIB_EXTENSION to .dylib (if you haven't already).

The function calls exist for posix unnamed semaphores on mac but return error codes indicate they are not implemented - mama doesn't log the failure cause its not an issue on any of the officially supported os. This stops any of the queues working. You can work around this by implementing named semaphores. I'd made some changes to do this for openmama1 and have got most of moved to a local openmama2, following the breakout of platforms in wombatcommon. Have added a darwin folder with appropriate changes.

Happy to pass it on once I get time to finish / tidy it up. Also had it setup in xcode.

Cheers

Phil

Philip Preston
NYSE Technologies

Adelaide Exchange
24-26 Adelaide St
Belfast, BT2 8GD
United Kingdom

t: +44 (0) 2890 822 091
m: +44 (0) 7903 300307
e: ppreston@nyx.com

NYSE Euronext
Powering the Exchanging World
www.nyse.com/technologies
_

----- Original Message -----
From: Gagan Sidhu [mailto:gagan@g-a.ca]
Sent: Thursday, November 29, 2012 06:08 PM
To: openmama-users@lists.openmama.org <openmama-users@lists.openmama.org>
Subject: Re: [Openmama-users] NO_BRIDGE_IMPL() issue (avis is compiled/linked properly)

Hey Glen,

On 2012-11-29, at 10:58 AM, Glenn McClements <gmcclements@nyx.com> wrote:

Hi Gigan,
This looks like the avis bridge lib isn't in being loaded for some reason
(FYI bridge libraries are dynamical *loaded* using dlopen() not
dynamically linked). Is the bridge library and the AVIS in your
DYLD_LIBRARY_PATH? Also putting mamalistenc in full verbose mode may give
more info, i.e:

./mamalistenc -m avis -v -v -v -v

As you said, OSX isn't currently supported but I do know of some people
who have tried in the past and did manage to get something up and running.
yeah, theoretically speaking there is not much of a difference in the required libs.
I installed avis in /usr/local so /usr/local/include contains the avis folder, and /usr/local/lib contains libavis
I didn't export DYLD_LIBRARY_PATH till now, but it looks like this:

GagansMacPro:c Gagan$ echo $DYLD_LIBRARY_PATH
/opt/openmama/lib:/usr/local/lib:

and changing -lmamaavisimpl to -lavis and re-compiling with Makefile -f sMakefile.sample still gets the same sort of issue.
I've tried -v -v -v -v before because will henry suggested it, but that didn't work:

GagansMacPro:c Gagan$ ./mamalistenc -m avis -v -v -v -v
Enter one symbol per line and terminate with a .
Symbol> .
Could not open MAMA avis bridge.

Given that the verbose output doesn't work, I'm really puzzled as to what is causing the issue.

Is there a way to check that the compiled libraries have everything?

FYI: I am new to the whole "trading" thing. I do not have any avis servers or anything like that setup, just the client installed.

I'm wondering why the examples say tiprv/elvin/one other oen, but do not mention avis? I assume elvin is avis but just slightly different.

In any case, is there a way to check the "integrity" of the libraries first? They must be the issue, as the programs compile fine but are failing to load the bridge.



Did you make any other changes to get it building on OSX? If so, and
provided other platforms aren't affected of course, then I'd be happy to
apply them. I can't see NYSE ever supporting this in their commercial
distribution as there isn't a demand for it with their customers, but for
the open source project additional platform support can only be a good
thing.
I agree, but I want to hold off on sharing those changes until we can ensure the build works properly.
They are small changes here and there, but most definitely should not be the reason for the error.

-gAgan ;)

Glenn


On 29/11/2012 17:13, "Gagan Sidhu" <gagan@g-a.ca> wrote:

Hi guys,

Currently I'm on OSX and trying to build the openMAMA libs for my system.

I understand that OSX is not officially supported, but the issue I'm
experiencing is not specific to this platform.

Specifically, I build and install the avis client, copy the config_h to
the suggested directories, and proceed to build mama.

The build and linking goes fine, from what I can see, however the example
programs do *not* work.

I have compiled each one using a slightly modified Makefile.sample (no
-lrt flag or -Xlinker before the -Bstatic/-Bdynamic).

This issue is very strange, because I saw someone else had a bridge issue
but the linked library spit out an error. All I see is:

here's the dump:

GagansMacPro:c Gagan$ make -f Makefile.sample
gcc -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamapublisherc mamapublisherc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamasubscriberc.o mamasubscriberc.c
mamasubscriberc.c: In function ŒwildCardMsgCb¹:
mamasubscriberc.c:280:56: warning: cast to pointer from integer of
different size [-Wint-to-pointer-cast]
mamasubscriberc.c:285:13: warning: cast from pointer to integer of
different size [-Wpointer-to-int-cast]
gcc -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamasubscriberc mamasubscriberc.o -Bstatic -lmamaavisimpl -lmama
-Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamasymbollistsubscriberc.o
mamasymbollistsubscriberc.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamasymbollistsubscriberc mamasymbollistsubscriberc.o -Bstatic
-lmamaavisimpl -lmama -Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamaproxyc.o mamaproxyc.c
mamaproxyc.c: In function ŒsubscribeToSymbols¹:
mamaproxyc.c:230:34: warning: cast to pointer from integer of different
size [-Wint-to-pointer-cast]
mamaproxyc.c: In function ŒsubscriptionHandlerOnNewRequestCb¹:
mamaproxyc.c:354:62: warning: cast to pointer from integer of different
size [-Wint-to-pointer-cast]
mamaproxyc.c: In function ŒsubscriptionHandlerOnRequestCb¹:
mamaproxyc.c:422:26: warning: cast from pointer to integer of different
size [-Wpointer-to-int-cast]
mamaproxyc.c:435:26: warning: cast from pointer to integer of different
size [-Wpointer-to-int-cast]
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamaproxyc mamaproxyc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamaio.o mamaio.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o mamaio
mamaio.o -Bstatic -lmamaavisimpl -lmama -Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamamultisubscriberc.o
mamamultisubscriberc.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamamultisubscriberc mamamultisubscriberc.o -Bstatic -lmamaavisimpl
-lmama -Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamaftmemberc.o mamaftmemberc.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamaftmemberc mamaftmemberc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
GagansMacPro:c Gagan$ ./mamalistenc
Enter one symbol per line and terminate with a .
Symbol> ,
Symbol> .
Could not open MAMA wmw bridge.
GagansMacPro:c Gagan$ ./mamalistenc -m avis
Enter one symbol per line and terminate with a .
Symbol> .
Could not open MAMA avis bridge.
Thanks,
Gagan Sidhu,
Director, General Analytics (GA) Inc.

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

________________________________

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
_______________________________________________
Openmama-users mailing list
Openmama-users@lists.openmama.org
https://lists.openmama.org/mailman/listinfo/openmama-users

________________________________

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Re: NO_BRIDGE_IMPL() issue (avis is compiled/linked properly)

Gagan Sidhu <gagan@...>
 

Hey Glen,

On 2012-11-29, at 10:58 AM, Glenn McClements <gmcclements@nyx.com> wrote:

Hi Gigan,
This looks like the avis bridge lib isn't in being loaded for some reason
(FYI bridge libraries are dynamical *loaded* using dlopen() not
dynamically linked). Is the bridge library and the AVIS in your
DYLD_LIBRARY_PATH? Also putting mamalistenc in full verbose mode may give
more info, i.e:

./mamalistenc -m avis -v -v -v -v

As you said, OSX isn't currently supported but I do know of some people
who have tried in the past and did manage to get something up and running.
yeah, theoretically speaking there is not much of a difference in the required libs.
I installed avis in /usr/local so /usr/local/include contains the avis folder, and /usr/local/lib contains libavis
I didn't export DYLD_LIBRARY_PATH till now, but it looks like this:

GagansMacPro:c Gagan$ echo $DYLD_LIBRARY_PATH
/opt/openmama/lib:/usr/local/lib:

and changing -lmamaavisimpl to -lavis and re-compiling with Makefile -f sMakefile.sample still gets the same sort of issue.
I've tried -v -v -v -v before because will henry suggested it, but that didn't work:

GagansMacPro:c Gagan$ ./mamalistenc -m avis -v -v -v -v
Enter one symbol per line and terminate with a .
Symbol> .
Could not open MAMA avis bridge.

Given that the verbose output doesn't work, I'm really puzzled as to what is causing the issue.

Is there a way to check that the compiled libraries have everything?

FYI: I am new to the whole "trading" thing. I do not have any avis servers or anything like that setup, just the client installed.

I'm wondering why the examples say tiprv/elvin/one other oen, but do not mention avis? I assume elvin is avis but just slightly different.

In any case, is there a way to check the "integrity" of the libraries first? They must be the issue, as the programs compile fine but are failing to load the bridge.



Did you make any other changes to get it building on OSX? If so, and
provided other platforms aren't affected of course, then I'd be happy to
apply them. I can't see NYSE ever supporting this in their commercial
distribution as there isn't a demand for it with their customers, but for
the open source project additional platform support can only be a good
thing.
I agree, but I want to hold off on sharing those changes until we can ensure the build works properly.
They are small changes here and there, but most definitely should not be the reason for the error.

-gAgan ;)

Glenn


On 29/11/2012 17:13, "Gagan Sidhu" <gagan@g-a.ca> wrote:

Hi guys,

Currently I'm on OSX and trying to build the openMAMA libs for my system.

I understand that OSX is not officially supported, but the issue I'm
experiencing is not specific to this platform.

Specifically, I build and install the avis client, copy the config_h to
the suggested directories, and proceed to build mama.

The build and linking goes fine, from what I can see, however the example
programs do *not* work.

I have compiled each one using a slightly modified Makefile.sample (no
-lrt flag or -Xlinker before the -Bstatic/-Bdynamic).

This issue is very strange, because I saw someone else had a bridge issue
but the linked library spit out an error. All I see is:

here's the dump:

GagansMacPro:c Gagan$ make -f Makefile.sample
gcc -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamapublisherc mamapublisherc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamasubscriberc.o mamasubscriberc.c
mamasubscriberc.c: In function ŒwildCardMsgCb¹:
mamasubscriberc.c:280:56: warning: cast to pointer from integer of
different size [-Wint-to-pointer-cast]
mamasubscriberc.c:285:13: warning: cast from pointer to integer of
different size [-Wpointer-to-int-cast]
gcc -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamasubscriberc mamasubscriberc.o -Bstatic -lmamaavisimpl -lmama
-Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamasymbollistsubscriberc.o
mamasymbollistsubscriberc.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamasymbollistsubscriberc mamasymbollistsubscriberc.o -Bstatic
-lmamaavisimpl -lmama -Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamaproxyc.o mamaproxyc.c
mamaproxyc.c: In function ŒsubscribeToSymbols¹:
mamaproxyc.c:230:34: warning: cast to pointer from integer of different
size [-Wint-to-pointer-cast]
mamaproxyc.c: In function ŒsubscriptionHandlerOnNewRequestCb¹:
mamaproxyc.c:354:62: warning: cast to pointer from integer of different
size [-Wint-to-pointer-cast]
mamaproxyc.c: In function ŒsubscriptionHandlerOnRequestCb¹:
mamaproxyc.c:422:26: warning: cast from pointer to integer of different
size [-Wpointer-to-int-cast]
mamaproxyc.c:435:26: warning: cast from pointer to integer of different
size [-Wpointer-to-int-cast]
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamaproxyc mamaproxyc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamaio.o mamaio.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o mamaio
mamaio.o -Bstatic -lmamaavisimpl -lmama -Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamamultisubscriberc.o
mamamultisubscriberc.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamamultisubscriberc mamamultisubscriberc.o -Bstatic -lmamaavisimpl
-lmama -Bdynamic -lpthread -lm -ldl
gcc -I/opt/openmama/include -c -o mamaftmemberc.o mamaftmemberc.c
g++ -I/opt/openmama/include -dynamic -L/opt/openmama/lib -o
mamaftmemberc mamaftmemberc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
GagansMacPro:c Gagan$ ./mamalistenc
Enter one symbol per line and terminate with a .
Symbol> ,
Symbol> .
Could not open MAMA wmw bridge.
GagansMacPro:c Gagan$ ./mamalistenc -m avis
Enter one symbol per line and terminate with a .
Symbol> .
Could not open MAMA avis bridge.
Thanks,
Gagan Sidhu,
Director, General Analytics (GA) Inc.

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

________________________________

Please consider the environment before printing this e-mail.

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 advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
121 - 140 of 234