Probably it is not "forever", but a long time needed to do something.
Try running it without the nohup and run a "KILL -3 <pid>" to the james pid. It will dump the stack trace to console: we need that stack trace. Maybe you want to do 2 or 3 dumps in the first seconds/minutes after running the application so that we can see what JAMES Server is doing. Stefano maomaode ha scritto: > Hi, > > I got a really abnormal case, the James server is OK this morning, but > this afternoon, it seems existed abnormally, and i found it can not be > started anymore. > > The output looks like this: > > ======================================================= > Using PHOENIX_HOME: /data2/softwares/james-2.3.1 > Using PHOENIX_TMPDIR: /data2/softwares/james-2.3.1/temp > Using JAVA_HOME: /data1/java/jdk1.5.0_10 > Running Phoenix: > > Phoenix 4.2 > ======================================================= > > > Previously i can see it list all the started port, but seems now it hang > there forever. > > I used the following command to launch the james server > >> nohup ./run.sh & > > And the platform is Suse linux, the i used the Java5 > > Can anyone help me out? > > > Thanks in advance > mao > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
