Re: Registry issue when persisting topology

2015-09-14 Thread Akila Ravihansa Perera
Hi Udara, Were you able to resolve this? Looks like Stratos integration tests are failing due to same issue. It seems Carbon registry transactions are failing when mock iaas component is trying to persist data. Thanks. On Mon, May 11, 2015 at 5:34 PM, Gayan Gunarathne wrote: > > > Please refer

Re: Registry issue when persisting topology

2015-05-11 Thread Gayan Gunarathne
Please refer the document[1] [1] http://dev.mysql.com/doc/innodb/1.1/en/innodb-other-changes-innodb_lock_wait_timeout.html Thanks, Gayan On Mon, May 11, 2015 at 5:21 PM, Udara Liyanage wrote: > Hi Gayan, > > Nope I haven't tries that. Could you please point me to the configuration > to be modi

Re: Registry issue when persisting topology

2015-05-11 Thread Udara Liyanage
Hi Gayan, Nope I haven't tries that. Could you please point me to the configuration to be modified? On Mon, May 11, 2015 at 5:03 PM, Gayan Gunarathne wrote: > [2015-05-11 09:37:43,396] ERROR > {org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO} - *Failed to > delete the resource with id

Re: Registry issue when persisting topology

2015-05-11 Thread Gayan Gunarathne
[2015-05-11 09:37:43,396] ERROR {org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO} - *Failed to delete the resource with id 386. Lock wait timeout exceeded; try restarting transaction* java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction What is the current lock wai

Re: Registry issue when persisting topology

2015-05-11 Thread Udara Liyanage
Hi, With MySQL, however frequency of getting the exception is lower. If I restart Stratos at this point, the error does not exist. On Mon, May 11, 2015 at 3:11 PM, Udara Liyanage wrote: > Hi Isuru, > > Even with MySQL, similar issue seems to exist > > in started successfully > [2015-05-11 09:36

Re: Registry issue when persisting topology

2015-05-11 Thread Udara Liyanage
Hi Isuru, Even with MySQL, similar issue seems to exist in started successfully [2015-05-11 09:36:43,786] INFO {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to spawn an instance via cloud controller: [cluster] single-cartridge-app.my-as-manager.appserver-manager.domain [

Re: Registry issue when persisting topology

2015-05-07 Thread Udara Liyanage
Hi, This seems to occur when metadata service too save properties in registry. This occurs when multiple clients(cartridge agent) call metadata service to publish property values. I did not see this error when only one client talks to metadata service. I guess h2 can not handle this. I will try wi

Re: Registry issue when persisting topology

2015-05-07 Thread Isuru Haththotuwa
This seems to be an issue with H2. There are many occasions that this error has been reported when using an H2 DB. Can you try: 1. replacing the currently used DB with a new H2 (from a fresh pack) 2. use a MySQL DB and see if the error is reproducible? On Thu, May 7, 2015 at 4:42 PM, Imesh Gunar

Re: Registry issue when persisting topology

2015-05-07 Thread Imesh Gunaratne
It looks like a database table lock is not being released until it reaches the timeout: Timeout trying to lock table "REG_RESOURCE"; SQL statement: SELECT REG_VERSION FROM REG_RESOURCE WHERE REG_PATH_ID=? AND REG_NAME=? AND REG_TENANT_ID=? [50200-140] The concern is we do not handle any database

Registry issue when persisting topology

2015-05-07 Thread Udara Liyanage
Hi, I frequently get this exception when running Stratos for longtime (10+ minutes). Please note that most failures occurs when metadata service also save properties in the registry (not all the time, this occurs when metadata is not persisting too). 2015-05-07 07:03:11,725] ERROR {org.apache.st