Thread application dumping on RH4

[parth.b.parekh at jpmorgan.com]

Hi,

I don't know whether its the right place to raise this issue.

We are facing one strange issue. We have one messaging application that 
uses SonicMQ series CPP client libraries. We have one wrapper library 
built over it. We migrated that wrapper library from RH2.1 to RH4. We had 
built that library using -m32 flag. Now when we tried to run that 
application on RH4, we are facing following thread issue:

(gdb) where
#0  0xf772f3f3 in EqQueue<InboundMessage*>::InternalGetExistingItem ()
   from /apps/edgapi/9.0.3.9/linux/lib/libmsgee.so
#1  0xf772ef5a in EqQueue<InboundMessage*>::GetItem ()
   from /apps/edgapi/9.0.3.9/linux/lib/libmsgee.so
#2  0xf7725e18 in EdgEngineData::processInboundMessages ()
   from /apps/edgapi/9.0.3.9/linux/lib/libmsgee.so
#3  0xf772601f in EdgEngineData::dispatcher ()
   from /apps/edgapi/9.0.3.9/linux/lib/libmsgee.so
#4  0xf76b4e35 in EqThread::Execute ()
   from /apps/edgapi/9.0.3.9/linux/lib/libmsges.so
#5  0xf76b3d00 in EqThreadable::IndirectEntryPoint ()
   from /apps/edgapi/9.0.3.9/linux/lib/libmsges.so
#6  0xf76b3d76 in s_Dispatcher ()
   from /apps/edgapi/9.0.3.9/linux/lib/libmsges.so
#7  0x00381371 in start_thread () from /lib/tls/libpthread.so.0
#8  0x003179be in clone () from /lib/tls/libc.so.6


Now to solve this issue, we found out that if we set LD_ASSUME_KERNEL to 
2.4.19, it'll take old thread library and not the NPTL one. So we had to 
set that environment variable. Now the application runs fine but 
infrequently it dumps. The stack trace is as follows:

(gdb) where
#0  0xf79437c8 in java::lang::String::lastIndexOf () from 
/home/release/pyrsyrel/opt/SonicCClient/SonicCClient-RH4.0-6.1-334/Linux_AS4/bin/release/libsmq.so
#1  0xf7bccef0 in progress::message::jclient::DestUtil::getRoutingName ()
   from 
/home/release/pyrsyrel/opt/SonicCClient/SonicCClient-RH4.0-6.1-334/Linux_AS4/bin/release/libsmq.so
#2  0xf7bcd0c2 in progress::message::jclient::DestUtil::getRoutingName ()
   from 
/home/release/pyrsyrel/opt/SonicCClient/SonicCClient-RH4.0-6.1-334/Linux_AS4/bin/release/libsmq.so
#3  0xf7be1d38 in progress::message::jclient::Message::setJMSDestination 
()
   from 
/home/release/pyrsyrel/opt/SonicCClient/SonicCClient-RH4.0-6.1-334/Linux_AS4/bin/release/libsmq.so
#4  0xf7c48391 in 
progress::message::jclient::TopicPublisher::internalPublish ()
   from 
/home/release/pyrsyrel/opt/SonicCClient/SonicCClient-RH4.0-6.1-334/Linux_AS4/bin/release/libsmq.so
#5  0xf7c4aabc in progress::message::jclient::TopicPublisher::publish ()
   from 
/home/release/pyrsyrel/opt/SonicCClient/SonicCClient-RH4.0-6.1-334/Linux_AS4/bin/release/libsmq.so
#6  0xf7f839dd in MessagingUtilities::doPublish (this=0x80b4270, 
topic=<incomplete type>, message=<incomplete type>, priority=4)
    at MessagingUtilities.cpp:732
#7  0xf7f836b4 in MessagingUtilities::processDeferredActions 
(this=0x80b4270) at MessagingUtilities.cpp:644
#8  0xf7f8342b in deferredActionProcessor (data=0x80b4270) at 
MessagingUtilities.cpp:610
#9  0xf7f2ac47 in EqThread::Execute (this=0x80b4bb8) at eqsync.cpp:994
#10 0xf7f29b8e in EqThreadable::IndirectEntryPoint (this=0x80b4bb8) at 
eqsync.cpp:759
#11 0xf7f29c1f in s_Dispatcher (void_thread=0x80b4bb8) at eqsync.cpp:784
#12 0xf75b0ce1 in pthread_start_thread () from /lib/i686/libpthread.so.0
#13 0xf7547ffa in clone () from /lib/i686/libc.so.6



We also tried to directly run the binaries built on RH2.1, on RH4, but we 
face the same issues.
Do you have any clue regarding above issue ?? Any help or information 
would be appreciated.



Thanks & Regards,
Parth Parekh
Pyramid and EIS Messaging AD Support Team
Office:   +44 207 325 5012
Mobile: +44 785 217 4254

This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates. This transmission may contain information that is
privileged, confidential, legally privileged, and/or exempt from
disclosure under applicable law. If you are not the intended
recipient, you are hereby notified that any disclosure, copying,
distribution, or use of the information contained herein (including
any reliance thereon) is STRICTLY PROHIBITED. Although this
transmission and any attachments are believed to be free of any
virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the
recipient to ensure that it is virus free and no responsibility is
accepted by JPMorgan Chase & Co., its subsidiaries and affiliates,
as applicable, for any loss or damage arising in any way from its
use. If you received this transmission in error, please immediately
contact the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you. Please refer
to http://www.jpmorgan.com/pages/disclosures for disclosures
relating to UK legal entities.