2 Replies Latest reply on Sep 22, 2004 11:40 AM by birjup

    hard locking on running app

    birjup

      Hi,
      I am running jboss 4rc1 on jdk1.5rc on linux fedora core 2. Everytime i run my application, it takes a random amount of time for the computer to hard-lock up. I can run other java applications eg eclipse without any problems on the box. There is nothing in syslog or server.log or the console to suggest why this is happening. I was having the same problem running jboss on jdk1.4.2. Has anyone had any similar problems? This is really weird!! The only one clue i ever had was something like
      'segmentation fault in run.sh' in the console. I had this message once.
      I've tried it using a modified jboss_init_redhat.sh and run.sh and the same problem occurs. I've reinstalled linux, reinstalled jboss, reinstalled the jdk etc! dmesg has nothing slabtop has nothing....someone must have had something similar, no?

      please help,
      birju

        • 1. Re: hard locking on running app
          genman


          I don't know if JDK 1.5 is ready or not. Could be it.

          You can get a stack trace with CTRL-\ on Linux and it might indicate if you have a dead lock or not.

          • 2. Re: hard locking on running app
            birjup

            It wasn't the app that was locking, but the os....
            I think it was an unstable kernel supplied with fedora core2 (2.5something).
            I upgraded it to 2.6something and I have been running without a problem.
            Odd numbered kernels are labeled as such to notify their instability, so why did redhat choose to use it....strange...?

            A bientot