4 Replies Latest reply on Oct 9, 2004 12:22 AM by Kevin Galligan

    debugging with JPDA

    Jon Beyer Newbie

      Platform is Eclipse 3.0 and JBoss 3.2.5 with integrated Tomcat. I'm trying to debug JSPs that call EJBs. I'm able to connect to JBoss through JPDA, but haven't figured out how to run Tomcat in debug mode. With standalone Tomcat, it's as simple as passing the command-line argument 'jpda', but I haven't been able to find how to do this with integrated Tomcat. Can this be done with integrated Tomcat, or do I need to use standalone?

      Thanks,
      Jon

        • 1. Re: debugging with JPDA
          Jboss JBoss Newbie

          Same here (except I'm mainly using NetBeans as debugging client). Please post any insight into running debugging for both JBoss/Tomcat. Thx.

          • 2. Re: debugging with JPDA
            Kevin Galligan Newbie

            Having the same problem. Does anybody know how to do this? I don't need to debug actual jsp's (although, that would be sweet). Just need to get into the regular classes in my webapp.

            I used to develop with tomcat and jboss in separate jvm's and did this type of thing regularly. I'm connected to 3.2.5 with jpda, no problem. It just doesn't stop at the breakpoint.

            • 3. Re: debugging with JPDA
              Scott Stark Master

              You startup jboss with the usual jpda debugging opts, for example, those given in the run.conf of the bin directory:

              JAVA_OPTS="-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=
              y $JAVA_OPTS"

              and embedded tomcat is in debug mode. I attach to the jboss/tomcat instance and can debug tomcat using Intellij without a problem. For eclipse specific issues try asking on the JBossIDE forum.

              • 4. Re: debugging with JPDA
                Kevin Galligan Newbie

                AHHH! Sorry, frustration. I'm using Idea 4.5.1, and I've had some serious upgrade pain from version 3. I use ant to compile and package, which worked ok in v3, but I guess v4.5 likes its output directories set "properly". Ehh, something like that. Anyway, its working now. Thanks.