Date   

Re: Tick42 for OpenMAMA 2.4

Tom Doust
 

Hi Holger

 

This sounds familiar. I have forwarded it to our dev who did the 2.4.0 work and I’ll get back to you

 

Tom

 

From: Holger Schluenzen [mailto:Holger.Schluenzen@...]
Sent: 05 May 2016 16:37
To: Tom Doust <tom.doust@...>; openmama-dev@...
Subject: RE: Tick42 for OpenMAMA 2.4

 

Hi Tom,

 

I have built it on Windows with VS2010 and boost 1.54 (VisualStudio 2015 didn’t work with boost), and boost 1.6 not with the bridge.

Now it compiles but the bridge is not loading properly. I get some errors when mama.c tries to allocate the bridge structure (the impl pointer is null).

 

 

Thanks

Holger

 

 

From: Tom Doust [mailto:tom.doust@...]
Sent: Dienstag, 3. Mai 2016 18:07
To: Holger Schluenzen <Holger.Schluenzen@...>; openmama-dev@...
Subject: RE: Tick42 for OpenMAMA 2.4

 

Hi Holger

 

There were a few compilation issues (expected) which we have addressed in our internal dev build.

 

I expect to push a new version to github in the next few days

 

Which environment (linux /win) are you using?

 

Tom

 

 

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Holger Schluenzen
Sent: 03 May 2016 08:39
To: openmama-dev@...
Subject: [Openmama-dev] Tick42 for OpenMAMA 2.4

 

Hi all, hi Tom,

 

I was trying to migrate the tick42blp bridge for OpenMAMA 2.4 but had some trouble with the new bridge initialization and setting the Mama Version in the bridge.

 

Is there perhaps a compatible version out there?

 

Cheers

Holger

 

 

 

 

 

 


Re: Tick42 for OpenMAMA 2.4

Holger
 

Hi Tom,

 

I have built it on Windows with VS2010 and boost 1.54 (VisualStudio 2015 didn’t work with boost), and boost 1.6 not with the bridge.

Now it compiles but the bridge is not loading properly. I get some errors when mama.c tries to allocate the bridge structure (the impl pointer is null).

 

 

Thanks

Holger

 

 

From: Tom Doust [mailto:tom.doust@...]
Sent: Dienstag, 3. Mai 2016 18:07
To: Holger Schluenzen <Holger.Schluenzen@...>; openmama-dev@...
Subject: RE: Tick42 for OpenMAMA 2.4

 

Hi Holger

 

There were a few compilation issues (expected) which we have addressed in our internal dev build.

 

I expect to push a new version to github in the next few days

 

Which environment (linux /win) are you using?

 

Tom

 

 

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Holger Schluenzen
Sent: 03 May 2016 08:39
To: openmama-dev@...
Subject: [Openmama-dev] Tick42 for OpenMAMA 2.4

 

Hi all, hi Tom,

 

I was trying to migrate the tick42blp bridge for OpenMAMA 2.4 but had some trouble with the new bridge initialization and setting the Mama Version in the bridge.

 

Is there perhaps a compatible version out there?

 

Cheers

Holger

 

 

 

 

 

 


Re: Publisher double free on create

Frank Quinn <f.quinn@...>
 

Hi Chris,

 

Yeah that’s definitely an issue – happens in two places too and looks like there’s another issue in a section below it where it will be accessed after the free. I went ahead and raised https://github.com/OpenMAMA/OpenMAMA/issues/168 to track this - if you want to submit a patch you can work away, otherwise we’ll get it fixed when we get a chance.


Cheers,

Frank

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Christopher Morgan
Sent: 04 May 2016 21:35
To: openmama-dev@...
Subject: [Openmama-dev] Publisher double free on create

 

Hi,

 

I think I found an issue with publisher create. On the error paths in _createByIndex, the function mamaPublisherImpl_cleanup(impl) is called and then the impl is immediately freed after but mamaPublisherImpl_cleanup(impl) also calls free on the impl as well. mamaPublisherImpl_cleanup was introduce in the publisher event feature, I believe, and is used as a publisher destroy.  Should the mamaPublisherImpl_cleanup function free the impl parameter or should create not free the impl on error paths?

 

Chris Morgan


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. SR Labs LLC


Publisher double free on create

cmorgan
 

Hi,

 

I think I found an issue with publisher create. On the error paths in _createByIndex, the function mamaPublisherImpl_cleanup(impl) is called and then the impl is immediately freed after but mamaPublisherImpl_cleanup(impl) also calls free on the impl as well. mamaPublisherImpl_cleanup was introduce in the publisher event feature, I believe, and is used as a publisher destroy.  Should the mamaPublisherImpl_cleanup function free the impl parameter or should create not free the impl on error paths?

 

Chris Morgan


Re: Tick42 for OpenMAMA 2.4

Tom Doust
 

Hi Holger

 

There were a few compilation issues (expected) which we have addressed in our internal dev build.

 

I expect to push a new version to github in the next few days

 

Which environment (linux /win) are you using?

 

Tom

 

 

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Holger Schluenzen
Sent: 03 May 2016 08:39
To: openmama-dev@...
Subject: [Openmama-dev] Tick42 for OpenMAMA 2.4

 

Hi all, hi Tom,

 

I was trying to migrate the tick42blp bridge for OpenMAMA 2.4 but had some trouble with the new bridge initialization and setting the Mama Version in the bridge.

 

Is there perhaps a compatible version out there?

 

Cheers

Holger

 

 

 

 

 

 


Tick42 for OpenMAMA 2.4

Holger
 

Hi all, hi Tom,

 

I was trying to migrate the tick42blp bridge for OpenMAMA 2.4 but had some trouble with the new bridge initialization and setting the Mama Version in the bridge.

 

Is there perhaps a compatible version out there?

 

Cheers

Holger

 

 

 

 

 

 


Re: coding standard

Dmitri Fedorov <dfedorov.solace@...>
 

Thank you Frank!
I'll see if I'd be able to recreate for vim

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.

On 28 April 2016 at 15:23, Frank Quinn <fquinn.ni@...> wrote:
Hi Dmitri,

I actually set up an eclipse one many moons ago which I have been using myself (attached). I should put that on that wiki page actually now that you mention it.

I'd be no good for vim / emacs but I would welcome any contributions :).

Cheers,
Frank

On Thu, Apr 28, 2016 at 7:32 PM, Dmitri Fedorov <dfedorov.solace@...> wrote:
Thanks Frank, that's a good document.

Would be nice to have editor settings to follow it (vim/emacs/Eclipse).

Cheers
Dmitri

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.

On 28 April 2016 at 14:09, Frank Quinn <fquinn.ni@...> wrote:
Hi Dmitri,

Indeed we do - check out https://github.com/OpenMAMA/OpenMAMA/wiki/Coding-Standards.

Any suggestions / gap fills welcome too.

Cheers,
Frank

On Thu, Apr 28, 2016 at 7:06 PM, Dmitri Fedorov <dfedorov.solace@...> wrote:
Gents, do we have a coding standard published somewhere, please?

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.

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






Re: coding standard

Frank Quinn <fquinn.ni@...>
 

Hi Dmitri,

I actually set up an eclipse one many moons ago which I have been using myself (attached). I should put that on that wiki page actually now that you mention it.

I'd be no good for vim / emacs but I would welcome any contributions :).

Cheers,
Frank

On Thu, Apr 28, 2016 at 7:32 PM, Dmitri Fedorov <dfedorov.solace@...> wrote:
Thanks Frank, that's a good document.

Would be nice to have editor settings to follow it (vim/emacs/Eclipse).

Cheers
Dmitri

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.

On 28 April 2016 at 14:09, Frank Quinn <fquinn.ni@...> wrote:
Hi Dmitri,

Indeed we do - check out https://github.com/OpenMAMA/OpenMAMA/wiki/Coding-Standards.

Any suggestions / gap fills welcome too.

Cheers,
Frank

On Thu, Apr 28, 2016 at 7:06 PM, Dmitri Fedorov <dfedorov.solace@...> wrote:
Gents, do we have a coding standard published somewhere, please?

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.

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





Re: coding standard

Dmitri Fedorov <dfedorov.solace@...>
 

Thanks Frank, that's a good document.

Would be nice to have editor settings to follow it (vim/emacs/Eclipse).

Cheers
Dmitri

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.

On 28 April 2016 at 14:09, Frank Quinn <fquinn.ni@...> wrote:
Hi Dmitri,

Indeed we do - check out https://github.com/OpenMAMA/OpenMAMA/wiki/Coding-Standards.

Any suggestions / gap fills welcome too.

Cheers,
Frank

On Thu, Apr 28, 2016 at 7:06 PM, Dmitri Fedorov <dfedorov.solace@...> wrote:
Gents, do we have a coding standard published somewhere, please?

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.

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




Re: coding standard

Frank Quinn <fquinn.ni@...>
 

Hi Dmitri,

Indeed we do - check out https://github.com/OpenMAMA/OpenMAMA/wiki/Coding-Standards.

Any suggestions / gap fills welcome too.

Cheers,
Frank

On Thu, Apr 28, 2016 at 7:06 PM, Dmitri Fedorov <dfedorov.solace@...> wrote:
Gents, do we have a coding standard published somewhere, please?

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.

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



coding standard

Dmitri Fedorov <dfedorov.solace@...>
 

Gents, do we have a coding standard published somewhere, please?

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.


Re: Market data subscriptions using qpid broker

Frank Quinn <fquinn.ni@...>
 

Hi Nestor,

Yes this is a strange one - you're right I could only recreate on a transient basis and only with the broker. I have put in a fix which seems to have prevented this behaviour in my environment by adding more forgiving timeouts particularly for the sending of subscription messages which I think may have been getting aborted in-flight.

Could you try the latest code off the OpenMAMA next branch and see if this helps in your environment?

Cheers,
Frank

On Tue, Apr 26, 2016 at 4:27 PM, Macrux <kmacrux@...> wrote:
Hi all,

I've been working with OpenMAMA 2.4.0 and the new Qpid Broker integration with the Java Qpid Broker implementation in Ubuntu 14.04. I've been experiencing some issues when I try to publish market data using capturereplayc. I use the next command

capturereplayc -S TEST -m qpid -tport broker -dictionary data/dictionaries/data.dict -f data/playbacks/openmama_utpcasheuro_capture.5000.10.qpid.mplay -r -v -v -v -v

Issues arise when I run mamalistenc or MamaListen.java example. For instance, with the next arguments they
can't get the dictionary:

mamalistenc -m qpid -tport broker -S TEST -s DE000CM95AU4.EUR.XPAR -v -v -v -v

I got this in mamalistenc console:

...
016-04-26 09:32:44: (15a53740) : deactivateAction(): (WOMBAT.DATA_DICT (DATA_DICT) (0x1152270)): mSubscBridge=(nil)
2016-04-26 09:32:44: (15a53740) : Subscription 0x1152270 is now at state MAMA_SUBSCRIPTION_DEACTIVATED.
2016-04-26 09:32:44: (15a53740) : imageRequest::timeoutCallback (): DATA_DICT: Timeout waiting for recap or initial value (subscription=0x1152270)
2016-04-26 09:32:44: (15a53740) : imageRequest::timeoutCallback (): source=WOMBAT; symbol=DATA_DICT
Timed out waiting for dictionary
Could not create dictionary.

And in the capturereplayc console, I got this:

...
2016-04-26 09:35:50: (f5dbf740) : Starting refresh message mini-cycle
2016-04-26 09:35:50: (f5dbf740) : No refreshes to send
2016-04-26 09:35:56: (f2552700) : qpidBridgeMamaTransportImpl_dispatchThread(): recv-ed
2016-04-26 09:35:56: (f5dbf740) : mamaSubscription_processMsg(): _MDDD.WOMBAT.DATA_DICT: msg = {{MdSubscSymbol,71,DATA_DICT},{MdSubscriptionType,60,4},{MdSubscMsgType,61,5},{MamaAppDataType,17,0},{MdSubscType,5,5},{MdSubscSourceHost,63,127.0.1.1}} subsc (0xacb940)


So I have to read the dictionary directly from file:

mamalistenc -m qpid -tport broker -S TEST -s DE000CM95AU4.EUR.XPAR -v -v -v -v -use_dict_file /home/nmarin/Apps/openmama-2.4.0/data/dictionaries/data.dict

Sometimes It just doesn't work and I got this message:

...
2016-04-26 09:46:53: (cd6a7740) : deactivateAction(): (TEST.DE000CM95AU4.EUR.XPAR (DE000CM95AU4.EUR.XPAR) (0x11113c0)): mSubscBridge=0x112b620
2016-04-26 09:46:53: (cd6a7740) : Subscription 0x11113c0 is now at state MAMA_SUBSCRIPTION_DEACTIVATED.
2016-04-26 09:46:53: (cd6a7740) : imageRequest::timeoutCallback (): DE000CM95AU4.EUR.XPAR: Timeout waiting for recap or initial value (subscription=0x11113c0)
2016-04-26 09:46:53: (cd6a7740) : imageRequest::timeoutCallback (): source=TEST; symbol=DE000CM95AU4.EUR.XPAR
An error occurred creating subscription for DE000CM95AU4.EUR.XPAR: STATUS_TIMEOUT


But sometimes if I restart capturereplayc and mamalistenc it works well. I'm actually a little confused with this behaviour, because sometimes it works, but sometimes doesn't work at all and I have to restart the broker, the capturereplayc or the mamalisten until this works. I've tested using regular transport (pub/sub) and it works perfect, so I think the issues show up only with the broker. I've also tested simple publish and subscribe with mamapublisherc, mamasubscriberc and it works fine.

Thanks for your help.

Nestor





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



Re: Market data subscriptions using qpid broker

macrux
 

Hi Frank, everything is running on Ubuntu 14.04, on the same machine. Qpid proton 0.9 and Qpid broker 6.0.1. Thanks.

Regards,

Nestor


On 26 April 2016 at 11:28, Frank Quinn <fquinn.ni@...> wrote:

Hi Nestor,

What versions of the Qpid broker and proton libraries are you using? Everything running on Ubuntu?

Cheers,
Frank


On Tue, 26 Apr 2016 16:27 Macrux, <kmacrux@...> wrote:
Hi all,

I've been working with OpenMAMA 2.4.0 and the new Qpid Broker integration with the Java Qpid Broker implementation in Ubuntu 14.04. I've been experiencing some issues when I try to publish market data using capturereplayc. I use the next command

capturereplayc -S TEST -m qpid -tport broker -dictionary data/dictionaries/data.dict -f data/playbacks/openmama_utpcasheuro_capture.5000.10.qpid.mplay -r -v -v -v -v

Issues arise when I run mamalistenc or MamaListen.java example. For instance, with the next arguments they
can't get the dictionary:

mamalistenc -m qpid -tport broker -S TEST -s DE000CM95AU4.EUR.XPAR -v -v -v -v

I got this in mamalistenc console:

...
016-04-26 09:32:44: (15a53740) : deactivateAction(): (WOMBAT.DATA_DICT (DATA_DICT) (0x1152270)): mSubscBridge=(nil)
2016-04-26 09:32:44: (15a53740) : Subscription 0x1152270 is now at state MAMA_SUBSCRIPTION_DEACTIVATED.
2016-04-26 09:32:44: (15a53740) : imageRequest::timeoutCallback (): DATA_DICT: Timeout waiting for recap or initial value (subscription=0x1152270)
2016-04-26 09:32:44: (15a53740) : imageRequest::timeoutCallback (): source=WOMBAT; symbol=DATA_DICT
Timed out waiting for dictionary
Could not create dictionary.

And in the capturereplayc console, I got this:

...
2016-04-26 09:35:50: (f5dbf740) : Starting refresh message mini-cycle
2016-04-26 09:35:50: (f5dbf740) : No refreshes to send
2016-04-26 09:35:56: (f2552700) : qpidBridgeMamaTransportImpl_dispatchThread(): recv-ed
2016-04-26 09:35:56: (f5dbf740) : mamaSubscription_processMsg(): _MDDD.WOMBAT.DATA_DICT: msg = {{MdSubscSymbol,71,DATA_DICT},{MdSubscriptionType,60,4},{MdSubscMsgType,61,5},{MamaAppDataType,17,0},{MdSubscType,5,5},{MdSubscSourceHost,63,127.0.1.1}} subsc (0xacb940)


So I have to read the dictionary directly from file:

mamalistenc -m qpid -tport broker -S TEST -s DE000CM95AU4.EUR.XPAR -v -v -v -v -use_dict_file /home/nmarin/Apps/openmama-2.4.0/data/dictionaries/data.dict

Sometimes It just doesn't work and I got this message:

...
2016-04-26 09:46:53: (cd6a7740) : deactivateAction(): (TEST.DE000CM95AU4.EUR.XPAR (DE000CM95AU4.EUR.XPAR) (0x11113c0)): mSubscBridge=0x112b620
2016-04-26 09:46:53: (cd6a7740) : Subscription 0x11113c0 is now at state MAMA_SUBSCRIPTION_DEACTIVATED.
2016-04-26 09:46:53: (cd6a7740) : imageRequest::timeoutCallback (): DE000CM95AU4.EUR.XPAR: Timeout waiting for recap or initial value (subscription=0x11113c0)
2016-04-26 09:46:53: (cd6a7740) : imageRequest::timeoutCallback (): source=TEST; symbol=DE000CM95AU4.EUR.XPAR
An error occurred creating subscription for DE000CM95AU4.EUR.XPAR: STATUS_TIMEOUT


But sometimes if I restart capturereplayc and mamalistenc it works well. I'm actually a little confused with this behaviour, because sometimes it works, but sometimes doesn't work at all and I have to restart the broker, the capturereplayc or the mamalisten until this works. I've tested using regular transport (pub/sub) and it works perfect, so I think the issues show up only with the broker. I've also tested simple publish and subscribe with mamapublisherc, mamasubscriberc and it works fine.

Thanks for your help.

Nestor




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


Re: Market data subscriptions using qpid broker

Frank Quinn <fquinn.ni@...>
 

Hi Nestor,

What versions of the Qpid broker and proton libraries are you using? Everything running on Ubuntu?

Cheers,
Frank


On Tue, 26 Apr 2016 16:27 Macrux, <kmacrux@...> wrote:
Hi all,

I've been working with OpenMAMA 2.4.0 and the new Qpid Broker integration with the Java Qpid Broker implementation in Ubuntu 14.04. I've been experiencing some issues when I try to publish market data using capturereplayc. I use the next command

capturereplayc -S TEST -m qpid -tport broker -dictionary data/dictionaries/data.dict -f data/playbacks/openmama_utpcasheuro_capture.5000.10.qpid.mplay -r -v -v -v -v

Issues arise when I run mamalistenc or MamaListen.java example. For instance, with the next arguments they
can't get the dictionary:

mamalistenc -m qpid -tport broker -S TEST -s DE000CM95AU4.EUR.XPAR -v -v -v -v

I got this in mamalistenc console:

...
016-04-26 09:32:44: (15a53740) : deactivateAction(): (WOMBAT.DATA_DICT (DATA_DICT) (0x1152270)): mSubscBridge=(nil)
2016-04-26 09:32:44: (15a53740) : Subscription 0x1152270 is now at state MAMA_SUBSCRIPTION_DEACTIVATED.
2016-04-26 09:32:44: (15a53740) : imageRequest::timeoutCallback (): DATA_DICT: Timeout waiting for recap or initial value (subscription=0x1152270)
2016-04-26 09:32:44: (15a53740) : imageRequest::timeoutCallback (): source=WOMBAT; symbol=DATA_DICT
Timed out waiting for dictionary
Could not create dictionary.

And in the capturereplayc console, I got this:

...
2016-04-26 09:35:50: (f5dbf740) : Starting refresh message mini-cycle
2016-04-26 09:35:50: (f5dbf740) : No refreshes to send
2016-04-26 09:35:56: (f2552700) : qpidBridgeMamaTransportImpl_dispatchThread(): recv-ed
2016-04-26 09:35:56: (f5dbf740) : mamaSubscription_processMsg(): _MDDD.WOMBAT.DATA_DICT: msg = {{MdSubscSymbol,71,DATA_DICT},{MdSubscriptionType,60,4},{MdSubscMsgType,61,5},{MamaAppDataType,17,0},{MdSubscType,5,5},{MdSubscSourceHost,63,127.0.1.1}} subsc (0xacb940)


So I have to read the dictionary directly from file:

mamalistenc -m qpid -tport broker -S TEST -s DE000CM95AU4.EUR.XPAR -v -v -v -v -use_dict_file /home/nmarin/Apps/openmama-2.4.0/data/dictionaries/data.dict

Sometimes It just doesn't work and I got this message:

...
2016-04-26 09:46:53: (cd6a7740) : deactivateAction(): (TEST.DE000CM95AU4.EUR.XPAR (DE000CM95AU4.EUR.XPAR) (0x11113c0)): mSubscBridge=0x112b620
2016-04-26 09:46:53: (cd6a7740) : Subscription 0x11113c0 is now at state MAMA_SUBSCRIPTION_DEACTIVATED.
2016-04-26 09:46:53: (cd6a7740) : imageRequest::timeoutCallback (): DE000CM95AU4.EUR.XPAR: Timeout waiting for recap or initial value (subscription=0x11113c0)
2016-04-26 09:46:53: (cd6a7740) : imageRequest::timeoutCallback (): source=TEST; symbol=DE000CM95AU4.EUR.XPAR
An error occurred creating subscription for DE000CM95AU4.EUR.XPAR: STATUS_TIMEOUT


But sometimes if I restart capturereplayc and mamalistenc it works well. I'm actually a little confused with this behaviour, because sometimes it works, but sometimes doesn't work at all and I have to restart the broker, the capturereplayc or the mamalisten until this works. I've tested using regular transport (pub/sub) and it works perfect, so I think the issues show up only with the broker. I've also tested simple publish and subscribe with mamapublisherc, mamasubscriberc and it works fine.

Thanks for your help.

Nestor




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


Market data subscriptions using qpid broker

macrux
 

Hi all,

I've been working with OpenMAMA 2.4.0 and the new Qpid Broker integration with the Java Qpid Broker implementation in Ubuntu 14.04. I've been experiencing some issues when I try to publish market data using capturereplayc. I use the next command

capturereplayc -S TEST -m qpid -tport broker -dictionary data/dictionaries/data.dict -f data/playbacks/openmama_utpcasheuro_capture.5000.10.qpid.mplay -r -v -v -v -v

Issues arise when I run mamalistenc or MamaListen.java example. For instance, with the next arguments they
can't get the dictionary:

mamalistenc -m qpid -tport broker -S TEST -s DE000CM95AU4.EUR.XPAR -v -v -v -v

I got this in mamalistenc console:

...
016-04-26 09:32:44: (15a53740) : deactivateAction(): (WOMBAT.DATA_DICT (DATA_DICT) (0x1152270)): mSubscBridge=(nil)
2016-04-26 09:32:44: (15a53740) : Subscription 0x1152270 is now at state MAMA_SUBSCRIPTION_DEACTIVATED.
2016-04-26 09:32:44: (15a53740) : imageRequest::timeoutCallback (): DATA_DICT: Timeout waiting for recap or initial value (subscription=0x1152270)
2016-04-26 09:32:44: (15a53740) : imageRequest::timeoutCallback (): source=WOMBAT; symbol=DATA_DICT
Timed out waiting for dictionary
Could not create dictionary.

And in the capturereplayc console, I got this:

...
2016-04-26 09:35:50: (f5dbf740) : Starting refresh message mini-cycle
2016-04-26 09:35:50: (f5dbf740) : No refreshes to send
2016-04-26 09:35:56: (f2552700) : qpidBridgeMamaTransportImpl_dispatchThread(): recv-ed
2016-04-26 09:35:56: (f5dbf740) : mamaSubscription_processMsg(): _MDDD.WOMBAT.DATA_DICT: msg = {{MdSubscSymbol,71,DATA_DICT},{MdSubscriptionType,60,4},{MdSubscMsgType,61,5},{MamaAppDataType,17,0},{MdSubscType,5,5},{MdSubscSourceHost,63,127.0.1.1}} subsc (0xacb940)


So I have to read the dictionary directly from file:

mamalistenc -m qpid -tport broker -S TEST -s DE000CM95AU4.EUR.XPAR -v -v -v -v -use_dict_file /home/nmarin/Apps/openmama-2.4.0/data/dictionaries/data.dict

Sometimes It just doesn't work and I got this message:

...
2016-04-26 09:46:53: (cd6a7740) : deactivateAction(): (TEST.DE000CM95AU4.EUR.XPAR (DE000CM95AU4.EUR.XPAR) (0x11113c0)): mSubscBridge=0x112b620
2016-04-26 09:46:53: (cd6a7740) : Subscription 0x11113c0 is now at state MAMA_SUBSCRIPTION_DEACTIVATED.
2016-04-26 09:46:53: (cd6a7740) : imageRequest::timeoutCallback (): DE000CM95AU4.EUR.XPAR: Timeout waiting for recap or initial value (subscription=0x11113c0)
2016-04-26 09:46:53: (cd6a7740) : imageRequest::timeoutCallback (): source=TEST; symbol=DE000CM95AU4.EUR.XPAR
An error occurred creating subscription for DE000CM95AU4.EUR.XPAR: STATUS_TIMEOUT


But sometimes if I restart capturereplayc and mamalistenc it works well. I'm actually a little confused with this behaviour, because sometimes it works, but sometimes doesn't work at all and I have to restart the broker, the capturereplayc or the mamalisten until this works. I've tested using regular transport (pub/sub) and it works perfect, so I think the issues show up only with the broker. I've also tested simple publish and subscribe with mamapublisherc, mamasubscriberc and it works fine.

Thanks for your help.

Nestor





Re: reserved fields documentation?

Dmitri Fedorov <dfedorov.solace@...>
 

Thanks Frank, no, I don't want a new field, I simply wanted to learn what these fields are.
Yes I could try to figure out from the code, but a little bit of explanation would be very helpful.

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.

On 22 April 2016 at 08:40, Frank Quinn <f.quinn@...> wrote:

Hi Dmitri,

 

I don’t believe such a thing exists, though I can confirm the reserved fid range ends at 100. Did you have a suggestion for a new field in mind?

 

Cheers,

Frank

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Dmitri Fedorov
Sent: 19 April 2016 14:39
To: openmama-dev <openmama-dev@...>
Subject: [Openmama-dev] reserved fields documentation?

 

Hi all,

 

Where do I find description of reserved fields listed in reservedfieldsimpl.h and reservedfields.c, please?

 

Thank you.

 

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.


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. SR Labs LLC


Re: reserved fields documentation?

Frank Quinn <f.quinn@...>
 

Hi Dmitri,

 

I don’t believe such a thing exists, though I can confirm the reserved fid range ends at 100. Did you have a suggestion for a new field in mind?

 

Cheers,

Frank

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Dmitri Fedorov
Sent: 19 April 2016 14:39
To: openmama-dev <openmama-dev@...>
Subject: [Openmama-dev] reserved fields documentation?

 

Hi all,

 

Where do I find description of reserved fields listed in reservedfieldsimpl.h and reservedfields.c, please?

 

Thank you.

 

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.


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. SR Labs LLC


Re: Using Qpid Broker

Frank Quinn <fquinn.ni@...>
 

Thanks for the update, Nestor, glad to see you got to the bottom of it!

Cheers,
Frank

On Thu, Apr 21, 2016 at 5:45 PM, Macrux <kmacrux@...> wrote:
Hi, its me again, I have resolved this just creating a new topic exchange called "MAMA". That's all. Thanks anyway.

Kind regards,

Nestor.


On 21 April 2016 at 11:21, Macrux <kmacrux@...> wrote:
Hi there,

I'm trying to use the Java Qpid Broker implementation with OpenMAMA 2.4.0. On the web management console of the broker I have created a queue called "test" and I've bound it to the "amqp.topic" exchange (that is there by default). As a binding key I'm using "MAMA.*". When I run the mamapublisherc with:

mamapublisherc -m qpid -tport broker

I got this message:

qpidBridgeMamaTransportImpl_start(): Subscribing to topic://127.0.0.1/MAMA/8c60fd18-07db-11e6-b2bd-d8fc939b9a65 : (null)

And it seems to connect correctly, but when I subscribe a client with:

mamasubscriberc -m qpid -tport broker

I got this message:

qpidBridgeMamaTransportImpl_start(): Subscribing to topic://127.0.0.1/MAMA/b45ca894-07db-11e6-8de4-d8fc939b9a65 : (null)

And although it seems to connect correctly to the broker, it doesn't receive anything.

I haven't modified anything in the mama.properties file, so I have an error in the configuration of the broker, I suppose.

Could anyone please give me a hand with this? Thanks in advance.

Nestor.



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



Re: Using Qpid Broker

macrux
 

Hi, its me again, I have resolved this just creating a new topic exchange called "MAMA". That's all. Thanks anyway.

Kind regards,

Nestor.

On 21 April 2016 at 11:21, Macrux <kmacrux@...> wrote:
Hi there,

I'm trying to use the Java Qpid Broker implementation with OpenMAMA 2.4.0. On the web management console of the broker I have created a queue called "test" and I've bound it to the "amqp.topic" exchange (that is there by default). As a binding key I'm using "MAMA.*". When I run the mamapublisherc with:

mamapublisherc -m qpid -tport broker

I got this message:

qpidBridgeMamaTransportImpl_start(): Subscribing to topic://127.0.0.1/MAMA/8c60fd18-07db-11e6-b2bd-d8fc939b9a65 : (null)

And it seems to connect correctly, but when I subscribe a client with:

mamasubscriberc -m qpid -tport broker

I got this message:

qpidBridgeMamaTransportImpl_start(): Subscribing to topic://127.0.0.1/MAMA/b45ca894-07db-11e6-8de4-d8fc939b9a65 : (null)

And although it seems to connect correctly to the broker, it doesn't receive anything.

I haven't modified anything in the mama.properties file, so I have an error in the configuration of the broker, I suppose.

Could anyone please give me a hand with this? Thanks in advance.

Nestor.



Using Qpid Broker

macrux
 

Hi there,

I'm trying to use the Java Qpid Broker implementation with OpenMAMA 2.4.0. On the web management console of the broker I have created a queue called "test" and I've bound it to the "amqp.topic" exchange (that is there by default). As a binding key I'm using "MAMA.*". When I run the mamapublisherc with:

mamapublisherc -m qpid -tport broker

I got this message:

qpidBridgeMamaTransportImpl_start(): Subscribing to topic://127.0.0.1/MAMA/8c60fd18-07db-11e6-b2bd-d8fc939b9a65 : (null)

And it seems to connect correctly, but when I subscribe a client with:

mamasubscriberc -m qpid -tport broker

I got this message:

qpidBridgeMamaTransportImpl_start(): Subscribing to topic://127.0.0.1/MAMA/b45ca894-07db-11e6-8de4-d8fc939b9a65 : (null)

And although it seems to connect correctly to the broker, it doesn't receive anything.

I haven't modified anything in the mama.properties file, so I have an error in the configuration of the broker, I suppose.

Could anyone please give me a hand with this? Thanks in advance.

Nestor.

601 - 620 of 2305