nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Transformation Service Not Working | Alfresco Port Change

milochanzy

We recently migrated to Alfresco 5.2 and Solr6. We have a restriction where Solr LBs need to be hosted on port 8080. So we swapped the ports of Alfresco and Solr on the server which hosts the Solr Service... So, Solr should run on 8080 and Alfresco on 8983. Following are some of the changes/config

global-properties
index.subsystem.name=solr6
solr.host=localhost
solr.port=8080
solr.secureComms=none
jodconverter.enabled=true
jodconverter.officeHome=/opt/libreoffice5.2
jodconverter.portNumbers=8101
solrcore.properties
alfresco.port.ssl=8443
alfresco.port=8983

The question is Transformation service is not working on the production environment. With default configuration solr (8983) and alfresco (8080) the Transformation service is working fine on all other servers.

Can someone help debug?

Thanks,

Milo.

Find more posts tagged with

Alfresco Content Services

Accepted answers

milochanzy

Hi Axel,

It turns out that Solr was "busy" with some other activity (unknown) for 1 week so was not doing content tracking, as per Alfresco Support team. One of the prod nodes have started content indexing now.

Fingers crossed for the other node! Thanks for your time and effort.

Thanks,

Milo.

All comments

afaust

Just to clarify: Are you talking about transformations in general / via the jodconverter (which you have included in your configuration properties) or the Transformeration Server, a specific addon product available from Alfresco and running (typically) on a separate Windows server to the (typically) Linux-based Alfresco / SOLR host.

A change in Alfresco / SOLR ports should generally have no impact on any transformations / the Transformation Server. Do you have any log output that is indicative of your error? Without such information it is hard to guess / indicate where you might want to start debugging.

Why does a LB have to run on port 8080? I would have expected a LB to use the well known ports 80/443 instead of the http-alt, commonly used for dev / host local / internal services.

What I am missing is you mentioning the port change in the Tomcat server.xml file of the Repository and the SOLR startup parameters / solr.in.sh / solr.in.cmd to complete the set of changes. WIth alfresco-global.properties / solrcore.properties alone the change is incomplete and will lead to a non-working system.

milochanzy

Hi Alex,

Thanks a lot for your valuable inputs. I am talking about the Transformation Service and not the External Transformation Server.

I will add more details to why I suspect Transformation service is not working... So we have multiple envs set up. In all the environments apart from production environment whenever we add content to the application we get following logs for Content Indexing

2018-05-20 14:12:40,057 TRACE [org.alfresco.repo.content.transform.TransformerDebug] [http-bio-8080-exec-24] 3 store://2018/5/20/14/12/8bf0e54a-d073-408c-8685-f53fa4c5d009.bin
2018-05-20 14:12:40,060 TRACE [org.alfresco.repo.content.transform.TransformerDebug] [http-bio-8080-exec-24] 3 application/vnd.openxmlformats-officedocument.wordprocessingml.document text/plain
2018-05-20 14:12:40,060 DEBUG [org.alfresco.repo.content.transform.TransformerDebug] [http-bio-8080-exec-24] 3 docx txt Issue_Cause.docx 68.8 KB -- index -- SolrIndexer
2018-05-20 14:12:40,061 DEBUG [org.alfresco.repo.content.transform.TransformerDebug] [http-bio-8080-exec-24] 3 workspace://SpacesStore/67cb7b86-09a6-4c5a-9f0a-f9bd7cc3d144
2018-05-20 14:12:40,061 DEBUG [org.alfresco.repo.content.transform.TransformerDebug] [http-bio-8080-exec-24] 3 **a) [120] TikaAuto 0 ms
2018-05-20 14:12:40,061 DEBUG [org.alfresco.repo.content.transform.TransformerDebug] [http-bio-8080-exec-24] 3 b) [130] OOXML 0 ms
2018-05-20 14:12:40,061 TRACE [org.alfresco.repo.content.transform.TransformerDebug] [http-bio-8080-exec-24] 3.1 store://2018/5/20/14/12/8bf0e54a-d073-408c-8685-f53fa4c5d009.bin
2018-05-20 14:12:40,061 TRACE [org.alfresco.repo.content.transform.TransformerDebug] [http-bio-8080-exec-24] 3.1 application/vnd.openxmlformats-officedocument.wordprocessingml.document text/plain
2018-05-20 14:12:40,062 DEBUG [org.alfresco.repo.content.transform.TransformerDebug] [http-bio-8080-exec-24] 3.1 docx txt Issue_Cause.docx 68.8 KB TikaAuto
2018-05-20 14:12:40,249 DEBUG [org.alfresco.repo.content.transform.TransformerLog] [http-bio-8080-exec-24] 3 docx txt INFO Issue_Cause.docx 68.8 KB 188 ms TikaAuto
2018-05-20 14:12:40,249 TRACE [org.alfresco.repo.content.transform.TransformerDebug] [http-bio-8080-exec-24] 3.1 Finished in 188 ms
2018-05-20 14:12:40,252 DEBUG [org.alfresco.repo.content.transform.TransformerDebug] [http-bio-8080-exec-24] 3 Finished in 195 ms

But no such logs in production. I checked all Transformation related setting on prod and non-prod servers, everything else is identical.

I'm left to believe that when we are added content to prod, the content transformation is either 1)not called 2) or, is called but is failing.

I can't find evidence for any of the above. Any more details I can provide to debug? I have enabled all Transformation logs, nothing gets logged to Prod server unless I "Test Transform" via JMX.

Thanks,

Milo.

afaust

So if the transformation is not being called / logged that means calls from SOLR might not reach Alfresco due to the (potentially incomplete) port changes. What about my other remarks regarding changes I would expect if ports are switched?

milochanzy

HI Axel,

Apologies for late response. The changes needed to switch port are all in place. I able to access Alfresco on port 8983 and Solr on 8080 port. When I invoke the "Test Transform" from the URL

http://localhost:8080/alfresco/service/enterprise/admin/admin-testtransform

The transformation is getting executed. I can see that in the "org.alfresco.repo.content.transform.TransformerDebug". But the Solr hosted on this node is not calling the transformation (ContentTracker) when new content is added. MetadataTracker, CascadeTracker, AclTracker etc are working fine.

Thanks,

Milan.