False error notifcation (double spent) 'code' => -4, 'message' Now and than I seem to get a consistent false error notification.

Error message:


  Request error: array ( 'code' => -4, 'message' => 'Error: The transaction was rejected! This might happen if some of the coins in your wallet were already spent, such as if you used a copy of the wallet and coins were spent in the copy but not marked as spent here.', ).


After the notifcation the getbalance and getbalance '' '1' are in conflict. Getbalance not showing the actual balance correct anymore.
Despite the error the bitcoin transactions gets broadcasted correctly on to the network and within a couple of days (most of the time) the transactions get processed successfully.

Info on client

{
  "version": 130000,
  "protocolversion": 70014,
  "walletversion": 130000,
  "balance": 13.56365098,
  "blocks": 455269,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 440779902286.5892,
  "testnet": false,
  "keypoololdest": 1488349424,
  "keypoolsize": 100,
  "paytxfee": 0.00150000,
  "relayfee": 0.00010000,
  "errors": ""
}


Anyone here having the same problems lately?
The reason for this could be that you spend a long chain of unconfirmed transactions. In 0.14, Core has improved this behaviour and added an startup option called -walletrejectlongchains (needs to be enabled, default is off).

Otherwise your wallet might spend long chains of unconfirmed coins but your node/mempool won't accept them.
Also, have a look at the -limitancestorcount settings and consider reading the pull request here