[Quickfix-developers] Core after converting to multi threaded application

[Mangalore, C. <cha...@cr...>]

Dear All,

I was trying to decouple the fromApp message receiving and the local
data processing.
I am copying the message received from the fromApp and pushing into the
queue. In the our test environment it worked wonderfully and passed all
the required test cases without any problem.

When we rolled out to production it started coring :-( below is the
stack trace of the core

(dbx) where
current thread: t@15
=>[1] t_delete(0x5d11e8, 0xfe43c008, 0xfe4427cc, 0xfe44284c, 0xfe442848,
0x0), at 0xfe3c27f0
  [2] _malloc_unlocked(0x44, 0x1d20c58, 0xfe43c008, 0x48, 0x5d11e8,
0x0), at 0xfe3c1e80
  [3] malloc(0x44, 0x0, 0xfe43c008, 0xfe3c1ce4, 0x222e8, 0x920f4), at
0xfe3c1cd8
  [4] malloc(0xfe3c1cb8, 0xfe3c1cb8, 0xfe5e3d20, 0x44, 0xc14, 0xc00), at
0xfe551c68
  [5] operator new(0x44, 0xfe3c1cb8, 0x13b88, 0xfe551c68, 0xfee1a08c,
0x44), at 0xfee06528
  [6] FIX::message_order::message_order(0x11, 0x523f38, 0x1400, 0x3,
0x17ac, 0xfe904df4), at 0xfe88a1a0
  [7] FIX::Message::setGroup(0xf6fffad4, 0x61713c, 0x617138, 0xf6fffc5c,
0xf6fff974, 0x0), at 0xfe855d30
  [8] FIX::Message::setString(0xf6fffad4, 0xf6fffc5c, 0x1, 0x5a3090,
0x6872b020, 0xf6fff94c), at 0xfe855a60
  [9] FIX::Message::Message(0xf6fffad4, 0xf6fffc5c, 0x5a3090,
0xf6fffb88, 0xf6fffb50, 0xf6fffb30), at 0xfe853274
  [10] FIX::Session::next(0x5a2f10, 0xf6fffc5c, 0x1, 0xf0e3d8, 0x76294,
0xfe909b74), at 0xfe87db3c
  [11] FIX::ThreadedSocketConnection::processStream(0x52a8e8, 0x1dfe550,
0x0, 0x2df240, 0x0, 0xfe5e3d20), at 0xfe88ebe4
  [12] FIX::ThreadedSocketConnection::readQueue(0x52a8e8, 0xfe90b5a4,
0x4851049f, 0x0, 0x0, 0x0), at 0xfe88ea1c
  [13] FIX::ThreadedSocketConnection::queueThread(0x52a8e8, 0xfe935d38,
0x1, 0xfe378d04, 0x0, 0x2), at 0xfe88f0c4

core '../log/core' of 14663:    
        data model = _ILP32
  /4:   flags = PR_PCINVAL
  sigmask = 0xffffbefc,0x00001fff  cursig = SIGBUS
  /5:   flags = PR_STOPPED
  why = PR_SUSPENDED
  /6:   flags = PR_STOPPED
  why = PR_SUSPENDED
  /7:   flags = PR_STOPPED
  why = PR_SUSPENDED
  sigmask = 0xffbffeff,0x00001fff
  /8:   flags = PR_STOPPED
  why = PR_SUSPENDED
  /9:   flags = PR_STOPPED
  why = PR_SUSPENDED
  /10:  flags = PR_STOPPED
  why = PR_SUSPENDED
  /11:  flags = PR_STOPPED
  why = PR_SUSPENDED
  /12:  flags = PR_STOPPED
  why = PR_SUSPENDED
  /13:  flags = PR_STOPPED
  why = PR_SUSPENDED
  /1:   flags = PR_STOPPED
  why = PR_SUSPENDED
  /2:   flags = PR_STOPPED|PR_ASLWP
  why = PR_SUSPENDED
  sigmask = 0xffbffeff,0x00001fff
  /3:   flags = PR_STOPPED
  why = PR_SUSPENDED

By any chance has anyone this kind of crash? What could be the possible
reason for it?

P.S. I am constructing a new message object and pushing in the queue. Am
I missing something while constructing an object?

You help in this matter will be highly appreciated.


Thanks
-Channa


P Please consider the environment before printing this e-mail. Thank
you. 



==============================================================================
Please access the attached hyperlink for an important electronic communications disclaimer: 

http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
==============================================================================