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 twister, 1 year ago
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 *********************************************************************
via Terracotta by hmak, 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 msbaek71, 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 sundarrajk, 7 months ago
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/kit/reflector?kitID=default&pageID=usoe *********************************************************************
via Terracotta by tranan, 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 fuzy, 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
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: http-8090-Processor22 in VM(22)
Shared Object Type: java.util.GregorianCalendar
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:202)	at com.tc.object.tx.ClientTransactionManagerImpl.fieldChanged(ClientTransactionManagerImpl.java:405)	at com.tc.object.TCObjectImpl.objectFieldChanged(TCObjectImpl.java:331)	at java.util.Calendar.__tc_setzone(Calendar.java)	at java.util.Calendar.writeObject(Calendar.java:2389)	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)	at java.lang.reflect.Method.invoke(Unknown Source)