83 - WireAPI: How to 'override' signal handlers?

Reported by g_makulikg_makulik (1263490390|%O ago)

I'm using OpenAPQ WireAPI within a multithreaded application, where the thread that sets up the message receive loop isn't the main thread, but is just one interface to interact with the process.
I should have some reasonable signal handling routines (esp. for SIGTERM, SIGINT & SIGQUIT) that allow to bring my application down using a proper shutdown behavior.
I've read the "Handling Ctrl-C in applications" tutorial of course, but it doesn't get to my point. It makes no sense if the thread using WireAPI 'detects' occurence of certain signals indirectly by asking for the connections (or sessions) alive flag, and inform my main application thread about this. I want to install my own signal handlers, period.
I've been trying several variants (using sigaction, signal), but I'm not able to install my own handlers for SIGTERM and SIGINT. For other signals everything is fine (so my basic approach how to install a signal handler works).
I've been trying to figure out from the WireAPI source code, how and when WireAPIs signal handlers are installed, but without success :-(.

Can anybody point me into the right direction, or is this a (unrecoverable) design flaw in WireAPI? If the latter, so I'd like to place a change request, to provide a mechanism that a WireAPI application may 'hook' the standard handlers somehow.



No files attached to this page.


Add a New Comment

Edit | Files | Tags | Print

rating: 0+x

Who's following this issue?

Watch: site | category | page

Submitted by g_makulikg_makulik

Use one of these tags to say what kind of issue it is:

  • issue - a fault in the software or the packaging or the documentation.
  • change - a change or feature request.

Use one of these tags to say what state the issue is in:

  • open - a new, open issue.
  • closed - issue has been closed.
  • rejected - the issue has been rejected.

Use one of these tags to say how urgent the issue is:

  • fatal - the issue is stopping all work.
  • urgent - it's urgent.

All open

89 - multi-threaded client connection failure (17 Nov 2012 16:28) [open]
87 - Zyre returns incomplete XML (26 Apr 2010 08:15) [open]
86 - SFL 'random(num)' macro is wrong in sfl.h (31 Mar 2010 09:23) [open]
85 - Zyre does not start on Solaris (23 Mar 2010 01:29) [open]
84 - OpenAMQ JMS - AMQTopic constructor use HEADER name and class instead of TOPIC (28 Jan 2010 17:04) [open]
83 - WireAPI: How to 'override' signal handlers? (14 Jan 2010 17:33) [open]
82 - Opf Classes Cannot Accept Default Values With Characte (06 Jan 2010 09:34) [open]
81 - AMQP Topic Exhange Routing (29 Dec 2009 00:21) [open]
80 - OpenAMQ reports malformed frame on 0-9-1 queue.unbind (20 Nov 2009 12:33) [open]
79 - AMQ Server crashing if subscribe topic is set as #.# (30 Oct 2009 06:11) [open]
78 - Error while publishing the messages faster (30 Oct 2009 05:57) [open]
77 - Tuning for latency (28 Oct 2009 16:47) [open]
76 - New user forum (28 Oct 2009 11:29) [change open]
74 - Simulaneous connect/disconnect from multiple threads crashes (03 Sep 2009 15:32) [open]
73 - Topic Exchange not sending a message to XXX.* (25 Aug 2009 21:10) [open]
72 - amq_content_basic_new() causes seg fault if not connected to broker (12 Aug 2009 23:50) [open]
71 - zyre bugs (06 Aug 2009 09:33) [open]
69 - OpenAMQ and Zyre (15 Jul 2009 11:27) [open]
68 - Change names of max and min source code macros (10 Jul 2009 16:52) [open]
67 - Server crash when multiple consumers ack on shared queue (26 Jun 2009 11:35) [open]

page 1 of 212next »

Most recent