[
https://issues.apache.org/jira/browse/CLOUDSTACK-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799101#comment-13799101
]
Milamber commented on CLOUDSTACK-4792:
--------------------------------------
I think we need 2 new parameters only (connecttimeout and timeout - the same
for http/https).
I'm not sure if is an acceptable change for minor version 4.2.1 in all cases
(hard coding in code or set by global conf).
I think with that 30 sec timeout (instead of infinite), you introduce a "new
behavior" which may prejudicial for current installation CS 4.2. For example,
if I have a CS installation with a good smtp server but it's very slow (> 30
secs) to accept a new email, then the 30 secs timeout will break the email
sending.
To respect the current behavior (CS 4.X), in my mind, we need to add these new
settings in global conf, with the default value 'infinite' (default value from
javamail), and allows user to change this in the Web UI.
If we select (or prefer to have) the default value to 30 secs, it's must be
annotated in Release Notes of 4.2.1.
I thinks that the master (4.3) branch must have too this new settings.
> Invalid SMTP breaks HA
> ----------------------
>
> Key: CLOUDSTACK-4792
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4792
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Anshul Gangwar
> Assignee: Anshul Gangwar
> Priority: Critical
> Fix For: 4.2.1
>
>
> Putting an invalid smtp ip in alert.smtp.host can potentially stop HA from
> working. If the smtp ip is listening but does not send a proper HELO HA hangs
> and will not proceed. It seems as if the code
> (agent.manager.AgentManagerImpl) doesn't receive a timeout it will not
> proceed.
> I tried putting a bogus ip in alert.smtp.host but HA worked fine. I believe
> we need to make HA independent of smtp alerts or at least put in a timeout so
> HA proceeds.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
