[OPNFLWPLUG-935] TransactionChain created in OperationProcessor.<init> line 36 is never closed Created: 29/Aug/17 Updated: 27/Sep/21 Resolved: 06/Sep/17 |
|
| Status: | Resolved |
| Project: | OpenFlowPlugin |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Michael Vorburger | Assignee: | Jozef Bacigal |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||||||||||||||
| External issue ID: | 9071 | ||||||||||||||||||||
| Description |
|
As found in see TransactionChain created in OperationProcessor.<init> line 36 is never closed |
| Comments |
| Comment by Abhijit Kumbhare [ 31/Aug/17 ] |
|
Any thoughts Tomas or someone? |
| Comment by Michael Vorburger [ 31/Aug/17 ] |
|
FYI: Since opening this bug (and others like it) I've understood that this is not yet necessarily proof of a real problem - see e.g. discussion in Basically if this OperationProcessor (which I've absolutely no idea what it is, obviously) has a lifecycle of application scope, that is if its an object you (Blueprint) creates on boot, with a single instance which stays alive for the entire ODL lifetime, where you create ONE (and always only ever one, never more) TransactionChain in there, and you are sure that under load you are not creating more TransactionChain instances which are never closed, then this was a false positive - please feel free to close this as RESOLVED INVALID, if you are sure that this it the case here (like in Also, I'll see if the |
| Comment by Michael Vorburger [ 06/Sep/17 ] |
|
Dupe to |