• Bug
  • Status: Open
  • 2 Major
  • Resolution:
  • nestrada
  • Reporter: nestrada
  • May 04, 2011
  • 0
  • Watchers: 2
  • May 04, 2011

Attachments

Description

The issue is shown here: http://forums.terracotta.org/forums/posts/list/5343.page

I have attached the simple test case and here is the output of that test case (on a local machine):

{quote} Starting terracotta client… 2011-05-04 17:33:16,891 INFO - Terracotta 3.4.1, as of 20110130-210115 (Revision 17072 by [email protected] from 3.4) 2011-05-04 17:33:17,188 INFO - Successfully loaded base configuration from server at ‘localhost:9510’. 2011-05-04 17:33:17,219 INFO - Successfully loaded base configuration from file at ‘C:\DOCUME~1\NICOLA~1\LOCALS~1\Temp\tc-config3048662235724200137.xml’. 2011-05-04 17:33:17,313 INFO - Log file: ‘C:\Documents and Settings\Nicolas Estrada\terracotta\client-logs\terracotta-client.log’. 2011-05-04 17:33:18,157 INFO - Connection successfully established to server at 172.30.85.59:9510 Startup took 2524 milliseconds! Shutting down terracotta client… Shutdown took 30524 milliseconds. 4 mai 2011 17:33:49 org.terracotta.express.ClientImpl cleanGoogleFinalizerThread INFO: Ripping L1Loader references from Thread[com.google.common.base.internal.Finalizer,5,main] {quote}

FYI the cluster is brand new, no objects allocated in the clustered heap besides the ones from the toolkit at first usage.

Comments

Nicolas Estrada 2011-05-04

I just looked at my terracotta-client.log and the culprit seems to be the {{Batch Recall Timer}} thread.

Here is a snippet of my log file (the interesting part).

{quote}

2011-05-04 17:33:18,157 [main] INFO com.terracottatech.console - Connection successfully established to server at 172.30.85.59:9510 2011-05-04 17:33:18,157 [main] INFO com.terracottatech.dso - Connection successfully established to server at 172.30.85.59:9510 2011-05-04 17:33:18,157 [WorkerThread(client_coordination_stage, 0)] INFO com.tc.management.remote.protocol.terracotta.TunnelingEventHandler - Client JMX server ready; sending notification to L2 server 2011-05-04 17:33:18,532 [main] INFO com.terracottatech.dso.runtime - Module framework shut down 2011-05-04 17:33:19,016 [main] INFO com.tc.object.tx.RemoteTransactionManagerImpl - ClientID[1]: stop(): took 0 millis to complete 2011-05-04 17:33:19,016 [main] INFO com.tc.net.protocol.transport.ConnectionHealthCheckerImpl: DSO Client - Connection to [L2-host:9510] CLOSED. Health Monitoring for this node is now disabled. 2011-05-04 17:33:19,016 [main] INFO com.tc.net.protocol.transport.ConnectionHealthCheckerImpl: DSO Client - HealthChecker STOP requested 2011-05-04 17:33:19,016 [main] INFO com.terracottatech.dso - L1 Exiting… 2011-05-04 17:33:19,844 [HealthChecker] INFO com.tc.net.protocol.transport.ConnectionHealthCheckerImpl: DSO Client - HealthChecker SHUTDOWN 2011-05-04 17:33:49,016 [main] WARN com.terracottatech.dso - Timed out waiting for TC thread group threads to die - probable shutdown memory leak Live threads: [Thread[Batch Recall Timer,5,TC Thread Group]] {quote}

Steve Harris 2011-05-04

Hi, Can you try with 3.5.1 I believe we improved shutdown time in that version. Can you give that a try and let us know

Nicolas Estrada 2011-05-04

Just downloaded it and it works great, running the exact same code I’m up to 3 sec for startup and 5 seconds (instead of 30) for shutdown! Thanks ;) Now to plan on migrating…