Details

    • Affects:
      Release Notes
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Downgrade JVM e.g. Sun JDK 1.6-u03

      Show
      Downgrade JVM e.g. Sun JDK 1.6-u03
    • Affects Testing:
      Regression
    • Release Notes Text:
      Hide
      When <function>java.sql.Date.valueOf</function> attempts to parse dates of the format yyyy-mm-dd, the TCK test threw a <errorcode>java.lang.IllegalArgumentException</errorcode>. This was due to a regression in the latest Sun JVM, Sun JDK 1.6.0_24 (see <ulink url="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6898593"/> for more information). The workaround for this issue is to downgrade to Sun JDK 1.6.0_17.
      Show
      When <function>java.sql.Date.valueOf</function> attempts to parse dates of the format yyyy-mm-dd, the TCK test threw a <errorcode>java.lang.IllegalArgumentException</errorcode>. This was due to a regression in the latest Sun JVM, Sun JDK 1.6.0_24 (see <ulink url=" http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6898593 "/> for more information). The workaround for this issue is to downgrade to Sun JDK 1.6.0_17.
    • Release Notes Docs Status:
      Documented as Known Issue
    • Docs QE Status:
      ON_QA
    • Similar Issues:
      Show 5 results 

      Description

      We are hitting issue in Sun JDK 1.6-u18 JVM which has been used to run this test.

      Problem is caused by java.sql.Date.valueOf method. Following example code ends with java.lang.IllegalArgumentException on JDK 1.6-u18 but works fine on previous version of JVM.

      public static void main(String[] args)

      { java.sql.Date jsd = java.sql.Date.valueOf("1999-5-5"); System.out.println(jsd); }

        Activity

        Hide
        Rajesh Rajasekaran
        added a comment -

        Reopening to include this in the release notes. Pavel, is U03 the latest downgrade that will work?
        Wouldn't U17 or U16 work?

        Show
        Rajesh Rajasekaran
        added a comment - Reopening to include this in the release notes. Pavel, is U03 the latest downgrade that will work? Wouldn't U17 or U16 work?
        Hide
        Rajesh Rajasekaran
        added a comment -

        Laura, can you add this to the release notes as known issue?

        Show
        Rajesh Rajasekaran
        added a comment - Laura, can you add this to the release notes as known issue?
        Hide
        Pavel Slavicek
        added a comment -

        I have tested one failed test with JDK 1.6.0_17-b04 and this version works fine too.

        Show
        Pavel Slavicek
        added a comment - I have tested one failed test with JDK 1.6.0_17-b04 and this version works fine too.
        Hide
        Laura Bailey
        added a comment -

        Can I get a more detailed description of this problem, please?

        Show
        Laura Bailey
        added a comment - Can I get a more detailed description of this problem, please?
        Hide
        Pavel Slavicek
        added a comment -

        Hi Laura,

        We have regressions in the TCK tests in module JDBC with the latest SUN JVM 1.6.0_18-b07. Regressions are caused by java.lang.IllegalArgumentException on method java.sql.Date.valueOf when tests tries to parse date in the format yyyy-mm-dd. This is caused by issue in JVM, issue was reported for previous JVM versions http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6898593. Previous JVM version works fine e.g. JDK 1.6.0_17-b04.

        Show
        Pavel Slavicek
        added a comment - Hi Laura, We have regressions in the TCK tests in module JDBC with the latest SUN JVM 1.6.0_18-b07. Regressions are caused by java.lang.IllegalArgumentException on method java.sql.Date.valueOf when tests tries to parse date in the format yyyy-mm-dd. This is caused by issue in JVM, issue was reported for previous JVM versions http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6898593 . Previous JVM version works fine e.g. JDK 1.6.0_17-b04.
        Hide
        Laura Bailey
        added a comment -

        Thanks Pavel. Since this is a workaround rather than a fix, should this be listed as a known issue instead?

        Show
        Laura Bailey
        added a comment - Thanks Pavel. Since this is a workaround rather than a fix, should this be listed as a known issue instead?
        Hide
        Laura Bailey
        added a comment -

        Pavel, if this is to be a fixed issue, it needs a description of the fix. If the only fix is the workaround, I think it should remain a known issue. Can you let me know?

        Show
        Laura Bailey
        added a comment - Pavel, if this is to be a fixed issue, it needs a description of the fix. If the only fix is the workaround, I think it should remain a known issue. Can you let me know?
        Hide
        Pavel Slavicek
        added a comment -

        Issue has been documented as known issue in release notes.

        Show
        Pavel Slavicek
        added a comment - Issue has been documented as known issue in release notes.
        Hide
        Pavel Slavicek
        added a comment -

        We hit this issue with EAP 5.1.1 ER1 and Java Version 1.6.0_24.

        This information should be included in release notes.

        04-24-2011 04:20:16: SVR-ERROR: java.lang.IllegalArgumentException
        at java.sql.Date.valueOf(Date.java:138)
        at com.sun.ts.tests.jdbc.ee.callStmt.callStmt2.callStmtClient2.testGetDate03(callStmtClient2.java:842)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        Show
        Pavel Slavicek
        added a comment - We hit this issue with EAP 5.1.1 ER1 and Java Version 1.6.0_24. This information should be included in release notes. 04-24-2011 04:20:16: SVR-ERROR: java.lang.IllegalArgumentException at java.sql.Date.valueOf(Date.java:138) at com.sun.ts.tests.jdbc.ee.callStmt.callStmt2.callStmtClient2.testGetDate03(callStmtClient2.java:842) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        Hide
        Pavel Slavicek
        added a comment -

        Hi Jared, could you update release notes, please?
        Thanks

        Show
        Pavel Slavicek
        added a comment - Hi Jared, could you update release notes, please? Thanks
        Hide
        Jared Morgan
        added a comment -

        I have taken the Release Note comment used for Release Notes 5.1.0, and reused it for Release Notes 5.1.1.

        Show
        Jared Morgan
        added a comment - I have taken the Release Note comment used for Release Notes 5.1.0, and reused it for Release Notes 5.1.1.
        Show
        Pavel Slavicek
        added a comment - Documented as known issue. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html-single/Release_Notes_5.1.1/index.html
        Hide
        Russell Dickenson
        added a comment -

        Pavel,

        This is a long-standing issue which, I believe, the affected version of the Sun JDK. For EAP release 5.1.2 would you prefer that we include this note in the Release Notes or instead move it into the documentation?

        Show
        Russell Dickenson
        added a comment - Pavel, This is a long-standing issue which, I believe, the affected version of the Sun JDK. For EAP release 5.1.2 would you prefer that we include this note in the Release Notes or instead move it into the documentation?
        Show
        Russell Dickenson
        added a comment - Pavel, In addition to my comment ( https://issues.jboss.org/browse/JBPAPP-3929?focusedCommentId=12621269&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12621269 ), will this issue affect EAP release 5.1.2?
        Hide
        Russell Dickenson
        added a comment -

        Reopened issue to change Release Notes Docs Status to "Needs More Info".

        Show
        Russell Dickenson
        added a comment - Reopened issue to change Release Notes Docs Status to "Needs More Info".
        Hide
        Anne-Louise Tangring
        added a comment -

        If this is an open issue due to a problem in the JVM, it should never have been resolved. It should be listed as an open and known issue in the release notes and be re-investigated for each update of the JVM and not closed until fixed by the JVM provider.

        Show
        Anne-Louise Tangring
        added a comment - If this is an open issue due to a problem in the JVM, it should never have been resolved. It should be listed as an open and known issue in the release notes and be re-investigated for each update of the JVM and not closed until fixed by the JVM provider.
        Hide
        Russell Dickenson
        added a comment -

        Anne-Louise,

        Thanks. I'll make sure it's included in the Release Notes.

        Show
        Russell Dickenson
        added a comment - Anne-Louise, Thanks. I'll make sure it's included in the Release Notes.
        Hide
        Anne-Louise Tangring
        added a comment -

        According to the attached JDK bug, it was fixed in 2009. If that is not the case, a new bug should be submitted on the JDK and added here.

        Show
        Anne-Louise Tangring
        added a comment - According to the attached JDK bug, it was fixed in 2009. If that is not the case, a new bug should be submitted on the JDK and added here.

          People

          • Assignee:
            Pavel Slavicek
            Reporter:
            Pavel Slavicek
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: