java.lang.IllegalStateException: There was a problem adding a JRubyPuppet instance to the pool.

JIRA | Chris Price | 2 years ago
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    As of ce030bb in the stable branch of Puppet Server, if you run the jruby-puppet-service-test in a loop: {code}for i in {1..100}; do lein test; done{code} You will occasionally see an error logged to the console: {code} lein test 2015-04-01 16:16:59,076 ERROR [p.t.internal] shutdown-on-error triggered because of exception! java.lang.IllegalStateException: There was a problem adding a JRubyPuppet instance to the pool. at$eval12054$prime_pool_BANG___12055$fn__12059.invoke(jruby_puppet_agents.clj:60) ~[na:na] at$eval12054$prime_pool_BANG___12055.invoke(jruby_puppet_agents.clj:38) ~[na:na] at$eval12160$send_prime_pool_BANG___12161$fn__12162$fn__12164.invoke(jruby_puppet_agents.clj:132) ~[na:na] at puppetlabs.trapperkeeper.internal$shutdown_on_error_STAR_.invoke(internal.clj:256) [na:na] at puppetlabs.trapperkeeper.internal$shutdown_on_error_STAR_.invoke(internal.clj:240) [na:na] at puppetlabs.trapperkeeper.internal$shutdown_service$reify__6095$service_fnk__5288__auto___positional$reify__6100.shutdown_on_error(internal.clj:295) [na:na] at puppetlabs.trapperkeeper.internal$eval6031$fn__6043$G__6017__6051.invoke(internal.clj:264) [na:na] at puppetlabs.trapperkeeper.internal$eval6031$fn__6043$G__6016__6060.invoke(internal.clj:264) [na:na] at clojure.lang.AFn.applyToHelper( [clojure-1.6.0.jar:na] at clojure.lang.AFn.applyTo( [clojure-1.6.0.jar:na] at clojure.core$apply.invoke(core.clj:626) [clojure-1.6.0.jar:na] at clojure.core$partial$fn__4228.doInvoke(core.clj:2468) [clojure-1.6.0.jar:na] at clojure.lang.RestFn.applyTo( [clojure-1.6.0.jar:na] at clojure.core$apply.invoke(core.clj:626) [clojure-1.6.0.jar:na] at clojure.core$partial$fn__4228.doInvoke(core.clj:2468) [clojure-1.6.0.jar:na] at clojure.lang.RestFn.invoke( [clojure-1.6.0.jar:na] at$eval12032$send_agent__12033$fn__12034$agent_fn__12035.invoke(jruby_puppet_agents.clj:32) [na:na] at clojure.core$binding_conveyor_fn$fn__4145.invoke(core.clj:1913) [clojure-1.6.0.jar:na] at clojure.lang.AFn.applyToHelper( [clojure-1.6.0.jar:na] at clojure.lang.RestFn.applyTo( [clojure-1.6.0.jar:na] at clojure.lang.Agent$Action.doRun( [clojure-1.6.0.jar:na] at clojure.lang.Agent$ [clojure-1.6.0.jar:na] at java.util.concurrent.ThreadPoolExecutor.runWorker( [na:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$ [na:1.7.0_55] at [na:1.7.0_55] Caused by: java.lang.Exception: JRuby service missing config value 'ruby-load-path' at$eval11795$create_pool_instance_BANG___11796$fn__11797.invoke(jruby_puppet_internal.clj:93) ~[na:na] at$eval11795$create_pool_instance_BANG___11796.invoke(jruby_puppet_internal.clj:83) ~[na:na] at$eval12054$prime_pool_BANG___12055$fn__12059.invoke(jruby_puppet_agents.clj:54) ~[na:na] ... 24 common frames omitted {code} I would guess it occurs somewhere on the order of once every 30 runs on my box. This does not cause any test failures. I've had a hard time tracking down exactly what's causing it; my best guess is that it is a test race and not an actual bug in the code, but I don't have any way to validate that yet. Talked through the issue with [~jeremy.barlow] and our theory is that it might have something to do with some random combination of: 1. If the TK app is shut down before the JRuby pool finishes initializing, the background thread that is doing the initializing keeps on going, 2. If we finished one test and moved on to the next one while issue #1 was occurring, it's possible that the logging could be re-initialized for the next test and that there would be a brief window where a log message would slip through to the console, and 3. There is at least one test in that namespace that is intentionally trying to cause/catch an exception. I've tried commenting out some of the tests in the namespace to see if I can narrow it down, but so far I haven't been able to repro it with *any* of the tests commented out. :( I also tried adding print statements to the beginning and end of each test. Every time I've witnessed the error message since then, it's happened during the execution of `test-with-jruby-puppet` (I see a print from the beginning of that test, then the error, and then a print from the end of that test each time.) However, I've tried commenting out all of the other tests besides that one and running in a loop, and haven't seen it repro so far. Will probably try adding back in the test just before and just after that one and see if that gives any more clues, and then punt on this for now.

    JIRA | 2 years ago | Chris Price
    java.lang.IllegalStateException: There was a problem adding a JRubyPuppet instance to the pool.
  2. 0 issue with really simple jaxrs project

    Google Groups | 1 year ago | Sebastien Blanc
    java.lang.Exception: WFLYSRV0056: Server boot has failed in an > unrecoverable manner; exiting. See previous messages for details. > at > > at
  3. 0

    Cannot open Planning application : An error occ... | Oracle Community | 1 year ago
    java.lang.Exception: No object were successfully created. This can be caused by any of the following: The OLAP Server is not running, The DBMS is not running, the DBMS is running on a different machine that the one specified, the name and password provided were incorrect.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Java applet failed to run - Java Programming Help - | 2 years ago
    java.lang.Exception: Unable to get input stream for lwjgl.jar at org.lwjgl.util.applet.AppletLoader.getJarInputStre am( at org.lwjgl.util.applet.AppletLoader.downloadJars(Ap at
  6. 0

    OpenESB Community Forum - Sending JMS to Weblogic JMS server | 9 months ago
    java.lang.Exception: JMSBC-W0728:Unable to send message to JMS provider, message exchange 65298394732535-46116-134707432119700042, end point caWebLogicJMS-sun-jms-binding{ and operation { .   at com.sun.jbi.jmsbc.OutboundMessageProcessor.processOneWayOutbound( at com.sun.jbi.jmsbc.OutboundMessageProcessor.execute( at at com.sun.jbi.jmsbc.OutboundReceiver$ at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( at java.util.concurrent.ThreadPoolExecutor$

    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.Exception

      JRuby service missing config value 'ruby-load-path'

      5 frames
    3. puppetlabs.trapperkeeper
      1. puppetlabs.trapperkeeper.internal$shutdown_on_error_STAR_.invoke(internal.clj:256)[na:na]
      2. puppetlabs.trapperkeeper.internal$shutdown_on_error_STAR_.invoke(internal.clj:240)[na:na]
      3. puppetlabs.trapperkeeper.internal$shutdown_service$reify__6095$service_fnk__5288__auto___positional$reify__6100.shutdown_on_error(internal.clj:295)[na:na]
      4. puppetlabs.trapperkeeper.internal$eval6031$fn__6043$G__6017__6051.invoke(internal.clj:264)[na:na]
      5. puppetlabs.trapperkeeper.internal$eval6031$fn__6043$G__6016__6060.invoke(internal.clj:264)[na:na]
      5 frames
    4. Clojure
      1. clojure.lang.AFn.applyToHelper([clojure-1.6.0.jar:na]
      2. clojure.lang.AFn.applyTo([clojure-1.6.0.jar:na]
      3. clojure.core$apply.invoke(core.clj:626)[clojure-1.6.0.jar:na]
      4. clojure.core$partial$fn__4228.doInvoke(core.clj:2468)[clojure-1.6.0.jar:na]
      5. clojure.lang.RestFn.applyTo([clojure-1.6.0.jar:na]
      6. clojure.core$apply.invoke(core.clj:626)[clojure-1.6.0.jar:na]
      7. clojure.core$partial$fn__4228.doInvoke(core.clj:2468)[clojure-1.6.0.jar:na]
      8. clojure.lang.RestFn.invoke([clojure-1.6.0.jar:na]
      8 frames
      1 frame
    6. Clojure
      1. clojure.core$binding_conveyor_fn$fn__4145.invoke(core.clj:1913)[clojure-1.6.0.jar:na]
      2. clojure.lang.AFn.applyToHelper([clojure-1.6.0.jar:na]
      3. clojure.lang.RestFn.applyTo([clojure-1.6.0.jar:na]
      4. clojure.lang.Agent$Action.doRun([clojure-1.6.0.jar:na]
      5. clojure.lang.Agent$[clojure-1.6.0.jar:na]
      5 frames
    7. Java RT
      1. java.util.concurrent.ThreadPoolExecutor.runWorker([na:1.7.0_55]
      2. java.util.concurrent.ThreadPoolExecutor$[na:1.7.0_55]
      3 frames