[jira] [Commented] (ARTEMIS-950) Change log level from INFO to WARN for "Invalid "host" value "0.0.0.0" detected for..." when Artemis is bound to 0.0.0.0

["Justin Bertram (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858037#comment-15858037 ] 

Justin Bertram commented on ARTEMIS-950:
----------------------------------------

Can you describe the use-case where a connector is being set to "0.0.0.0".  Is this an embedded use-case with a server-side JNDI implementation?

> Change log level from INFO to WARN for "Invalid "host" value "0.0.0.0" detected for..." when Artemis is bound to 0.0.0.0
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-950
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-950
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.5.2
>            Reporter: Martin Stefanko
>            Priority: Minor
>
> If server is bound to 0.0.0.0 then Artemis logs:
> {code}
> 13:21:58,111 INFO  [org.apache.activemq.artemis.jms.server] (ServerService Thread Pool -- 92) AMQ121005: Invalid "host" value "0.0.0.0" detected for "connector" connector. Switching to "dhcp-10-40-5-102.brq.redhat.com". If this new address is incorrect please manually configure the connector to use the proper one.
> {code}
> This is misconfiguration and administrator should be warned. INFO will get lost in the server output.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)