topic Issue migrating to ACS 6.1.2 in Alfresco Forum

Issue migrating to ACS 6.1.2

peterdavie — Sun, 10 Mar 2019 08:35:28 GMT

I am attempting to migrate an Alfresco Community 5.x (201602 to be specific) implementation to Alfresco Content Services v6.1.2. Having migrated a number of Alfresco versions, I am reasonably experienced at the usual upgrade path. I have copied the old Alfresco Community environment to a new serve

Re: Issue migrating to ACS 6.1.2

angelborroy — Sun, 10 Mar 2019 22:18:28 GMT

It seems that your alfresco-global.properties is not picked from the classpath.

Check if you have included following Tomcat configuration setting:

$ vi /opt/alfresco/tomcat/conf/catalina.properties 
shared.loader=${catalina.base}/shared/classes,${catalina.base}/shared/lib/*. jar‍‍‍

.1Re: Issue migrating to ACS 6.1.2

kamendrasingh — Tue, 24 Sep 2019 09:22:47 GMT

Iam facing the same problem in migrating alfresco 5.2 to 6.1.2. Iam running it locally and iam getting the jdbc connectivity error and following error.

Sep 24, 2019 2:51:30 PM org.apache.catalina.startup.ContextConfig processAnnotationsJar
SEVERE: Unable to process Jar entry [module-info.class] from Jar [jar:file:/home/kamendra/indsolv-alfresco/target/tomcat/webapps/indsolv-alfresco-platform/WEB-INF/lib/FastInfoset-1.2.15.jar!/] for annotations
org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 19
at org.apache.tomcat.util.bcel.classfile.Constant.readConstant(Constant.java:133)
at org.apache.tomcat.util.bcel.classfile.ConstantPool.<init>(ConstantPool.java:60)
at org.apache.tomcat.util.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:209)
at org.apache.tomcat.util.bcel.classfile.ClassParser.parse(ClassParser.java:119)
at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2134)
at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:2010)
at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1976)
at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1961)
at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1319)
at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:376)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5322)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)

Re: .1Re: Issue migrating to ACS 6.1.2

afaust — Tue, 24 Sep 2019 11:13:46 GMT

It looks like you have a totally different issue then the original poster, which should have been addressed in a separate post / thread.

Anyway, I assume you are either using the wrong Java or Tomcat version with Alfresco 6.1.2 as indicated by the ClassFormatException, which should only occur when a class file is read that was generated of a newer Java version than the Java runtime used to run Alfresco or the library used to process the class file (in this case this appears to be Tomcat BCEL library - whatever that is). A quick Google shows similar issues reported on StackOverflow and some even hinted that this may be a Tomcat bug that resurfaced.

Anyway: Check the supported platforms documents and use the documented Tomcat version.

Re: .1Re: Issue migrating to ACS 6.1.2

kamendrasingh — Wed, 25 Sep 2019 07:09:39 GMT

Yeah i think that is the problem with tomcat. Iam running it locally so its using embedded tomcat 7.0.47. How to change that?