4 Replies Latest reply on Aug 7, 2012 8:38 AM by asibrahim

    JBoss crash After changing Kernel parameters

    asibrahim

      Hello guys,

       

      This is my first time to post something on the community, hope that i will not annoy anyone.

      My problem is that we have JBoss running on HP server using operation system HP-UX 11i v3, after changing these kernel parameters vx_ninode=40000 & vxfs_ifree_timelag=-1. I was not able to start the JBoss server by any means and get the below error. The JBoss version we are using is 5.1.0.GA

      Thanks guys for help

        • 1. Re: JBoss crash After changing Kernel parameters
          sfcoy

          Is that all that changed? Is it possible that the default thread stack size was changed as well?

          • 2. Re: JBoss crash After changing Kernel parameters
            asibrahim

            Actually these 2 are the only kernel parameters that have been modified , I do not know if they might have impact on the thread stack size or not.

            Do you think it is worth to change the thread stack size using the option -Xss?

            Is it possible to be done during the JBoss start up?

             

            Thanks for your quick reply.

             

            Regards

            Ahmed,

            • 3. Re: JBoss crash After changing Kernel parameters
              sfcoy

              I'd be surprised if those kernel parameters had any impact on the stack size.

               

              Do you have a backup of the previous sysctl.conf file? What happens if you rollback to the old one? Have you compared the old with the new?

               

              What is the output of sysctl -a?

               

              You could try adding the -Xss option in the bin/run.conf file to the line that sets up JAVA_OPTS, but that does not seem like the root cause. Normally we use that to reduce the default stack size, which can be pretty big (2M on Linux).

              • 4. Re: JBoss crash After changing Kernel parameters
                asibrahim

                When rolling back these parameters the JBoss worked fine without any problems, i.e when the backup was restored the problem was solved.

                I will get back to with these output of sysctl -a when i get it from the system admin.

                Thanks again for your help.

                 

                Regards,

                Ahmed