beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satish Subhashrao Saley (JIRA)" <>
Subject [jira] [Created] (BEAM-552) TimeZone.getTimeZone has performance issue.
Date Mon, 15 Aug 2016 18:36:20 GMT
Satish Subhashrao Saley created BEAM-552:

             Summary: TimeZone.getTimeZone has performance issue.
                 Key: BEAM-552
             Project: Beam
          Issue Type: Bug
            Reporter: 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
<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(
	- locked <0x00000005c00876d8> (a java.lang.Class for java.util.TimeZone)
	at org.apache.oozie.CoordinatorJobBean.toJSONObject(
	at org.apache.oozie.CoordinatorJobBean.toJSONArray(
	at org.apache.oozie.servlet.V1JobsServlet.getCoordinatorJobs(
	at org.apache.oozie.servlet.V1JobsServlet.getJobs(


This message was sent by Atlassian JIRA

View raw message