1 Reply Latest reply on Sep 3, 2008 11:17 AM by jaikiran pai

    Starting JAS in Debug mode

    Cle' Diggins Newbie

      I am having a problem starting JAS in debug mode, and don't know what could be causing it since I got the error using 4.2.2GA and then did a clean install of 4.2.3GA and still have the same error.

      What happens is when I try to start my server in debug mode through myEclipse, It stops after

      16:04:38,213 INFO [Server] Starting JBoss (MX MicroKernel)...
      16:04:38,213 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)
      16:04:38,213 INFO [Server] Home Dir: C:\jboss-4.2.3.GA
      16:04:38,213 INFO [Server] Home URL: file:/C:/jboss-4.2.3.GA/
      16:04:38,213 INFO [Server] Patch URL: null
      16:04:38,213 INFO [Server] Server Name: default
      16:04:38,213 INFO [Server] Server Home Dir: C:\jboss-4.2.3.GA\server\default
      16:04:38,213 INFO [Server] Server Home URL: file:/C:/jboss-4.2.3.GA/server/default/
      16:04:38,213 INFO [Server] Server Log Dir: C:\jboss-4.2.3.GA\server\default\log
      16:04:38,213 INFO [Server] Server Temp Dir: C:\jboss-4.2.3.GA\server\default\tmp
      16:04:38,213 INFO [Server] Root Deployment Filename: jboss-service.xml
      16:04:38,464 INFO [ServerInfo] Java version: 1.6.0_03,Sun Microsystems Inc.
      16:04:38,464 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0_03-b05,Sun Microsystems Inc.
      16:04:38,464 INFO [ServerInfo] OS-System: Windows XP 5.1,x86

      as if it has hit a breakpoint, and in the development window I get the message 'Source not found for XMLEntityScanner.load(int, boolean) line: not available'

      Pressing the continue execution button just brings up more of the same error. If anyone has an idea of what could be causing this, or anything else I can check, please share.

      Thanks,
      CDiggins

        • 1. Re: Starting JAS in Debug mode
          jaikiran pai Master

          Some of the things you could try:

          1) Let JBoss start successfully. Then start your debug mode in Eclipse (for this to happen, you should configure suspend=n in the JAVA_OPTS in run.bat for JBoss).

          2) In the "Breakpoints" window of your project, if you see any breakpoints already set, then remove them.

          3) In the "Debug..." window of Eclipse, remove/delete any existing debug configurations. Then create a new configuration.