• Release Notes
    • Workaround Exists
    • Hide

      Restart JBDS with a different workspace and then switch workspaces

      Show
      Restart JBDS with a different workspace and then switch workspaces
    • Hide
      Restarting a virtual machine in which JBoss Developer Studio was running at the time of the virtual machine suspension results in JBoss Developer Studio immediately terminating with errors logged in the output. This may also be followed with error prompts when subsequently restarting JBoss Developer Studio with the same workspace. To work around this issue, to avoid terminating errors ensure you close JBoss Developer Studio prior to suspending the virtual machine. When this is not possible, to workaround workspace error prompts start JBoss Developer Studio with a different workspace and then change to the original workspace by clicking File > Switch Workspace.
      Show
      Restarting a virtual machine in which JBoss Developer Studio was running at the time of the virtual machine suspension results in JBoss Developer Studio immediately terminating with errors logged in the output. This may also be followed with error prompts when subsequently restarting JBoss Developer Studio with the same workspace. To work around this issue, to avoid terminating errors ensure you close JBoss Developer Studio prior to suspending the virtual machine. When this is not possible, to workaround workspace error prompts start JBoss Developer Studio with a different workspace and then change to the original workspace by clicking File > Switch Workspace.
    • NEW

      During testing with Virtual Machines, if the machine is shutdown/stopped without closing JBDS, on restart JBDS doesn't start and we get a lot of errors (see attached).

      Some of these are JBoss Tools errors and other Eclipse errors. Is there anything we can do on JBoss Tools or raise this with Eclipse developers upstream to look at?

            [JBDS-3069] Ungraceful shutdown results in multiple errors on startup

            Nick Boldt added a comment -

            Assign to Snjeza for 8.0.x so jiralint will shut up.

            Nick Boldt added a comment - Assign to Snjeza for 8.0.x so jiralint will shut up.

            My env: Fedora19, 64-bit, OpenJDK 1.7.0_55

            I think it is a JBDS 7 issue only (tried repeatedly in JBDS 8Beta2 but could get JBDS to crash).

            • Start JBDS 7.1.1 from the command line
            • Suspend VM
            • Restart VM
            • Either one of the following happens:
              • JBDS crashes immediately (think this is the case when workspace has a project)
              • JBDS features don't work, e.g. project wizards don't start, servers won't start (think this is the case when have empty workspace)
            • Command line output from crash (or closing JBDS via X in top right-hand corner)
              #
              # A fatal error has been detected by the Java Runtime Environment:
              #
              # SIGBUS (0x7) at pc=0x00007f34a602aead, pid=4566, tid=139864110065408
              #
              # JRE version: OpenJDK Runtime Environment (7.0_55-b13) (build 1.7.0_55-mockbuild_2014_04_16_06_38-b00)
              # Java VM: OpenJDK 64-Bit Server VM (24.51-b03 mixed mode linux-amd64 compressed oops)
              # Problematic frame:
              # C [libzip.so+0x4ead] Java_java_util_zip_ZipFile_getZipMessage+0x10bd
              #
              # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
              #
              # An error report file with more information is saved as:
              # /tmp/jvm-4566/hs_error.log
              Compiled method (nm) 310124 493 n java.util.zip.ZipFile::getEntry (native)
              total in heap [0x00007f349d1f3fd0,0x00007f349d1f4330] = 864
              relocation [0x00007f349d1f40f0,0x00007f349d1f4140] = 80
              main code [0x00007f349d1f4140,0x00007f349d1f4330] = 496
              #
              # If you would like to submit a bug report, please include
              # instructions on how to reproduce the bug and visit:
              # http://icedtea.classpath.org/bugzilla
              # The crash happened outside the Java Virtual Machine in native code.
              # See problematic frame for where to report the bug.
              #
              Bus error (core dumped)
              

            On occasion it has also messed up the workspace, prompting with some error message on restart. I couldn't figure out how to fix the error so resorted to deleting the workspace and making a new one. I couldn't get that to happen today but if I see it again I'll add info here.

            Michelle Murray (Inactive) added a comment - My env: Fedora19, 64-bit, OpenJDK 1.7.0_55 I think it is a JBDS 7 issue only (tried repeatedly in JBDS 8Beta2 but could get JBDS to crash). Start JBDS 7.1.1 from the command line Suspend VM Restart VM Either one of the following happens: JBDS crashes immediately (think this is the case when workspace has a project) JBDS features don't work, e.g. project wizards don't start, servers won't start (think this is the case when have empty workspace) Command line output from crash (or closing JBDS via X in top right-hand corner) # # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0x7) at pc=0x00007f34a602aead, pid=4566, tid=139864110065408 # # JRE version: OpenJDK Runtime Environment (7.0_55-b13) (build 1.7.0_55-mockbuild_2014_04_16_06_38-b00) # Java VM: OpenJDK 64-Bit Server VM (24.51-b03 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libzip.so+0x4ead] Java_java_util_zip_ZipFile_getZipMessage+0x10bd # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /tmp/jvm-4566/hs_error.log Compiled method (nm) 310124 493 n java.util.zip.ZipFile::getEntry (native) total in heap [0x00007f349d1f3fd0,0x00007f349d1f4330] = 864 relocation [0x00007f349d1f40f0,0x00007f349d1f4140] = 80 main code [0x00007f349d1f4140,0x00007f349d1f4330] = 496 # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # http://icedtea.classpath.org/bugzilla # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # Bus error (core dumped) On occasion it has also messed up the workspace, prompting with some error message on restart. I couldn't figure out how to fix the error so resorted to deleting the workspace and making a new one. I couldn't get that to happen today but if I see it again I'll add info here.

            Hey! give me a minute - trying as you write!

            Michelle Murray (Inactive) added a comment - Hey! give me a minute - trying as you write!

            Nick Boldt added a comment -

            mmurray1@redhat.com Blah blah please provide details blah blah steps to reproduce... java version, JBDS version, OS name/version, core dump log, etc. Need more than "me too!"

            Nick Boldt added a comment - mmurray1@redhat.com Blah blah please provide details blah blah steps to reproduce... java version, JBDS version, OS name/version, core dump log, etc. Need more than "me too!"

            I have this issue too! I installed VMs with Fedora guest about 1 month ago and have been experiencing this. Assumed it was just VMware causing the issue.

            Michelle Murray (Inactive) added a comment - I have this issue too! I installed VMs with Fedora guest about 1 month ago and have been experiencing this. Assumed it was just VMware causing the issue.

            Can you reproduce this by kill -9 devstudio ?

            Any specific steps you did before the hard shutdown?

            Max Andersen added a comment - Can you reproduce this by kill -9 devstudio ? Any specific steps you did before the hard shutdown?

            Nick Boldt added a comment -

            rhn-support-mus Does the problem persist with JBDS 8? Maybe things have improved in Luna.

            Nick Boldt added a comment - rhn-support-mus Does the problem persist with JBDS 8? Maybe things have improved in Luna.

              snjeza_jira Snjezana Peco (Inactive)
              rhn-support-mus Mustafa Musaji
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: