I found this question on how to automatically start nView at Windows boot, but unfortunately, the answers there are not very helpful as there is no exe file to start the manager, but it did get me to find the following information.
I just had this problem with my laptop and I found out that it was nview desktop manager. I had turned it on experimenting with different settings. As soon as I disabled the nview, the problem went away within eclipse juno.
Had the same problem for a couple of weeks now after my Eclipse and Java update on my Win7 desktop machine. I realized that I had exactly the same problem in other Java-based applications as well so I was pretty sure it was the Java update. Tried following:
The new features in Borland Enterprise Server 5.2 focus on improving developer productivity and application performance Enhanced integration with Borland JBuilder 8 accelerates development and deployment cycles Support for the new Java Development Kit 1.4.1 improves Java application scalability and performance Support for IPv6 specification enables deployment on next- generation TCP/IP networks Native messaging support eases integration with non-CORBA applications Enhanced access and reporting of process utilization assists developers and IT managers in optimizing application performance