Hi Martin,
thanks for your willing to contribute.
PostgreSQL is my personal (and my company's) preferred choice for our
customers, when deploying Apache Syncope.
With such configuration, we are running Syncope in production in several
environments (most of them are Debian / Ubuntu, but also RedHat / CentOS).
Moreover, there is a work-in-progress about Syncope on Docker, currently
based on DEB distribution and Syncope 2.0.2 at
https://github.com/andrea-patricelli/syncope-docker/tree/2_0_X
All that to say that the problem you are experiencing is definitely not
something that should depend on the product itself but rather somehow on
your environment / configuration.
I have only found the following reference in Syncope:
https://issues.apache.org/jira/browse/SYNCOPE-606
where the problem was that the DataSource was manually enabled in
/etc/tomcat7/Catalina/localhost/syncope.xml
(/etc/tomcat8/Catalina/localhost/syncope.xml in your case).
Would you mind to try again in a fresh Debian / Ubuntu box (VM or Docker
image is just fine) by following the steps in
http://syncope.apache.org/docs/getting-started.html#debian-packages
and nothing more? I've just been through it and everything worked
flawlessly.
Regards.
On 04/07/2017 22:19, Böhmer, Martin wrote:
Hi Francesco,
I downloaded & installed the latest JDBC 4.2 driver (as I am running
Oracle Java 8). Unfortunately the problem stays exactly the same.
Here are some ideas from my side. They are just educated guesses and
may lead the wrong way as I am unable to further validate them due to
my lack of knowledge about Syncope’s implementation.
1.Quartz Scheduler configuration issue
(org.quartz.jobStore.dontSetAutoCommitFalse)
http://www.quartz-scheduler.org/documentation/quartz-2.2.x/configuration/ConfigJobStoreTX.html
2.Issue with Spring Batch an Postgres transactions
https://stackoverflow.com/questions/32113132/jdbc-auto-commit-not-working-with-postgresql-9-driver
Best regards,
Martin
*Von:*Francesco Chicchiriccò [mailto:ilgro...@apache.org]
*Gesendet:* Dienstag, 4. Juli 2017 12:01
*An:* user@syncope.apache.org
*Betreff:* Re: Notification page crashes in Console UI after e-mail config
On 04/07/2017 10:33, Böhmer, Martin wrote:
Hi Francesco,
sorry to hear that.
PostgreSQL (provided by Ubuntu repos): 9.5+173
JDBC (shipped with PostgreSQL): postgresql-jdbc4-9.2.jar
This JDBC Driver is way too old for PostgreSQL 9.5; please download
the latest 42.1.1 for JDBC 4.1 (if using JDK 7) or for JDBC 4.2 (if
using JDK 8) from
https://jdbc.postgresql.org/download.html
Regards.
*Von:*Francesco Chicchiriccò [mailto:ilgro...@apache.org]
*Gesendet:* Freitag, 30. Juni 2017 16:50
*An:* user@syncope.apache.org <mailto: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/
