We got a few comments about lack of visibility into what's going on
inside the OMS: whether it's connected, where it's pointing to, etc.
Our bad. I've just added quick-and-dirty rudimentary JMX mbean to show
a few pieces of data.
It's a temporary implementation that will do until the next version of
QuickfixJ is out, which includes support for JMX instrumentation.
I've modified the OrderManagementSystem to create and register an OMSAdminMBean.
The mbean shows the following:
beginString
targetCompID
senderCompID
isLoggedOn
sessionID
nextSenderMsgSeqNum
nextTargetMsgSeqNum
In order to connect to the JMX Server you need to add
'-Dcom.sun.management.jmxremote' to the java command when you run the
OMS.
I've modified the script that creates the runOMS.sh/runOMS.bat scripts
to include that, so if you run 'mav clean package assembly:directory
antrun:run' from the top-level directory the created OMS should have
the right flags set.
Otherwise you can set that in Eclipse or IntelliJ when you run it, and
for some reason the current version of maven-exec-plugin doesn't work
with passed arguments, so if you run "mvn exec:java' the JMX Server
won't be setup.
again this is quick-and-dirty, the prettier version will be available
once the next version of QuickfixJ is out.
--
Toli Kuznets
http://www.marketcetera.com: Open-Source Trading Platform
download.run.trade.
_______________________________________________
m-etc-dev mailing list
[hidden email]
http://lists.marketcetera.org/cgi-bin/mailman/listinfo/m-etc-dev
