[
https://issues.apache.org/jira/browse/SYNCOPE-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491387#comment-13491387
]
Francesco Chicchiriccò commented on SYNCOPE-232:
------------------------------------------------
Colm, your suspicion was right: I've changed a some time ago the way how Spring
manages DataSource, and the bug - actually a misconfiguration - was there.
I've just committed the fix: for any 1.0.2 / 1.0.3 user, you can still have the
fix by downloading [1] in your project's core/src/main/resources directory.
Regards.
[1]
https://svn.apache.org/repos/asf/incubator/syncope/branches/1_0_X/core/src/main/resources/persistenceContext.xml
> "Connection is read-only" during initialization
> -----------------------------------------------
>
> Key: SYNCOPE-232
> URL: https://issues.apache.org/jira/browse/SYNCOPE-232
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0.2-incubating, 1.0.3-incubating
> Environment: MySQL
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Fix For: 1.0.4-incubating, 1.1.0
>
>
> During initialization, when MySQL is used, a set of exceptions are thrown
> like as:
> ...
> Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: Connection is
> read-only. Queries leading to data modification are not allowed
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
