[pshetty620]

Hi,

I am using myeclipse 5.0GA,
I used to get as error popup saying “An Internal error occured during: ‘Myeclipse Memory Monitor'”.
This is happening most of the time as below.
1.Building workspace
2.Switching workspace
3.deploying project.
4.cleaning project… so on.

Even I have changed common parameter as below. Even then it persists.
-Xms256M -Xmx1024M

Perviously I have used 4.1GA. It was working fine.

My system conf : windows 2000 professsional. 1GB RAM.

Could you please help me in rectifying this.

Thanks in advance.

-Prakash Shetty

[Riyad Kalla]

Prakash,
Can you go to your MyEclipse menu, then Installation Summary > Installation Details and post the text here for me?

[pshetty620]

Hi Riyad,

Thanks for reply.

Here is the details

*** Date: Wed Nov 08 14:21:14 GMT+05:30 2006

*** System properties:
OS=Windows2000
OS version=5.0
Java version=1.5.0_04

*** MyEclipse details:
MyEclipse Enterprise Workbench

Version: 5.0 GA
Build id: 20060805-5.0-GA

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 5.0.1 GA
Build id: 20060810-5.0.1-GA

Eclipse Graphical Editing Framework

Version: 3.2.0.v20060626
Build id: 20060627-0816

Eclipse Platform

Version: 3.2.0.v20060609m-AgOexn6hlEUsvBO
Build id: M20060629-1905

Eclipse RCP

Version: 3.2.0.v20060609m-SVDNgVrNoh-MeGG
Build id: M20060629-1905

Eclipse Java Development Tools

Version: 3.2.0.v20060609m-F7snq1fxia-Z4XP
Build id: M20060629-1905

Eclipse Plug-in Development Environment

Version: 3.2.0.v20060609m——6zXJJzJzJq
Build id: M20060629-1905

Eclipse Project SDK

Version: 3.2.0.v20060609m-GNq6oQq-7es-Y81
Build id: M20060629-1905

Eclipse startup command=-data
C:\CARA\Source_mockup
-os
win32
-ws
win32
-arch
x86
-launcher
C:\Eclipse3.2\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
1e4_78
-product
com.genuitec.myeclipse.product.ide
-vm
C:\bea_WL_9.1\jrockit90_150_04\jre\bin\javaw.exe

– Prakash Shetty

[Scott Anderson]

Prakash,

The memory monitor requires JDK 1.5, which you have, but you’ve got a rather early version (1.5.0_04). Could you try upgrading your JDK to the latest 1.5 version? Some of the earlier releases had bugs in the memory management area that could be causing the issue. The issue might also be some sort of incompatibility with the JRocket VM, that you’re using, versus the ones from Sun. Could you try the latest Sun VM and see if that resolves the issue?

[pshetty620]

@support-scott wrote:

Prakash,

The memory monitor requires JDK 1.5, which you have, but you’ve got a rather early version (1.5.0_04). Could you try upgrading your JDK to the latest 1.5 version? Some of the earlier releases had bugs in the memory management area that could be causing the issue. The issue might also be some sort of incompatibility with the JRocket VM, that you’re using, versus the ones from Sun. Could you try the latest Sun VM and see if that resolves the issue?

Hi Scott,

It worked. I have used JDK 1.5.0_09 from sun. It is working. And I have waited for one month for any chance of getting error. I didn’t get any error. So everything is working fine now.

This thread can be closed.
Thanks very much

Regard,.
Prakash Shetty

[Riyad Kalla]

Prakash,
Thank you for following up, we are glad to hear it’s working.

[Author]

Posts