java.lang.IllegalArgumentException: null

JIRA | Jeremy Barlow | 7 months ago
  1. 0

    If the {{jruby-puppet.max-active-instances}} setting in puppetserver.conf is set to a value less than or equal to zero, Puppet Server fails to start with a confusing error message in the log file: In Puppet Server 2.2.1: {noformat} 2016-03-23 16:40:25,345 ERROR [main] [p.t.internal] Error during service init!!! java.lang.IllegalArgumentException: null at java.util.concurrent.LinkedBlockingDeque.<init>( ~[na:1.8.0_71] at com.puppetlabs.puppetserver.pool.JRubyPool.<init>( ~[puppet-server-release.jar:na] at$instantiate_free_pool.invoke(jruby_puppet_internal.clj:60) ~[na:na] at$eval24401$create_pool_from_config__24402$fn__24406.invoke(jruby_puppet_internal.clj:166) ~[na:na] at$eval24401$create_pool_from_config__24402.invoke(jruby_puppet_internal.clj:162) ~[na:na] at$eval25234$create_pool_context__25235$fn__25236.invoke(jruby_puppet_core.clj:223) ~[na:na] at$eval25234$create_pool_context__25235.invoke(jruby_puppet_core.clj:212) ~[na:na] at$reify__25604$service_fnk__4363__auto___positional$reify__25615.init(jruby_puppet_service.clj:39) ~[na:na] {noformat} In Puppet Server 2.3.0, it's even more confusing to identify the problem because Puppet Server hangs - with the webserver never coming to ready - during initialization. I believe that's because with the changes we made to the JRubyPool class, we're no longer throwing an exception for a value less than 1: -- It would seem to be better to throw a failure with a more meaningful error message which ties back to the max-active-instances config setting - maybe somewhere around where the jruby-puppet service sources its config: Just as a fail-safe / defensive programming, throwing an exception from the JRubyPool class constructor for a size less than 1 seems worthwhile.

    JIRA | 7 months ago | Jeremy Barlow
    java.lang.IllegalArgumentException: null
  2. 0


    Google Groups | 9 years ago | Simon
  3. 0

    GitHub comment 754#132444574

    GitHub | 1 year ago | Hubcapp
    java.lang.IllegalArgumentException: null
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    @Named causes Fatal error compiling: IllegalArgumentException

    GitHub | 11 months ago | db82407
    java.lang.IllegalArgumentException: null
  6. 0

    Error in GWT Dev Shell

    Google Groups | 1 decade ago | Madox
    java.lang.IllegalArgumentException: null

    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. java.lang.IllegalArgumentException


      at java.util.concurrent.LinkedBlockingDeque.<init>()
    2. Java RT
      1. java.util.concurrent.LinkedBlockingDeque.<init>([na:1.8.0_71]
      1 frame
    3. com.puppetlabs.puppetserver
      1. com.puppetlabs.puppetserver.pool.JRubyPool.<init>([puppet-server-release.jar:na]
      1 frame
      6 frames