Remote Debugging using Jbuilder X and Jboss 3.2.x

I want to do remote debugging using Jbuilder X and Jboss 3.2.x
The Jboss server is installed on a Linux Machine (Red Hat 9) and Jbuilder is on a Windows 2000 machine.
To do remote debugging I need to start the Jboss server on the linux machine in debug mode, for which I need to make some changes in run.sh file.
I have consulted this document
http://www.oracle.com/technology/products/jdev/howtos/appservers/debug_in_jboss.html

but the lines it suggests to change in UNIX are not there in my Linux run.sh file. There is no seperate information about Linux.

Also i have consulted
http://www.borland.com/products/white_papers/pdf/jb_ejb_development_using_jbx_and_jboss.pdf

But it doesn't say anything about the remote machine being a Linux machine.
Can some please tell me what changes do i need to make in run.sh so that remote debugging is possible

Thanks

The arguments that you need to add are for the line that calls java.

So there is a line somewhere in there that calls java from the command line, that is where you will need to add the debug arguments.

Or you might have a line in there that sets some variable that is used in the call to Java and could put it there.

You can post your run.sh and we can point you to the correct line.

Mark

Thanks for replying
Here is my run.sh

#!/bin/sh
### ====================================================================== ###
##                                                                          ##
##  JBoss Bootstrap Script                                                  ##
##                                                                          ##
### ====================================================================== ###
 
### $Id: run.sh,v 1.9.2.5 2004/01/01 01:20:38 starksm Exp $ ###
 
DIRNAME=`dirname $0`
PROGNAME=`basename $0`
GREP="grep"
 
# Use the maximum available, or set MAX_FD != -1 to use that
MAX_FD="maximum"
 
#
# Helper to complain.
#
warn() {
    echo "${PROGNAME}: $*"
}
 
#
# Helper to puke.
#
die() {
    warn $*
    exit 1
}
 
# OS specific support (must be 'true' or 'false').
cygwin=false;
darwin=false;
case "`uname`" in
    CYGWIN*)
        cygwin=true
        ;;
 
    Darwin*)
        darwin=true
        ;;
esac
 
# Read an optional running configuration file
if [ "x$RUN_CONF" = "x" ]; then
    RUN_CONF="$DIRNAME/run.conf"
fi
if [ -r $RUN_CONF ]; then
    . $RUN_CONF
fi
 
# For Cygwin, ensure paths are in UNIX format before anything is touched
if $cygwin ; then
    [ -n "$JBOSS_HOME" ] &&
        JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
    [ -n "$JAVA_HOME" ] &&
        JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
    [ -n "$JAVAC_JAR" ] &&
        JAVAC_JAR=`cygpath --unix "$JAVAC_JAR"`
fi
 
# Setup JBOSS_HOME
if [ "x$JBOSS_HOME" = "x" ]; then
    # get the full path (without any relative bits)
    JBOSS_HOME=`cd $DIRNAME/..; pwd`
fi
export JBOSS_HOME
 
# Increase the maximum file descriptors if we can
if [ "$cygwin" = "false" ]; then
    MAX_FD_LIMIT=`ulimit -H -n`
    if [ $? -eq 0 ]; then
if [ "$MAX_FD" = "maximum" -o "$MAX_FD" = "max" ]; then
    # use the system max
    MAX_FD="$MAX_FD_LIMIT"
fi
 
ulimit -n $MAX_FD
if [ $? -ne 0 ]; then
    warn "Could not set maximum file descriptor limit: $MAX_FD"
fi
    else
warn "Could not query system maximum file descriptor limit: $MAX_FD_LIMIT"
    fi
fi
 
# Setup the JVM
if [ "x$JAVA" = "x" ]; then
    if [ "x$JAVA_HOME" != "x" ]; then
JAVA="$JAVA_HOME/bin/java"
    else
JAVA="java"
    fi
fi
 
# Setup the classpath
runjar="$JBOSS_HOME/bin/run.jar"
if [ ! -f $runjar ]; then
    die "Missing required file: $runjar"
fi
JBOSS_BOOT_CLASSPATH="$runjar"
 
# Include the JDK javac compiler for JSP pages. The default is for a Sun JDK
# compatible distribution which JAVA_HOME points to
if [ "x$JAVAC_JAR" = "x" ]; then
    JAVAC_JAR="$JAVA_HOME/lib/tools.jar"
fi
if [ ! -f "$JAVAC_JAR" ]; then
   # MacOSX does not have a seperate tools.jar
   if [ "$darwin" != "true" ]; then
      warn "Missing file: $JAVAC_JAR"
      warn "Unexpected results may occur.  Make sure JAVA_HOME points to a JDK and not a JRE."
   fi
fi
 
if [ "x$JBOSS_CLASSPATH" = "x" ]; then
    JBOSS_CLASSPATH="$JBOSS_BOOT_CLASSPATH:$JAVAC_JAR"
else
    JBOSS_CLASSPATH="$JBOSS_CLASSPATH:$JBOSS_BOOT_CLASSPATH:$JAVAC_JAR"
fi
 
# If JAVA_OPTS is not set try check for Hotspot
if [ "x$JAVA_OPTS" = "x" ]; then
 
    # Check for SUN(tm) JVM w/ HotSpot support
    if [ "x$HAS_HOTSPOT" = "x" ]; then
HAS_HOTSPOT=`$JAVA -version 2>&1 | $GREP -i HotSpot`
    fi
 
    # Enable -server if we have Hotspot, unless we can't
    if [ "x$HAS_HOTSPOT" != "x" ]; then
# MacOS does not support -server flag
if [ "$darwin" != "true" ]; then
    JAVA_OPTS="-server"
fi
    fi
fi
 
# Setup JBoss sepecific properties
JAVA_OPTS="$JAVA_OPTS -Dprogram.name=$PROGNAME"
 
# For Cygwin, switch paths to Windows format before running java
if $cygwin; then
    JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
    JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
    JBOSS_CLASSPATH=`cygpath --path --windows "$JBOSS_CLASSPATH"`
fi
 
# Display our environment
echo "========================================================================="
echo ""
echo "  JBoss Bootstrap Environment"
echo ""
echo "  JBOSS_HOME: $JBOSS_HOME"
echo ""
echo "  JAVA: $JAVA"
echo ""
echo "  JAVA_OPTS: $JAVA_OPTS"
echo ""
echo "  CLASSPATH: $JBOSS_CLASSPATH"
echo ""
echo "========================================================================="
echo ""
 
STATUS=10
while [ $STATUS -eq 10 ]
do
# Execute the JVM
   "$JAVA" $JAVA_OPTS \
      -classpath "$JBOSS_CLASSPATH" \
      org.jboss.Main "$@"        
   STATUS=$?
   # if it doesn't work, you may want to take a look at this:
   #    <a href="http://developer.java.sun.com/developer/bugParade/bugs/4465334.html" target="_blank" rel="nofollow">http://developer.java.sun.com/developer/bugParade/bugs/4465334.html</a>
done

and here is my run.conf

## -*- shell-script -*- ######################################################
##                                                                          ##
##  JBoss Bootstrap Script Configuration                                    ##
##                                                                          ##
##############################################################################
 
### $Id: run.conf,v 1.2.2.2 2004/08/02 13:20:44 pilhuhn Exp $
 
#
# This file is optional; it may be removed if not needed.
#
 
#
# Specify the maximum file descriptor limit, use "max" or "maximum" to use
# the default, as queried by the system.
#
# Defaults to "maximum"
#
#MAX_FD="maximum"
 
#
# Specify the profiler configuration file to load.
#
# Default is to not load profiler configuration file.
#
#PROFILER=""
 
#
# Specify the location of the Java home directory.  If set then $JAVA will
# be defined to $JAVA_HOME/bin/java, else $JAVA will be "java".
#
#JAVA_HOME="/opt/java/jdk"
 
#
# Specify the exact Java VM executable to use.
#
#JAVA=""
 
#
# Specify options to pass to the Java VM.
#
#JAVA_OPTS="-server -Xms128m -Xmx512m"
# Sample JDK 1.3.1 JPDA settings
#JAVA_OPTS="-classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y $JAVA_OPTS"
 
# Sample JDK 1.4.1 JPDA settings
#JAVA_OPTS="-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y $JAVA_OPTS"

I also tried removing the comment from teh last line of run.conf, but after that the server didn't start. It hanged after displaying the following

changing

-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y
to
-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n

makes the server run properly
but when i try ot attach from my remote Jbuilder, I get the follwoing exception

- IOException attaching Remote Java debug process --
java.net.ConnectException: Connection refused: connect

Here is the options that I put in my Bea Weblogic config file, and the original Options are appended to the variable.

-Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=5005,suspend=n

of course you would change the address to be your port address.

How are you connecting? What IDE, and is it using the same port?

Mark

Thanks a lot.
It started working after I restarted the server .