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
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
