What kind of balance are you querying for? *I am querying for ESTIMATED_SPENDABLE balance.* When querying server 2, was the transaction already propagated from server 1 to server 2 (as pending transaction)?
*Yes, the transaction is in pending state i.e The transaction is broadcasted from SERVER 1 wallet but the same wallet which is at SERVER 2 knows about this transaction after 1 confirmation.* I am also facing one more issue in Transaction. i will explain this with an scenario: USER X did a transaction using SERVER 1 and then he did a transaction one more time, This time load balancer redirect his request to SERVER 2 where the same wallet does not knows about his previous transaction done by same wallet from SERVER 1 . The transaction was successful, USER X got different transaction hash for these two transactions. *ISSUE*:The issue here is that one transaction got successfully broadcasted but another one does NOT . The reason i got is *BAD Tranasaction inputs *and the transaction confidenece type i got is DEAD. i think same transaction input is used for both transaction because of which one got broadcasted another one does not. So @Andreas could you please provided some solution for this problem(Transaction and balance issue). I have searched through out internet but i can't get any solution for my problem . How can i synchronize same wallet reside inside two server after transaction. Thanks On Monday, July 3, 2017 at 5:15:18 PM UTC+5:30, Andreas Schildbach wrote: > > What kind of balance are you querying for? Also, when querying server 2, > was the transaction already propagated from server 1 to server 2 (as > pending transaction)? > > In general, I'm not sure if the Bitcoin network protocol is suitable for > synchronizing load-balanced servers. It might be much easier to > introduce server affinity to your load balancing logic. > > > On 06/29/2017 01:32 PM, Ajit Soman wrote: > > We have setup two same bitcoin back-end server for load balancing > > purpose. We are facing an issue on transaction. Consider that a user X > > is going to perform a bitcoin transaction. user X is able to perform > > transaction successfully using SERVER 1 . When user X calls get our > > balance API he gets actual balance from SERVER 1 after that he calls the > > balance API one more time this time load balancer redirect request to > > SERVER 2, he get his previous balance before transaction. After 1 > > confirmation user X is able to see actual balance. > > > > Can anybody suggest how to deal with this issue? > > > > -- > > You received this message because you are subscribed to the Google > > Groups "bitcoinj" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to [email protected] <javascript:> > > <mailto:[email protected] <javascript:>>. > > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "bitcoinj" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
