[CONTROLLER-168] NotSupportedException thrown by ConnectionManager when adding nodes Created: 20/Feb/14  Updated: 25/Jul/23  Resolved: 19/May/16

Status: Resolved
Project: controller
Component/s: adsal
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Moiz Raja Assignee: Unassigned
Resolution: Won't Do 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: 437

 Description   

To reproduce,

1. Get the openflowplugin repo
2. mvn clean install from root
3. Got to the distribution folder and run it.
4. Once the controller has started using mininet add topology using the following command. You should see the following exception,

2014-02-19 17:39:57.359 PST [md-sal-binding-notification-0] ERROR o.o.c.c.scheme.AbstractScheme - Excepion in adding Controller to a Node
javax.transaction.NotSupportedException: BaseTransaction.checkTransactionState - ARJUNA016051: thread is already associated with a transaction!
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:72) ~[na:na]
at org.opendaylight.controller.clustering.services_implementation.internal.ClusterManager.tbegin(ClusterManager.java:594) ~[na:na]
at org.opendaylight.controller.clustering.services_implementation.internal.ClusterManager.tbegin(ClusterManager.java:571) ~[na:na]
at org.opendaylight.controller.clustering.services_implementation.internal.ClusterManagerCommon.tbegin(ClusterManagerCommon.java:255) ~[na:na]
at org.opendaylight.controller.connectionmanager.scheme.AbstractScheme.putNodeToController(AbstractScheme.java:244) [bundlefile:na]
at org.opendaylight.controller.connectionmanager.scheme.AbstractScheme.addNode(AbstractScheme.java:298) [bundlefile:na]
at org.opendaylight.controller.connectionmanager.scheme.AbstractScheme.addNode(AbstractScheme.java:305) [bundlefile:na]
at org.opendaylight.controller.connectionmanager.internal.ConnectionManager.updateNode(ConnectionManager.java:215) [bundlefile:na]
at org.opendaylight.controller.sal.implementation.internal.Inventory.updateNode(Inventory.java:115) [bundlefile:na]
at org.opendaylight.controller.sal.compatibility.InventoryAndReadAdapter.publishNodeUpdate(InventoryAndReadAdapter.java:1031) [bundlefile:na]
at org.opendaylight.controller.sal.compatibility.InventoryAndReadAdapter.onNodeUpdated(InventoryAndReadAdapter.java:631) [bundlefile:na]
at org.opendaylight.controller.sal.compatibility.InventoryAndReadAdapter$$Broker$ListenerInvoker.onNotification(InventoryAndReadAdapter$$Broker$ListenerInvoker.java) [bundlefile:na]
at org.opendaylight.controller.sal.binding.impl.NotifyTask.call(NotifyTask.java:59) [bundlefile:na]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [na:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_45]
at java.lang.Thread.run(Thread.java:744) [na:1.7.0_45]
Caused by: java.lang.IllegalStateException: BaseTransaction.checkTransactionState - ARJUNA016051: thread is already associated with a transaction!
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.checkTransactionState(BaseTransaction.java:266) ~[na:na]
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:68) ~[na:na]
... 16 common frames omitted

 Comments   
Comment by James Gregory Hall [ 07/Mar/14 ]

Hi Moiz,

I'm trying to reproduce this bug. What command you use to add nodes?

I just tried this:

sudo mn --top tree,2 --controller 'remote,ip=192.168.130.184,port=6633' --switch ovskk,protocols=OpenFlow13

and I'm seeing a very different exception.

2014-03-07 04:26:08.852 EST [md-sal-binding-notification-1] ERROR o.o.o.t.OpenflowpluginTestCommandProvider - Error notification flow Xid.........................106
2014-03-07 04:26:08.986 EST [nioEventLoopGroup-10-2] WARN i.n.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
java.lang.NullPointerException: null
at org.opendaylight.openflowplugin.openflow.md.core.sal.convertor.match.MatchConvertorImpl.fromOFMatchToSALMatch(MatchConvertorImpl.java:546) ~[na:na]
at org.opendaylight.openflowplugin.openflow.md.core.translator.PacketInTranslator.translate(PacketInTranslator.java:99) ~[na:na]
at

Comment by Moiz Raja [ 07/Mar/14 ]

James, The command I used was similar to what you used.

Comment by Carol Sanders [ 04/May/15 ]

This bug is part of the project to Move all ADSAL associated component bugs to ADSAL

Comment by Robert Varga [ 19/May/16 ]

AD-SAL has been removed, this issue will not be fixed.

Generated at Wed Feb 07 19:52:21 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.