What steps will reproduce the problem? 1. go to job monitor screen with active jobs running 2. 3.

What is the expected output? What do you see instead? Date and time instead of NaN

What version of the product are you using? On what operating system? JWatch 0.8 - Quartz 2.0.1 - CentOS 5.5 - Tomcat 6

Please provide any additional information below.

Interesting. I never tested in a clustered environment, but good to know it sorta works. ;-)

Can you tell me briefly: 1. What browser/version are you using? 2. Can you paste what the JSON output looks like by hitting the RESTFul url? http://localhost:8081/jwatch/ui?action=monitor_jobs

This is likely a client-rendering issue.

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

Here is the json result.

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.

even I am also getting the same issue

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).