Re: FW: [Quickfix-developers] QF 1.6 JVM crashes on connect/logon.
Brought to you by:
orenmnero
From: Alex H. <al...@an...> - 2003-10-22 11:30:15
|
Yes, the Linux JVMs really don't like it when start() creates a thread from C++. Using blockingStart() avoids this - if you want the equivalent of the start() behavoir you can always create a thread in java then call blockingStart() in it. Perhaps the java start() implementations should not call the C++ start(), and instead be implemented in terms of creating a Java thread from java, then calling blockingStart()? - that way we avoid the "java thread created from C++" problem. Cheers, Alex. Verma, Sanjay wrote: > While the apparent problem was not exactly the same as Arif's problem, > I guess the root cause was the same. Thanks for pointing me to it > Asad. I replaced start() with blockingStart() and the JVM stopped > crashing. > > -----Original Message----- > *From:* Verma, Sanjay > *Sent:* Monday, October 20, 2003 6:36 PM > *To:* 'qui...@li...' > *Subject:* FW: [Quickfix-developers] QF 1.6 JVM crashes on connect/logon. > > I managed to attach gdb to the running JVM and tried debugging the C++ > source code. The JVM crash is not always in the same place or at the > same execution sequence. Sometimes it crashes in ~Acceptor though I > have also seen it crash in ~SessionID. Also, sometimes it crashes as > soon as the logon message is received whereas other times it chashes > after responding to the first heartbeat message! > > I am using JDK 1.4.2 on RedHat Linux 8. QuickFix version, as I > mentioned, is 1.6 > > It I am attaching the captured output here. Hopefully it is not too > much! Any help would be welcome. > > Thanks. > > > -----Original Message----- > *From:* Verma, Sanjay > *Sent:* Monday, October 20, 2003 3:20 PM > *To:* qui...@li... > *Subject:* [Quickfix-developers] QF 1.6 JVM crashes on connect/logon. > > I am using version 1.6. I have a thread in a program that accepts > connections. As soon as the tradeclient (example) connects and sends a > login message, the JVM crashes. The output is not particularly > helpful. This happens repeatedly. No other debugging info is > available. I cannot seem to use either jdb or strace to get any further. > > 1. Has anyone else run into this? > 2. How do you debug when you have problem such as this? What debugger > or what means of getting more info? > > Thanks. > DISCLAIMER > e-mail, and any attachments thereto, is intended only for use by the > addressee(s) named herein and may contain legally privileged and/or > confidential information. If you are not the intended recipient of > this e-mail, you are hereby notified that any dissemination, > distribution or copying of this e-mail, and any attachments thereto, > is strictly prohibited. If you have received this e-mail in error, > please immediately notify me and permanently delete the original and > any copy of any e-mail and any printout thereof. > > E-mail transmission cannot be guaranteed to be secure or error-free. > The sender therefore does not accept liability for any errors or > omissions in the contents of this message which arise as a result of > e-mail transmission. > > REGARDING PRIVACY AND CONFIDENTIALITY > Crown Financial Group may, at its discretion, monitor and review the > content of all e-mail communications. > > DISCLAIMER > > e-mail, and any attachments thereto, is intended only for use by the > addressee(s) named herein and may contain legally privileged and/or > confidential information. If you are not the intended recipient of > this e-mail, you are hereby notified that any dissemination, > distribution or copying of this e-mail, and any attachments thereto, > is strictly prohibited. If you have received this e-mail in error, > please immediately notify me and permanently delete the original and > any copy of any e-mail and any printout thereof. > > > E-mail transmission cannot be guaranteed to be secure or error-free. > The sender therefore does not accept liability for any errors or > omissions in the contents of this message which arise as a result of > e-mail transmission. > > REGARDING PRIVACY AND CONFIDENTIALITY > > Crown Financial Group may, at its discretion, monitor and review the > content of all e-mail communications. > > > DISCLAIMER > > e-mail, and any attachments thereto, is intended only for use by the > addressee(s) named herein and may contain legally privileged and/or > confidential information. If you are not the intended recipient of > this e-mail, you are hereby notified that any dissemination, > distribution or copying of this e-mail, and any attachments thereto, > is strictly prohibited. If you have received this e-mail in error, > please immediately notify me and permanently delete the original and > any copy of any e-mail and any printout thereof. > > > E-mail transmission cannot be guaranteed to be secure or error-free. > The sender therefore does not accept liability for any errors or > omissions in the contents of this message which arise as a result of > e-mail transmission. > > REGARDING PRIVACY AND CONFIDENTIALITY > > Crown Financial Group may, at its discretion, monitor and review the > content of all e-mail communications. > > |