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
Related
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.
An infuriating problem.
My Netbeans IDE 7.2 refuses to shutdown when I try to shutdown my machine.
I have got to use task manager to close the beast.
Its a windows 7 64 bit machine.
I have tried the usual Netbeans forums.
Any Ideas?
PS: I also use the well behaved Eclipse.
from what I'm seeing, you might have a corrupted install of netbeans cause usually it is light on a system. How long ago did you install it? Did you make any major changes before this all started, from evinvorment setting changes to major changes like how the thing complies etc...? I would say, the easiest bet is to back up the settings, if possible, and reinstall or do a repair install, if offered, of netbeans.
Upgraded to 7.3 and I no longer have a problem.
BTW Netbeans 7.3 is great for developing HTML 5 code.
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.
Hi guys I have a very frustrating and strange thing happening here, when I first ran my enterprise application everything was fine in netbeans and it deployed my project. When I went to run my application the 2nd time the project was being deployed for 2 hours and nothing ever happened. I know that it is not connecting to the glassfish server , but netbeans wont even let me change server either. I created a few other projects and I have the same problem, I tried re-installing it and it didnt help , if anyone knows the problem it would be much appreciated !
I was using jdk 1.7 so I changed to 1.6 and it worked :)
I am using RAD 7.5 on a Windows XP m/c. Whenever I try to do a clean up/build the project, I get a message saying
The project was not built due to "Could not delete 'D:\Documents and Settings\User\My Documents\project\exe\EXE\WebContent\WEB-INF\classes\BusinessRules.properties'.". Fix the problem, then try refreshing this project and building it since it may be inconsistent
To overcome this problem, I need to stop the server, manually delete this file & then build & restart the server. Any idea why I am facing this issue?
I've experienced the issue in RAD 8.0, but not nearly as consistently as you. A second build attempt nearly always resolves the problem for me.
Although there are a number of references to this issue on the Eclipse bug tracking site, none of the bugs I've read have a definitive answer on the cause. There is some speculation that it may be due to a file handle leak. The problem appears to have begun around Eclipse version 3.6.1. I'm not sure exactly which Eclipse version RAD 7.5 is based on, but I believe it is 3.6.1 or later.
Does the issue only occur when the application is deployed and the server is running? I was wondering if you'd gotten the same results with the server shut down.
Unfortunately, the only concrete suggestions I can offer are to try refreshing the project frequently, and perhaps creating a new workspace -- its a bit of a hack, but a creating a fresh workspace has fixed a few really odd RAD issues I've encountered.
Here are a couple of the bug reports from the Eclipse bug tracking site:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=309235
https://bugs.eclipse.org/bugs/show_bug.cgi?id=332607