Unless you are using rawtransactions or modified your bitcoin.conf file, Bitcoin-Qt should prevent you from creating transactions like this. If you just used the "Send" feature in the User Interface it is very odd that his happened and seems like it could be a bug in the interface.
That being said, yes it is quite unlikely that this transaction will be confirmed anytime in the next few weeks. For that matter, it's unlikely that it will be confirmed in the next few months.
Most of the peers on the bitcoin network aren't relaying the transaction, so most miners aren't even hearing about it. Even if they did hear about it, it is considered very low priority, so other transactions will be confirmed first.
You may want to look into the following process:
- Make certain that you are running Bitcoin-Qt version 0.8.6 (if you are not, then upgrade your Bitcoin-Qt)
- Shut down Bitcoin-Qt
- remove the transaction from your Bitcoin-Qt wallet with pywallet
- leave Bitcoin-Qt shut down for a few days until the transaction is dropped from the memory pool of any peers that might have accepted it
- start Bitcoin-Qt back up
- Send the transaction with a proper fee (at least 0.0004 BTC), and without an output valued at less than 0.00006 BTC
Thanks for the info. Looks like I will have to move my P2Pool server to another machine then do what you suggested after I take pywallet to it.