I am using Google App Engine plugin with eclipse to create some web application, every time after I modify the program and run it, the modification does not take effect instantly. I have to kill the one (sometime mistakenly will kill the eclipse program) of the javaw.exe process and re-run again. Sometime it will hang at the "datanucleus enhancer".
I know it happen because the new javaw.exe run on the same port as the previous instance. But no point to kill the previous javaw.exe instance manually everytime, it is very annoying.
I thought I can save the source file and it will be automatically deploy to the development server, but it does not. What can I do so I do not have to manually kill the process?
If you run your app in debug mode-- that is, via Debug As > Web Application (rather than Run As > Web Application)-- it should reflect your changes to source. (For some changes it may need to terminate and restart the server, in which case it will notify you).
Related
I am using JBoss Developer studio 10.1.0.GA.
I have a fuse integration project. In my JMX Navigator there are so many unused maven[id] formed. How can they be removed/deleted?
Please refer the image.
Wow, how did that happen? I guess you ran a Camel context locally several times? Did you stop the process in DevStudio console view? That should usually make those processes disappear. In your case there might be several running processes in the console view so stop and close one by one.
Alternatively you could terminate them manually either via the Task Manager (Windows) or by invoking "kill " (Linux).
I would really love to hear what you did to get into that state.
I was using the add-on builder until today, now that it's dead I'm using the command-line tools. The problem with cfx is that every time I run it, FF is killed and restarted, I then need to go through my add-on's sign-in process every time and since it's a clean version of FF I can't even get it to remember my login details. Needless to say, going through these steps every time is a huge waste of time.
Given it's a restartless add-on that uses the add-on SDK, is there any way to reload the add-on without restarting FF?
You can try Extension Auto-Installer by Wladimir Palant. It should give to you exactly what you're looking for.
You could use cfx xpi, then drag the file to Firefox to avoid restarting.
However, I suggest to just close the browser and specify a profile directory so that the state of the session is persisted across restarts:
cfx run --profiledir=/tmp/myprofile
or (Windows):
cfx run --profiledir=%TMP%\myprofile
(-p is a shorthand for --profiledir, so you can also use cfx run -p/tmp/myprofile)
I have deployed my application on WAS 8 as debug. The server status is [Debugging, Synchronized]. When I put breakpoints and start the application, it doesn't stop at the breakpoints. I don't see the debugger thread start either.
I am using RAD 8.0.4 and JDK 1.6.0_31. I have tried cleaning the project and re-deploying but it still doesn't work.
I was able to get it working via a complete clean install of my app. Then removing it from the server via add remove. Clearing cache from the websphere/profiles/myprofile directory. and clearing all bits of my app from the profiles folder via a search for its containing file aka (myproject-folder). Then re-installed the app via add remove on the server and it worked for me.
Best guess I have is something was actually out of sync even though the server though everything was A okay.
WebSphere is a PITA and seems to get out of state too easily.
I'd restart the server and perhaps do a clean on the server (right click on the server, click "Clean...". If that doesn't work, you'll have to take a careful look at the location of your break points. They might not be on code that's getting executed. Place a break point further upstream if necessary, follow it down just to confirm the flow.
I have setup tomcat for remote debugging through eclipse, I have added following configuration in tomcat startup script
export JPDA_ADDRESS=9999
export JPDA_TRANSPORT=dt_socket
echo $JPDA_ADDRESS
…….
exec "$PRGDIR"/"$EXECUTABLE" jpda start "$#"
However, there are multiple developers working on this server and when my debugger stops at breakpoint I added, other developers get stuck, is there anyway in tomcat which will allow other developers to continue running application seamlessly while I am debugging?
As you made me realise, you really need a second independent tomcat instance. As underlined in the comment below, the debug breakpoint mechanism in the JVM would stop all webapps reaching the breakpoint even if you duplicate them (said otherwise regardless of the number of working threads, each thread would freeze and wait or resume signal).
Is is possible to 'unleash', or whatever, a process in Eclipse that you've been debugging, or simply started with 'run'? Would be nice. After such an 'unleash-ment', the unleashed process should not die when Eclipse is shut down, and should be removed from the debug view, to avoid accidentally killing it. Essentially, become a regular application process.
thanks, -j
There is no such command/option in Eclipse and it might not even possible depending on the OS. If you want a Java process to survive the end of Eclipse, you must start it outside.
It's sad that, after more than a decade, creating standalone processes in Java is still so painful. There is the -jar option but there is no way to have more than a single main() method this way, few people know how to build a working classpath when starting your app this way.