Problem with application developed with vtapi(Vt Systems) - events

Question

Hello!
I'm developing aplication based on api prepared by VT Systems (http://www.cmsfx.com/en/trading-software/download-vt-trader/download-vt-trader-api/).
This api is used to perform forex transactions. I've written a Web
Service which connects with this api and
alows other modules of my application to perform transactions. I'm
using JAX-WS and Sun Java Application Server.
This is sample of Web Service :
@WebService()
public class ForexService{
protected static VT_API api;
Checker checker;
String userName = "***";
String userPassword = "***";
ConstRecord constants;
public static IVT_APIEventsAdapterExtended events;
public void initAPI(){
try{
System.loadLibrary("bridge2java");
OleEnvironment.Initialize();
api = new VT_API();
api.setForceDisableSSL(false);
events = new IVT_APIEventsAdapterExtended(api);
api.addIVT_APIEventsListener(events);
constants = new ConstRecord();
}catch(Exception e) {
e.printStackTrace();
public ForexService(){
initAPI();
logonResult = api.Login(userName, userPassword, 0) ;
System.out.println("Rezultat logowania: " + logonResult);
checker = new Checker(this);
new Thread(checker).start();
@WebMethod
public String getLogonResult() {
return new Integer(logonResult).toString();
@WebMethod
public String getServerList(){
return api.GetServerList();
I'm using event listener which was attached to Java Sample in
documentation.
public class IVT_APIEventsAdapterExtended extends
IVT_APIEventsAdapter{
private VT_API api;
public IVT_APIEventsAdapterExtended(VT_API apiInstance) {
api = apiInstance;
public void
OnInstrumentChange(IVT_APIEvents_OnInstrumentChangeEvent e)
super.OnInstrumentChange(e);
System.out.println("instrument change - " +
e.get_InstrumentID());
public void
OnNewServerMessage(IVT_APIEvents_OnNewServerMessageEvent e)
super.OnNewServerMessage(e);
System.out.println("Server message :" +
api.get_ServerMessages().get_Items(e.get_MsgID()).get_Text());
I've problem with listening events incoming from forex server. When I
run Wireshark(Network Protocol Analyzer) I can see that events income
to my computer (on different ports - for example: 2070, 2071, 2072),
but don't income to Sun Java Application Server. I suspect that server
don't listen on this ports, but how can I fix this? Maybe should I
choose a other server? I've tried also Tomcat -with similar result :(
Regards,
Peter
//Sorry for my english :)

Answer 1

Thank you very much for the reply :-)
We have been fiddling with the platform on many levels yesterday, and one thing we did do was bump that value up from 1024 to 8192... This made a HUGE improvement in ensuring the platform now holds the live streaming connections. (up to 8000 per edge)
I think for other future reference and to aid other people that might run into this problem in the future, its a good idea to increase this value.  From what we have seen, read and heard, that default value is fairly conservative, its suppose to grow when the load demands it, however, if you have a large scale of connections coming in at once from multiple locations, it can happen that it grows too quickly which can result in the application to be reloaded (which disconnects all users, i.e. all edge servers connected to this origin).
Another option we were recommended to modify was the following :
In adaptor.xml you currently have this line:
<HostPort name="edge1" ctl_channel="localhost:19350" rtmfp="${ADAPTOR.HOSTPORT}">${ADAPTOR.HOSTPORT}</HostPort>
You can set this to
                <HostPort name="edge1" ctl_channel="localhost:19350" rtmfp=":80">:80</HostPort>
<HostPort name="edge2" ctl_channel="localhost:19351" rtmfp=":1935">:1935</HostPort>
This will create two edge processes for both ports 80 and 1935. Currently both ports are served from the same fmsedge process.
Of course this is not a huge performance improvement, but should further distribute load over more processes which is a good thing. Especially when there are that many connections.
This setting can be made on all machines (origin + edge)
Hopefully this could help other people also running into the same problems we have seen ...