[James I. Falek]

@support-rkalla wrote:

Hrrm it looks like you are running out of environment space when it tried to execute too long of a command to compile the page… a real test would be to install Eclipse to C:\Eclipse, and put your workspace in C:\Eclipse\workspace and then try it…. but I realie this could be a huge PIA.

Can you try removing extraneous libraries from your classpath? Maybe that library set if you don’t need it, and instead add the jsp-api.jar and servlet-api.jar files from your Tomcat install?

This is a known problem with Windows in general, sometimes when you install Tomcat to C:\Program Files\Apache Group\Tomcat 5.0 which is its default, it can’t start up either because it tries to build its classpath via FQ path names for the JARs and the command just gets too long for the windows shell to execute…

I don’t know if it makes a difference, but we are using WebLogic 8, not TomCat 5. I’ve never tried deleting the library set before – this may take another night of sleep before I try. If you have any other ideas…?!

Thanks,
James

[Scott Anderson]

James,

Caused by: java.io.IOException: CreateProcess: javac.exe -classpath
C:\IbiIDE\eclipse\startup.jar;C:\ibiIDE\workspace\utilities\lib\jakarta-oro-2.0.8.jar;C:\j2sdk1.4.2_03\jre\lib\rt.jar;C:\j2sdk1.4.2_03\jre\lib\sunrsasign.jar;C:\j2sdk1.4.2_03\jre\lib\jsse.jar;C:\j2sdk1.4.2_03\jre\lib\jce.jar;C:\j2sdk1.4.2_03\jre\lib\charsets.jar;C:\j2sdk1.4.2_03\jre\lib\ext\Coroutine4Java.jar;C:\j2sdk1.4.2_03\jre\lib\ext\dnsns.jar;C:\j2sdk1.4.2_03\jre\lib\ext\ldapsec.jar;C:\j2sdk1.4.2_03\jre\lib\ext\localedata.jar;C:\j2sdk1.4.2_03\jre\lib\ext\sunjce_provider.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\jstl.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\standard.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\struts-el.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-beanutils.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\struts.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-collections.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-digester.jar;C:\ibiIDE\workspace\workbench\WebRoot\WE?

What you’re experiencing is known problem that is exacerbated by lack of
a proper error message. The key to this issue is what you see above.
The reason you can’t create the process is likely that javac.exe literally
can’t be found. Naturally, in order to validate your JSP’s MyEclipse needs
to parse then compile them. However, if you’re running Eclipse with a JRE,
instead of a JDK, there won’t be a java compiler available on the path.
From your particular error, it appears that you have a full JDK installed,
but it looks like Eclipse is being launched with the javaw.exe that is in the
<jdk>/jre/bin directory. I believe the easiest fix to this is to ensure that
the <jdk>/bin directory is on your system’s path, then relaunching Eclipse.
In addition, to be sure you’re using the version of the JDK really want,
I’d suggest launching with commandline arguments that point to the jdk
like: <path-to-eclipse>\eclipse.exe -vm <path-to-jdk>\bin\javaw.exe

Please let us know if that resolves the issue.

[James I. Falek]

Scott,

All that makes sense so maybe I am doing something fundamentally wrong. Here is what I wrote in a earlier post in this thread – am I using the wrong j2sdk?

I downloaded the latest sdk and started Eclipse with the command line :

C:\ibiIDE\eclipse\eclipse.exe -vm C:\j2sdk1.4.2_05\bin\javaw.exe -clean -vmargs -Xms256m -Xmx256m

but I still have the following error:

Severity    Description    Resource    In Folder    Location    Creation Time
1    IWAE0010E Run-time exception java.lang.ExceptionInInitializerError occurred during validation. The validator being run was JSP Validator and the message thrown was .    webProject            September 2, 2004 8:22:51 AM

Thanks,

James

[Riyad Kalla]

James,
Can you edit your environment variable “PATH” and make sure to add: “C:\j2sdk1.4.2_05\bin” to it and see if that fixes the problem?

I misunderstood earlier that javac.exe HAS to be in your path, before I thought specifying -vm was enough.

[James I. Falek]

@support-rkalla wrote:

James,
Can you edit your environment variable “PATH” and make sure to add: “C:\j2sdk1.4.2_05\bin” to it and see if that fixes the problem?

I misunderstood earlier that javac.exe HAS to be in your path, before I thought specifying -vm was enough.

The directory is the first one in the build path and even using the -vm argument I still have the exception. Any other suggestion?

Thanks,
James

[Scott Anderson]

The directory is the first one in the build path

Just to be clear, you don’t mean the build path in Eclipse, right? Riyad is specifically referring to the
Windows environment PATH, as seen when you execute “echo %PATH%” from the command line. When
you do this, what does your path look like?

[James I. Falek]

@support-scott wrote:

The directory is the first one in the build path

Just to be clear, you don’t mean the build path in Eclipse, right? Riyad is specifically referring to the
Windows environment PATH, as seen when you execute “echo %PATH%” from the command line. When
you do this, what does your path look like?

Sorry – poor use of words on my part. Yes, the bin directory is the first item in the windows environment path.

[Scott Anderson]

OK. I just reread this entire thread and have a few more thoughts.

First, I should note that we should all ignore error messages from the JSP compiler in the log, *unless* validation is not working properly.
The Jasper compiler throws an exception and stops execution (currently with a log entry) whenever it finds an error in a JSP
page. This isn’t a sign of a problem in the validation or configuration. In 3.8.2 we’ll remove the log entry due to the confusion
it causes.

Second, I’d like to suggest that we try a parallel “do over” on this installation, with a fresh workspace. I want to see if we
can get a simple basic configuration working so we can separate any workspace migration issues from any configuration
issues. Additionally, the installers that are on the server currently already have all quickfixes applied so we won’t need
to be concerned with problems installing them. So, toward this end, James could you please bear
with us and install *in parallel to your current installations* a new
Eclipse 3.0 release and download a fresh copy of MyEclipse from the website. Install the MyEclipse release on the
new Eclipse release, create a new web project with a default JSP page. Verify that JSP validation is enabled and then introduce
some errors into the JSP. Are they marked on the JSP and reported in the Problems View? Please remeber that you’ll
have to set the filters on the Problems View to show MyEclipse errors. Please let us know how this works
and we’ll know how to proceed form there.

[Scott Anderson]

Internally, we’re trying to reproduce this issue so we can provide a more meaningful error message and diagnostic.
Here’s what we tried:
1) Opened a command shell and set the PATH to be *only* c:\windows\system32;c:\windows;c:\windows\system32\wbem
2) Changed to Eclipse directory with MyEclipse installed and ran eclipse.exe.
3) Somewhat surprisingly, JSP compilation / validation worked fine, even without the JDK on the path

From the command prompt, java -version yielded:
java version “1.4.2_05”
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)

This is the java.exe installed by the Sun JDK installer into c:\windows\system32

So, it appears that for compilation to work properly the PATH may have been a “red herring”
since even this simplest of setups behaves properly. However, that then causes the
deeper question of “so what’s really happening in your configuration”. As a result,
I’d still like to recommend the clean parallel test outlined in my last post to isolate the issue.

[James I. Falek]

I did a complete new install of Eclipse and MyEclipse and things “look” ok. It will take me a few more hours (5?) to copy the files over and make sure that the hooks to cvs align up (I didn’t do it exactly right when I did my first try and therefore have to start over – sigh). But there were no errors.

I did try turning off JSP validation for the project and that, of course, made the error disappear. It would be alot easier to not re-build (copy each of the files, make sure that the 200-odd junit’s run, testing the build, etc) the app, so can you tell me the implications of turning JSP validation off before I embark on this jouney?

I also re-installed 3.81 a few times, but that did nothing. Is it possible to uninstall it and then to install it? Would any of the changes that y’all are making for 3.82 possibly fix it?

Thanks,
James

[Scott Anderson]

James,

It will take me a few more hours (5?) to copy the files over and make sure that the hooks to cvs align up

Rather than doing that, how about making a complete copy of your old workspace and then pointing the new install to the copy.
That should be an easy way to test that minimizes manual setup.

can you tell me the implications of turning JSP validation off

Bascially, JSP’s won’t be compiled when saved or when the workspace build runs. However, you can validate them one at a time
by right-clicking on the file in the Package Explorer and selecting Validate JSP.

Is it possible to uninstall it and then to install it?

If you used the double-click installer you can run the uninstaller.
Otherwise, you can follow the manual reinstall steps here:
http://myeclipseide.com/FAQ+index-myfaq-yes-id_cat-4-parent_id-0.html#156

[James I. Falek]

@support-scott wrote:

James,

It will take me a few more hours (5?) to copy the files over and make sure that the hooks to cvs align up

Rather than doing that, how about making a complete copy of your old workspace and then pointing the new install to the copy.
That should be an easy way to test that minimizes manual setup.

can you tell me the implications of turning JSP validation off

Bascially, JSP’s won’t be compiled when saved or when the workspace build runs. However, you can validate them one at a time
by right-clicking on the file in the Package Explorer and selecting Validate JSP.

Is it possible to uninstall it and then to install it?

If you used the double-click installer you can run the uninstaller.
Otherwise, you can follow the manual reinstall steps here:
http://myeclipseide.com/FAQ+index-myfaq-yes-id_cat-4-parent_id-0.html#156

I performed the uninstall/reinstall as per the url. So, I deleted my directories, reinstalled eclipse (bringing it up first to let it finish the install), reinstalled myeclipse, brought it up, imported all of the projects. When I brought in my web project, I still go the same error. Argg.

I do notice that on my three non-web projects that in the list of builders is one with a red circle containing the letter “X” called “Invalid External Tool Builder”. Looking at the log file (which is attached), I noticed something called “net.sourceforge.metrics.builder”. Maybe that is something left over from the previous world (Eclipse 2.x). Could this be the problem? Any suggestions on how to remove this?

Thanks,
James

Here is the eclipse log file:

!SESSION Sep 09, 2004 09:01:38.821 ---------------------------------------------
eclipse.buildId=I200406251208
java.version=1.4.2
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

!ENTRY com.genuitec.eclipse.wizards 1 1 Sep 09, 2004 09:01:38.821
!MESSAGE Installed snippet library: C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wizards_3.8.1\snippets\css_snippets.xml

!ENTRY com.genuitec.eclipse.wizards 1 1 Sep 09, 2004 09:01:38.931
!MESSAGE Installed snippet library: C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wizards_3.8.1\snippets\forms_lists_snippets.xml

!ENTRY com.genuitec.eclipse.wizards 1 1 Sep 09, 2004 09:01:38.961
!MESSAGE Installed snippet library: C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wizards_3.8.1\snippets\htmlform_snippets.xml

!ENTRY com.genuitec.eclipse.wizards 1 1 Sep 09, 2004 09:01:39.01
!MESSAGE Installed snippet library: C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wizards_3.8.1\snippets\html_snippets.xml

!ENTRY com.genuitec.eclipse.wizards 1 1 Sep 09, 2004 09:01:39.41
!MESSAGE Installed snippet library: C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wizards_3.8.1\snippets\javascript_snippets.xml

!ENTRY com.genuitec.eclipse.wizards 1 1 Sep 09, 2004 09:01:39.81
!MESSAGE Installed snippet library: C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wizards_3.8.1\snippets\jsf_f_snippets.xml

!ENTRY com.genuitec.eclipse.wizards 1 1 Sep 09, 2004 09:01:39.141
!MESSAGE Installed snippet library: C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wizards_3.8.1\snippets\jsf_h_snippets.xml

!ENTRY com.genuitec.eclipse.wizards 1 1 Sep 09, 2004 09:01:39.182
!MESSAGE Installed snippet library: C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wizards_3.8.1\snippets\struts_bean_snippets.xml

!ENTRY com.genuitec.eclipse.wizards 1 1 Sep 09, 2004 09:01:39.242
!MESSAGE Installed snippet library: C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wizards_3.8.1\snippets\struts_html_snippets.xml

!ENTRY com.genuitec.eclipse.wizards 1 1 Sep 09, 2004 09:01:39.302
!MESSAGE Installed snippet library: C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wizards_3.8.1\snippets\struts_logic_snippets.xml

!ENTRY com.genuitec.eclipse.wizards 1 1 Sep 09, 2004 09:01:39.362
!MESSAGE Installed snippet library: C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wizards_3.8.1\snippets\struts_tiles_snippets.xml
!SESSION Sep 09, 2004 09:06:50.780 ---------------------------------------------
eclipse.buildId=I200406251208
java.version=1.4.2
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

!ENTRY org.eclipse.core.resources 2 1 Sep 09, 2004 09:06:50.780
!MESSAGE Skipping builder net.sourceforge.metrics.builder for project model. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.
!SESSION Sep 09, 2004 09:13:10.746 ---------------------------------------------
eclipse.buildId=I200406251208
java.version=1.4.2
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

!ENTRY org.eclipse.core.resources 2 1 Sep 09, 2004 09:13:10.746
!MESSAGE Skipping builder net.sourceforge.metrics.builder for project model. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.

!ENTRY org.eclipse.ui 4 4 Sep 09, 2004 09:17:49.917
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 Sep 09, 2004 09:17:49.927
!MESSAGE java.lang.OutOfMemoryError
!STACK 0
java.lang.OutOfMemoryError

!ENTRY org.eclipse.core.runtime 4 2 Sep 09, 2004 09:17:49.937
!MESSAGE An internal error occurred during: "Building workspace".
!STACK 0
java.lang.OutOfMemoryError
!SESSION Sep 09, 2004 09:18:29.294 ---------------------------------------------
eclipse.buildId=I200406251208
java.version=1.4.2
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

!ENTRY org.eclipse.core.resources 2 1 Sep 09, 2004 09:18:29.294
!MESSAGE Skipping builder net.sourceforge.metrics.builder for project model. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.

!ENTRY com.ibm.etools.validation 4 0 Sep 09, 2004 09:18:53.649
!MESSAGE 
*** ERROR ***: Thu Sep 09 09:18:53 EDT 2004    java.lang.ExceptionInInitializerError

[Scott Anderson]

James,

!MESSAGE An internal error occurred during: “Building workspace”.
!STACK 0
java.lang.OutOfMemoryError

It looks like you’re running out of memory when building the workspace and this will cause all sort of issues.
You can adjust the memory settings you use to start Eclipse with -vm -Xmx128M -Xmx256M
Hopefully, this will correct the issue, but there is a known bug in JSP validation that uses an inordinate
amount of memory. We’ve corrected the problem internally and it will be part of 3.8.2. However the
best workaround right now is to simply turn off automatic JSP validation at Window > Preferences > MyEclipse > Validation.

Once the memory problem is resolved / worked around I believe you regain proper functionality as all the other
messages after this one could simply be symptomatic of running out of memory.

As for the old builder, yes, it’s likely left over from your old work. You should be able to remove it
by right-clicking on the project in the Package Explorer and selecting Properties > Builders

[James I. Falek]

@support-scott wrote:

James,

!MESSAGE An internal error occurred during: “Building workspace”.
!STACK 0
java.lang.OutOfMemoryError

It looks like you’re running out of memory when building the workspace and this will cause all sort of issues.
You can adjust the memory settings you use to start Eclipse with -vm -Xmx128M -Xmx256M
Hopefully, this will correct the issue, but there is a known bug in JSP validation that uses an inordinate
amount of memory. We’ve corrected the problem internally and it will be part of 3.8.2. However the
best workaround right now is to simply turn off automatic JSP validation at Window > Preferences > MyEclipse > Validation.

I am currently using the following to start up Eclipse, so I am not sure that the memory issue applies:

C:\ibiIDE\eclipse\eclipse.exe  -vm C:\ibiIDE\j2sdk1.4.2_05\bin\javaw.exe  -vmargs -Xms256m -Xmx1024m

Are you recommending that we just wait for 3.8.2 and see if that resolves the issue?

Once the memory problem is resolved / worked around I believe you regain proper functionality as all the other
messages after this one could simply be symptomatic of running out of memory.

As for the old builder, yes, it’s likely left over from your old work. You should be able to remove it
by right-clicking on the project in the Package Explorer and selecting Properties > Builders

Thanks for the easy directions! When I go to builders, there is one labeled “Missing Builder (net.sourceforge.metrics.builder), but when I select it, the “Remove” button is not selectable. However, I am able to uncheck it. It sounds like this is not a MyEclipse issue, but if you have any suggestions about how to delete it completely, it would be appreciated!

Thanks again,
James

[Riyad Kalla]

James,
You can remove any builder manually by editing the .project file and removing the appropriate builder entry section.

[Author]

Posts