Did everything described at Axelor Installation Guide, configure Java, Tomcat and Postgresql accordingly an got this error today:
What is missing with the Axelor DB? Thanks in advance and regards
/opt/tomcat/logs/Catalina.out
After reading the catalina.out regarding the Java, remove the Oracle Java and deploy the OpenJava and fix some errors, the last I have is this related to the DB…
2020-04-20 22:01:09.189 ERROR 746 — [io-8080-exec-16] org.postgresql.Driver : Connection error:
org.postgresql.util.PSQLException: FATAL: database “axelor” does not exist
I need to create the DB on Postgresql? Please advise, think this is the last challenge todeploy the Axelor.
Hi have the same error 500 at the time to try login with admin… is with version axelor-erp-v5.3.3 and Apache Tomcat/8.5.54 after i got thiswhen tryto manage users—>
com.axelor.internal.javax.el.ELException: Unable to find ExpressionFactory of type: # Licensed to the Apache Software Foundation (ASF) under one or more
ERROR 500 looks like this---->
Estado HTTP 500 – Internal Server Error
Tipo Informe de Excepción
mensaje Work already begun on this thread. Looks like you have called UnitOfWork.begin() twice without a balancing call to end() in between.
Descripción El servidor encontró un error interno que hizo que no pudiera rellenar este requerimiento.
excepción
java.lang.IllegalStateException: Work already begun on this thread. Looks like you have called UnitOfWork.begin() twice without a balancing call to end() in between. com.google.common.base.Preconditions.checkState(Preconditions.java:508) com.google.inject.persist.jpa.JpaPersistService.begin(JpaPersistService.java:73) com.google.inject.persist.PersistFilter.doFilter(PersistFilter.java:92) com.axelor.db.tenants.AbstractTenantFilter.doFilter(AbstractTenantFilter.java:67) com.axelor.web.servlet.CorsFilter.doFilter(CorsFilter.java:132) com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:121) com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:133)
nota La traza completa de la causa de este error se encuentra en los archivos de registro del servidor.