1. Openmama-users@lists.openmama.org

Re: Capturec and tick42blp bridge

macrux
 

Hi,

I recorded just a few seconds of the AAPL US Equity from Bloomberg yesterday (I sent a bigger capture in my first message). The playback is attached in the file 1325551007.playback. The log of the capturerec is attached in the file capturerec-aapl.log, and for the capturereplayc two logs are attached: one in the file capturereplayc-aapl-ubuntu.log and the other in the file capturereplayc-aapl-windows.log. It was done using the openmama 2.3.1 release in windows using the bridge tick42blp to connect to the bloomberg terminal. I used the same parameters mentioned before:

capturec -m tick42blp -MS BlpMktData:blp_tport:symbols.sym

Where symbols.sym is a file containing only one symbol: "AAPL US Equity"

It starts to recording a file. After a while I stop the process with CTLR+C. Then I try to use the capturereplayc to play the file:

capturereplayc -S TEST -m qpid -tport pub -dictionary data/dictionaries/data.dict -f 1325551007.playback

The fact is that capturereplayc cannot even start when I try to reproduce the file in ubuntu (in this machine I have the openmama 2.3.3 release), it happens a "segmentation fault" as you can see in the ubuntu log. If I try to reproduce it in a windows machine (with windows 10 and openmama 2.3.1), then the capturereplayc starts listening and when I start a mamalistenc, it stops abruptly, but the verbose log of capturereplayc doesn't say anything. The same happens if I do it in the machine where I have the bloomberg terminal (with windows 7 machine and openmama 2.3.1), so I'm stuck in this problem.


Thanks in advance,

Nestor.


On 2 October 2015 at 02:45, Damian Maguire <d.maguire@...> wrote:
Hey Nestor, 

Do you have a verbose log file from capturereplay up to the point at which it stops? And does the process simply hang, or is it crashing? I’ve never tried capturereplay with the Bloomberg bridge, though Tom and co will likely have a better idea of the issues there, but if it’s a bug in capturereplay we should be able to get a better idea of where from the logs.

Cheers, 

D

Damian Maguire
Senior Sales Engineer

SR.LABS Proven High Speed Electronic Trading Solutions

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

d.maguire@...  

+44 7835 844770



From: <openmama-users-bounces@...> on behalf of Macrux
Date: Thursday, October 1, 2015 at 10:23 PM
To: "openmama-dev@...", "openmama-users@..."
Subject: [Openmama-users] Capturec and tick42blp bridge

Hi folks,

As part of the work I'm doing with bloomberg and openmama, I'm trying to record the data coming from bloomberg through the bridge, I'm using this instruction:

capturec -m tick42blp -MS BlpMktData:blp_tport:symbols.sym

Where symbols.sym is a file containing only one symbol: "AAPL US Equity"

It starts to recording a file. After a while I stop the process with CTLR+C. Then I try to use the capturereplayc to play the file:

capturereplayc -S TEST -m qpid -tport pub -dictionary bbdict.txt -f 1221191001.playback

But the capturereplayc stops abruptly. The same happens if I try to use the dictionary provided in the openmama release.

So my question is, how could I record the data coming from bloomberg and then play them with the capturereplayc tool.

Thanks for your help. I appreciate your patience, I'm really new with openama.

Best regards,



PD: I attached the playback file recorded today just in case someone wants to test it.




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

?
1325551007.playback
?
capturerec-aapl.log
?
capturereplayc-aapl-ubuntu.log
?
capturereplayc-aapl-windows.log

Join Openmama-users@lists.openmama.org to automatically receive all group messages.