[DISPATCH-270] Specifying a maxSessions limit of 1 allows unlimited sessions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 0.6.0
• Fix Version/s: 0.6.0
• Component/s: Policy Engine
• Assignee: Unassigned
• Reporter: Charles E. Rolke
• Created: 08/Apr/16 20:58
• Updated: 11/Apr/16 13:36
• Resolved: 11/Apr/16 13:36

Description

This is an issue of cascading magic numbers. Policy keeps the numbers in normal human readable form. The number is decremented when it's handed over to proton to put into channel-max.
So a policy limit of 1 gets decremented to zero when sent to proton. Proton sees a zero and sends no channel-max in the Open frame, allowing the maximum number of sessions.

A user must specify two or more for the maxSessions in order to get the expected number.

Dispatch router policy should fail when a user specifies maxSessions = 1.