[OCPPLUGIN-3] # of outstanding OCP messages per connection should not exceed one Created: 25/Apr/16 Updated: 19/Oct/17 Resolved: 16/Jun/16 |
|
| Status: | Resolved |
| Project: | ocpplugin |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Chin-Hung Chien | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 5793 |
| Priority: | High |
| Description |
|
The current implementation of the OCP plugin does not place a limitation on the number of outstanding OCP messages per connection, and will likely cause the OCP agent (running on RRH) to crash. As per the OCP specification, at any given time, the number of outstanding OCP messages per connection must NOT exceed one. |