[
https://issues.apache.org/jira/browse/UIMA-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik resolved UIMA-3588.
---------------------------------
Resolution: Won't Fix
Another fix to deal with "Wire format exception" has been committed under JIRA
https://issues.apache.org/jira/browse/UIMA-3595
> UIMA-AS service should use maxInactivityDurationInitalDelay property
> --------------------------------------------------------------------
>
> Key: UIMA-3588
> URL: https://issues.apache.org/jira/browse/UIMA-3588
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.4.2AS
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Priority: Minor
> Fix For: 2.5.0AS
>
>
> When handling the first request message from a client, the UIMA-AS service
> establishes a connection to a broker, creates a session and a producer and
> caches it for a subsequent use.
> To the broker URL the service currently appends
> wireFormat.maxInactivityDuration=0 to disable inactivity monitor. The service
> should support other decorations as well. For example, the
> wireFormat.maxInactivityDurationInitalDelay=M, to deal with Wire Format
> Negotiation Timeout errors which may occur when the broker is very busy or
> the network is saturated causing delays.
> Consider using a (optional) property file to externalize uima-as settings
> which are currently passed in via -D's.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
