Problem with starting ARIS Busines Server - Launch of ARIS Lockservice failed!

Hi,

This log file doesn't show anything...



Check if the lockservice is configured correct to use Oracle

Program files\Server\Config\lockservice.cfg

BR,

 

Yeah, I checked it and think it is alright.

For me all the settings looks fine.

#D:\ARIS7.2\server\config\Lockservice.cfg.bak
#Wed Jun 19 15:43:49 CEST 2013
url=jdbc\:oracle\:thin\:@oyama.hhs.nl\:1521\:aristest
startdb=yes
ls.mappingclass=com.idsscheer.dl.mapimpl.ora.AMapping
dl.mappingclass=com.idsscheer.dl.mapimpl.ora.dl.AMapping
arisadm_user=aris71
db.startup.maxwait=180000
dbms_major_version=11
arisadm_schema=aris71adm
pwderrcode=e;1017
dbadmin_pwd=95c6c8fc5f7af626b7b87630d1094ce1
lssid=23
arisadm_pwd=cf5062b3e1da3b92e6a52bfd63bffdba
dbmsname=Oracle
driver=oracle.jdbc.OracleDriver

Hi

You can check the exception when the connection is attempted on internalerr0.log.

Regards

Rui

Hi Kees,

You are using the complete name of Oracle server as "oyama.hhs.nl" you could change for IP Address of Oracle server and also check if the DBA changed the password of "aris71" user which is used by application to login on the Oracle BD. If DBA changed the password on the Oracle he also have to set the same password on the Lockservice.cfg ..

Also copy the internalerr0.log here as our friend said and we will know better whats happen...

BR,

Hi,

Thanx, yes i see "There is already an instance of the lockservice running". The complete errorlog is at the botom.

Were are running on VMware and it looks to me that the machine is going very fast down and the lockservice isn't properly closed.

I will do some tests to check it.

@ Andre: I don't think it is the passwd or server name because when I start the service manual (with the same config file) it keeps on running.

Thanks for the reply's,

 

Best regards,

Kees Hoogenboezem

2013-06-19T15:31:29,117 com.idsscheer.aris.server.Exceptions - Launch failed!
com.idsscheer.aris.server.launcher.AArisLauncher.trystart
com.idsscheer.aris.server.common.launch.AFatalLaunchableInitException: Launch of ARIS Lockservice failed!
    at com.idsscheer.aris.server.launcher.AArisLaunchable.startup(Unknown Source)
    at com.idsscheer.aris.server.launcher.AArisLauncher.startService(Unknown Source)
    at com.idsscheer.aris.server.launcher.AArisLauncher.startServices(Unknown Source)
    at com.idsscheer.aris.server.launcher.AArisLauncher.launchAll(Unknown Source)
    at com.idsscheer.aris.server.launcher.AArisLauncher.trystart(Unknown Source)
    at com.idsscheer.aris.server.launcher.AArisLauncher.startup(Unknown Source)
    at com.idsscheer.aris.server.launcher.AArisLauncher.main(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
    at com.exe4j.runtime.WinLauncher.main(Unknown Source)
Caused by: java.lang.RuntimeException: There is already an instance of the lockservice running
    at com.idsscheer.aris.server.launcher.ARemoteLockServiceLaunchable$ALaunchableImpl.startup(Unknown Source)
    ... 13 more
Caused by: com.idsscheer.dl.ls.core.AFatalInitException: There is already an instance of the lockservice running
    at com.idsscheer.dl.mapimpl.ora.ls.AORADatabaseManager.<init>(AORADatabaseManager.java:255)
    at com.idsscheer.dl.mapimpl.ora.AMapping.createDatabaseManager(AMapping.java:62)
    at com.idsscheer.dl.ls.core.logic.ALockServiceFactoryInternal.createLockService(ALockServiceFactoryInternal.java:73)
    at com.idsscheer.dl.ls.core.ALockServiceFactory.createLockService(ALockServiceFactory.java:23)
    ... 14 more
Caused by: com.idsscheer.dl.ls.core.ALockServiceAlreadyRunningException: There is already an instance of the lockservice running
    at com.idsscheer.dl.mapimpl.ora.ls.AORADatabaseManager$AORAValidDatabaseManager.<init>(AORADatabaseManager.java:93)
    at com.idsscheer.dl.mapimpl.ora.ls.AORADatabaseManager.changeStateToValid(AORADatabaseManager.java:302)
    at com.idsscheer.dl.mapimpl.ora.ls.AORADatabaseManager.<init>(AORADatabaseManager.java:252)
    ... 17 more
Caused by: java.sql.SQLException: ORA-00054: De resource is bezet. Ophalen met NOWAIT is verlopen of de time-out is verlopen.

    at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
    at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:110)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:171)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
    at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1030)
    at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:183)
    at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:936)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1222)
    at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1770)
    at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1739)
    at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:298)
    at com.idsscheer.dl.mapimpl.ora.ls.AORADatabaseManager$AORAValidDatabaseManager.lockDummyTable(AORADatabaseManager.java:212)
    at com.idsscheer.dl.mapimpl.ora.ls.AORADatabaseManager$AORAValidDatabaseManager.<init>(AORADatabaseManager.java:74)
    ... 19 more

Hi Kees,

Thanks for info...

I saw the error in Log :

ORA-00054:	resource busy and acquire with NOWAIT specified
Cause:	Resource interested is busy.
Action:	Retry if necessary.

Try to do the step below:

 1- Stop the ARIS server

 2- Stop the instance which ARIS is using on the Oracle 

 3- Start the instance again on the Oracle

 4- Start the ARIS server

Try to do the tests again and see if the service keep running..

The steps above will close any busy resource in Oracle DB and ARIS will reconnect on the instance again..

Let me know the results

BR,

Hi,

Andre thanks for your response ...

Last Friday I did some more tests and yes when the serer reboots not all the database sessions are closed. Mostly two (sometimes more) sessions keep existing in de db-server.

The result is that ARIS Busines Server can't start. When you wait for about 10-15 min. then the service wil start.

Starting the sevice direct after the failure can result in a mess, and then the only solution is stop/start apllication/database instance (as you suggested).

When you stop/start the service manual all works fine (all sessions are closed).

 

So it looks like a reboot of the VMware server (MS-Windows) is too fast so the ARIS application can't close all the database sessions.

Does anybody knows a solution for this problem?

Hi Kees, thanks for info...

In particular I don't know what exactly caused this behavior, but is probably that ARIS lost a connection with DB server and reconnected in short time because some resources keep running on the DB server...

Also you could check why Oracle got the ORA00054 error, and if there is a info to avoid this  error...



If anybody here in community knows could help ..



BR

 

Hi,

I am facing same issue as that of Kees. Can anyone provide me the correct solution over it?

Hi Jayshree,

you can workaround this issue on startup of ARIS 7.2 Business Server by adding the following line to your Lockservice.cfg file:

 

dbmslock=no

 

Cheers

Gerald

 

Thanks Gerald for your response... 

But it is not working, still facing the same issue & I have checked with many test cases but no solution yet.

 

Hi Jayshree, 

Try this configuration to Oracle side :)

Oracle specific:

After a specified time, Oracle sees that the Session doesn't exist any more and deletes it.  After this the ARIS-Server will start again. To solve this Problem please add the following line to your SQLNET.ORA-File. 

     SQLNET.EXPIRE_TIME = 2

If this Line is activated, Oracle checks every 2 Minutes for inactive Sessions and deletes them. After this 2 Minutes the ARIS-Server will start again.

 

BR

AO