logged out the genome window, its [1]

1. We are writing a java program to generate PDF as a output through our
> java based web portal.
> 2. While generating PDF we are calling java swing /servlet feature of
> java.
> 3. Our java program require X-11 graphical feature of OS to run/execute
> the program.
>
> Happy Conditions:
> 1. We are logging to solaris box from remote access and opening with
> GENOME desktop using x-manager utility.
> 2. Our GENOME window at remote machine is open.
> 3. Opening server terminal and started Tomcat server.
> 4. And executing our PDF generation program from any client machine we are
> getting output as per the requirement.
> Issues occurs during operation:
> 1. Here we logged out the genome window and which is by default closing
> the the X-11 window session.
> 2. But Tomcat server is already started.
> 3. And executing our PDF generation program from any client machine but
> program is not running my java program reaching to hanging state.
> Looking for the solution and suggestions for below mentioned assumptions :
> 1. What can be the issue for the same?
> 2. If it is related to X-11 window session then how to set X-11 graphical
> window setting on solaris box which should remain always as an active
> session?
> 3. If it is related to .profile setting in the user or root profile then
> please share some sample .profile with standard setting with X-11 display
> or else whatever needed.
> Details of the Hardware/Software:
> 1. OS : Solaris 5.9 Sun fire v240
> 2. Tomcat version : 5.0
> 3. Java version JDK 1.5
> 4. Java swing/servlet
> 5. Using X-manager to login Solaris Box


Program Ver. : Xmanager 3.0
Connection Method : Xstart connection

Let me make sure if I understood the problem correctly.

You use Xmanager to logon to remote Solaris Gnome. On Gnome, you start Tomcat server and the PDF generator. And, once you log out of Gnome, you can no longer use the PDF generator.

Am I understanding the problem correctly? Please correct me if there are any parts I am not understanding correctly.

If my understanding is correct, then you can try using the nohup (no hangup) command.
This command prevents a program from exiting after user logs out. To execute the nohup command, use the following format:

nohup command &



---
Technical Support