topic Error in catalina.out in Alfresco Archive

Error in catalina.out

buxtonmarauder — Thu, 21 Oct 2010 15:21:43 GMT

I'm getting a repeated error in catalina.outERROR: org.alfresco.wcm.client.util.impl.GuestSessionFactoryImpl - Repository not available: Cannot access http://localhost:8080/alfresco/service/cmis: Connection refusedWhen I installed (using the pre-packaged installer of the community edition) I changed

Re: Error in catalina.out

derek — Fri, 22 Oct 2010 22:25:41 GMT

You have the Web Quick Start extension installed:

Change the properties found in:
alfresco/wcmqs-api.properties
by adding properties to:
alfresco/extension/wqsapi-custom.properties

Re: Error in catalina.out

bremmington — Mon, 25 Oct 2010 08:41:47 GMT

The answer above from Derek is correct for builds taken from HEAD (which will become 3.4.b in a couple of weeks' time), but in 3.4.a the API is configured slightly differently. This is described on the wiki here http://wiki.alfresco.com/wiki/Web_Quick_Start_Developer_Guide#Configuring_the_API, a summary of which is to create a file named "wcmqs-api.properties" in a folder named "/webapps/wcmqs/WEB-INF/classes/alfresco/" below your Alfresco Tomcat folder. Put the following into that file:


wcmqs.api.alfresco=http://localhost:8080/alfresco
wcmqs.api.user=admin
wcmqs.api.password=admin

wcmqs.api.alfresco.cmis=%{wcmqs.api.alfresco}/service/cmis
wcmqs.api.alfresco.webscript=%{wcmqs.api.alfresco}/service/api/
‍‍‍‍‍‍‍‍

and then adjust the values as needed in your installation.

For 3.4.b and beyond, properties can be changed individually using the wqsapi-custom.properties file that Derek refers to.

Re: Error in catalina.out

buxtonmarauder — Mon, 25 Oct 2010 12:57:18 GMT

Great.. thanks for the response.

My mistake was to search for the entire URL string when I should have just searched for 8080.

When I do, however, it seems to me that there is a LOT of hard coded references to localhost:8080 in lots of configuration files.

If you allow the installer to offer the ability to utilise a different port upon installation why is that new port not rippled through to all the configuration files ?

Is this something that is different on the enterprise version ?