Can you restate your problem. Can you run jhs801 OK?
By default JHS701 and JHS801 both use port 65001 so you can only run one of them at a time. If one is running, starting the other will fail because the port is already in use. It only makes sense to run that ps command if starting a JHS server fails with an error report that the port is in use. Then you can use ps to find the task that is using (to your surprise) the port. With the result of the ps you could kill the port. Or more likely you could connect to jijx in your browser and do an exit''. On Tue, Feb 11, 2014 at 1:47 PM, Brian Schott <schott.br...@gmail.com> wrote: > Bill, > > Below are 3 examples of running "ps -au brian |grep jconsole" > > 1) Run while jhs701 is successfully running > 2) Run after "exit ''" in jhs701 > 3) Run after jhs801 is launched > > Can you see anything important there? > > server:~ brian$ ps -au brian|grep jconsole > 501 2616 ttys000 0:00.00 grep jconsole > 501 2600 ttys004 0:00.13 /Users/brian/j64-701/bin/jconsole > ~addons/ide/jhs/core.ijs -js init_jhs_'' > server:~ brian$ ps -au brian|grep jconsole > 501 2622 ttys000 0:00.00 grep jconsole > server:~ brian$ ps -au brian|grep jconsole > 501 2631 ?? 0:00.03 > /Users/brian/j64-801/jhs801.app/Contents/MacOS/../../../bin/jconsole > ~addons/ide/jhs/core.ijs -js init_jhs_'' > 501 2637 ttys000 0:00.00 grep jconsole > server:~ brian$ > > > > On Tue, Feb 11, 2014 at 11:33 AM, bill lam <bbill....@gmail.com> wrote: > >> Perhaps you can try "ps -aux |grep jconsole" to list possbile >> runaway jhs and kill them using kill or killall commands. >> >> -- > (B=) > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
