JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
enhancement_small.png
CLOSED  Enhancement JPPF-224  -  Improve notes about driver1.jppf.pool.size setting to specimen client properties file
Posted Feb 24, 2014 - updated Mar 28, 2016
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Enhancement
  • Status
     
    		 Closed
  • Assigned to
    lolo4j
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    AndrewL
  • Owned by
    Not owned by anyone
  • Category
    Documentation
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 4.0.x
Issue description
I am writing an application that needs to have several jobs/tasks executed in parallel by nodes. (I would think that this is a very common use case). I was finding that Jobs were executing sequentially on nodes. This was because I had made no setting to driver1.jppf.pool.size and thus it was using the default of 1. The documentation was not clear for me in the specimen client properties files, and I think it would be helpful to others to add remove some misleading text and add more detail.

1) I believe this setting does not work, so should be removed: line 166 of JPPF-4.0-application-template/config/jppf.properties 
#------------------------------------------------------------------------------#
# Size of the connection pool for each discovered driver; default is 1         #
#------------------------------------------------------------------------------#
 
#jppf.pool.size = 1
 2) at line 50 of JPPF-4.0-application-template/config/jppf.properties change from: 
#------------------------------------------------------------------------------#
# Priority given to the driver                                                 #
# The client is always connected to the available driver(s) with the highest   #
# priority. If multiple drivers have the same priority, they will be used as a #
# pool and tasks will be evenly distributed among them.                        #
# default value is 0; uncomment to specify a different value                   #
#------------------------------------------------------------------------------#
 
driver1.jppf.priority = 10
#driver1.jppf.pool.size = 10
 
#driver2.jppf.server.host = localhost
#driver2.class.server.port = 11121
#driver2.jppf.priority = 10
 to 
#------------------------------------------------------------------------------#
# Priority given to the driver                                                 #
# The client is always connected to the available driver(s) with the highest   #
# priority. If multiple drivers have the same priority, they will be used as a #
# pool and tasks will be evenly distributed among them.                        #
# default value is 0; uncomment to specify a different value                   #
# Each driver requires a pool size; if you wish to be able to run jobs in      #
# parallel from the client to a particular driver then you need to increase    #
# the pool size from its default of 1                                          #
#------------------------------------------------------------------------------#
 
driver1.jppf.priority = 10
#driver1.jppf.pool.size = 10
 
#driver2.jppf.server.host = localhost
#driver2.class.server.port = 11121
#driver2.jppf.priority = 10
#driver2.jppf.pool.size = 10


#2
Comment posted by
lolo4j
Feb 24, 09:15
"jppf.pool.size = 1" does work. It only applies when server discovery is enabled, I will clarify that in the config file. I will also clarify the use of priority and pool size for manual configuration.
#4
Comment posted by
lolo4j
Feb 24, 19:38
Implemented in: