Re: Issue 1 in jwatch: NaN in job monitor screen

23 views
Skip to first unread message

jwa...@googlecode.com

unread,
Oct 12, 2011, 2:38:44 PM10/12/11
to jwatc...@googlegroups.com

Comment #2 on issue 1 by tglu...@gmail.com: NaN in job monitor screen
http://code.google.com/p/jwatch/issues/detail?id=1

Hi I am experiencing the same issue as described here. I am using quartz
2.0.2, apache-tomcat 6.0.33. Do you have a solution or an idea where to
look for this. Tested Firefox 6 and Internet Explorer 8 with same results.

Thanks,
Torsten

jwa...@googlecode.com

unread,
Oct 12, 2011, 2:46:54 PM10/12/11
to jwatc...@googlegroups.com

Comment #3 on issue 1 by tglu...@gmail.com: NaN in job monitor screen
http://code.google.com/p/jwatch/issues/detail?id=1

Here is the json result.

Attachments:
ui 81.1 KB

jwa...@googlecode.com

unread,
Apr 26, 2012, 9:18:18 AM4/26/12
to jwatc...@googlegroups.com

Comment #4 on issue 1 by kalle.ma...@gmail.com: NaN in job monitor screen
http://code.google.com/p/jwatch/issues/detail?id=1

I run in the same issue. In my case problem was e.g. a date 04/26/12
15:29:00 EEST. Reason is that javascript date.parse fails to parse some
timezone declarations. I fixed this by changing the date format pattern in
the Tools.java to "MM/dd/yy HH:mm:ss Z" which produces date as e.g.
04/26/12 15:29:00 +0300.

jwa...@googlecode.com

unread,
Jan 11, 2013, 6:44:01 AM1/11/13
to jwatc...@googlegroups.com

Comment #5 on issue 1 by kcc...@gmail.com: NaN in job monitor screen
http://code.google.com/p/jwatch/issues/detail?id=1

even I am also getting the same issue

Attachments:
jwatch.png 116 KB

jwa...@googlecode.com

unread,
Nov 12, 2013, 4:14:32 PM11/12/13
to jwatc...@googlegroups.com

Comment #6 on issue 1 by lucas.sa...@cortex-intelligence.com: NaN in job
monitor screen
http://code.google.com/p/jwatch/issues/detail?id=1

The date value is read by the application as a String instead a Date. When
passing the date String to the Ext.util.Format.date method the parser
doesn't understand the timezone code in the end of the String.

What I did to solve the problem temporally was remove the timezone code
before parsing the date String.

I did something like:

function removeTimeZone(input) {
var patt = '\\d+/\\d+/\\d+\\s\\d+:\\d+:\\d+';
return input.match(patt);
}

So, the String '11/12/13 17:58:03 BRST' becomes '11/12/13 17:58:03' and the
parsing works like a charm.

I'll commit this fix in my fork at GitHub
(https://github.com/lucassaldanha/jwatch).

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Reply all
Reply to author
Forward
0 new messages