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 *********************************************************************

Terracotta | twister | 7 years ago
  1. 0

    Shared Object Type: java.util.GregorianCalendar, problem with unvisible method

    Terracotta | 7 years ago | twister
    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 *********************************************************************
  2. 0

    I got UnlockedSharedObjectException !!

    Terracotta | 9 years ago | msbaek71
    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. Please alter the locks section of your Terracotta configuration so that this access is auto-locked or protected by a named lock. For more information on this issue, please visit our Troubleshooting Guide at: http://terracotta.org/kit/troubleshooting Caused by Thread: http-8080-Processor24 in VM(0) Shared Object Type: net.daum.gaia.core.domain.model.article.ArticleContent *******************************************************************************
  3. 0

    Re:Hashtable UnlockedSharedObjectException

    Terracotta | 7 years ago | dondragon2
    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 *********************************************************************
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    How can I resolve this issue?

    Terracotta | 5 years ago | ancong20
    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: main in VM(627) Shared Object Type: java.util.TreeMap 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/kit/reflector?kitID=default&pageID=usoe *********************************************************************
  6. 0

    source: http://forums.terracotta.org/forums/posts/list/723.page If one takes a clustered ehcache CacheManager instance and try to register it with an MBeanServer, you'll get an UnlockedSharedObjectException. Making a call like this (passing a shared cacheManager) should produce the issue net.sf.ehcache.management.ManagementService.registerMBeans(cacheManager, ManagementFactory.getPlatformMBeanServer(), true, true, true, true); It looks like an attempt was made to make this transient since "net.sf.ehcache.CacheManager.cacheManagerEventListener" is declared transient in terracotta.xml in both the 1.2.4 and 1.3.0 modules. Unfortunately that field does not exist. Correcting the field name will just lead to an NPE on other nodes. This is the exception text: 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. Please alter the locks section of your Terracotta configuration so that this access is auto-locked or protected by a named lock. For more information on this issue, please visit our Troubleshooting Guide at: http://terracotta.org/kit/troubleshooting Caused by Thread: main in VM(0) Shared Object Type: java.util.HashSet ******************************************************************************* at com.tc.object.tx.ClientTransactionManagerImpl.getTransaction(ClientTransactionManagerImpl.java:278) at com.tc.object.tx.ClientTransactionManagerImpl.checkWriteAccess(ClientTransactionManagerImpl.java:291) at com.tc.object.bytecode.ManagerImpl.checkWriteAccess(ManagerImpl.java:662) at com.tc.object.bytecode.ManagerUtil.checkWriteAccess(ManagerUtil.java:364) at java.util.HashSet.add(HashSet.java) at net.sf.ehcache.event.CacheManagerEventListenerRegistry.registerListener(CacheManagerEventListenerRegistry.java:65) at net.sf.ehcache.management.ManagementService.init(ManagementService.java:137) at net.sf.ehcache.management.ManagementService.registerMBeans(ManagementService.java:110) at Foo.main(Foo.java:11)

    Terracotta Project Issue Tracker | 9 years ago | Tim Eck
    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. Please alter the locks section of your Terracotta configuration so that this access is auto-locked or protected by a named lock. For more information on this issue, please visit our Troubleshooting Guide at: http://terracotta.org/kit/troubleshooting Caused by Thread: main in VM(0) Shared Object Type: java.util.HashSet *******************************************************************************

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. 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()
    2. com.tc.object
      TCObjectImpl.objectFieldChanged
      1. com.tc.object.tx.ClientTransactionManagerImpl.getTransaction(ClientTransactionManagerImpl.java:202)
      2. com.tc.object.tx.ClientTransactionManagerImpl.fieldChanged(ClientTransactionManagerImpl.java:405)
      3. com.tc.object.TCObjectImpl.objectFieldChanged(TCObjectImpl.java:331)
      3 frames
    3. Java RT
      Method.invoke
      1. java.util.Calendar.__tc_setzone(Calendar.java)
      2. java.util.Calendar.writeObject(Calendar.java:2389)
      3. sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      4. sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      5. sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      6. java.lang.reflect.Method.invoke(Unknown Source)
      6 frames