[jboss-cvs] JBossCache/src/org/jboss/cache/demo ...

[Galder Zamarreno]

  User: gzamarreno
  Date: 07/05/20 06:51:50

  Modified:    src/org/jboss/cache/demo  JBossCacheGUI.java
  Log:
  [JBCACHE-1041] use newCachedThreadPool instead of fixed thread pool.
  
  Revision  Changes    Path
  1.3       +4 -4      JBossCache/src/org/jboss/cache/demo/JBossCacheGUI.java
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: JBossCacheGUI.java
  ===================================================================
  RCS file: /cvsroot/jboss/JBossCache/src/org/jboss/cache/demo/JBossCacheGUI.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -b -r1.2 -r1.3
  --- JBossCacheGUI.java	18 May 2007 19:38:28 -0000	1.2
  +++ JBossCacheGUI.java	20 May 2007 10:51:50 -0000	1.3
  @@ -69,11 +69,11 @@
      private boolean useConsole = false;
   
      /**
  -    * Run any work that happens in this interface in a separate thread.  This is good practise. Initialised to 3
  -    * threads based on the number of concurrent actions that could be happening at the same time (view change,
  -    * click on node,...etc) 
  +    * Run any work that happens in this interface in a separate thread.  This is good practise. Unless there's a
  +    * resource-managemenet requirement, such as in an application server, newCachedThreadPool is a good option as it
  +    * provides better queuing performance.
       */
  -   private Executor executor = Executors.newFixedThreadPool(3);
  +   private Executor executor = Executors.newCachedThreadPool();
   
      public JBossCacheGUI(CacheModelDelegate cacheDelegate, boolean useConsole) throws Exception
      {