[gang.yang]

Hi,

I downloaded MyEclipse 2014 (full version), but could not even start it. I got “An internal error occurred during: “Updating indexes”. Java heap space” error. I increased the memory settings in the myeclipse.ini to the following and still fails:

-vmargs
-Xms256m
-Xmx1536m
-XX:PermSize=128m
-XX:MaxPermSize=512m
-XX:ReservedCodeCacheSize=256m

What’s going on? I did not a GA product to behave like this.

Thanks,
Gang

[support-pradeep]

Gang,

Sorry that you are seeing this issue.

Can you try deleting the maven cache folder from Maven repository directory (default ~/.m2/repository/.cache) and check if you can start MyEclipse without any issues ?

If you are still facing issues, can you please answer some more queries to help us investigate further :
1) Can you please clarify which MyEclipse edition (MyEclipse Professional, MyEclipse Spring, MyEclipse Blue, MyEclipse Bling) did you download and install ?
2) Can you please attach the .log file located at <workspace dir>/.metadata/.log ? Also attach the screenshot of the error to help us get a visual of the issue.
3) Clear the .log file (<workspace dir>/.metadata/.log), replicate the issue and attach the .log file to help us investigate further
4) Also, can you please send us the Java dump file in the temp directory to help us investigate further ?
5) Can you please share your OS name and version details ? Also let us know which bit version (32 or 64 bit) of MyEclipse did you install ?

[gang.yang]

Thanks for the reply.

I could not find any .cache file under Maven’s repository directory. I installed the MyEclipse 2014 Professional in Windows 2008 R2 VMware on a 64-bit machine (Host system is Windows 7). Attached is the .log file you requested. I could not find any Java dump file.

I re-installed it again and did select 64-bit during the installation. The problem persisted.

One more detail: I’m using an external Maven installation, which is 3.0.5. I got the same error before and after I configured MyEclipse 2014 to use the external Maven.

My current MyEclipse 10 does not have the problem.

I downloaded MyEclipse 2015 CI and installed it. It did not have the problem.

Thanks,
Gang

[support-pradeep]

Gang,

I downloaded MyEclipse 2015 CI and installed it. It did not have the problem.

As the problem doesn’t exhibit in MyEclipse 2015, do you still want us to investigate the problem in MyEclipse 2014 ? If yes, can you please provide the information that was asked in my earlier reply. (The .log files attachments are missing in your reply)

Can you please clarify whether this is a sporadic error ? If yes, you could try turning off automatic updating of indexes (Window -> Preferences -> MyEclipse -> Maven4MyEclipse and uncheck ‘Download repository index updates on startup’) and see if it resolves the issue.

[gang.yang]

I would think it’s Genuitech’s best interest to get this problem understood and resolved. It happens consistently even after I uninstalled and reinstalled MyEclipse 2014. It’s a GA product.

I thought I copy pasted the .log’s content to the post. But obviously it was missing. I’m attaching it here.

Thanks,
Gang

Attachments:

You must be logged in to view attached files.

[support-tony]

Gang,

You’re right that it would be best for us to solve your particular issue on the 2014 release.

However, that task is difficult when we can’t replicate the issue. This might be because there is something specific to your set-up and installation, and we can’t always replicate every user’s environment. In your case, you have installed MyEclipse Professional 2014 (64 bit) on Windows 2008 R2 in a virtual machine provided by VMWare, under Windows 7. There may be networking issues from the virtual machine that we don’t know about but, in any case, it’s not an environment that we can easily replicate, if at all. I have tried 2014 on Windows 8 running in a virtual machine (not VMWare) and don’t see the issue.

Your issue is not one that I recall seeing reported before, so we can be confident that the error is rare. In any case, our primary concern is to get the user running again. Consequently, workarounds are often tried which achieve that aim, even if the original problem can’t be determined. In this case, the suggestion of using 2015 CI was aimed at that, since there have been numerous fixes and the underlying eclipse version has changed. Fortunately, that did fix the problem for you.

Our other suggestion, which you didn’t mention that you’d tried, was to turn off the updating of maven indexes at start up. The other workaround, mentioned by Pradeep, was to delete the maven repository cache, but, as you didn’t have a .cache folder, at the time, this didn’t apply to you, though other eclipse users have been advised to try this (on external sites).

You say that the problem is consistent but you also mentioned that you changed the maven runtime configuration in MyEclipse, which is done via the preferences. This would indicate that you can start MyEclipse and use it, to some degree, at least in some sessions. Could you clarify this? If you can use it enough to alter the preferences, then it might be useful to alter the preference to not update indexes at start up, as mentioned earlier. Open Preferences and then go to MyEclipse->Maven4Myeclipse, disable the “Download repository index updates on startup” and click OK.

As far as fixing the original problem, it’s difficult to know how we can replicate the issue in order to fix it. Can you install 2014 on your host system, rather than a virtual machine to see if the problem only occurs with your virtual machine set up?

Please let us know if this helps and sorry for the inconvenience you’ve had.

[gang.yang]

Tony,

Thanks for the reply. I understand it is difficult to debug a rarely-occurring problem, especially only happens in a customer’s environment. Having said that, I have to point out that both MyEclipse 10 and MyEclipse 2015 CI runs fine in my same environment. That would indicate that MyEclipse 2014 definitely has a problem. I would have to say that using VMware has become very common because it’s easy to duplicate and standardize. I would’ve thought that MyEclipse has been tested with VMware.

The problem is persistent because it run into this problem every time I start it. However, I do have a small window where MyEclipse is operative because the update index is running in the background. During this window, I can and have tried to disable the index update and it prevented the error. So this tells that the problem is isolated in the index updating are and it’s memory issue. I don’t know how difficult to discover the problem just by looking at the code.

Gang

[support-tony]

Gang,

Thanks for the reply. Yes, it does seem to be connected to the update indexes job. As I say, I’ve tried to replicate in a virtual machine (VirtualBox), but the update indexes runs to completion, without error. I don’t have a Windows 2008 license but will try to set up a VMWare machine with a Windows system, to check if the problem is only associated with VMWare and 2014.

Yes, virtual systems are becoming more common but yours is the first report we’ve had of this issue. I don’t know if others are running MyEclipse in a Windows virtual machine, under VMWare, but, if they are, then there must be some other variable which causes the issue.

[support-tony]

Gang,

I just tried a VMWare player, first with Windows XP and then with Windows 7 but couldn’t replicate the issue. I don’t have access to a Windows 2008 R2 system, so I can’t try that.

[Author]

Posts