Two Atlas instances running simultaneously causes application lock issue

Technote (troubleshooting)


Problem(Abstract)


Setting up a second instance of IBM Atlas eDiscovery Process Management(Atlas) for fail over purposes causes an application lock error.

Symptom

The application is down, login screen is inaccessible and a lock error appears in the logs.


Cause


When two instances of Atlas are running at the same time, the ApplicationLock mechanism will prevent both instances from accessing the same database.


Environment

Occurs in all environments.


Diagnosing the problem

There will be an application lock error in the logs indicating another instance has tried to access the same database:

Error]-[Unable to lock application [PolicyAtlas] due to
[com.secretseal.policyatlas.service.exceptions.ApplicationLockException:
Lock for application [PolicyAtlas] is unavailable at this time.].]:
com.secretseal.policyatlas.service.exceptions.ApplicationLockException:
Unable to lock application [PolicyAtlas] due to
[com.secretseal.policyatlas.service.exceptions.ApplicationLockException:
Lock for application [PolicyAtlas] is unavailable at this time.].

Resolving the problem

There is no fail-over functionality available in Atlas at this time. In order to achieve this, one server must be physically stopped, before you start the other.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Atlas eDiscovery Process Management
Data sources

Software version:

3.0, 4.5.1, 4.5.2, 5.0.1, 6.0, 6.0.1, 6.0.1.1, 6.0.1.2, 6.0.1.3

Operating system(s):

Linux, Solaris, Windows

Reference #:

1623932

Modified date:

2013-02-11

Translate my page

Machine Translation

Content navigation