Comment 24 for bug 1099742

I have a 100% repro test case (see mariadb bug from #23) on centos 5.8. Here is the output with wsrep_debug=1:

130212 3:42:48 [Note] WSREP: Shifting OPEN -> CLOSED (TO: 1745947)
130212 3:42:48 [Note] WSREP: New cluster view: global state: 91e773e6-725d-11e2-0800-1d679f8c5252:1745947, view# -1: non-Primary, number of nodes: 1, my index: 0, protocol version 2
130212 3:42:48 [Note] WSREP: Setting wsrep_ready to 0
130212 3:42:48 [Note] WSREP: RECV thread exiting 0: Success
130212 3:42:48 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
130212 3:42:48 [Note] WSREP: recv_thread() joined.
130212 3:42:48 [Note] WSREP: Closing slave action queue.
130212 3:42:48 [Note] WSREP: New cluster view: global state: 91e773e6-725d-11e2-0800-1d679f8c5252:1745947, view# -1: non-Primary, number of nodes: 0, my index: -1, protocol version 2
130212 3:42:48 [Note] WSREP: Setting wsrep_ready to 0
130212 3:42:48 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
130212 3:42:48 [Note] WSREP: applier thread exiting (code:0)
130212 3:42:48 [Note] WSREP: closing applier 5
130212 3:42:48 [Note] WSREP: applier thread exiting (code:5)
130212 3:42:48 [Note] WSREP: closing applier 2
130212 3:42:48 [Note] WSREP: applier thread exiting (code:5)
130212 3:42:48 [Note] WSREP: closing applier 4
130212 3:42:48 [Note] WSREP: applier thread exiting (code:5)
130212 3:42:48 [Note] WSREP: closing applier 3
130212 3:42:50 [Note] WSREP: waiting for client connections to close: 5
130212 3:42:50 [Note] WSREP: Informing thread 5 that it's time to die
130212 3:42:50 [Note] WSREP: Informing thread 4 that it's time to die
130212 3:42:50 [Note] WSREP: Informing thread 3 that it's time to die
130212 3:42:50 [Note] WSREP: Informing thread 2 that it's time to die
130212 3:42:50 [Note] WSREP: Informing thread 1 that it's time to die
130212 3:42:51 [Note] WSREP: Before Lock_thread_count

I will be happy to try any patches or code change suggestions.