Update on this topic: the bug is finally fixed in
1.0.4-incubating-SNAPSHOT but you can have it fixed on 1.0.2 / 1.0.3 as
well by:
 * removing the workaround suggested below
 * 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

On 02/11/2012 20:04, ernst Developer wrote:
> Hi Francesco, 
> Thanks for the workaround, I will fix it in my version of the code. I
> will share the results.
> Regards,
> Ernst
>
>
> 2012/11/2 Francesco Chicchiriccò <[email protected]
> <mailto:[email protected]>>
>
>     Ernst,
>     this turned to be an actual bug affecting 1.0.2-incubating and
>     even the not-yet-released 1.0.3-incubating.
>
>     I've opened SYNCOPE-232 and fixed this in 1.0.4-incubating-SNAPSHOT.
>
>     As workaround:
>     1. download JobInstanceLoader.java ([1] for 1.0.2-incubating, [2]
>     for 1.0.3-incubating)
>     2. put it under your overlay's
>     core/src/main/java/org/apache/syncope/core/init
>     3. replace
>
>     -    @Transactional(readOnly = true)
>     +    @Transactional
>          public void load() {
>
>     This should solve the bug until 1.0.4-incubating is released.
>
>     Regards.
>
>     [1]
>     
> https://svn.apache.org/repos/asf/incubator/syncope/tags/syncope-1.0.2-incubating/core/src/main/java/org/apache/syncope/core/init/JobInstanceLoader.java
>     [2]
>     
> https://svn.apache.org/repos/asf/incubator/syncope/tags/syncope-1.0.3-incubating/core/src/main/java/org/apache/syncope/core/init/JobInstanceLoader.java
>
>
>
>     On 02/11/2012 14:04, ernst Developer wrote:
>>     Here's a clean set of log files.
>>
>>
>>     2012/11/2 Francesco Chicchiriccò <[email protected]
>>     <mailto:[email protected]>>
>>
>>         On 02/11/2012 13:54, ernst Developer wrote:
>>>         I did a test with the user that connects to the databse.
>>>         Find below the things I did.
>>>
>>>         [...]
>>>
>>>         So it looks like it works fine with the user on the MySQL
>>>         prompt.
>>
>>         Ok, could you please check in all Syncope and especially
>>         Tomcat log files if there is any initialization error?
>>
>>         Regards.
>>
>>
>>>         2012/11/2 Francesco Chicchiriccò <[email protected]
>>>         <mailto:[email protected]>>
>>>
>>>             On 02/11/2012 13:41, ernst Developer wrote:
>>>             > Hi,
>>>             > Today I started using 1.0.2-incubating.
>>>             > I followed the steps in the
>>>             > wiki:
>>>             
>>> https://cwiki.apache.org/confluence/display/SYNCOPE/Create+a+new+Syncope+project
>>>             >
>>>             > I installed tomcat: apache-tomcat-7.0.32.
>>>             >
>>>             > Then I did the changes suggested
>>>             > in:
>>>             
>>> https://cwiki.apache.org/confluence/display/SYNCOPE/Run+Syncope+in+real+environments#RunSyncopeinrealenvironments-MySQL
>>>             > Because we are using MySQL.
>>>             >
>>>             > I started with an empty database. I got the error:
>>>             >
>>>             > [...]
>>>             >
>>>             > Does somebody have any suggestions?
>>>
>>>             This:
>>>
>>>             > org.apache.ibatis.exceptions.PersistenceException:
>>>              ### Error updating
>>>             > database.  Cause:
>>>             org.apache.openjpa.lib.jdbc.ReportingSQLException:
>>>             > Connection is read-only
>>>
>>>             sounds very strange to me: can you please check that the
>>>             configured user
>>>             is allowed to write on the database or if the db is put
>>>             in read-only for
>>>             some weird reason?
>>>
>>>             Regards.
>>>
-- 
Francesco Chicchiriccò

ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/

Reply via email to