- This topic has 9 replies, 4 voices, and was last updated 19 years, 11 months ago by Greg.
-
AuthorPosts
-
alexdotcMemberHello,
I’m trying to run Resin inside of Eclipse in debug mode and I’m getting a popup error with an error message. It starts ok in “Run mode” but I would like to use it in “Debug mode”. I’ve tried adding all the jars in the resin/lib folder to the classpath inside Eclipse’s preferences > My Eclispse > Application Servers > Resin 3, but that didn’t seem to work.
Here is the popup message:
A configuration error occurred during startup. Please
verify the preference field with the prompt: Error[0]
in gethostbyname() call!
err::Success
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.
In the Eclipse log, I get the following message:
!SESSION Jan 29, 2005 17:54:17.701 ———————————————
eclipse.buildId=M200409161125
java.version=1.4.2_07
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US!ENTRY com.genuitec.eclipse.easie.resin3 1 1 Jan 29, 2005 17:54:17.702
!MESSAGE Error starting Resin: Error [0] in gethostbyname() call!
err:: Success
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.Here is my setup and version numbers:
Eclipse: 3.0.1
MyEclipseIDE: 3.8.4 Manual Install
Resin: Pro 3.0.10
OS: Fedora Core 3
Kernel: 2.6.10-1.741_FC3.stk16Under my Eclipse preferences:
MyEclipse > Application Servers > Resin 3:
Resin Server: Enabled
Resin Home Directory: /opt/resin
Configuration File: /opt/resin/conf/resin.confMyEclipse > Application Servers > Resin 3 > JDK:
Resin JDK name: j2sdk1.4.2_07
No Optional Java VM ArgumentsMyEclipse > Application Servers > Resin 3 > Launch:
* Debug modeMyEclipse > Application Servers > Resin 3 > Paths:
Prepend to classpath:
Append to classpath:
retroweaver.jar – /opt/resin/lib/retroweaver.jar
Append to library path:
bin – /opt/resin/binWell, that’s about it. Please help.
Thanks,
Alex
Riyad KallaMemberAlex,
Does is this the issue where Resin pops up a dialog, and if you hit OK the server goes ahead and finishes starting up just fine and you can access running web apps and such, or does this stop Resin from starting up all together? Admitedly I haven’t seen this issue before…
alexdotcMemberThe server doesn’t start at all. It does start ok when I try to start it in “Run mode” inside Eclipse. It also starts ok on the command line when I use the following command.
httpd.sh -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n
It’s only when I try to run Resin inside of Eclipse in “Debug mode” that I get this error and it doesn’t start after the error.
Riyad KallaMember-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n
Have you tried adding these to the “Option VM Arguments” portion of the config for Resin? Did you make sure you setup the Resin 3 connector and not the Resin 2? Do you have a license for Resin (Resin Pro) or is it the free download?
alexdotcMemberThis is configured in the Resin 3 connector and not Resin 2. Resin pro is a free download. I tried adding the parameters as optional VM arguments as you suggested but I received the same error.
Scott AndersonParticipantI tried to replicate the problems you’re having so here’s what I did.
1) Freshly installed Eclipse 3.0.1 / MyEclipse 3.8.4
2) Downloaded Resion 3.0.10 Pro using this link: http://www.caucho.com/download/resin-pro-3.0.10.zip
3) Unzipped Resin to a local directory at C:\dev\appservers\resin\resin-pro-3.0.10
4) Launched MyEclipse and configured the server by setting only the following:
Resin Home Directory: C:\dev\appservers\resin\resin-pro-3.0.10
Configuration File: C:\dev\appservers\resin\resin-pro-3.0.10\conf/resin.conf
Resin JDK Name: j2sdk1.4.2_06 (which is a local full install of JDK 1.4.2)
Debug mode was the default
5) Started Resin using the connector and it launched with no problems whatsoever
6) Opened an internal browser window and pointed at to http://localhost:8080 and verified Resin was runningWhat did I do that was different than what you did?
alexdotcMemberI was developing on Windows and it was working fine for me. Now, I have to work on Linux and this is where the problem is happening using the same setup.
GregMemberI followed the exact same steps that Scott performed on window but this time on our linux workstation. I was able to start the server in debug mode and set a breakpoint in a jsp with no problem.
If you have followed Scott’s steps exactly and are still getting the gethostbyname() error there must be some other configuration that isn’t MyEclipse specific. The problem might lie in your linux network configuration.
alexdotcMemberYou’re right. The problem was in my /etc/hosts file. It was missing the entry:
127.0.0.1 localhost
Once added, it started up just fine. I don’t know why it would start ok in “Run moide” but not in “Debug mode” but at least it’s working now. Thank you for your help.
GregMemberHmm, that is interesting, in debug mode the jvm binds to a port to listen for incoming jdpa connections. In run mode it might not be listening to anything. Regardless, we’re glad your up and running.
-
AuthorPosts