[
https://issues.apache.org/jira/browse/ACE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15121461#comment-15121461
]
J.W. Janssen commented on ACE-520:
----------------------------------
There is an option to disable the checking of URLs:
{{agent.discovery.checking}}, by default it is enabled, but that would only
make sense if there are actually more server URLs to check. We should probably
only check URLs if there are more URLs provided.
> Only available serverurl gets blacklisted, broke our application
> ----------------------------------------------------------------
>
> Key: ACE-520
> URL: https://issues.apache.org/jira/browse/ACE-520
> Project: ACE
> Issue Type: Bug
> Components: Management Agent
> Affects Versions: 2.0.1
> Environment: Windows XP and up
> Reporter: Robert Mather
> Labels: ace-next
>
> We only have one ACE server running and it became unavailable for an extended
> period due to a maintenance window. All of our client applications (running
> the agent bundle) blacklisted the server address and failed to detect when
> the server came back online. Also, immediately following the agent
> blacklisting the server, our application's DS services silently stopped
> working (no indication they had been deactivated, just stopped communicating
> with our servers). We had to manually restart the application at all our
> customer locations to get them working again.
> The server and agent were taken from the latest release, 2.0.1, and we're
> using Felix release 5.0.0. The agent bundle is loaded from the Felix auto
> deploy directory. Here are the Felix and ACE settings we use:
> Felix:
> felix.auto.deploy.action=install,start,update
> # DEBUG level logging
> felix.log.level=4
> ACE:
> agent.identification.agentid=<removed>
> agent.discovery.serverurls=<removed>
> agent.controller.syncinterval=420
> agent.logging.level=DEBUG
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
