Forum Discussion

wula007's avatar
wula007
Occasional Contributor
9 years ago

a problem of database initializing

Since my team had been upgraded ReadyAPI from 1.3.1 to 1.4.1,  our test jobs in Jenkins often got timeout error. the root cause it the database initializing operation costs a lot of time. the average is 5 mins. Below is the log.  From the log I guess it was cause by the sync lock, our jenkins will start multiple test jobs at the same time. However we never use database function of readyAPI, is there any setting in the readyAPI that can skip the database initializing operation?

 

16:30:22,882 INFO [SoapUIProGroovyScriptEngineFactory] Setting Script Library to [D:\Program Files\SmartBear\ReadyAPI-1.3.1\bin\scripts]
16:30:22,884 INFO [DefaultSoapUICore] Adding listeners from [D:\Program Files\SmartBear\ReadyAPI-1.4.1\bin\listeners\demo-listeners.xml]
16:30:23,792 INFO [LiquibaseDbInitializer] Initializing database..
16:35:25,346 ERROR [LiquibaseDbInitializer] Failed to initialize database
liquibase.exception.LockException: Could not acquire change log lock. Currently locked by MSWSTESTWIN81 (172.28.17.83) since 11/30/15 8:16 PM
at liquibase.lockservice.StandardLockService.waitForLock(StandardLockService.java:174)
at liquibase.Liquibase.update(Liquibase.java:186)
at liquibase.Liquibase.update(Liquibase.java:181)
at com.smartbear.ready.db.init.liquibase.LiquibaseDbInitializer.initdb(LiquibaseDbInitializer.java:38)
at com.smartbear.ready.db.init.liquibase.LiquibaseDbInitializer$$FastClassByGuice$$2a5f2037.invoke(<generated>)

3 Replies

  • This can happen sometimes when you're running with the new feature Test history enabled, which it is by default in the Maven plugin. In hindsight, we should probably have changed this so that the default is to have Test history disabled instead.

     

    To disable Test history, add this element to the plugin configuration in your POM file (if you already have a readyApiProperties element, you should just add the property element, of course):

     

    <readyApiProperties>
    <
    property>
    <name>test.history.disabled</name>
    <value>true</value>
    </property>
    </readyApiProperties>

     

    Kind regards,

    Manne, Ready! API Developer

  • wula007's avatar
    wula007
    Occasional Contributor

    there is another error of the database initialization

     

    17:00:20,065 INFO [LiquibaseDbInitializer] Initializing database..
    17:00:41,466 ERROR [LiquibaseDbInitializer] Failed to initialize database
    liquibase.exception.LockException: liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: org.h2.jdbc.JdbcSQLException: Connection is broken: "session closed" [90067-176]
    at liquibase.lockservice.StandardLockService.acquireLock(StandardLockService.java:215)
    at liquibase.lockservice.StandardLockService.waitForLock(StandardLockService.java:154)
    at liquibase.Liquibase.update(Liquibase.java:186)
    at liquibase.Liquibase.update(Liquibase.java:181)
    at com.smartbear.ready.db.init.liquibase.LiquibaseDbInitializer.initdb(LiquibaseDbInitializer.java:38)
    at com.smartbear.ready.db.init.liquibase.LiquibaseDbInitializer$$FastClassByGuice$$2a5f2037.invoke(<generated>)
    at com.google.inject.internal.cglib.reflect.$FastMethod.invoke(FastMethod.java:53)
    at com.google.inject.internal.SingleMethodInjector$1.invoke(SingleMethodInjector.java:56)
    at com.google.inject.internal.SingleMethodInjector.inject(SingleMethodInjector.java:90)
    at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110)
    at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:94)
    at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
    at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:54)
    at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)

  • nmrao's avatar
    nmrao
    Champion Level 3
    The following excerpt from above tell, it got locked by:
    Could not acquire change log lock. Currently locked by MSWSTESTWIN81 (172.28.17.83)