Community Edition 6.2 GA docker-compose up hang on proxy

[m_reardon]

Hello, trying to run 6.2 GA on Windows 2019 using EE and Composer.  Startup keeps failing on Proxy, see info below. 

Docker Ver: 19.03.5
Docker Compose Ver: 1.25.5

docker-compose up command, will hang here forever:
PS C:\mtg\docker-compose-6.2-ga> docker-compose up
Starting docker-compose-62-ga_activemq_1 ... done
Starting docker-compose-62-ga_imagemagick_1 ... done
Starting docker-compose-62-ga_solr6_1 ... done
Starting docker-compose-62-ga_postgres_1 ... done
Starting docker-compose-62-ga_tika_1 ... done
Starting docker-compose-62-ga_share_1 ... done
Starting docker-compose-62-ga_alfresco_1 ... done
Starting docker-compose-62-ga_libreoffice_1 ... done
Starting docker-compose-62-ga_alfresco-pdf-renderer_1 ... done
Starting docker-compose-62-ga_transform-misc_1 ... done
Starting docker-compose-62-ga_proxy_1 ...

Verbose Log at point of hang:
compose.parallel.feed_queue: Pending: {<Service: proxy>}
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: {<Service: proxy>}
compose.parallel.feed_queue: Pending: {<Service: proxy>}
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: {<Service: proxy>}
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: {<Service: proxy>}
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: {<Service: proxy>}
compose.parallel.feed_queue: Pending: set()
Starting docker-compose-62-ga_share_1 ... done
0b530fda74dea54ba86f697bbb53/start HTTP/1.1" 204 0
compose.cli.verbose_proxy.proxy_callable: docker start -> None
compose.parallel.parallel_execute_iter: Finished processing: <Container: docker-compose-62-ga_share_1 (a49cf0)>
compose.parallel.feed_queue: Pending: {<Service: proxy>}
compose.parallel.feed_queue: Pending: set()
compose.parallel.parallel_execute_iter: Finished processing: <Service: share>
compose.parallel.feed_queue: Pending: {<Service: proxy>}
compose.parallel.feed_queue: Starting producer thread for <Service: proxy>
Starting docker-compose-62-ga_proxy_1 ...
compose.parallel.feed_queue: Pending: {<Container: docker-compose-62-ga_proxy_1 (32cdee)>}
compose.parallel.feed_queue: Starting producer thread for <Container: docker-compose-62-ga_proxy_1 (32cdee)>
compose.cli.verbose_proxy.proxy_callable: docker attach <- ('32cdee0d279d67b3629161b9b591fc4e5e86cf634de0efb9db076d248a2ca4fd', stdout=True, stderr=True, stream=True)
urllib3.connectionpool._make_request: http://localhost:None "POST /v1.24/containers/32cdee0d279d67b3629161b9b591fc4e5e86cf634de0efb9db076d248a2ca4fd/attach?logs=0&stdout=1&stderr=1&stream=1 HTTP/1.1" 101 0
urllib3.connectionpool._make_request: http://localhost:None "GET /v1.24/containers/32cdee0d279d67b3629161b9b591fc4e5e86cf634de0efb9db076d248a2ca4fd/json HTTP/1.1" 200 None
compose.cli.verbose_proxy.proxy_callable: docker attach -> <docker.types.daemon.CancellableStream object at 0x0000019D8379C588>
compose.cli.verbose_proxy.proxy_callable: docker start <- ('32cdee0d279d67b3629161b9b591fc4e5e86cf634de0efb9db076d248a2ca4fd')
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()

[EddieMay]

Hi @m_reardon & welcome to Alfresco!

How much memory is assigned? Also, have you tried disabling Windows Defender temporarily?

[m_reardon]

Good morning, the VM has 24 GB assigned. I have not adjuted the docker settings to date.  There is no external AV installed, will test by disabling defender and see if that helps. 

[m_reardon]

Disabling defender did not  change the behavior, compose up still hangs on ga_proxy_1. Unsure as to why at this point. 

[EddieMay]

Hi @m_reardon,

Not sure if you've seen this => https://github.com/Alfresco/alfresco-docker-installer? I used this successfully on my Mac to install 6.2 using Docker Desktop.  I encountered a couple of issues relating to Yeoman but Google quickly resolved these.

HTH,

[m_reardon]

Update,

I doubled the memory allocated to Proxy and I was able to get beyond my first sticking point.  Now the Alfresco image is throwing and error on load:

alfresco_1 | 2020-04-23 12:20:57,291 WARN [context.support.XmlWebApplicationContext] [localhost-startStop-1] Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.beans.factory.config.CustomEditorConfigurer#0' defined in class path resource [alfresco/core-services-context.xml]: Cannot resolve reference to bean 'customPropertyEditorRegistrar' while setting bean property 'propertyEditorRegistrars' with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'customPropertyEditorRegistrar' defined in class path resource [alfresco/core-services-context.xml]: Cannot resolve reference to bean 'NamespaceService' while setting bean property 'namespaceService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dictionaryDAO' defined in class path resource [alfresco/core-services-context.xml]: Cannot resolve reference to bean 'tenantService' while setting bean property 'tenantService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'tenantService' defined in URL [jar:file:/usr/local/tomcat/webapps/alfresco/WEB-INF/lib/alfresco-repository-7.134.1.jar!/alfresco/mt/mt-context.xml]: Cannot resolve reference to bean 'tenantAdminDAO' while setting bean property 'tenantAdminDAO'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'tenantAdminDAO' defined in class path resource [alfresco/dao/dao-context.xml]: Cannot resolve reference to bean 'repoSqlSessionTemplate' while setting bean property 'sqlSessionTemplate'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'repoSqlSessionTemplate' defined in class path resource [alfresco/ibatis/ibatis-context.xml]: Cannot resolve reference to bean 'repoSqlSessionFactory' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'repoSqlSessionFactory' defined in class path resource [alfresco/ibatis/ibatis-context.xml]: Cannot resolve reference to bean 'dialectResourceLoader' while setting bean property 'resourceLoader'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dialectResourceLoader' defined in class path resource [alfresco/ibatis/ibatis-context.xml]: Cannot create inner bean 'org.springframework.beans.factory.config.PropertyPathFactoryBean#46906a69' of type [org.springframework.beans.factory.config.PropertyPathFactoryBean] while setting bean property 'dialectClass'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.beans.factory.config.PropertyPathFactoryBean#46906a69' defined in class path resource [alfresco/ibatis/ibatis-context.xml]: Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dialect': FactoryBean threw exception on object creation; nested exception is org.springframework.jdbc.CannotGetJdbcConnectionException: Failed to obtain JDBC Connection; nested exception is org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (The connection attempt failed.)
alfresco_1 | 2020-04-23 12:20:57,310 ERROR [web.context.ContextLoader] [localhost-startStop-1] Context initialization failed

[EddieMay]

Hi,

Are you using a database for persistence? Similar errors reported here and here point to DB connection issues.

[m_reardon]

Hi, this is my first attempt at startup, I have not yet modified any settings other then the memory allocation to Proxy yet. 

[m_reardon]

Update on the issue.  reset permissions on the folder with the yaml file and c:\programdata\docker to allow full access.   Post change Postgres now starts which is progress.  New error on image Alfresco1: "WARNING: An illegal reflective access operation has ccurred" on startup. Trying to sort out this new latest issue. 

[afaust]

The "WARNING: An illegal reflective access operation has ccurred" is to be expected. This is not an error, but a warning about some library in Alfresco making a refective call which may be forbidden in future Java versions. In JDK 11 though it is still allowed, especially with the start configuration used by Alfresco, but it still emits a warning. This is a Java-emitted warning and Alfresco cannot suppress it. It has no functional consequences at this point.