diff options
| author | Rainer Gerhards <rgerhards@adiscon.com> | 2009-06-26 14:08:30 +0200 |
|---|---|---|
| committer | Rainer Gerhards <rgerhards@adiscon.com> | 2009-06-26 14:08:30 +0200 |
| commit | 6be06d50e328c4b8c79b263e176e6b4e384a03f9 (patch) | |
| tree | 4e443d83edf86726e10154bde72afeb2e432e75d /tests/threadingmq.sh | |
| parent | d88803c8e471b0b822108106137f5383c7efd57e (diff) | |
| download | rsyslog-6be06d50e328c4b8c79b263e176e6b4e384a03f9.tar.gz rsyslog-6be06d50e328c4b8c79b263e176e6b4e384a03f9.tar.xz rsyslog-6be06d50e328c4b8c79b263e176e6b4e384a03f9.zip | |
added some basic multithreading tests to testbench
Diffstat (limited to 'tests/threadingmq.sh')
| -rwxr-xr-x | tests/threadingmq.sh | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/tests/threadingmq.sh b/tests/threadingmq.sh new file mode 100755 index 00000000..5c29ec60 --- /dev/null +++ b/tests/threadingmq.sh @@ -0,0 +1,15 @@ +# test many concurrent tcp connections +# we send 100,000 messages in the hopes that his puts at least a little bit +# of pressure on the threading subsystem. To really prove it, we would need to +# push messages for several minutes, but that takes too long during the +# automatted tests (hint: do this manually after suspect changes). Thankfully, +# in practice many threading bugs result in an abort rather quickly and these +# should be covered by this test here. +# rgerhards, 2009-06-26 +echo TEST: threadingmq.sh - main queue concurrency +source $srcdir/diag.sh init +source $srcdir/diag.sh startup threadingmq.conf +source $srcdir/diag.sh tcpflood 127.0.0.1 13514 2 100000 +source $srcdir/diag.sh shutdown-when-empty # shut down rsyslogd when done processing messages +source $srcdir/diag.sh seq-check 0 99999 +source $srcdir/diag.sh exit |