Closed L2G closed 12 years ago
Hi
Thank you for your report. I've tried to figure out what happened, but I can't. So I wonder if you'd like to show the method signature of the interface that causes runtime error.
Best regards.
I will have to reduce the code to a minimal example so as not to violate my non-disclosure agreement with my employer. I will see what I can do. If I don't respond in the next day or two, it'll be because I've run out of time to work on this and my boss asked me to move on to something else.
We determined that we were really running up against Rjb's documented incompatibility with multiple Java threads. We were using Java code that was multithreaded and we didn't realize it.
Is the Java thread problem something that is impossible to fix? If I have some code I can give you that reproduces this problem repeatably, would that be helpful to you?
I'm working on some code that uses RJB to create a Java object. The constructor requires a reference to an object with a callback method. The object I'm passing to the constructor is a Ruby object bound to a Java class with Rjb::bind, so the callback is Ruby code within the Ruby object.
Everything is fine up to the point where the Java code tries to call the callback, and then it breaks down. It blames a C library routine called RtlUlonglongByteSwap, so immediately I thought of the problems that used to exist with building RJB on Windows.
This is on Windows 7, using Ruby 1.9.2p290 and the latest DevKit (DevKit-tdm-32-4.5.2-20111229-1559). Due to the nature of my project, I'm not allowed to use a newer Ruby interpreter.