Bug 489346 - Possible issue with FailoverManager - segfaults registered
Summary: Possible issue with FailoverManager - segfaults registered
Keywords:
Status: CLOSED DUPLICATE of bug 489351
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 1.1
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: 1.1.1
: ---
Assignee: Gordon Sim
QA Contact: Frantisek Reznicek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-09 16:19 UTC by David Sommerseth
Modified: 2016-05-22 23:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-09 16:37:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description David Sommerseth 2009-03-09 16:19:15 UTC
Using the FailoverManager, the client often segfaults when a broker in a cluster is killed.

** Preparation
- Configure and start openais

- Start 4 brokers which creates a cluster:
$ rm -rf /var/lib/qpidd/qpid1/ && qpidd --worker-threads 10 --log-to-stderr 0 --daemon --cluster-name=rocks --log-to-file /var/log/qpidd1.log --data-dir /var/lib/qpidd/qpid1 --port 5672 --auth 0
$ rm -rf /var/lib/qpidd/qpid2/ && qpidd --worker-threads 10 --log-to-stderr 0 --daemon --cluster-name=rocks --log-to-file /var/log/qpidd2.log --data-dir /var/lib/qpidd/qpid2 --port 9102 --auth 0
$ rm -rf /var/lib/qpidd/qpid3/ && qpidd --worker-threads 10 --log-to-stderr 0 --daemon --cluster-name=rocks --log-to-file /var/log/qpidd3.log --data-dir /var/lib/qpidd/qpid3 --port 9103 --auth 0
rm -rf /var/lib/qpidd/qpid4/ && qpidd --worker-threads 10 --log-to-stderr 0 --daemon --cluster-name=rocks --log-to-file /var/log/qpidd4.log --data-dir /var/lib/qpidd/qpid4 --port 9104 --auth 0

- Start the fom_timed_sender client (will be attached soon)

- Do this loop until the client crashes:
  - Kill qpid process 1 (qpid1)

Comment 1 David Sommerseth 2009-03-09 16:37:54 UTC

*** This bug has been marked as a duplicate of bug 489351 ***


Note You need to log in before you can comment on or make changes to this bug.