Why not modify j.jar to run with standard timing except when it fails
toget java metrics. Then, instead of posting the message, wait a few
more seconds? I know nothing about java programming, but j.jar must know
when it has failed to get java metrics or it could not post the message.
On 01/06/2013 02:49 AM, bill lam wrote:
The "new" jar will add a few seconds delay when starting.
Сб., 05 янв. 2013, Eldon Eller писал(а):
Thank you; that did it. Just out of idle curiosity, is there any
reason the "new" j.jar, which works, shouldn't replace the "old"
j.jar, which fails at least some of the time, in the j602a download?
On 01/05/2013 04:45 PM, bill lam wrote:
this link might help,
http://old.nabble.com/Re%3A-Failed-to-get-Java-metrics-p19247269s24193.html
Сб., 05 янв. 2013, Eldon Eller писал(а):
0) Forgive me for bringing this up again. I installed j602a on
openSuse and when I try to open jwd, I get "Failed to get java
metrics." This has happened before and I found and installed the fix
and all was well. I can no longer find the fix. Where is it?
1) Why doesn't someone fix this once and or all?
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
