[
https://issues.apache.org/jira/browse/DEFT-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084631#comment-13084631
]
Johnathan Meehan commented on DEFT-131:
---------------------------------------
I think so; the behaviour is now potentially quite confusing as we might
retrieve something entirely unexpected. If the caller is making this kind of
mistake, we should probably just let him know. Perhaps it's enough to document
the thrown exception for the affected methods?
> AsynchronousHttpClient.fetch(..) "leaks" IllegalArgumentException if port is
> out of range
> -----------------------------------------------------------------------------------------
>
> Key: DEFT-131
> URL: https://issues.apache.org/jira/browse/DEFT-131
> Project: Deft
> Issue Type: Bug
> Assignee: Johnathan Meehan
> Priority: Trivial
> Fix For: 0.4.0
>
>
> Exception in thread "I/O-LOOP" java.lang.IllegalArgumentException: port out
> of range:80811
> Its because we create an java.net.InetSocketAddress..
> doc for ISA:
> IllegalArgumentException - if the port parameter is outside the range of
> valid port values, or if the hostname parameter is null.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
