Hi Francesco, sorry to hear that.
PostgreSQL (provided by Ubuntu repos): 9.5+173 JDBC (shipped with PostgreSQL): postgresql-jdbc4-9.2.jar Best regards, Martin Von: Francesco Chicchiriccò [mailto:ilgro...@apache.org] Gesendet: Freitag, 30. Juni 2017 16:50 An: user@syncope.apache.org Betreff: Re: AW: Notification page crashes in Console UI after e-mail config Hi Martin, I went through your logs and cannot guess much. Only questions coming to my mind are: * PostgreSQL DB version? * PostgreSQL JDBC JAR version? Regards. On 29/06/2017 11:17, Böhmer, Martin wrote: clearing the logs was exactly what I did to provide the core and console log attached to my previous email. Anyway, I did as you suggested and included all the logs from Tomcat and Syncope. Please find them attached (access to Pastebin from our company network is blocked). Best regards, Martin Von: Francesco Chicchiriccò [mailto:ilgro...@apache.org] Gesendet: Donnerstag, 29. Juni 2017 09:10 An: user@syncope.apache.org<mailto:user@syncope.apache.org> Betreff: Re: Notification page crashes in Console UI after e-mail config Hi Martin, see my replies below. Regards. On 28/06/2017 16:44, Böhmer, Martin wrote: Hi, I tried to activate the notification feature, but ran into an error I am unable to tackle. Here is what I did: 1. Adjusted mail.properties file according to our local setup (i.e. changed the server name) 2. Via the Console UI I changed the parameter “notificationjob.cronExpression” from empty string to: * 0/5 * * * ? * 3. Restarted Tomcat 4. Opened Notifications page in Console UI: Configuration --> Notifications (in order to create a notification task to check e-mail config) At step 4 I was redirected to the login screen showing the message “Error while contacting Syncope core”. I attached the Core and Console log files. Root cause seems to be: org.apache.syncope.common.lib.SyncopeClientException: DataIntegrityViolation [Cannot commit when autoCommit is enabled.] Did I do something wrong? No, you didn't. The Admin Console's behavior is due to an unhanded exception raised by the Core. Unfortunately, the message above does not help in recognizing what could have happened. Can you please stop Tomcat, clear all logs, replicate the problem and paste all of your logs via pastebin or similar? My setup is: Apache Syncope 2.0.3 Redhat distribution, JDK 1.8.0_131-b11 from Oracle, Tomcat 8.0.32-1ubuntu1, Ubuntu 16.04 LTS. You might want to give a try to the latest 2.0.4-SNAPSHOT from: * https://repository.apache.org/content/groups/snapshots/org/apache/syncope/syncope-deb-core/2.0.4-SNAPSHOT/ * https://repository.apache.org/content/groups/snapshots/org/apache/syncope/syncope-deb-console/2.0.4-SNAPSHOT/ * https://repository.apache.org/content/groups/snapshots/org/apache/syncope/syncope-deb-enduser/2.0.4-SNAPSHOT/ -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
