ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexWebSphere Technologies FAQEnvironment variable AMQ_ABORT_ON_EXCEPTION

Post new topicReply to topic
Environment variable AMQ_ABORT_ON_EXCEPTION View previous topic :: View next topic
Author Message
xiiszb
PostPosted: Fri Nov 22, 2002 12:45 am Post subject: Environment variable AMQ_ABORT_ON_EXCEPTION Reply with quote

Newbie

Joined: 17 Mar 2002
Posts: 2
Location: Triaton GmbH

What is the meaning of the variable AMQ_ABORT_ON_EXCEPTION and where can I find a description?
Back to top
View user's profile Send private message
dgolding
PostPosted: Fri Nov 22, 2002 6:13 am Post subject: Reply with quote

Yatiri

Joined: 16 May 2001
Posts: 668
Location: Switzerland

Here's an excerpt from an earlier post of mine (copied from the world-renowned Justin Fries). Basically, this variable determines if MQ cuts a coredump when it traps a SEGV or something - or generates an unhelpful FDC that makes you thing it's MQ in error, and not the program. AFAIK is yet another undocumented feature of MQ.

The post is at:

http://www.webmq.com/phpBB2/viewtopic.php?t=4104

here's the relevant bit:

In order to solve these problems, I suggest exporting
AMQ_ABORT_ON_EXCEPTION=TRUE. If this variable is set in the environment in
which the application is running, the MQSeries exception handler will abort
the process after cutting the FDC. This will produce a core file which we
can investigate to determine conclusively who is at fault and what needs to
be done to solve the problem. If the failing program is an MQSeries
program we can examine the core file, but if it is a customer program they
will need to use dbx, gdb, or their favourite debugger to dump the stacks
for each thread in the process. We can examine cores from customer
applications only when we have their compiled application as well as all
libraries on which it depends. If their application is linked with
MQSeries, Tuxedo, Oracle, CORBA, and half a dozen other things, forget it.
If it's a straight MQSeries application we may be able to work on it
provided that we have the binary program, the core file, and a system at
the same OS and maintenance level. If not, things get very tricky very
quickly.

I hope this helps.

Cheers,

Justin T. Fries
MQSeries Support
Raleigh, North Carolina
(919) 254-1422 TL 444-1422
Email: justinf@us.ibm.com
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Technologies FAQEnvironment variable AMQ_ABORT_ON_EXCEPTION
Jump to:



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.