AOS module install failure with Community 7.4

cancel
Showing results for 
Search instead for 
Did you mean: 
atTheBeach
Active Member II

AOS module install failure with Community 7.4

Jump to solution

I've been running a test Community 7.4 setup for a while, with only the 'alfresco-share-services' module installed (this is the only module in the 7.4 Community zip). The various tutorials I found on the web used Java 11, so I ran on Java 11, and this worked fine. This is on Ubuntu 22.04, which defaults to Java 17, but also has 11 available.

I've just installed 'org.alfresco.integrations.google.docs' and 'alfresco-aos-module', which are the two additional modules in the Community Ansible install. I used the current AMPs on Nexus, which are

alfresco-aos-module-2.0.0-M1.amp
alfresco-googledrive-repo-community-4.0.0-M1.amp
alfresco-googledrive-share-4.0.0-M1.amp

These AMPs were compiled for Java 17, so I've moved on to Java 17. Startup is failing with the new modules:

org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'AosVirtualFileSystem': Lookup method resolution failed; nested
exception is java.lang.IllegalStateException: Failed to introspect Class
[org.alfresco.module.aosmodule.vfs.AlfrescoVirtualFileSystem] from ClassLoader
[ParallelWebappClassLoader
...
Caused by: java.lang.IllegalStateException: Failed to introspect Class
[org.alfresco.module.aosmodule.vfs.AlfrescoVirtualFileSystem] from ClassLoader
[ParallelWebappClassLoader
...
Caused by: java.lang.NoClassDefFoundError: jakarta/servlet/ServletException
...
Caused by: java.lang.ClassNotFoundException: jakarta.servlet.ServletException

This feels like a versioning issue with AOS - is it? Any ideas how toget around this?

 

1 Solution

Accepted Solutions
atTheBeach
Active Member II

Re: AOS module install failure with Community 7.4

Jump to solution

I fixed this by going back to version 1.6.2-A3.

View solution in original post

1 Reply
atTheBeach
Active Member II

Re: AOS module install failure with Community 7.4

Jump to solution

I fixed this by going back to version 1.6.2-A3.