Absent Member.. JasonCantrell Absent Member..
Absent Member..
54 views

[OO Tip] Clustered Central will not start after a crash

Problem:

In the Operations Orchestration (OO) Terracotta-wrapper.log, it shows terracotta starting and shows the other node joining the cluster. Then 5:30 minutes later, that node leaves the cluster and terracotta shuts down. One reference from previous startup attempt of terracotta mentions a dirty database (DB) on the other node.

 

INFO   | jvm 1    | 2011/10/11 17:12:35 | *******************************************************************************
INFO   | jvm 1    | 2011/10/11 17:12:35 | Attempt to write to a shared object inside the scope of a lock declared as a
INFO   | jvm 1    | 2011/10/11 17:12:35 | read lock. All writes to shared objects must be within the scope of one or
INFO   | jvm 1    | 2011/10/11 17:12:35 | more shared locks with write access defined in your Terracotta configuration.
INFO   | jvm 1    | 2011/10/11 17:12:35 |
INFO   | jvm 1    | 2011/10/11 17:12:35 | Please alter the locks section of your Terracotta configuration so that this
INFO   | jvm 1    | 2011/10/11 17:12:35 | access is auto-locked or protected by a named lock with write access.
INFO   | jvm 1    | 2011/10/11 17:12:35 |
INFO   | jvm 1    | 2011/10/11 17:12:35 | For more information on this issue, please visit our Troubleshooting Guide at:
INFO   | jvm 1    | 2011/10/11 17:12:35 | http://terracotta.org/kit/troubleshooting
INFO   | jvm 1    | 2011/10/11 17:12:35 |
INFO   | jvm 1    | 2011/10/11 17:12:35 |     Caused by Thread: WrapperSimpleAppMain  in  VM(44)
INFO   | jvm 1    | 2011/10/11 17:12:35 |     Failed To Modify Field:  com.iconclude.dharma.commons.repo.DharmaPathReference.path in com.iconclude.dharma.commons.repo.DharmaPathReference
INFO   | jvm 1    | 2011/10/11 17:12:35 | *******************************************************************************
INFO   | jvm 1    | 2011/10/11 17:12:35 |
INFO   | jvm 1    | 2011/10/11 17:12:35 | com.tc.object.util.ReadOnlyException:

 

Solution:

The tc-config.xml needs to be edited on both nodes and the following lines have to be added in the locks section after the first <autolock> block

<autolock auto-synchronized="true">
           <method-expression>* com.iconclude.dharma.commons.repo.DharmaPathReference.*(..)</method-expression>
           <lock-level>write</lock-level>
</autolock>

 

Direct link to the knowledge article here:

http://support.openview.hp.com/selfsolve/document/KM1254982

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Labels (2)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.