[Dana]

Hi!,
Please help me with this.

I’m using MyEclipse2.1 and Tomcat Server 5. When I try to start the TomcatServer I go only as far as:

************************************************************
Jun 2, 2004 10:26:36 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 80
Jun 2, 2004 10:26:36 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1578 ms
Jun 2, 2004 10:26:37 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jun 2, 2004 10:26:37 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.0.19
Jun 2, 2004 10:26:37 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Jun 2, 2004 10:26:37 AM org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
Jun 2, 2004 10:26:37 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:C:\demo_dev55\tomcat\conf\Catalina\localhost\admin.xml
************************************************************

And from my C:\eclipse\workspace\.metadata\.log file I have the last few lines pasted here:

——–java.version=1.4.2
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
!ENTRY org.eclipse.osgi Jun 02, 2004 09:51:31.444
!MESSAGE Bundle reference:file:c:/eclipse/plugins/org.eclipse.debug.ui_3.0.0 [18] was not resolved
!ENTRY org.eclipse.osgi Jun 02, 2004 09:51:31.444
!MESSAGE Bundle reference:file:c:/eclipse/plugins/org.eclipse.jdt.debug_3.0.0 [27] was not resolved

[Riyad Kalla]

Posting in wrong forum, moving to Support.

[Riyad Kalla]

Dana,
Please post all of your console output from starting Tomcat. The reason I say this is because what you posted above looks fine, so I’m guessing there is some more text or some behavior that suggests to your that its not working? Can you tell us what you are doing that is telling you its not working? (can’t access it with a browser, etc.).

Also please tell us what version of Eclipse, MyEclipse and JDK you are running:
1) Eclipse, click on Help > About, at top, look for “Version:”
2) MyEclipse, click on Help > About, click MyEclipse button, read version from any of the plugin lines with Provider “Genuitec, LLC”.
3) JDK, drop to a command line and type “java -version” and paste the result here.

Also please clarify what steps you are taking to use Tomcat, and why you feel its not working.

[Dana]

Thank you Riyad.
I did paste the complete Console Message, however I get this
error line:
Source not found for StandardContext.start() line: 4097

1) Eclipse:3.0.0
2) MyEclipse: 3.7.0
3) JDK: 1.4.2

When I run the Tomcat server using the command line it seems to be working fine.

-Dana

[Scott Anderson]

Dana,

Specifically which version of Tomcat 5 are you running? Also, is the configuration you’re starting customized in any way or is it the standard default server?

[Dana]

Thank you.
Yeah, my configuration is customized.
Tomcat Version: 5.0.19
Here are two things you would be interested in
1. The tomcat server starts up fine in ‘run Mode’ under MyEclipse.
2. someone else here is using the same server version with identical environment and it seems to be working fine.

Thank you,
Dana

[Scott Anderson]

Dana,

Thanks for the additional info. From that the issue seems environmental and given your ‘run Mode’ comment I’m going to take a shot and guess that it might be the JDK you’re launching the server with. Some early versions of 1.4.2 had bugs that caused interaction problems with the Eclipse debugger and since this is the primary difference between ‘debug’ and ‘run’ modes, this seems likely. If you have a version of JDK 1.4.1 installed, could you try launching Tomcat with that? We’ve never seen problems with JDK 1.4.1.

[Dana]

Thank you Scott.
I will try to run it with JDK 1.4.1. While I do that, I just want to mention that when I run Tomcat Server in the debug mode on command line, it does so successfully.

-Dana

[Scott Anderson]

I just want to mention that when I run Tomcat Server in the debug mode on command line, it does so successfully.

That may be, but you’re doing it without a JPDA debug client attached that’s trying to control it so it’s not really the same thing.

Another thing to test is whether or not you can start with JDK 1.4.2 in debug mode after removing ALL breakpoints (see Breakpoints View).

[Dana]

Thank you again Scott. It’s interesting to know the difference.
I do not have any breakpoints, but like you said before I guess I should try it with the JDK 1.4.1 version and check it out.

[Scott Anderson]

The ‘no breakpoints’ thing was just a shot.

2. someone else here is using the same server version with identical environment and it seems to be working fine.

It can’t be *totally* identical as software is typically not capricious. 😉 It would be interesting to check the precise versions of: the Eclipse launch JVM, the Tomcat JVM, Tomcat version, Eclipse version, MyEclipse version, Tomcat connector configuration and any other additional plugins you might be using. There will be *some* difference somewhere. The hard part is determining it. My bet is still on the JDK’s.

[Dana]

Hi Scott,
Seems like it was a memory problem.
After doing:
Windows-> Preferences -> MyEclipse -> Application Servers ->TomCat5 -> JDK ->Optional Java VM Arguments = -Xms512M -Xmx1024M
it seems to work fine.

Thanks a lot for your time.

[Riyad Kalla]

Dana,
We are glad you are up and running now, please come back if you run into any other weirdness.

[Author]

Posts