Satish Subhashrao Saley created OOZIE-2635:
----------------------------------------------
Summary: TimeZone.getTimeZone has performance issue.
Key: OOZIE-2635
URL: https://issues.apache.org/jira/browse/OOZIE-2635
Project: Oozie
Issue Type: Bug
Reporter: Satish Subhashrao Saley
Assignee: Satish Subhashrao Saley
While preparing Json response, we calculate the time zone for time related
fields in response. Most of times user will not pass timezone. We can easily
avoid TimeZone.getTimeZone for GMT timezone.
{code}
<0x00000005c00876d8> (a java.lang.Class for java.util.TimeZone): 0 Thread(s)
sleeping, 28 Thread(s) waiting, 1 Thread(s) locking
java.lang.Thread.State: BLOCKED (on object monitor)
at java.util.TimeZone.getTimeZone(TimeZone.java:516)
- locked <0x00000005c00876d8> (a java.lang.Class for java.util.TimeZone)
at
org.apache.oozie.client.rest.JsonUtils.formatDateRfc822(JsonUtils.java:47)
at
org.apache.oozie.CoordinatorJobBean.toJSONObject(CoordinatorJobBean.java:1119)
at
org.apache.oozie.CoordinatorJobBean.toJSONArray(CoordinatorJobBean.java:1061)
at
org.apache.oozie.servlet.V1JobsServlet.getCoordinatorJobs(V1JobsServlet.java:359)
at
org.apache.oozie.servlet.V1JobsServlet.getJobs(V1JobsServlet.java:156)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)