Re[2]: [JBoss-user] ^C and kil <pid> doesn't cleanly shutdown JBoss

[Alex L. <lou...@ua...>]

^C on the console doesn't make a clean shutdown in my environment.
RH7.2, JRockit, JBoss-3.0.1RC1. After server stopped I can see running
java processes and ports are bound. I am not an experienced linux
user.
I remember someone wrote that if I see some running java threads
that's not a fact that there are running threads, but just not closed
files. Is that right?
But after ^C I can't start JBoss that claiming about bound ports.

shutdown.sh works fine. That's true :)

alex


DC> This has always worked for me. Which pid are you trying to kill? Under 
DC> linux, you have to be careful about the ps output - each thread shows up 
DC> as a separate process - I do a 'ps axf', look for the 'java' process 
DC> that is the parent for all the other java processes and kill that. Of 
DC> course, ^C in the terminal you run JBoss from should always work (unless 
DC> the JBoss process is in the background, of course)

DC> hth,
DC> danch

DC> Jonathan Cowherd wrote:
>> It seems after an application gets deployed under Jboss, neither ^C or kill
>> <pid> will kill Jboss 2.4.4 on linux with Sun's JDK-1.3, or start the
>> undeploy processes.
>> 
>> There must be a better way (or cleaner way) to shutdown jboss.  Currently I
>> try to just do kill <pid> but I usually must kill -9 <pid>.
>> 
>> The log file shows that the shutdown hooks are added, so I think Jboss is
>> starting and setting up correctly. 
>> 
>> Any help would be appreciated.
>> 
>> Jonathan Paul Cowherd
>> Linux and Java Administrator
>> Genscape, Inc.
>> Email:  jon...@ge...
>> Office: (502) 583-3730
>> 
>> 
>> -------------------------------------------------------
>> This sf.net email is sponsored by:ThinkGeek
>> PC Mods, Computing goodies, cases & more
>> http://thinkgeek.com/sf
>> _______________________________________________
>> JBoss-user mailing list
>> JBo...@li...
>> https://lists.sourceforge.net/lists/listinfo/jboss-user
>>

-- 
Best regards,
 Alex Loubyansky