[
http://jira.nuxeo.org/browse/NXP-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florent Guillaume resolved NXP-2790.
------------------------------------
Resolution: Fixed
Done.
http://hg.nuxeo.org/addons/nuxeo-platform-shell/rev/3c1d37cd9883
Also needed a fix in runtime to avoid logging stack traces during connections
to bad IPs:
http://hg.nuxeo.org/nuxeo/nuxeo-runtime/rev/2a68e1bee280
> Nuxeo shell shouldn't cause spurious stack trace in logs
> --------------------------------------------------------
>
> Key: NXP-2790
> URL: http://jira.nuxeo.org/browse/NXP-2790
> Project: Nuxeo Enterprise Platform
> Issue Type: Improvement
> Reporter: Florent Guillaume
> Assignee: Florent Guillaume
> Fix For: 5.1.7
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> When a Nuxeo Shell connects to a Nuxeo server, there is an initial spurious
> log:
> ERROR [SocketServerInvoker] Failed to accept socket connection
> java.lang.reflect.InvocationTargetException
> ...
> Caused by: java.net.SocketException: Connection reset
> This is due to the fact that, to find the correct interface, Nuxeo Shell
> tries to establish a socket to all of the candidates and closes it
> immediately. This immediate close during the scan causes the log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
