[
https://issues.apache.org/jira/browse/IGNITE-25955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Mukhopadhyay reassigned IGNITE-25955:
--------------------------------------------
Assignee: Aditya Mukhopadhyay
> Change error name/code used in case of a server socket BindException
> --------------------------------------------------------------------
>
> Key: IGNITE-25955
> URL: https://issues.apache.org/jira/browse/IGNITE-25955
> Project: Ignite
> Issue Type: Improvement
> Components: network ai3
> Affects Versions: 3.0.0-beta1
> Reporter: Aditya Mukhopadhyay
> Assignee: Aditya Mukhopadhyay
> Priority: Major
> Labels: ignite-3
>
> [https://github.com/apache/ignite-3/blob/bf4d9a008afbb05df3b26a5b3edf48399ea92ea2/modules/api/src/main/java/org/apache/ignite/lang/ErrorGroups.java#L519]
> The error code PORT_IN_USE is always used in case a BindException is raised
> even though the underlying cause could be an incorrect or an unavailable
> address.
> To effectively communicate that the issue source could be either address or
> port, a more generic error code - something like BIND_ERR - should be used
> instead. This should use the same error code value as PORT_IN_USE, so as to
> not break compatibility with existing clients who are aware only of the
> existing error codes.
> The new error code would effectively be an alias of the old one, having the
> same value. The old error code would have to be marked as deprecated.
> This depends on a future enhancement that allows for aliases to be defined
> for error codes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
