topic Re: SDK 3.0.1 - not running in Alfresco Forum

SDK 3.0.1 - not running

kem — Wed, 28 Feb 2018 14:42:55 GMT

Hello,I am testing alfresco AIO SDK 3.0.1 as in the Getting started with Alfresco SDK 3.0 | Alfresco Documentation run.sh not working. I am getting the following error:2018-02-28 15:18:45,055 ERROR [solr.tracker.AbstractTracker] [org.alfresco.solr.AlfrescoCoreAdminHandler@22ce14b1_Worker-6] Model t

Re: SDK 3.0.1 - not running

krutik_jayswal — Thu, 01 Mar 2018 06:24:33 GMT

Please add full error log , better you you add it in a file.This is just the solr tracking error part.

Re: SDK 3.0.1 - not running

anakin59490 — Fri, 02 Mar 2018 08:05:27 GMT

i don't remember if it was the same error but try to use maven 3.3.3

I had problem too with maven 3.5.2

Re: SDK 3.0.1 - not running

kem — Fri, 02 Mar 2018 10:51:53 GMT

mvn 3.3 didn't help. Thanks

Re: SDK 3.0.1 - not running

angelborroy — Sun, 04 Mar 2018 09:17:09 GMT

The real problem is dumped some lines above that HTTP 404 from SOLR (this only shows that SOLR is not connecting to Alfresco Repo as this has not been started). If you scroll up in your log, you'll find:

org.alfresco.error.AlfrescoRuntimeException: 02020000 Bootstrap failed: org.apache.commons.collections.functors.* unsafe serialization classes found in classpath.

You can find handling information and workarounds for this issue at https://issues.alfresco.com/jira

https://issues.alfresco.com/jira/browse/ALF-21568

https://issues.alfresco.com/jira/browse/ACE-5004

It seems something related to Spring Loaded configuration.

Re: SDK 3.0.1 - not running

angelborroy — Sun, 04 Mar 2018 09:31:50 GMT

The problem is that you (probably) has Spring Loaded being included by your MAVEN_OPTS. Due to previous configurations in your environment (as Spring Loaded was used till Alfresco SDK 2.2.0).

You can solve the problem by removing that configuration from your MAVEN_OPTS or by configuring the new HotSwap Agent / JRebel agent tools available from Alfresco SDK 3.0

Re: SDK 3.0.1 - not running

kem — Sun, 04 Mar 2018 11:19:54 GMT

Thanks a lot Angel. The issue was related to a previous configuration where springloaded was part of MAVEN_OPTS.