[LISPMAP-141] Error during Map-Register performance test Created: 11/Oct/16  Updated: 19/Oct/17  Resolved: 13/Oct/16

Status: Resolved
Project: lispflowmapping
Component/s: Service
Affects Version/s: Boron
Fix Version/s: None

Type: Bug
Reporter: Lori Jakab 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: 6925
Priority: Normal

 Description   

When doing performance testing, these errors show up in the logs, and performance decreases for Map-Registers.

2016-10-11 10:32:00,230 | ERROR | pool-24-thread-1 | DOMNotificationRouterEvent | 167 - org.opendaylight.controller.sal-broker-impl - 1.5.0.SNAPSHOT | Delivery of notification org.opendaylight.controller.md.sal.binding.impl.LazySerializedDOMNotification@533ce44e caused an error in listener org.opendaylight.controller.md.sal.binding.impl.BindingDOMNotificationListenerAdapter@495c4b05
java.lang.NullPointerException

 Comments   
Comment by Lori Jakab [ 11/Oct/16 ]

This bug was introduced while fixing LISPMAP-126 with https://git.opendaylight.org/gerrit/#/c/43473/

Comment by Lori Jakab [ 11/Oct/16 ]

Full stack trace:

2016-10-11 11:12:05,812 | ERROR | pool-24-thread-1 | DOMNotificationRouterEvent | 167 - org.opendaylight.controller.sal-broker-impl - 1.5.0.SNAPSHOT | Delivery of notification org.opendaylight.controller.md.sal.binding.impl.LazySerializedDOMNotification@a8d2b9f caused an error in listener org.opendaylight.controller.md.sal.binding.impl.BindingDOMNotificationListenerAdapter@4e01d9e3
java.lang.NullPointerException
at org.opendaylight.lispflowmapping.mapcache.SimpleMapCache.getXtrIdTable(SimpleMapCache.java:74)[274:org.opendaylight.lispflowmapping.mappingservice.mapcache:1.5.0.SNAPSHOT]
at org.opendaylight.lispflowmapping.mapcache.SimpleMapCache.updateMappingRegistration(SimpleMapCache.java:343)[274:org.opendaylight.lispflowmapping.mappingservice.mapcache:1.5.0.SNAPSHOT]
at org.opendaylight.lispflowmapping.implementation.MappingSystem.updateMappingRegistration(MappingSystem.java:117)[275:org.opendaylight.lispflowmapping.mappingservice.implementation:1.5.0.SNAPSHOT]
at org.opendaylight.lispflowmapping.implementation.MappingService.updateMappingRegistration(MappingService.java:190)[275:org.opendaylight.lispflowmapping.mappingservice.implementation:1.5.0.SNAPSHOT]
at org.opendaylight.lispflowmapping.implementation.LispMappingService.onMappingKeepAlive(LispMappingService.java:237)[275:org.opendaylight.lispflowmapping.mappingservice.implementation:1.5.0.SNAPSHOT]
at org.opendaylight.yangtools.yang.binding.util.NotificationListenerInvoker.invokeNotification(NotificationListenerInvoker.java:91)[73:org.opendaylight.mdsal.yang-binding:0.10.0.SNAPSHOT]
at org.opendaylight.controller.md.sal.binding.impl.BindingDOMNotificationListenerAdapter.onNotification(BindingDOMNotificationListenerAdapter.java:44)[169:org.opendaylight.controller.sal-binding-broker-impl:1.5.0.SNAPSHOT]
at org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouterEvent.deliverNotification(DOMNotificationRouterEvent.java:56)[167:org.opendaylight.controller.sal-broker-impl:1.5.0.SNAPSHOT]
at org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouter$1.onEvent(DOMNotificationRouter.java:68)[167:org.opendaylight.controller.sal-broker-impl:1.5.0.SNAPSHOT]
at org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouter$1.onEvent(DOMNotificationRouter.java:65)[167:org.opendaylight.controller.sal-broker-impl:1.5.0.SNAPSHOT]
at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:129)[154:com.lmax.disruptor:3.3.4]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_91]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_91]

Comment by Lori Jakab [ 11/Oct/16 ]

Fix proposed: https://git.opendaylight.org/gerrit/#/c/46799/

Needs to be back-ported to Boron.

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