You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@syncope.apache.org by ernst Developer <er...@gmail.com> on 2012/11/02 13:41:59 UTC
Error using syncope 1.0.2-incubating
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:
SEVERE: Exception sending context initialized event to listener instance of
class org.springframework.web.context.ContextLoaderListener
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'springContextInitializer' defined in file
[/opt/tomcat/apache-tomcat-7.0.32/webapps/syncope/WEB-INF/classes/org/apache/syncope/core/init/SpringContextInitializer.class]:
Invocation of init method failed; nested exception is
org.apache.ibatis.exceptions.PersistenceException:
### Error updating database. Cause:
org.apache.openjpa.lib.jdbc.ReportingSQLException: Connection is read-only.
Queries leading to data modification are not allowed {prepstmnt 546819090
insert into ACT_RE_DEPLOYMENT(ID_, NAME_, DEPLOY_TIME_)
values(?, ?, ?) [params=?, ?, ?]} [code=0, state=S1009]
### The error may involve
org.activiti.engine.impl.persistence.entity.DeploymentEntity.insertDeployment-Inline
### The error occurred while setting parameters
### Cause: org.apache.openjpa.lib.jdbc.ReportingSQLException: Connection is
read-only. Queries leading to data modification are not allowed {prepstmnt
546819090 insert into ACT_RE_DEPLOYMENT(ID_, NAME_, DEPLOY_TIME_)
values(?, ?, ?) [params=?, ?, ?]} [code=0, state=S1009]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1455)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:609)
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:469)
at
org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:383)
at
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283)
at
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4791)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:968)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1646)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.ibatis.exceptions.PersistenceException:
### Error updating database. Cause:
org.apache.openjpa.lib.jdbc.ReportingSQLException: Connection is read-only.
Queries leading to data modification are not allowed {prepstmnt 546819090
insert into ACT_RE_DEPLOYMENT(ID_, NAME_, DEPLOY_TIME_)
values(?, ?, ?) [params=?, ?, ?]} [code=0, state=S1009]
### The error may involve
org.activiti.engine.impl.persistence.entity.DeploymentEntity.insertDeployment-Inline
### The error occurred while setting parameters
### Cause: org.apache.openjpa.lib.jdbc.ReportingSQLException: Connection is
read-only. Queries leading to data modification are not allowed {prepstmnt
546819090 insert into ACT_RE_DEPLOYMENT(ID_, NAME_, DEPLOY_TIME_)
values(?, ?, ?) [params=?, ?, ?]} [code=0, state=S1009]
at
org.apache.ibatis.exceptions.ExceptionFactory.wrapException(ExceptionFactory.java:8)
at
org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.java:124)
at
org.apache.ibatis.session.defaults.DefaultSqlSession.insert(DefaultSqlSession.java:111)
at
org.activiti.engine.impl.db.DbSqlSession.flushInserts(DbSqlSession.java:437)
at org.activiti.engine.impl.db.DbSqlSession.flush(DbSqlSession.java:347)
at
org.activiti.engine.impl.interceptor.CommandContext.flushSessions(CommandContext.java:149)
at
org.activiti.engine.impl.interceptor.CommandContext.close(CommandContext.java:105)
at
org.activiti.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:49)
at
org.activiti.spring.SpringTransactionInterceptor$1.doInTransaction(SpringTransactionInterceptor.java:42)
at
org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:130)
at
org.activiti.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:40)
at
org.activiti.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:33)
at
org.activiti.engine.impl.RepositoryServiceImpl.deploy(RepositoryServiceImpl.java:46)
at
org.activiti.engine.impl.repository.DeploymentBuilderImpl.deploy(DeploymentBuilderImpl.java:106)
at
org.apache.syncope.core.init.ActivitiWorkflowLoader.load(ActivitiWorkflowLoader.java:52)
at
org.apache.syncope.core.init.SpringContextInitializer.afterPropertiesSet(SpringContextInitializer.java:68)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1514)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1452)
... 26 more
Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: Connection is
read-only. Queries leading to data modification are not allowed {prepstmnt
546819090 insert into ACT_RE_DEPLOYMENT(ID_, NAME_, DEPLOY_TIME_)
values(?, ?, ?) [params=?, ?, ?]} [code=0, state=S1009]
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:247)
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:223)
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:72)
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.execute(LoggingConnectionDecorator.java:1258)
at
org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:367)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.execute(JDBCStoreManager.java:1768)
at
org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:367)
at
org.apache.ibatis.executor.statement.PreparedStatementHandler.update(PreparedStatementHandler.java:22)
at
org.apache.ibatis.executor.statement.RoutingStatementHandler.update(RoutingStatementHandler.java:51)
at
org.apache.ibatis.executor.SimpleExecutor.doUpdate(SimpleExecutor.java:29)
at org.apache.ibatis.executor.BaseExecutor.update(BaseExecutor.java:88)
at
org.apache.ibatis.executor.CachingExecutor.update(CachingExecutor.java:43)
at
org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.java:122)
... 42 more
Oct 26, 2012 3:04:09 PM org.apache.catalina.core.ApplicationContext log
INFO: Closing Spring root WebApplicationContext
Does somebody have any suggestions?
Cheers!
Ernst
Re: Error using syncope 1.0.2-incubating
Posted by Francesco Chicchiriccò <il...@apache.org>.
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ò <ilgrosso@apache.org
> <ma...@apache.org>>
>
> 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ò <ilgrosso@apache.org
>> <ma...@apache.org>>
>>
>> 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ò <ilgrosso@apache.org
>>> <ma...@apache.org>>
>>>
>>> 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/
Re: Error using syncope 1.0.2-incubating
Posted by ernst Developer <er...@gmail.com>.
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ò <il...@apache.org>
> 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ò <il...@apache.org>
>
>> 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ò <il...@apache.org>
>>
>>> 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 Memberhttp://people.apache.org/~ilgrosso/
>
>
Re: Error using syncope 1.0.2-incubating
Posted by Francesco Chicchiriccò <il...@apache.org>.
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ò <ilgrosso@apache.org
> <ma...@apache.org>>
>
> 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ò <ilgrosso@apache.org
>> <ma...@apache.org>>
>>
>> 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/
Re: Error using syncope 1.0.2-incubating
Posted by ernst Developer <er...@gmail.com>.
And here is the /var/log/syncope stuff.
Sorry I forgot...
2012/11/2 ernst Developer <er...@gmail.com>
> Here's a clean set of log files.
>
>
> 2012/11/2 Francesco Chicchiriccò <il...@apache.org>
>
>> 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ò <il...@apache.org>
>>
>>> 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/
>>>
>>>
>>
>>
>> --
>> Francesco Chicchiriccò
>>
>> ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Memberhttp://people.apache.org/~ilgrosso/
>>
>>
>
Re: Error using syncope 1.0.2-incubating
Posted by ernst Developer <er...@gmail.com>.
Here's a clean set of log files.
2012/11/2 Francesco Chicchiriccò <il...@apache.org>
> 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ò <il...@apache.org>
>
>> 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/
>>
>>
>
>
> --
> Francesco Chicchiriccò
>
> ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Memberhttp://people.apache.org/~ilgrosso/
>
>
Re: Error using syncope 1.0.2-incubating
Posted by Francesco Chicchiriccò <il...@apache.org>.
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ò <ilgrosso@apache.org
> <ma...@apache.org>>
>
> 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/
> <http://people.apache.org/%7Eilgrosso/>
>
>
--
Francesco Chicchiriccò
ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
Re: Error using syncope 1.0.2-incubating
Posted by ernst Developer <er...@gmail.com>.
I did a test with the user that connects to the databse. Find below the
things I did.
mysql> describe UserRequest;
+---------+-------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+---------+-------------+------+-----+---------+-------+
| id | bigint(20) | NO | PRI | NULL | |
| payload | text | YES | | NULL | |
| type | varchar(20) | YES | | NULL | |
+---------+-------------+------+-----+---------+-------+
3 rows in set (0.00 sec)
mysql> insert into UserRequest values (100, "test", "100");
Query OK, 1 row affected (0.08 sec)
mysql> commit
-> ;
Query OK, 0 rows affected (0.00 sec)
mysql> select * from UserRequest;
+-----+---------+------+
| id | payload | type |
+-----+---------+------+
| 100 | test | 100 |
+-----+---------+------+
1 row in set (0.00 sec)
mysql> delete from UserRequest;
Query OK, 1 row affected (0.05 sec)
mysql> commit;
Query OK, 0 rows affected (0.00 sec)
mysql>
So it looks like it works fine with the user on the MySQL prompt.
Regards,
Ernst
2012/11/2 Francesco Chicchiriccò <il...@apache.org>
> 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/
>
>
Re: Error using syncope 1.0.2-incubating
Posted by Francesco Chicchiriccò <il...@apache.org>.
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/