Re: [jira] [Commented] (UIMA-5562) UIMA AS fails with HttpConnector

2017-10-16 Thread Jaroslaw Cwiklik
I plan to include the new AMQ in the next UIMA-AS release. Have not reviewed impact of that change yet. Jerry On Mon, Oct 16, 2017 at 10:04 AM, John (JIRA) wrote: > > [ https://issues.apache.org/jira/browse/UIMA-5562?page= >

[jira] [Commented] (UIMA-5562) UIMA AS fails with HttpConnector

2017-10-16 Thread John (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205952#comment-16205952 ] John commented on UIMA-5562: [~cwiklik], as AMQ 5.15.1 is released now and UIMA AS contains an adapted version

[jira] [Commented] (UIMA-5562) UIMA AS fails with HttpConnector

2017-10-11 Thread Jerry Cwiklik (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200947#comment-16200947 ] Jerry Cwiklik commented on UIMA-5562: - John, I was able to reproduce the problem. The workaround for

Re: [jira] [Commented] (UIMA-5562) UIMA AS fails with HttpConnector

2017-09-27 Thread Jaroslaw Cwiklik
John, can you provide a link to the AMQ JIRA? I am still not following how this is their problem. If this is in fact AMQ problem, than UIMA JIRA should be closed. Thanks Jerry On Tue, Sep 26, 2017 at 5:37 AM, John (JIRA) wrote: > > [

[jira] [Commented] (UIMA-5562) UIMA AS fails with HttpConnector

2017-09-26 Thread John (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180539#comment-16180539 ] John commented on UIMA-5562: Problem is caused by this bug in AMQ. As this is fixed in master it will be part

Re: [jira] [Commented] (UIMA-5562) UIMA AS fails with HttpConnector

2017-09-25 Thread Jaroslaw Cwiklik
Let me review: 1) With tcp based broker specification ( tcp://broker:port ) and prefetch property omitted the deployment works. 2) With http based broker specification ( http://broker:port ) and prefetch property omitted the deployment fails. To fix case#2 you add prefetch property and that

[jira] [Commented] (UIMA-5562) UIMA AS fails with HttpConnector

2017-09-25 Thread John (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178942#comment-16178942 ] John commented on UIMA-5562: A workaround is setting the attribute {{prefetch}} in element {{inputQueue}} in

[jira] [Commented] (UIMA-5562) UIMA AS fails with HttpConnector

2017-09-13 Thread John (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16165022#comment-16165022 ] John commented on UIMA-5562: It works if TCP connector is used on consumer/deploy side. > UIMA AS fails with