QuickFIX/J - Open Source Java FIX Engine

I am creating a QuickfixJ application that uses a  
ThreadedSocketAcceptor. The problem I have encountered is that even  
though I call "stop()" on the acceptor, some of the quickfixJ threads  
do not finish, and the application continues to run. This only  
happens if something happens to connect to the acceptor while the  
application is running - if no one connects then the application  
finishes gracefully. I believe it is the QF/J Session dispatcher  
threads that don't finish when the counterparty disconnects.

Specifically my application looks like:
{
       SessionSettings settings = new SessionSettings(new  
FileInputStream(fileName));
       MessageStoreFactory messageStoreFactory =  new FileStoreFactory 
(settings);
       quickfix.LogFactory qfLogFactory = new FileLogFactory(settings);
       MessageFactory messageFactory = new DefaultMessageFactory();
       Connector connector = new ThreadedSocketAcceptor(this,  
messageStoreFactory, settings,
                                                                         
                                  qfLogFactory, messageFactory);
         } else {
           connector = new SocketAcceptor(this, messageStoreFactory,  
settings,
                                               qfLogFactory,  
messageFactory);
         }
       }
       connector.start();
       this.run();
       connector.stop();
}

I am running the application with jrockit and java 6, though I doubt  
this is to blame.

Many thanks for any help you can provide!
-Dan

We are not in production yet, but just finished getting 'certified' by 
their lab folks. I didn't have any problems with the heartbeats, but 
spent a fair bit of time on change to Quickfix/J to make it work in 
their environment.

Jay

David Abbs wrote:
> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> QuickFIX/J Support: http://www.quickfixj.org/support/
>
>
> Does anyone else use quickfixj with the icap ebs fix exchange in a  
> live production environment? If so what are the gotchas that people  
> found, did you have problems with heartbeats?
>
> Any help greatly appreciated.
>
> Thanks
>
> Dave
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Quickfixj-users mailing list
> Quickfixj-users@...
> https://lists.sourceforge.net/lists/listinfo/quickfixj-users
>
>

I am creating a QuickfixJ application that uses a  
ThreadedSocketAcceptor. The problem I have encountered is that even  
though I call "stop()" on the acceptor, some of the quickfixJ threads  
do not finish, and the application continues to run. This only  
happens if something happens to connect to the acceptor while the  
application is running - if no one connects then the application  
finishes gracefully (I believe it is the QF/J Session dispatcher  
threads that don't finish).

Specifically my application looks like:
{
       SessionSettings settings = new SessionSettings(new  
FileInputStream(fileName));
       MessageStoreFactory messageStoreFactory =  new FileStoreFactory 
(settings);
       quickfix.LogFactory qfLogFactory = new FileLogFactory(settings);
       MessageFactory messageFactory = new DefaultMessageFactory();
       Connector connector = new ThreadedSocketAcceptor(this,  
messageStoreFactory, settings,
                                                                         
                                  qfLogFactory, messageFactory);
         } else {
           connector = new SocketAcceptor(this, messageStoreFactory,  
settings,
                                               qfLogFactory,  
messageFactory);
         }
       }
       connector.start();
       this.run();
       connector.stop();
}

I am running the application with jrockit and java 6, though I doubt  
this is to blame. I realize I can always call "System.exit()" to make  
the application finish, but I figure it shouldn't be necessary if  
things are working correctly...

Many thanks for any help you can provide!
-Dan