TIBCO Enterprise Administrator(TEA) startup fails working with the error, "Database may be already in use".

book

Article ID: KB0094050

calendar_today

Updated On:

Products Versions
TIBCO Enterprise Administrator (TEA) -
Not Applicable -

Description

Resolution:
Description:
=======
 Tibco Enterprise Administrator(TEA) does not start and the exception below is seen:



TIBCO Enterprise Administrator v2.2.0 (pid: 13664)

Reading configuration from file C:\ProgramData\Dev\tibco\cfgmgmt\tea\conf\tea.conf

Writing server logs in C:\ProgramData\Dev\tibco\cfgmgmt\tea\logs

Initializing datastore C:\ProgramData\Dev\tibco\cfgmgmt\tea\data

WRAPPER - start method threw an exception

Exception in thread "TIBCO Enterprise Administrator Main" java.lang.RuntimeException: org.h2.jdbc.JdbcSQLException: Database may be already in use: "Locked by another process". Possible solutions: close all other connection(s); use the server mode [90020-176]

        at com.tibco.trinity.realm.core.provider.realm.jdbc.ConnectorManagedConnectionImpl.<init>(ConnectorManagedConnectionImpl.java:46)

        at com.tibco.trinity.realm.core.provider.realm.jdbc.ConnectorManagedConnectionFactoryImpl.createManagedConnection(ConnectorManagedConnectionFactoryImpl.java:58)

        at com.tibco.trinity.runtime.base.connector.j2ee.ConnectorDefaultConnectionManager.allocateConnection(ConnectorDefaultConnectionManager.java:19)

        at com.tibco.trinity.runtime.base.connector.j2ee.ConnectorConnectionFactory.getConnection(ConnectorConnectionFactory.java:90)

        at com.tibco.trinity.runtime.base.connector.jvm.ConnectorUtils.lookup(ConnectorUtils.java:90)

        at com.tibco.trinity.runtime.base.connector.ConnectorUtils.lookup(ConnectorUtils.java:34)

        at com.tibco.tea.server.TeaServer.startActorsSystem(TeaServer.java:628)

        at com.tibco.tea.server.TeaServer.start(TeaServer.java:495)

        at com.tibco.tea.server.TeaServer.main(TeaServer.java:139)

Caused by: org.h2.jdbc.JdbcSQLException: Database may be already in use: "Lockedby another process". Possible solutions: close all other connection(s); use the

server mode [90020-176]

        at org.h2.message.DbException.getJdbcSQLException(DbException.java:344)

        at org.h2.message.DbException.get(DbException.java:178)

        at org.h2.message.DbException.get(DbException.java:154)

        at org.h2.store.FileLock.getExceptionAlreadyInUse(FileLock.java:462)

        at org.h2.store.FileLock.lockFile(FileLock.java:356)

        at org.h2.store.FileLock.lock(FileLock.java:136)

        at org.h2.engine.Database.open(Database.java:622)

        at org.h2.engine.Database.openDatabase(Database.java:260)

        at org.h2.engine.Database.<init>(Database.java:254)

        at org.h2.engine.Engine.openSession(Engine.java:57)

        at org.h2.engine.Engine.openSession(Engine.java:164)

        at org.h2.engine.Engine.createSessionAndValidate(Engine.java:142)

       at org.h2.engine.Engine.createSession(Engine.java:125)

        at org.h2.engine.Engine.createSession(Engine.java:27)

        at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:331)

        at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:107)

        at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:91)

        at org.h2.Driver.connect(Driver.java:74)

        at org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:191)

        at org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:354)

        at org.h2.jdbcx.JdbcDataSource.getPooledConnection(JdbcDataSource.java:386)

        at org.h2.jdbcx.JdbcConnectionPool.getConnectionNow(JdbcConnectionPool.java:228)

        at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:200)

        at com.tibco.trinity.realm.core.provider.realm.jdbc.oOOO.Ê00000(SGRMSTransactionalWrapper.java:44)

        at com.tibco.trinity.realm.core.provider.realm.jdbc.DBRealmProvider.o00000(DBRealmProvider.java:75)

        at com.tibco.trinity.realm.core.provider.realm.jdbc.DBRealmProvider.<init>(DBRealmProvider.java:63)

        at com.tibco.trinity.realm.core.provider.realm.jdbc.ConnectorManagedConnectionImpl.<init>(ConnectorManagedConnectionImpl.java:43)

        ... 8 more

Resolution:
=======
1). Kill all tea.exe from the process tab of the task manager.
2). Start TEA from the service tab if configured as an NT service or run tea.exe from commandline.

Issue/Introduction

TIBCO Enterprise Administrator(TEA) startup fails working with the error, "Database may be already in use".