The jAWTRobot library can give you your server's processID. This will help you determine what to kill in Task Manager.
Additionally, you should download Process Explorer from sysinternals.com. It is a far superior version of Task Manager that shows you the full command that spawned a process, which other process spawned it, the working directory, etc... Using that, it's a pretty simple matter to determine which java process is which.
thanks for the reply's. It not exactly what I am looking for. We are re-developing all our servers apps in B4J (leap of faith) and our system can be offered as a cloud service or deployed as an in house service to our customer base. At the moment when we look at task manager we can see what .exe's are running, but with b4j it is not that easy. So if a server app needs to be restarted for what ever reason we wont be able to identify which one it is.
I thought the maybe a command arg to app to the app that would mask the javaw.exe name with another.
If you can assure that the JDK will be installed on the clients then you can create a small B4J UI app that will call JPS and show the running servers.
If you can assure that the JDK will be installed on the clients then you can create a small B4J UI app that will call JPS and show the running servers.