What you need is this:
In a *non clustered environment*:
Send a single message, get the server to crash after the send but before the response is written.
Try to send the message again
You should get a PK violation.
If you don't then you've written the test wrong.
Then, create a JIRA task, and fix it as per my comments at the beginning of the thread.
I would recommend a flag in the pm config which ignores duplicate sends and is on in a clustered config, but off otherwise.
I am open to other ideas.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011390#4011390
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011390
"timfox" wrote : I'm not sure what those tests do, but you just need to do this:
|
|
| |
| | 1. send message
| | 2. crash the server in the poison interceptor after the send has been handled but before the response is written
| | 3. client will get an exception
| | 4. try and send the message again - should give a PK violation.
| |
|
|
That's what FailoverTest::testFailureRightAfterSend and FailoverTest::testFailureRightAfterSend are about.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011383#4011383
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011383