6 Replies Latest reply on Dec 7, 2011 5:56 AM by Muhammad Irfan Masood

    Jboss running in debug mode

    Muhammad Irfan Masood Newbie

      Hi,

       

      What can be difference in terms of accepting number of incoming requests, no of active threads while JBoss is running in debug mode as compare to JBoss running in run mode.

       

      The JBoss I am using is 3.2.5.

       

      Best Regards!

        • 1. Re: Jboss running in debug mode
          Wolf-Dieter Fink Master

          What you mean by debug/run mode?

          Setting remote debug or logging??

          • 2. Re: Jboss running in debug mode
            Muhammad Irfan Masood Newbie

            I mean when server is started for debugging with IDE for example JDeveloper. In  run.bat file, if we add like below:

             

            set JBOSS_DEBUG_FLAGS=-ojvm -XXdebug,detached,quiet,port4000

            "%JAVA%" %JAVA_OPTS% -classpath "%JBOSS_CLASSPATH%" org.jboss.Main %*

             

             

             

             

             

            Thanks!

            • 3. Re: Jboss running in debug mode
              Wolf-Dieter Fink Master

              I do not know such option for debug, I use "-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n" to connect a debugger against the Sun-JVM.

               

              But nevertheless debugger options should not have an effect to incomming requests and threads.

              What happen is that most of race condiditons disapear because of different timing and the application might be slower.

               

              Maybe you have to provide more details about your issue, what you try to achieve?

              I suppose you use Windows, what version and what JVM?

              • 4. Re: Jboss running in debug mode
                Muhammad Irfan Masood Newbie

                Actually, we were using JBoss 3.2.5 with JDK 1.4.2 32 bit on Windwos 2008 R2 64 bit machine with 32 bit Java Wrapper that runs JBoss as windows service. We planned to use 64 bit JDK 1.6.0_29 for which we downloaded JBoss native for Windows 2.0.9 x64 bit version from JBoss download area but with same JBoss 3.2.5, after testing on staging we applied it over production, but it produced very starnge behavious over production. Out of 28 banks, 25 banks were able to succesfully send transaction through our web service but 3 of them who send huge transactions about 70 % of total transaction a day were not getting any response from our web service, there (some not all ) transactions were logged in our system but they were not getting any response back. There was no errors except Connection Reset which means banks application were timing out. Finally we rolled back to old set up and every thing start working perfectly.

                 

                JBoss native for windows invoke the run.bat file which was not in use previously,  that have the line in it that I written in my previous message.

                 

                set JBOSS_DEBUG_FLAGS=-ojvm -XXdebug,detached,quiet,port4000

                "%JAVA%" %JAVA_OPTS% -classpath "%JBOSS_CLASSPATH%" org.jboss.Main %*

                 

                So I doubt that this might be the issue, so thats why I was asking that if by chance Jboss is running in debug mode, then will it limit traffic in terms of number of requests processing etc.

                 

                Or might be Jboss 3.2.5 might not be compatible with either JDK 1.6.0_29 or with JBoss native for windows 2.0.9 64 bit ...

                 

                Thanks a lot!

                • 5. Re: Jboss running in debug mode
                  Wolf-Dieter Fink Master

                  As I see the JBOSS_DEBUG_FLAGS not within the JAVA command I'm not sure whether it is used.

                  Do you see these options in the boot.log?

                   

                  I suppose that it might be an issue with the new JDK but I'm not sure.

                  • 6. Re: Jboss running in debug mode
                    Muhammad Irfan Masood Newbie

                    Yes its not there in boot.log. Thanks for your kind help.