Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Critical Critical
    • Resolution: Incomplete
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Compiler
    • Labels:
      None
    • Number of attachments :
      0

      Description

      Once the server code for JRUBY-2307 jits, it starts spitting out this text, which would mean that a break jump is getting all the way out to a thread:

      [headius @ cnutter:~/projects/jruby]
      $ Exception in thread "Thread-62" org.jruby.exceptions.JumpException$BreakJump 
      jruby client.rb 
      Worked with size 1007
      Worked with size 1008
      [headius @ cnutter:~/projects/jruby]
      $ Exception in thread "Thread-63" org.jruby.exceptions.JumpException$BreakJump
      jruby client.rb 
      Worked with size 1007
      Worked with size 1008
      ...
      

      It did not appear to affect execution, but could mean there's some logging we need to remove. It also likely means break handling is broken somewhere in the compiler.

        Activity

        Hide
        Rick Ohnemus added a comment -

        I thought I had posted most information about what I saw happening. However, since I don't see it in the comments, that must have been when I was having network problems and then completely forgot about posting a comment when the network came back.

        I was only seeing this happen on 2 Windows systems. Everything worked fine on 3 other Windows systems and 2 Linux systems. I couldn't find any significant differences between any of the Windows systems (Windows Server 2003 with the same patches, etc.).

        The error happened on line 1610 of lib/ruby/1.8/drb/drb.rb when DRb was started with 0.0.0.0 in the URL (e.g. "druby://0.0.0.0:12345"). No idea why 0.0.0.0 worked on most systems and caused the break jump error on 2 systems. Removing 0.0.0.0 from the URL allowed the code to work on all systems.

        Show
        Rick Ohnemus added a comment - I thought I had posted most information about what I saw happening. However, since I don't see it in the comments, that must have been when I was having network problems and then completely forgot about posting a comment when the network came back. I was only seeing this happen on 2 Windows systems. Everything worked fine on 3 other Windows systems and 2 Linux systems. I couldn't find any significant differences between any of the Windows systems (Windows Server 2003 with the same patches, etc.). The error happened on line 1610 of lib/ruby/1.8/drb/drb.rb when DRb was started with 0.0.0.0 in the URL (e.g. "druby://0.0.0.0:12345"). No idea why 0.0.0.0 worked on most systems and caused the break jump error on 2 systems. Removing 0.0.0.0 from the URL allowed the code to work on all systems.
        Hide
        Charles Oliver Nutter added a comment -

        Rick: Ok, thank you for the update. It could still be broken, since the default bind URL may have changed due to other fixes. I'll have a second look at the lines you mention from drb.rb and see if I can come up with a reproduction case.

        Show
        Charles Oliver Nutter added a comment - Rick: Ok, thank you for the update. It could still be broken, since the default bind URL may have changed due to other fixes. I'll have a second look at the lines you mention from drb.rb and see if I can come up with a reproduction case.
        Hide
        Charles Oliver Nutter added a comment -

        Rick: I've still been unable to reproduce this. Two questions for you:

        • Can you still reproduce this on any version of JRuby?
        • What priority do you think should be assigned to this issue?
        Show
        Charles Oliver Nutter added a comment - Rick: I've still been unable to reproduce this. Two questions for you: Can you still reproduce this on any version of JRuby? What priority do you think should be assigned to this issue?
        Hide
        Hiro Asari added a comment -

        Rick and Ben,

        Is this still observed in 1.5.0? Or better yet, in the current trunk?

        Show
        Hiro Asari added a comment - Rick and Ben, Is this still observed in 1.5.0? Or better yet, in the current trunk?
        Hide
        Charles Oliver Nutter added a comment -

        No follow-up from any reporters in two years.

        Show
        Charles Oliver Nutter added a comment - No follow-up from any reporters in two years.

          People

          • Assignee:
            Charles Oliver Nutter
            Reporter:
            Charles Oliver Nutter
          • Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: