No - as I mentioned the caller must coordinate access.
On Tue, Mar 7, 2017 at 2:06 AM, Satish Dutt wrote:
> Yes Tom, we are accessing a chain concurrently. Is there any waiting
> mechanism provided by the transaction chain such that the transaction chain
> waits for
Yes Tom, we are accessing a chain concurrently. Is there any waiting mechanism
provided by the transaction chain such that the transaction chain waits for
allocating a new one till the previous write transaction is submitted ?
Regards
-Satish
From: Tom Pantelis [mailto:tompante...@gmail.com]
It seems you're trying to access a chain concurrently? If so, this is not
supported. You must coordinate access to the chain such that the previous
write transaction is submitted before you allocate a new one.
Tom
On Mon, Mar 6, 2017 at 7:05 AM, Satish Dutt wrote:
>
On 03/06/2017 01:05 PM, Satish Dutt wrote:
> Thanks Robert for the clarification. So to solve the issue, can I handle this
> IllegalStateException and retry the read or write operations for a finite
> number of times, which makes the best effort of previous write-capable
> transactions to get
Hello controller-dev,
do you know what could be causing this new SingleFeatureTest (SFT) failure?
java.lang.IllegalStateException: Can't install feature
odl-netvirt-api/0.4.0-SNAPSHOT:
Could not start bundle
mvn:org.opendaylight.controller/blueprint/0.6.0-SNAPSHOT in feature(s)
Hello Team,
I have an application (let us assume here HelloWorld App only). In that i
define rpc and register this rpc to RpcProviderRegistry.
Please clarify on this,
1. When i invoke the NB rest API, how the restconf gets the context of this
particular provider and invoking this
Thanks Robert for the clarification. So to solve the issue, can I handle this
IllegalStateException and retry the read or write operations for a finite
number of times, which makes the best effort of previous write-capable
transactions to get completed. Or is there a more elegant way of solving
On 03/06/2017 12:39 PM, Satish Dutt wrote:
> When multiple requests are sent concurrently, IllegalStateException is
> thrown. Is there any way to solve this issue, apart from synchronizing
> the method which does the above operations ?
This is actually part of the API contract:
Hi,
In a method we are creating a new instance of ReadOnlyTransaction and
WriteTransaction from the transaction chain and subsequently doing the read and
write operations on the datastore. When multiple requests are sent
concurrently, IllegalStateException is thrown. Is there any way to solve