set typeManager service declaration to look at local first and avoid flooding
logs with warnings on a multimachine deployment
-----------------------------------------------------------------------------------------------------------------------------
Key: NXP-3015
URL: http://jira.nuxeo.org/browse/NXP-3015
Project: Nuxeo Enterprise Platform
Issue Type: Improvement
Reporter: Julien Carsique
For the moment, on a bi-machine, logs are flooded by:
WARN [org.nuxeo.runtime.api.ServiceManager] Existing binding but unreachable
service for org.nuxeo.ecm.platform.types.TypeManager ! Fallback on local
service...
DEBUG [org.nuxeo.runtime.api.ServiceManager] TypeManagerBean not bound Check
binding declaration: [name=null, group=platform,
instanceName=org.nuxeo.ecm.platform.types.TypeManager locator:
nuxeo/TypeManagerBean/remote]
The logs shouldn't be changed as this warning is pertinent in other cases, for
other services.
--
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
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
