[TOPOPROCES-42] Concurent exception is thrown while processing aggregation Created: 25/Nov/15  Updated: 24/Nov/17  Resolved: 19/Feb/16

Status: Resolved
Project: topoprocessing
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Samuel Kontris Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 4673

 Description   

Sometimes (not always) exception is thrown while processing aggregation.
This causes that in resulting topology are not all nodes that meets specified criteria.

This exception is thrown:
Exception in thread "CommitFutures-4" java.lang.NullPointerException
at org.opendaylight.topoprocessing.impl.writer.TopologyWriter.onTransactionChainFailed(TopologyWriter.java:263)
at org.opendaylight.controller.md.sal.dom.broker.impl.PingPongTransactionChain$1.onTransactionChainFailed(PingPongTransactionChain.java:102)
at org.opendaylight.controller.cluster.databroker.DOMBrokerTransactionChain.transactionFailed(DOMBrokerTransactionChain.java:137)
at org.opendaylight.controller.cluster.databroker.DOMBrokerTransactionChain.access$100(DOMBrokerTransactionChain.java:30)
at org.opendaylight.controller.cluster.databroker.DOMBrokerTransactionChain$1.onFailure(DOMBrokerTransactionChain.java:98)
at com.google.common.util.concurrent.Futures$6.run(Futures.java:1310)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

 Comments   
Comment by Andrej Záň [ 22/Dec/15 ]

When this problem appear, there is also lot of OptimisticLockFailedException exceptions:
OptimisticLockFailedException

{message=Optimistic lock failed., errorList=[RpcError [message=Optimistic lock failed., severity=ERROR, errorType=APPLICATION, tag=resource-denied, applicationTag=null, info=null, cause=org.opendaylight.yangtools.yang.data.api.schema.tree.ConflictingModificationAppliedException: Node was created by other transaction.]]}

...

This can be seen for example in this CSIT job karaf.log:
https://jenkins.opendaylight.org/releng/job/topoprocessing-csit-verify-1node-topology-operations/40/
There is also above mentioned ConcurentException

Comment by Andrej Záň [ 19/Feb/16 ]

Boron: https://git.opendaylight.org/gerrit/#/c/34687/
Beryllium: https://git.opendaylight.org/gerrit/#/c/34813/

Generated at Wed Feb 07 20:40:32 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.