Hi,

I run a binary application[Java] with GUI accessibility. To launch and close the application i follow the following steps:

1.Log into a console session. Export display to the local workstation.
2.Launch X windows app ( eXceed )
3.From terminal session go to the my application directory and run the following command : nohup /.myapplication &
4.The application service will run and the UI will launch.

[supose i did something with my applicaiton] now I will cose the GUI window.

5.Close the UI and choose to exit the myapplication workspace.
6.The UI is closed but the myapplication process is still running.
7.Close the terminal session
8.The session closes / exits but the smartreplicator process is still running
9.Close xwindows ( eXceed )
10.Exceed exits and the myapplication process is killed.

But it need be running. It seems as soon as i get out from the eXceed window my process is killed, I don't want that. How can I keep my process running exiting from the eXceed window??

eXceed is X server for windows, so this is expected -> when you close the parent, the child also dies. This won't happen if you're running Linux for example :
Then if I exit the terminal session and enter again, it's still running, since it haven't received SIGKILL or other signal.

What happens if you start myapplication in the background from the system console, or start it as a service somewhere in /etc/rc2.d ?