[jira] [Closed] (UIMA-3617) UIMA-AS not handling broker url params correctly

["Jerry Cwiklik (JIRA)" <de...@uima.apache.org>]

     [ https://issues.apache.org/jira/browse/UIMA-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik closed UIMA-3617.
-------------------------------

    Resolution: Fixed

> UIMA-AS not handling broker url params correctly 
> -------------------------------------------------
>
>                 Key: UIMA-3617
>                 URL: https://issues.apache.org/jira/browse/UIMA-3617
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.4.2AS
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.5.0AS
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)