[
https://issues.apache.org/jira/browse/DISPATCH-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433791#comment-16433791
]
ASF GitHub Bot commented on DISPATCH-154:
-----------------------------------------
Github user fgiorgetti commented on the issue:
https://github.com/apache/qpid-dispatch/pull/285
Yes I see that as well, but it happens before the connection is
established. Right after that I am seeing the error below:
2018-04-11 08:47:15.086037 -0300 CONN_MGR (info) Configured Connector:
unresolvable.host.name:amqp proto=any, role=normal
(/home/fgiorget/git/qpid-dispatch-fgiorgetti/src/connection_manager.c:623)
2018-04-11 08:47:15.194168 -0300 SERVER (info) Connection to
unresolvable.host.name:amqp failed: **proton:io Name or service not known** -
connect to unresolvable.host.name:5672
(/home/fgiorget/git/qpid-dispatch-fgiorgetti/src/server.c:921)
I will investigate further and report back if in case I find something new.
> dispatch-router coredumps when connector address is unresolvable
> ----------------------------------------------------------------
>
> Key: DISPATCH-154
> URL: https://issues.apache.org/jira/browse/DISPATCH-154
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
> Reporter: Ted Ross
> Assignee: Ted Ross
> Priority: Major
> Fix For: 0.5
>
>
> If the address of a connector is unresolvable, the router will crash upon
> resolution failure. This can be reproduced by adding the following
> configuration:
> {noformat}
> connector {
> addr: unres.bogus.unreg
> port: amqp
> role: on-demand
> saslMechanisms: ANONYMOUS
> name: bogus
> }
> linkRoutePattern {
> prefix: abc
> connector: bogus
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
