2014-05-28 12:51:21,544 | qtp9134464-89 | ResponseTrackerImpl | WARN | Received multiple responses for reservationId W3sia2V5IjoiMDExMjc0NkQ5RDNBMjJDQ0E0QUQ3NEM1Njg3NjgzRDkiLCJ1cm5QcmVmaXgiOiJ1cm46d2lzZWJlZDp1emwxOiJ9XQ== and requestId -209749208858434418. Ignoring subsequent responses...
2014-05-28 12:51:21,545 | qtp9134464-89 | ResponseTrackerImpl | WARN | Received multiple responses for reservationId W3sia2V5IjoiMDExMjc0NkQ5RDNBMjJDQ0E0QUQ3NEM1Njg3NjgzRDkiLCJ1cm5QcmVmaXgiOiJ1cm46d2lzZWJlZDp1emwxOiJ9XQ== and requestId -209749208858434418. Ignoring subsequent responses...
2014-05-28 12:51:21,545 | qtp9134464-89 | ResponseTrackerImpl | WARN | Received multiple responses for reservationId W3sia2V5IjoiMDExMjc0NkQ5RDNBMjJDQ0E0QUQ3NEM1Njg3NjgzRDkiLCJ1cm5QcmVmaXgiOiJ1cm46d2lzZWJlZDp1emwxOiJ9XQ== and requestId -209749208858434418. Ignoring subsequent responses...
It seems that some operation (or requestId) was messed up and responses were correlated wrongly. It seems there's a conflict with some "old" requestId, this time resulting in operations always showing "ERROR: node is not connected" as response.
From the logs:
It seems that some operation (or requestId) was messed up and responses were correlated wrongly. It seems there's a conflict with some "old" requestId, this time resulting in operations always showing "ERROR: node is not connected" as response.