I am currently encountering the following issue:
I am using a Glassfish 3.1 Server to deploy my applications on and am frequently restarting him from within Eclipse to have a clean Glassfish (he sometimes keeps some old classfiles and I just want to make sure...)
That should be working fine, but every ~5 times restarting the server it wont start up again. The log output looks like this:
INFO: Server shutdown initiated
INFO: JMX002: JMXStartupService: Stopped JMXConnectorServer: null
INFO: JMX001: JMXStartupService and JMXConnectors have been shut down.
INFO: Shutdown procedure finished
After this no more lines are printed out. I already tried to wait for some time but it wont start again from itself.
Meanwhile Eclipse is constantly showing "Restarting Glassfish 3.1 at localhost" in the Prograss View. If i click the stop button it only turns gray but wont vanish. Also telling the server to start up again is not working as it waits for the "restarting" to finish and well... that isnt happening.
To still be able to work I have to restart Eclipse every time the Glassfish server wont stop...
I can work with it, but am interested if anyone has experienced similar behavior and maybe even has a solution :)
Edit 1
Forgot to include that I am using Eclipse Keppler.
Make sure you've installed the latest version of the Glassfish Tools from Oracle.
http://www.oracle.com/technetwork/developer-tools/eclipse/downloads/index.html
My eclipse base version is:
Version: Luna Service Release 2 (4.4.2)
I had this problem also.
Removing, then re-adding the Glassfish server instance did the trick for me. Nothing else required.
Related
I have Developer Studio set up with an instance of JBoss EAP 6.4.0.GA. I added it using the 6.1+ server type:
When I start and stop the server - either in debug mode or not - things seem to work fine. When the server is running and I try to restart it by clicking on the debug button or the play button for non-debug mode, Developer Studio restarts the server (I can see this happening in the logs) but loses track of the server and gives me an error saying:
After this, the server is running but Dev Studio doesn't know so if I try to start the server, I get this dialog:
If I then connect, the UI doesn't seem to update so I can't shut down the server:
This never happens when starting the server from scratch. It's only restarts. I was having this issue with JBoss Developer Studio (Eclipse) with 10.1.0 GA and am now also having the issue with 10.2.0 GA. Is there anything I can tweak to fix this?? Is there a startup or restart timeout that needs to be changed?
This was fixed recently :D It was a long-standing bug and had a race-condition in it.
https://issues.jboss.org/browse/JBIDE-20426
I am working on my own, learning about Java servlets and JSPs. My machine configuration as follows is from NetBeans' About page.
Product Version: NetBeans IDE 8.0.1 (Build 201408251540)
Updates: NetBeans IDE is updated to version NetBeans 8.0.1 Patch 1.1
Java: 1.8.0_20; Java HotSpot(TM) 64-Bit Server VM 25.20-b23
Runtime: Java(TM) SE Runtime Environment 1.8.0_20-b26
System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
Tomcat 8.0.14 for Windows x64 is also installed as the web server.
I created a tiny web app yesterday, which was working as expected. When I went to the next exercise in the book, it was necessary to install MySQL. That seemed pretty straightforward, but alas, the install ran into a couple of problems. Unfortunately, I had not created a restore point right before that attempt, so I went back to the restore point created before the Tomcat install.
I re-installed Tomcat, and as a sanity check, started it, started NetBeans, tried to the run the tiny web app and after removing the server and re-adding it (because I got an error about the server) in NetBeans, got a message that I needed to set the build.dir.
For a tiny app, this is just annoying, but when working on a large app, it would be nice to avoid this problem. Another book author supplied app was working before, and is still working so...
Here are my questions:
1) Why/how would simply re-installing Tomcat cause a break in something that was working?
2) It seems as if the build.dir is set in build-impl.dir (in the app that is working) with a statement like (the opening and closing tags are missing so the statements would appear):
property location="${build.dir}/empty" name="empty.dir"
One post I read somewhere said that the above statement should be before the:
fail unless="build.dir">Must set build.dir
3) How/where is this build.dir set during the creation of a NetBeans web app? Is there some dialog box that I'm not completing correctly? If I miss it, is there a way to get back to it after the app gets "confused"?
Thanks in advance for any help on this.
I have been facing the "Unable to validate Weblogic domain" issue from OEPE for last 2 days. I have tried
(a) downloading and installing different versions of OEPE ;
(b) Using Eclipse and Oracle Weblogic separately ; outside of OEPE etc
It used to work previously and then one day last week, my system shut down unexpectedly and since then I am not able to get Eclipse (irrespective of version) and Weblogic to work together.
I have moved on to using Jboss for the time being. But since my production environment is Weblogic and I would like to use Weblogic for development purposes as well, I am trying to get this issue resolved.
I did search the Oracle and other communities and somebody mentioned its because of difference in java version and to add
-Dsun.lang.ClassLoader.allowArraySyntax=true
in eclipse.ini. My eclipse.ini already has this statement and I still face the issue.Please help.
Iam not the person who answers this question. But the comment above is the answer for this question and it worked for me too. Below is the solution.
I finally got the resolution for this issue. Actually the full credit goes to my colleague, who resolved this bugging bug. Since it drove me crazy, decided that I would spare others from the same experience First of all, there were no errors in any of the logs. Server was starting up but Eclipse did not recognize it as such. And here is the resolution : Go to Window Tab -> Preferences -> General -> Network Connections Change the Active provider to "Direct". The default is usually Native. and that's it. Close and restart eclipse.
It happened to me as well, I even reinstalled weblogic again, after a bit of research I decided to kill the Java(TM) Platform SE Binary process via Task Manager and restarted the Server.
That's all It took to resolve the issue.
I've been trying to update my netbeans plugins ever since 7.0.1, but I've never been able to get beyond half of the installation bar. It just freezes at around 50% each time. After I close the IDE, it will attempt to update but fail. I've updated to 7.1 but the issue still persists even for the initial Junit plugin installation after a fresh installation of 7.1.
I've attached a screenshot. Does anybody know what is the issue here?
I read in the Definitive Guide to NB Platform 7.1 that you have to install NetBeans (well because of the JUnit) into the folder, where it has write rights. Which is not the Progam Files in Windows 7.
So try to install it for example into C:\Programs or something like that. You can install new version (7.1.1) even without uninstalling the older one and then let the NB get your previous settings (it will ask).
You can try temporarily disabling your firewall and/or antivirus. I got the same problem, and disabling AVG Internet Security everything worked fine. Hope it helps!
I think that problem is in network. So try to change network you are on. I am using university network that has many policies and only JUnit plugin installation stucks. Went to local wireles public network and JUnit plugin was installed successfully.
I am facing a weired problem, I have configured WebLogic 9.2 with Eclipse Helios. I have started the server in debug mode, It works fine in debug mode, however after a while it changes its state to "started" or "stopped". It is behaving weirdly.
I have re-installed and re configured WebLogic and its domain, used a new Workspace. However the problem persists.
Any suggestions please.
Regards,
Sarbbottam
I realized that this issue started suddenly after installing launchy. I have not uninstall-ed launchy but just exited it process. The issue seems to be resolved. Really crazy and weired.
Regards,
Sarbbottam