[UIMA-3617] UIMA-AS not handling broker url params correctly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.2AS
• Fix Version/s: 2.6.0AS
• Component/s: Async Scaleout
• Assignee: Jaroslaw Cwiklik
• Reporter: Jaroslaw Cwiklik
• Created: 14/Feb/14 19:41
• Updated: 18/Feb/14 19:20
• Resolved: 18/Feb/14 19:20

Description

When handling a reply the uima-as service creates a jms connection using broker url provided by the client and caches it for reuse. The broker url is actually modified to add wireFormat.maxInactivityDuration=0 to turn off amq inactivity monitor.

The problem is that the code assumes that the client's broker url doesnt contain any params and just appends its own with ?wireFormat.maxInactivityDuration=0.

Assuming that client uses the following broker ur: tcp://localhost:61616?wireFormat.maxFrameSize=209715200

The uima-as service code will incorrectly modify it as follows:

tcp://localhost:61616?wireFormat.maxFrameSize=209715200?wireFormat.maxInactivityDuration=0.

Whats strange is that the connection is made with the above with no error.
The AMQ code seems to skip to the last ? and parses from there. The consequence is that client's parameters are lost.