SOAPConnection sends duplicate payload on SocketException?

Question

Using the version of SAAJ (1.2.2) provided in JWSDP 1.6, it appears that something within the implementation of SOAPConnection's call(message, uri) method will try to re-transmit the message if a SocketException occurs or if the connection receives a RST segment.
Does this seem correct?
I have established a test server where I consume the request sent via:
SOAPMessage response = connection.call(request, endPoint);
and do a close() on the Socket (on the server side), without sending a response back. This triggers a SocketException on the client (desired), but, in monitoring the TCP/IP traffic between the two ports, I can confirm that the contents of 'request' get transmitted twice (undesired!) by the client.
This seems like a bad idea; if I was performing a financial transaction that removed money from my account, I'd hate to have the deduction submitted twice because of some network hiccup.
What I want to do, is accept the SocketException (or whatever) in response, and handle the communications myself (not have the implementation automatically try to recover, or whatever it's doing), so that I can ask the server whether it received the original payload, and resend it if needed.
Any ideas, experience, or insight on this?
Thanks!

Answer 1

Hm, swapping out 1.2.2 and using the Axis 1.3 implementation results in desired behavior; an interruption to the original transaction does not result in a duplicate being sent. Not sure if this is just a matter of difference in implementation, or a bug in the JWSDP libraries ...