I have been having an issue with eclipse oxygen, as I am trying to develop JAVA EE program, it appears that the console is always blank and not responding.
I am using server GlassFish 4.1.0 to connect.
Console view is always blank, I have tried to change multiple output displays but without any changes happened.
I have tried several solutions to try to get this fixed:
re-installing GlassFish again
New eclipse updates
Changing console mode
nothing changes
Looking forward for help
(Note: Using MacOS)
make sure you're looking at the correct console, change console
view log server
I am experimenting with a combination of Vagrant+VirtualBox+JRebel+Eclipse+Tomcat to develop a Java Servlet application. My Tomcat instance runs in a VirtualBox VM, which for Eclipse purposes means it is a remote server. I was able to get hot deploying (JRebel) and debug mode working.
I haven't yet found a good way to get the logs to show up in Eclipse, though. Ideally, I'd like something very similar to the Console view that Eclipse/WTP gives for local Tomcat instances. Some features I like:
Lines in stack traces are clickable, taking me right to the source file
Easily searchable
Highlighting (errors show up in red)
Shows up right in my IDE
Can be cleared when I'm sick of seeing too much
The first two features (clickable and searchable) are the most important to me. Does anyone know of a plugin or separate app that can accomplish this?
LogViewer appears to be abandoned (and possibly non-functional in current Eclipse versions), and JLV doesn't appear to have clickable source lines.
NTail might do the job. It hasn't been updated since 2010, but it seems to work on Eclipse Luna.
Sometimes when I try to Run or Debug program several times in a row without changes Ecipse does nothing but outputs current Java version in console. Sometimes it works OK and I didn't find any correlation between my actions and its behavior. Any insignificant change in text helps, so this error is not serious but rather irritating. But anyway, do you have any idea why it happens?
Eclipse Kepler. Problem stays both for Java programs and C++ ones (via CDT).
I'm using Eclipse Juno to debug a java class while testing with junit, but the debugger has been acting flakey. I will reach the breakpoint I want and all seems well with the variable values, but in my console, all of the print statements I set up later in the code are popping out as if I were stepping through it!
(note: they aren't printing as fast as they normally would if I had simply run it, and the output itself is a bit garbled compared to normal output).
Somehow, the code is executing through without me pressing a button. If I try to step through, my view of the code and variables is correct, but debugging stops once Eclipse thinks the program has finished.
Something I should probably mention is that I recently put Fedora on my laptop, so I haven't been running eclipse on it for very long and this is my first time trying junit. Is is possible that I need to download something for my debugger?
I'm new to Java (come from C++/.NET background) and am experiencing very strange error. I am developing w/ Eclipse IDE on Windows XP on my local desktop. It seems that for some reason, an older (and of course buggier) instance of my application stays running for some very odd reason which I cannot understand.
Even when I close eclipse, this old version of my application is running in the background. So unless I reboot, when I try to test new version of the code, this 'old, rogue instance' is fighting for the resources that are used (files on a share) with the newer (hopfully less buggy) version of the code.
Has anyone experienced this? Does the JVM cache old versions of your Java application for some reason? What am I missing here? When I reboot my machine, the instance finally dies...
I was ripping my hair out trying to figure out why the new version of my code still had the same old bug until I realized this was happening... shrug
Thanks for any help!
Do you by chance either run your program multiple times, or have forgotten to close one instance of it prior to re-running it from Eclipse?
One thing, that is not very obvious when using Eclipse, is that it allows to run any number of instances of Java programs simultaneously. When you have the Console view active, you have the option to terminate the latest launch.
To switch the console to a different launch (if there are multiple running) you can select from a list, by pressing the "Display Selected Console" icon, which is the monitor icon to the top-right in the Console view.
You can also remove any and all terminated launch console outputs from the Console view, by pressing "Remove All Terminated Launches", if every launch have been terminated it should now display "No consoles to display at this time", otherwise the next-newest running launch will be brought to the top.
If this isn't the problem, and indeed Eclipse have lost track of a launch (which is quite rare, but can happen - especially if you spawn sub processes yourself), you can safely terminate any run-amock java.exe process from the Task Manager, as Eclipse runs wrapped in a Windows executable on the Windows platform.
Java applications run under "java.exe", so you can look for that in the task list. Sadly, if several Java applications are running at the same time, it's hard to tell which is which.
I'm not terribly familiar with Eclipse, but it seems like Eclipse should tell your old version to terminate when you close Eclipse. The JVM doesn't cache past versions.
Hope this helps.
I had a problem like this as well. I would try to run the program after making changes, and it would run the older version of it, and still report errors and stop on lines that I had even commented out. I tried micdah's solution, but there were no java.exe processes in Task Manager. I solved the problem by killing the Eclipse process from the Task Manager, which closed the program without saving Eclipse Workspace settings. When I relaunched, everything I had saved in the .java files launched normally.
Could be a bug in Eclipse. Could be some code in your application that's spawning a new process. Impossible to tell from over here.
If you haven't already, check out the jps tool, which is included with the regular JDK. It might make it easier to diagnose the problem.