🚀 go-pugleaf

Mike Slinn wrote:
> I'm having trouble debugging a servlet running under Tomcat.  I copied
> the command and ran it at a comand line prompt (under Linux) so I could
> see the problem better:
> 
> /opt/JBuilder2005/jdk1.4/bin/java -classpath
> "/opt/JBuilder2005/thirdparty/jakarta-tomcat-5.0.27/bin/bootstrap.jar:/home/mslinn/work/zamples/projects/JspExplorer/build/classes:/opt/JBuilder2005/thirdparty/junit3.8/junit.jar:/opt/JBuilder2005/lib/unittest.jar:/opt/JBuilder2005/thirdparty/jakarta-tomcat-5.0.27/common/lib/servlet-api.jar:/opt/JBuilder2005/thirdparty/jakarta-tomcat-5.0.27/common/lib/jsp-api.jar:/opt/JBuilder2005/lib/saaj.jar:/opt/JBuilder2005/lib/jaxrpc.jar:/opt/JBuilder2005/lib/axis.jar:/opt/JBuilder2005/lib/axis-ant.jar:/opt/JBuilder2005/lib/wsdl4j.jar:/opt/JBuilder2005/lib/commons-logging.jar:/opt/JBuilder2005/lib/commons-discovery.jar:/home/mslinn/work/zamples/projects/JspExplorer/build/lib/ojdbc14.jar:/home/mslinn/work/zamples/home/www/zamples.com/www/staging/webapps/JspExplorer/WEB-INF/lib/commons-httpclient-3.0-alpha1.jar:/home/mslinn/work/zamples/home/www/zamples.com/www/staging/webapps/JspExplorer/WEB-INF/lib/commons-codec-1.2.jar:/home/mslinn/work/zamples/home/www/zamples.com/www/staging/webapps
/J
> spExplorer/WEB-INF/lib/commons-logging.jar:/home/mslinn/work/zamples/home/www/zamples.com/www/staging/webapps/JspExplorer/WEB-INF/lib/commons-logging-api.jar:/home/mslinn/work/zamples/home/www/zamples.com/www/staging/webapps/JspExplorer/WEB-INF/lib/cos.jar:/opt/JBuilder2005/jdk1.4/lib/tools.jar"
>  "-Dcatalina.home=/opt/JBuilder2005/thirdparty/jakarta-tomcat-5.0.27"
> -Dje.etc=home/www/zamples.com/www/staging/jeEtc
> -Dje.sessions=home/www/zamples.com/www/staging/webapps/jeSessions/
> -Xdebug -Xnoagent -Djava.compiler=NONE
> -Xrunjdwp:transport=dt_socket,address=poi:1162,suspend=y
> org.apache.catalina.startup.Bootstrap -config
> /home/mslinn/work/zamples/Tomcat/conf/server8080.xml start -f
> projects/JspExplorer/server.xml
> Error [111] in connect() call!
> err:: Connection refused
> Socket transport failed to init.
> Transport dt_socket failed to initialize, rc = -1.
> FATAL ERROR in native method: No transports initialized
> 
> 
> Any ideas?
> 
> Mike

When looking at these things, you need to look at the first error, not 
the last.  The first error is "Connection refused".

Now, remote or local, when you are debugging server-side stuff it is 
going to make a socket connection to the debugging port, which is 
specified here as "1162".  The "Connection refused" is telling you that 
it could not make a connection on port 1162.

This is almost always a firewall issue.  Your machine must be configured 
to accept connections on the debugging port.  You can change to a 
different port (one which is not being blocked) or you can alter your 
firewall settings for port 1162.

-- 

Regards,

Lori Olson [TeamB]

------------

Save yourself, and everyone else, some time and search the
newsgroups and the FAQ-O-Matic before posting your next
question.

Google Advanced Newsgroup Search
     http://www.google.ca/advanced_group_search
Other Newsgroup Searches:
     http://www.borland.com/newsgroups/ngsearch.html
Joi Ellis's FAQ-O-Matic:
     http://www.visi.com/~gyles19/fom-serve/cache/1.html