|
From: Toli K. <to...@ma...> - 2006-08-15 00:24:31
|
Hi,
I have a basic app that uses QFJ to communicate. I have a bunch of uni
tests running continiously, and they've been passing with the app
linked to 1.0.0-final of QuickFix/J.
However, as soon as i tried switching to 1.0.2 i get the following error:
Exception in thread "QFJ Socket Acceptor 126f75b" java.lang.NullPointerException
at quickfix.mina.SingleThreadedEventHandlingStrategy$SessionMessageEvent.processMessage(SingleThreadedEventHandlingStrategy.java:131)
at quickfix.mina.SingleThreadedEventHandlingStrategy.block(SingleThreadedEventHandlingStrategy.java:70)
at quickfix.mina.SingleThreadedEventHandlingStrategy$1.run(SingleThreadedEventHandlingStrategy.java:86)
at java.lang.Thread.run(Unknown Source)
There's no nested exception, and it's a thread created by QFJ and not my app.
Switching the code back to using 1.0.0-final fixes the problem. I
never used 1.0.1 so i can't tell if the problem manifests itself there
as well.
Any ideas on what could be causing this?
This is happening both on Ubuntu Linux and MacOSX. Not even sure how
to debug this since the exception is coming from a QFJ/mina code.
thanks
|
|
From: Steve B. <st...@te...> - 2006-08-15 06:54:44
|
Hello Toli, It appears that somehow block() is processing a message and session object is null. I've looked at the code and I don't see how this would happen. Is it possible for you to send me your failing unit test failing (off list)? If not, is your application an acceptor or an initiator? Is there anything relevant in the log file? Thanks, Steve > -----Original Message----- > From: qui...@li... > [mailto:qui...@li...] On > Behalf Of Toli Kuznets > Sent: Tuesday, August 15, 2006 2:24 AM > Cc: qui...@li... > Subject: [Quickfixj-users] NullPointerException in QFJ 1.0.2 > that didn'tused to exist in 1.0.0-final > > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > Hi, > > I have a basic app that uses QFJ to communicate. I have a bunch of uni > tests running continiously, and they've been passing with the app > linked to 1.0.0-final of QuickFix/J. > > However, as soon as i tried switching to 1.0.2 i get the > following error: > Exception in thread "QFJ Socket Acceptor 126f75b" > java.lang.NullPointerException > at > quickfix.mina.SingleThreadedEventHandlingStrategy$SessionMessa geEvent.processMessage(SingleThreadedEventHandlingStrategy.java:131) > at > quickfix.mina.SingleThreadedEventHandlingStrategy.block(Single > ThreadedEventHandlingStrategy.java:70) > at > quickfix.mina.SingleThreadedEventHandlingStrategy$1.run(Single > ThreadedEventHandlingStrategy.java:86) > at java.lang.Thread.run(Unknown Source) > > There's no nested exception, and it's a thread created by QFJ > and not my app. > > Switching the code back to using 1.0.0-final fixes the problem. I > never used 1.0.1 so i can't tell if the problem manifests itself there > as well. > > Any ideas on what could be causing this? > This is happening both on Ubuntu Linux and MacOSX. Not even sure how > to debug this since the exception is coming from a QFJ/mina code. > > thanks > > -------------------------------------------------------------- > ----------- > Using Tomcat but need to do more? Need to support web > services, security? > Get stuff done quickly with pre-integrated technology to make > your job easier > Download IBM WebSphere Application Server v.1.0.1 based on > Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057& > dat=121642 > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > |
|
From: Joerg T. <Joe...@ma...> - 2006-08-15 15:46:15
|
On 08/15/06 08:54, Steve Bate wrote:
> It appears that somehow block() is processing a message and session
> object is null. I've looked at the code and I don't see how this would
> happen. Is it possible for you to send me your failing unit test
> failing (off list)? If not, is your application an acceptor or an
> initiator? Is there anything relevant in the log file?
Steve, the same happened to me. Today I got with version 1.0.1 this error=
:
[2006-08-15 17:41:47,472] [INFO ] [quickfix.mina.acceptor.AcceptorIoHandl=
er] (SocketAcceptor-0) MINA
session created: /192.168.1.8:57611
[2006-08-15 17:41:47,573] [DEBUG] [FixLogFactory] (AnonymousIoService-1-2=
)
FIX.4.2:FixGateway->FixClient: incoming:
8=3DFIX.4.2|9=3D62|35=3D5|34=3D1|49=3DFixClient|52=3D20060815-15:41:47.5=
40|56=3DFixGateway|10=3D091|
Exception in thread "QFJ Socket Acceptor 992bae" java.lang.NullPointerExc=
eption
at=20
quickfix.mina.SingleThreadedEventHandlingStrategy$SessionMessageEvent.pro=
cessMessage(SingleThreadedEventHandlingStrategy.java:131)
at=20
quickfix.mina.SingleThreadedEventHandlingStrategy.block(SingleThreadedEve=
ntHandlingStrategy.java:70)
at=20
quickfix.mina.SingleThreadedEventHandlingStrategy$1.run(SingleThreadedEve=
ntHandlingStrategy.java:86)
at java.lang.Thread.run(Thread.java:595)
If I can reproduce this error tomorrow, I will send you more details.
Cheers, J=F6rg
--=20
Joerg Thoennes
http://macd.com
Tel.: +49 (0)241 44597-24 Macdonald Associates GmbH
Fax : +49 (0)241 44597-10 Lothringer Str. 52, D-52070 Aachen
|
|
From: Toli K. <to...@ma...> - 2006-08-15 19:49:38
|
Steve, This appears to be a "heisen-bug". I've spent a fair amount of time trying to isolate and reproduce it, but it seems to have disappeared. There was nothing relevant in the log when the error was reproducible. I have two apps, one is an OrderManagementSystem an the other an ExchangeSimulator. Both use the same underlying core library that uses QFJ, and both send/receive QFJ. However, only the ExchangeSimulator unit tests exhibited this problem, and that code is an Acceptor, while OMS is an Initiator and didn't have the problem. Interestingly, after i went from using 1.0.2 to 1.0.0-final back a forth a few times, the bug has disappeared. I tried it on fresh checkouts, different machines and different users, and it's gone. I'll keep an eye out on its reemergence, and will let the list know. Joerg, if you end up being able to reproduce it as well, please keep me posted and perhaps we can figure the problem out together. thanks for your help! On 8/14/06, Steve Bate <st...@te...> wrote: > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > Hello Toli, > > It appears that somehow block() is processing a message and session > object is null. I've looked at the code and I don't see how this would > happen. Is it possible for you to send me your failing unit test > failing (off list)? If not, is your application an acceptor or an > initiator? Is there anything relevant in the log file? > > Thanks, > > Steve > > > > > -----Original Message----- > > From: qui...@li... > > [mailto:qui...@li...] On > > Behalf Of Toli Kuznets > > Sent: Tuesday, August 15, 2006 2:24 AM > > Cc: qui...@li... > > Subject: [Quickfixj-users] NullPointerException in QFJ 1.0.2 > > that didn'tused to exist in 1.0.0-final > > > > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > > QuickFIX/J Support: http://www.quickfixj.org/support/ > > Hi, > > > > I have a basic app that uses QFJ to communicate. I have a bunch of uni > > tests running continiously, and they've been passing with the app > > linked to 1.0.0-final of QuickFix/J. > > > > However, as soon as i tried switching to 1.0.2 i get the > > following error: > > Exception in thread "QFJ Socket Acceptor 126f75b" > > java.lang.NullPointerException > > at > > quickfix.mina.SingleThreadedEventHandlingStrategy$SessionMessa > geEvent.processMessage(SingleThreadedEventHandlingStrategy.java:131) > > at > > quickfix.mina.SingleThreadedEventHandlingStrategy.block(Single > > ThreadedEventHandlingStrategy.java:70) > > at > > quickfix.mina.SingleThreadedEventHandlingStrategy$1.run(Single > > ThreadedEventHandlingStrategy.java:86) > > at java.lang.Thread.run(Unknown Source) > > > > There's no nested exception, and it's a thread created by QFJ > > and not my app. > > > > Switching the code back to using 1.0.0-final fixes the problem. I > > never used 1.0.1 so i can't tell if the problem manifests itself there > > as well. > > > > Any ideas on what could be causing this? > > This is happening both on Ubuntu Linux and MacOSX. Not even sure how > > to debug this since the exception is coming from a QFJ/mina code. > > > > thanks > > > > -------------------------------------------------------------- > > ----------- > > Using Tomcat but need to do more? Need to support web > > services, security? > > Get stuff done quickly with pre-integrated technology to make > > your job easier > > Download IBM WebSphere Application Server v.1.0.1 based on > > Apache Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057& > > dat=121642 > > _______________________________________________ > > Quickfixj-users mailing list > > Qui...@li... > > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > > > > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > -- Toli Kuznets http://www.marketcetera.com: Open-Source Trading Platform download.run.trade. |
|
From: Steve B. <st...@te...> - 2006-08-15 20:41:46
|
> Toli Kuznets wrote: > This appears to be a "heisen-bug". I've spent a fair amount of time > trying to isolate and reproduce it, but it seems to have disappeared. > There was nothing relevant in the log when the error was reproducible. This sounds like a race condition. I'll try to reproduce with my own test case. The only test I have for block() right now is on the initiator side and I don't use block() myself. I'll also review the code again and see if I can visually spot any potential problems. Of course, if you find more information then send it my way. Regards, Steve |