You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/08/15 20:56:20 UTC
[jira] [Commented] (OOZIE-2635) TimeZone.getTimeZone has
performance issue.
[ https://issues.apache.org/jira/browse/OOZIE-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421656#comment-15421656 ]
Hadoop QA commented on OOZIE-2635:
----------------------------------
Testing JIRA OOZIE-2635
Cleaning local git workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than 132
. {color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
. Tests run: 1792
. Tests failed: 1
. Tests errors: 0
. The patch failed the following testcases:
. testCoordStatus_Failed(org.apache.oozie.command.coord.TestCoordChangeXCommand)
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/3227/
> 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
> Attachments: OOZIE-2635-1.patch
>
>
> 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)