does this issue imply that a java application server like glassfish cant run several different apps with several different versions of jruby/openssl/BC?

@joedaniels29 the above problem is when you have several jruby runtimes (or ScriptingContainers) inside one classloader. all those runtimes share a child classloader the JRubyClassloader. with this JRubyClassLoader requiring BC and all the other jars needs to be synchroinized.

having several webapps inside a servlet engine are nicely separated and can run different versions of jruby or BC, etc.

two possible implementations:

• each runtime gets it own JRubyClassloader and with this each one has its own set of loaded jars
• ensure one the same jar is loaded only once into the JRubyClassLoader which is not the case right now. with one runtime, the require does take care of it, but with several runtimes sharing the same JRubyClassLoader this needs extra work

@kares would appreciate your input here :)

@mkristian aah, get it now - thanks for the explanation. never realised the case but it makes sense.
hmm I would vote for the "easy" way 1. but I'm afraid to put it in 1.1.x stable. on the other hand sounds like this might be JRubyClassLoader's responsibility (or we could setup a custom class-loader in JRuby-Rack assuming we can change the JRubyClassLoader used in Ruby) - probably doable decently. let me know if you're not looking into it, I will (if I do not forget or someone ping-s me)

@kares for me 1) is the only clean solution - let me see what it needs and then we look at the "risk"

I looked into this and the following class can reproduce it with jruby-1_7

public class Hmm {


    public static void main(String... args) throws Exception {
        int num = 20;
        if (args.length > 0) {
            num = Integer.parseInt(args[0]);
        }
        Thread[] threads = new Thread[num];
        final ScriptingContainer runtime = new ScriptingContainer(LocalContextScope.THREADSAFE);
        for(int i = 0; i < threads.length; i++) {
            threads[i] = new Thread(new Runnable() {
                public void run() {
                    System.err.println(runtime.parse("p JRuby.runtime.jruby_class_loader;require 'openssl';p $CLASSPATH").run());
                }
            });
        }
        for(Thread t: threads) {
            t.start();
        }
        for(Thread t: threads) {
            t.join();
        }
    }
}

I used jruby-complete.jar and this class one the classpath.

with jruby-9k I do not see the error.

apparently then I created the issue something was really obvious for me BUT I can not see anything why the JRubyClassLoaders are not separated :(

since jruby-9k does not see the original error I am inclined to "won't fix" it on jruby-1_7 and close the issue.

beside this I still think this issue is related to jruby/warbler#356

@mkristian thanks, as I quickly looked through jruby-rack I did not find how you'd like to proceed on 1)
... as the runtime has always its own JRubyClassLoader - feel the same - not worth looking (as its clearly not obvious) unless paid by the hour :)

it works on jruby-9k and as an etch-case I am closing it