[tenjin]

Hi,

The problem was caused by the location of the Java SDK.

It was stored in “D:\Program Files\Java”

When moved to “D:\Java” everything worked fine. I guess the space in the path messed things up.

Regards

Darren.

[Riyad Kalla]

Darren,
Does that workaround solve the problem for you right now? i’m going to file a bug for this to get addressed ASAP so you guys don’t need to work around the issue.

[tenjin]

Hi,

That did fix the problem, so I think the space in the path to the JDK must be significant. It would be great to log that as an enhancement request.

I have also noticed the following associated behaviour:

When trying to diagnose this problem I created a series of new JRE configs. These get listed in:

WINDOWS->PREFERENCES->Installed JREs

I then tried to delete the duplicates by clicking on each one and selecting “REMOVE”. Although this appeared to work if I then clicked “OK” to close the PREFERENCES window and then reopened it again, the JREs reappeared.

So, removing the JREs doesn’t seem to work. NOt a big issue, but again would be good to log as a defect.

BTW, I am using:

Eclipse 3.2.0
MyEclipse 5.0 GA
Sun Java 1.5
Windows XP Pro

Regards

Darren.

[Riyad Kalla]

Darren,
That is very odd, can you check your log file under (<workspace dir>\.metadata\.log) for messages pertaining to removing the JDKs?

[tenjin]

Hi,

There is nothing in the log file for this activity. In fact, I cleared the log and it’s still empty after reproducing the bug.

I have noticed that if I start Eclipse and try to remove the JRE as the first action it works fine. If I then add another JRE (through the Application Servers->Resin2->JDK menu) I can’t delete it unless I restart Eclipse.

Is there any way to force Eclipse to log information about this failure?

Regards

Darren.

[Riyad Kalla]

Darren,
Unfotunately not, but I was able to reproduce this strange behavior very quickly with your steps… I’ll file it as a bug ASAP.

[tenjin]

Hi,

This problem continues I’m afraid, although I think I have tracked down the cause.

Firstly, the reason I thought it had been fixed was because if I manually run Resin outside of MyEclipse and then view the web app from within the embedded browser it all works fine. Until that is I change one of the pages, and then the compilation of that page fails.

I was confused about where Resin was running.

Earlier on in this thread I mentioned a fix that I had found on this site for the “logging” error when using Resin 2.1.x

The fix for that was to add this string:

-Xbootclasspath/p:d:\resin\lib\dom.jar;d:\resin\lib\jaxp.jar;d:\resin\lib\jmx.jar;d:\resin\lib\jsdk23.jar;d:\resin\lib\jta_101.jar;d:\resin\lib\resin.jar;d:\resin\lib\sax.jar;d:\resin\lib\webutil.jar

– to the “Optional Java VM Arguments” section of the JDK setup in the Resin preferences section of Eclipse.

This arguments list is breaking the compilation of new pages. I have removed it and although the logging error is back Eclipse is now able to compile the pages.

Any ideas how I can change the arguments list so that the logging error goes away but the complilation works?

Regards

Darren.

[Riyad Kalla]

Darren,
The compilation is happening outside of MyEclipse on Resin, so if the compilation is failing, what is the error being given? If it’s complaining about a lack of a compiler or missing “tools.jar”, you may just need to make sure to find tools.jar in your JDK install and add it to the bootclasspath as well.

[tenjin]

Hi,

Thanks for the post.

Adding d:\Java\lib\tools.jar to the “optional Java VM arguments” section in the MyEclipse preferences seems to have done the trick. The logging error is gone, and the pages still compile.

I did try this once before, but that was when Java was installed in “d:\Program Files\Java” and then of course the space-in-the-path issue was a problem.

Anyway, it really does look fixed now.

Thanks for your help

Regards

Darren.

[Riyad Kalla]

Darren,
That’s great news, I’m glad it’s working now.

[Author]

Posts