docs/DEVELOPER_README

Print this page




 321 
 322 
 323 SYSTEM PROPERTY: nashorn.tcs.miss.samplePercent=<x>
 324 
 325 When running with the trace callsite option (-tcs), Nashorn will count
 326 and instrument any callsite misses that require relinking. As the
 327 number of relinks is large and usually produces a lot of output, this
 328 system property can be used to constrain the percentage of misses that
 329 should be logged. Typically this is set to 1 or 5 (percent). 1% is the
 330 default value.
 331 
 332 
 333 SYSTEM_PROPERTY: nashorn.profilefile=<filename>
 334 
 335 When running with the profile callsite options (-pcs), Nashorn will
 336 dump profiling data for all callsites to stderr as a shutdown hook. To
 337 instead redirect this to a file, specify the path to the file using
 338 this system property.
 339 
 340 









 341 ===============
 342 2. The loggers.
 343 ===============
 344 
 345 It is very simple to create your own logger. Use the DebugLogger class
 346 and give the subsystem name as a constructor argument.
 347 
 348 The Nashorn loggers can be used to print per-module or per-subsystem
 349 debug information with different levels of verbosity. The loggers for
 350 a given subsystem are available are enabled by using
 351 
 352 --log=<systemname>[:<level>]
 353 
 354 on the command line.
 355 
 356 Here <systemname> identifies the name of the subsystem to be logged
 357 and the optional colon and level argument is a standard
 358 java.util.logging.Level name (severe, warning, info, config, fine,
 359 finer, finest). If the level is left out for a particular subsystem,
 360 it defaults to "info". Any log message logged as the level or a level




 321 
 322 
 323 SYSTEM PROPERTY: nashorn.tcs.miss.samplePercent=<x>
 324 
 325 When running with the trace callsite option (-tcs), Nashorn will count
 326 and instrument any callsite misses that require relinking. As the
 327 number of relinks is large and usually produces a lot of output, this
 328 system property can be used to constrain the percentage of misses that
 329 should be logged. Typically this is set to 1 or 5 (percent). 1% is the
 330 default value.
 331 
 332 
 333 SYSTEM_PROPERTY: nashorn.profilefile=<filename>
 334 
 335 When running with the profile callsite options (-pcs), Nashorn will
 336 dump profiling data for all callsites to stderr as a shutdown hook. To
 337 instead redirect this to a file, specify the path to the file using
 338 this system property.
 339 
 340 
 341 SYSTEM_PROPERTY: nashorn.regexp.impl=[jdk|joni]
 342 
 343 This property defines the regular expression engine to be used by
 344 Nashorn. The default implementation is "jdk" which is based on the
 345 JDK's java.util.regex package. Set this property to "joni" to install
 346 an implementation based on Joni, the regular expression engine used by
 347 the JRuby project.
 348 
 349 
 350 ===============
 351 2. The loggers.
 352 ===============
 353 
 354 It is very simple to create your own logger. Use the DebugLogger class
 355 and give the subsystem name as a constructor argument.
 356 
 357 The Nashorn loggers can be used to print per-module or per-subsystem
 358 debug information with different levels of verbosity. The loggers for
 359 a given subsystem are available are enabled by using
 360 
 361 --log=<systemname>[:<level>]
 362 
 363 on the command line.
 364 
 365 Here <systemname> identifies the name of the subsystem to be logged
 366 and the optional colon and level argument is a standard
 367 java.util.logging.Level name (severe, warning, info, config, fine,
 368 finer, finest). If the level is left out for a particular subsystem,
 369 it defaults to "info". Any log message logged as the level or a level