Following on from earlier comments, I've just tried the same software
on another machine and got better results.
Once the main Java process is started, and goes into wait state, using
the 'jps' command to list current Java processes lists the process id
and also the main class name being executed.
Using jconsole with the pid on this machine works fine.
On the machine where jconsole cannot connect, the output indicates the
process id(s) but, except for jps itself, the output indicates
-- process information unavailable
Presumably this is the same problem seen by jconsole.
No help as to why I am getting that at present, but potentially closer
to finding a solution.
Regards,
John
Rut the Nut - 27 Apr 2006 11:56 GMT
The standalone machine on which the JMX software ran successfully had
local security, not part of a Windoze domain, whereas the original
machine (a laptop) was part of a Windoze security domain but not
directly connected to that network at the time.
With the machine physically on the domain network, the software runs
correctly.
So it looks as though there are security issues whereby cached
credentials do not apply :(
That's probably all I'm going to do as far as investigating the
problem, but it will be a real nuisance if I am unable to run the
software on a disconnected laptop for demo purposes.
Perhaps it would work if I logged-in to the machine using local admin
credentials rather than my off-line user account...
Regards,
John