com.tc.object.tx.UnlockedSharedObjectException: ********************************************************************* Attempt to access a shared object outside the scope of a shared lock. All access to shared objects must be within the scope of one or more shared locks defined in your Terracotta configuration. Caused by Thread: pool-3-thread-1 in VM(0) Shared Object Type: java.util.Hashtable The cause may be one or more of the following: * Terracotta locking was not configured for the shared code. * The code itself does not have synchronization that Terracotta can use as a boundary. * The class doing the locking must be included for instrumentation. * The object was first locked, then shared. For more information on how to solve this issue, see: http://www.terracotta.org/usoe *********************************************************************

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Terracotta by dondragon2, 1 year ago
synchronization that Terracotta can use as a boundary. * The class doing the locking must be included for instrumentation. * The object was first locked, then shared. For more information on how to solve this issue, see: http://www.terracotta.org/usoe *********************************************************************
via Terracotta by sirode, 1 year ago
******************************************************************************* Attempt to access a shared object outside the scope of a shared lock. All access to shared objects must be within the scope of one or more shared locks defined in your
via Terracotta by safarje, 1 year ago
******************************************************************************* Attempt to access a shared object outside the scope of a shared lock. All access to shared objects must be within the scope of one or more shared locks defined in your
via Terracotta Project Issue Tracker by Tim Eck, 1 year ago
******************************************************************************* Attempt to access a shared object outside the scope of a shared lock. All access to shared objects must be within the scope of one or more shared locks defined in
via Terracotta Project Issue Tracker by Tim Eck, 1 year ago
******************************************************************************* Attempt to access a shared object outside the scope of a shared lock. All access to shared objects must be within the scope of one or more shared locks defined
via Terracotta by ancong20, 1 year ago
Terracotta can use as a boundary. * The class doing the locking must be included for instrumentation. * The object was first locked, then shared. For more information on how to solve this issue, see: http://www.terracotta.org/kit/reflector?kitID=default&pageID=usoe *********************************************************************
com.tc.object.tx.UnlockedSharedObjectException: ********************************************************************* Attempt to access a shared object outside the scope of a shared lock. All access to shared objects must be within the scope of one or more shared locks defined in your Terracotta configuration. Caused by Thread: pool-3-thread-1 in VM(0) Shared Object Type: java.util.Hashtable The cause may be one or more of the following: * Terracotta locking was not configured for the shared code. * The code itself does not have synchronization that Terracotta can use as a boundary. * The class doing the locking must be included for instrumentation. * The object was first locked, then shared. For more information on how to solve this issue, see: http://www.terracotta.org/usoe *********************************************************************
at com.tc.object.tx.ClientTransactionManagerImpl.getTransaction(ClientTransactionManagerImpl.java:365)
at com.tc.object.tx.ClientTransactionManagerImpl.checkWriteAccess(ClientTransactionManagerImpl.java:378)
at com.tc.object.bytecode.ManagerImpl.checkWriteAccess(ManagerImpl.java:755)
at com.tc.object.bytecode.ManagerUtil.checkWriteAccess(ManagerUtil.java:397)
at java.util.Hashtable.put(Hashtable.java)
at com.gcomp.common.api.MessageObject.setMessageString(MessageObject.java:40)
at com.gcomp.server.process.PromptNode.execute(PromptNode.java:60)
at com.gcomp.server.executors.NodeExecutor.transition(NodeExecutor.java:51)
at com.gcomp.server.executors.NodeExecutor.transition(NodeExecutor.java:81)
at com.gcomp.server.executors.NodeExecutor.transition(NodeExecutor.java:81)
at com.gcomp.server.executors.NodeExecutor.processNode(NodeExecutor.java:43)
at com.gcomp.server.executors.ProcessExecutor.run(ProcessExecutor.java:98)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.