You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Davor Bonaci (JIRA)" <ji...@apache.org> on 2016/12/28 22:31:58 UTC

[jira] [Updated] (BEAM-552) TimeZone.getTimeZone has performance issue.

     [ https://issues.apache.org/jira/browse/BEAM-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davor Bonaci updated BEAM-552:
------------------------------
    Component/s: sdk-java-core

> TimeZone.getTimeZone has performance issue.
> -------------------------------------------
>
>                 Key: BEAM-552
>                 URL: https://issues.apache.org/jira/browse/BEAM-552
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Satish Subhashrao Saley
>             Fix For: Not applicable
>
>
> 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)