Port binding / Address already in use exception in Alfresco:
If you face above exception/errors in your alfresco logs, it means you are have a conflict with the port which is already running the service.
Steps to troubleshoot and resolve:
1) Check the logs carefully and find out which port is already bind (in use) and by which application it is used. It can be any other java application hosted in your tomcat or other application server.
2) Your alfresco uses multiple ports like tomcat port 8080 for startup, 8005 for shutdown, 50500 for RMI, 8009 for AJP, 8443 for redirect/secured connection/ssl etc.
One of these ports can conflict with your running services.
3) To ensure that you get rid off the above error, you need to change the port of either your running application or alfresco.
4) For changing the alfresco services ports, you need to make the change in the following files:
a) Stop alfresco (if already running)
b) Assuming that your alfresco is hosted in tomcat container, go to ALFRESCO_INSTALLATION_DIR/tomcat/conf/server.xml file:
Change the port no. 8080 to say 8081 (which should not be already in use).
Same way change the port no. 8443 and 8009 to other ports. Save it.
c) Open alfresco-global.properties and see if you have mentioned in port in alfresco.host , share.host properties.
Change the port no. If you have found conflicting port as 50500 (for RMI), then change the port in this property: alfresco.rmi.services.port=50500
d) If you are changing the solr port in alfresco-global.properties (i.e solr.port.ssl=8443 and solr.port=8080), then you need to make the change in solrcore.properties file also (ALFRESCO_INSTALLATION_DIR/solr4/workspace-SpacesStore/conf and /opt/alfresco-5.0.2.2/solr4/archive-SpacesStore/conf)
Changing the solr port, but not making the port change in solrcore.properties will result in Model tracking failed error in alfresco logs on startup.
As a result of which, alfresco search won't work. Because alfresco won't be able to create indexes at the desired location if the port doesnot match.
e) Open share-config-custom.xml file, check for the port usage. There might be occurences of <endpoint-url> which you might require to change after port change. Change it and save.
f) Start alfresco.
Following above steps should resolve the error.
If you face above exception/errors in your alfresco logs, it means you are have a conflict with the port which is already running the service.
Steps to troubleshoot and resolve:
1) Check the logs carefully and find out which port is already bind (in use) and by which application it is used. It can be any other java application hosted in your tomcat or other application server.
2) Your alfresco uses multiple ports like tomcat port 8080 for startup, 8005 for shutdown, 50500 for RMI, 8009 for AJP, 8443 for redirect/secured connection/ssl etc.
One of these ports can conflict with your running services.
3) To ensure that you get rid off the above error, you need to change the port of either your running application or alfresco.
4) For changing the alfresco services ports, you need to make the change in the following files:
a) Stop alfresco (if already running)
b) Assuming that your alfresco is hosted in tomcat container, go to ALFRESCO_INSTALLATION_DIR/tomcat/conf/server.xml file:
Change the port no. 8080 to say 8081 (which should not be already in use).
Same way change the port no. 8443 and 8009 to other ports. Save it.
c) Open alfresco-global.properties and see if you have mentioned in port in alfresco.host , share.host properties.
Change the port no. If you have found conflicting port as 50500 (for RMI), then change the port in this property: alfresco.rmi.services.port=50500
d) If you are changing the solr port in alfresco-global.properties (i.e solr.port.ssl=8443 and solr.port=8080), then you need to make the change in solrcore.properties file also (ALFRESCO_INSTALLATION_DIR/solr4/workspace-SpacesStore/conf and /opt/alfresco-5.0.2.2/solr4/archive-SpacesStore/conf)
Changing the solr port, but not making the port change in solrcore.properties will result in Model tracking failed error in alfresco logs on startup.
As a result of which, alfresco search won't work. Because alfresco won't be able to create indexes at the desired location if the port doesnot match.
e) Open share-config-custom.xml file, check for the port usage. There might be occurences of <endpoint-url> which you might require to change after port change. Change it and save.
f) Start alfresco.
Following above steps should resolve the error.
No comments:
Post a Comment