[jira] [Created] (DBCP-356) ManagedDataSource doesn't work with an active transaction in progress on IBM JDK 6+

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (DBCP-356) ManagedDataSource doesn't work with an active transaction in progress on IBM JDK 6+

David Mollitor (Jira)
ManagedDataSource doesn't work with an active transaction in progress on IBM JDK 6+
-----------------------------------------------------------------------------------

                 Key: DBCP-356
                 URL: https://issues.apache.org/jira/browse/DBCP-356
             Project: Commons Dbcp
          Issue Type: Bug
    Affects Versions: 1.4, 1.3
         Environment: IBM JDK 6
java version "1.6.0"
Java(TM) SE Runtime Environment (build pwa6460sr9fp1-20110208_03(SR9 FP1))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 amd64-64 jvmwa6460sr9-20110203_74623 (JIT enabled, AOT enabled)
J9VM - 20110203_074623
JIT  - r9_20101028_17488ifx3
GC   - 20101027_AA)
JCL  - 20110203_01

commons-dbcp of version 1.3 / 1.4
            Reporter: an envy guest


When using IBM JDK 6+ and trying to build commons-dbcp, these tests fail:

org.apache.commons.dbcp.managed.TestBasicManagedDataSource
org.apache.commons.dbcp.managed.TestManagedDataSourceInTx

with error:

java.sql.SQLException: Connection does not have a registered XAResource null, UserName=null, null
        at org.apache.commons.dbcp.managed.TransactionRegistry.getXAResource(TransactionRegistry.java:81)
        at org.apache.commons.dbcp.managed.TransactionContext.setSharedConnection(TransactionContext.java:88)
        at org.apache.commons.dbcp.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:131)
        at org.apache.commons.dbcp.managed.ManagedConnection.<init>(ManagedConnection.java:55)
        at org.apache.commons.dbcp.managed.ManagedDataSource.getConnection(ManagedDataSource.java:76)
        at org.apache.commons.dbcp.managed.TestManagedDataSource.getConnection(TestManagedDataSource.java:53)
        at org.apache.commons.dbcp.TestConnectionPool.newConnection(TestConnectionPool.java:81)
        at org.apache.commons.dbcp.managed.TestManagedDataSourceInTx.testMaxActive(TestManagedDataSourceInTx.java:102)

When used in conjunction with OpenEJB 3.1.4 examples, the error is the same.

The problem disappears when switched to Oracle JDK 1.6.24 (so, all tests are passed and OpenEJB examples are working).

I beleive this has something to do with differences in java.lang.ref.WeakReference implementations between IBM and Oracle JDKs, which was already discussed here:
http://www.mail-archive.com/dev@.../msg13107.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (DBCP-356) ManagedDataSource doesn't work with an active transaction in progress on IBM JDK 6+

David Mollitor (Jira)

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

Phil Steitz updated DBCP-356:
-----------------------------

    Fix Version/s: 1.4.1
                   1.3.1

> ManagedDataSource doesn't work with an active transaction in progress on IBM JDK 6+
> -----------------------------------------------------------------------------------
>
>                 Key: DBCP-356
>                 URL: https://issues.apache.org/jira/browse/DBCP-356
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.3, 1.4
>         Environment: IBM JDK 6
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwa6460sr9fp1-20110208_03(SR9 FP1))
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 amd64-64 jvmwa6460sr9-20110203_74623 (JIT enabled, AOT enabled)
> J9VM - 20110203_074623
> JIT  - r9_20101028_17488ifx3
> GC   - 20101027_AA)
> JCL  - 20110203_01
> commons-dbcp of version 1.3 / 1.4
>            Reporter: an envy guest
>              Labels: ibm, xaresource
>             Fix For: 1.3.1, 1.4.1
>
>
> When using IBM JDK 6+ and trying to build commons-dbcp, these tests fail:
> org.apache.commons.dbcp.managed.TestBasicManagedDataSource
> org.apache.commons.dbcp.managed.TestManagedDataSourceInTx
> with error:
> java.sql.SQLException: Connection does not have a registered XAResource null, UserName=null, null
> at org.apache.commons.dbcp.managed.TransactionRegistry.getXAResource(TransactionRegistry.java:81)
> at org.apache.commons.dbcp.managed.TransactionContext.setSharedConnection(TransactionContext.java:88)
> at org.apache.commons.dbcp.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:131)
> at org.apache.commons.dbcp.managed.ManagedConnection.<init>(ManagedConnection.java:55)
> at org.apache.commons.dbcp.managed.ManagedDataSource.getConnection(ManagedDataSource.java:76)
> at org.apache.commons.dbcp.managed.TestManagedDataSource.getConnection(TestManagedDataSource.java:53)
> at org.apache.commons.dbcp.TestConnectionPool.newConnection(TestConnectionPool.java:81)
> at org.apache.commons.dbcp.managed.TestManagedDataSourceInTx.testMaxActive(TestManagedDataSourceInTx.java:102)
> When used in conjunction with OpenEJB 3.1.4 examples, the error is the same.
> The problem disappears when switched to Oracle JDK 1.6.24 (so, all tests are passed and OpenEJB examples are working).
> I beleive this has something to do with differences in java.lang.ref.WeakReference implementations between IBM and Oracle JDKs, which was already discussed here:
> http://www.mail-archive.com/dev@.../msg13107.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (DBCP-356) ManagedDataSource doesn't work with an active transaction in progress on IBM JDK 6+

David Mollitor (Jira)
In reply to this post by David Mollitor (Jira)

    [ https://issues.apache.org/jira/browse/DBCP-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032004#comment-13032004 ]

Satya commented on DBCP-356:
----------------------------

My application uses BasicManagedDatasource. Transaction management is handled using JOTM.
It is a standalone java application running inside a JVM.
The implementation works on Oracle JDK (1.6.24) but fails when it runs on AIX with an error.

The call that fails is a simple 'getConnection' on the BasicManagedDatsource.
The error logged is:
java.sql.SQLException: Unable to connect to database. Connection does not have a registered XAResource jdbc:oracle:thin:@xyz:1521:ABCD, UserName=XYZ, Oracle JDBC driver

Is this the same error as in this issue?

If it is, is there a workaround that I can use for the present?


> ManagedDataSource doesn't work with an active transaction in progress on IBM JDK 6+
> -----------------------------------------------------------------------------------
>
>                 Key: DBCP-356
>                 URL: https://issues.apache.org/jira/browse/DBCP-356
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.3, 1.4
>         Environment: IBM JDK 6
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwa6460sr9fp1-20110208_03(SR9 FP1))
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 amd64-64 jvmwa6460sr9-20110203_74623 (JIT enabled, AOT enabled)
> J9VM - 20110203_074623
> JIT  - r9_20101028_17488ifx3
> GC   - 20101027_AA)
> JCL  - 20110203_01
> commons-dbcp of version 1.3 / 1.4
>            Reporter: an envy guest
>              Labels: ibm, xaresource
>             Fix For: 1.3.1, 1.4.1
>
>
> When using IBM JDK 6+ and trying to build commons-dbcp, these tests fail:
> org.apache.commons.dbcp.managed.TestBasicManagedDataSource
> org.apache.commons.dbcp.managed.TestManagedDataSourceInTx
> with error:
> java.sql.SQLException: Connection does not have a registered XAResource null, UserName=null, null
> at org.apache.commons.dbcp.managed.TransactionRegistry.getXAResource(TransactionRegistry.java:81)
> at org.apache.commons.dbcp.managed.TransactionContext.setSharedConnection(TransactionContext.java:88)
> at org.apache.commons.dbcp.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:131)
> at org.apache.commons.dbcp.managed.ManagedConnection.<init>(ManagedConnection.java:55)
> at org.apache.commons.dbcp.managed.ManagedDataSource.getConnection(ManagedDataSource.java:76)
> at org.apache.commons.dbcp.managed.TestManagedDataSource.getConnection(TestManagedDataSource.java:53)
> at org.apache.commons.dbcp.TestConnectionPool.newConnection(TestConnectionPool.java:81)
> at org.apache.commons.dbcp.managed.TestManagedDataSourceInTx.testMaxActive(TestManagedDataSourceInTx.java:102)
> When used in conjunction with OpenEJB 3.1.4 examples, the error is the same.
> The problem disappears when switched to Oracle JDK 1.6.24 (so, all tests are passed and OpenEJB examples are working).
> I beleive this has something to do with differences in java.lang.ref.WeakReference implementations between IBM and Oracle JDKs, which was already discussed here:
> http://www.mail-archive.com/dev@.../msg13107.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (DBCP-356) ManagedDataSource doesn't work with an active transaction in progress on IBM JDK 6+

David Mollitor (Jira)
In reply to this post by David Mollitor (Jira)

    [ https://issues.apache.org/jira/browse/DBCP-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032433#comment-13032433 ]

Michael Glauche commented on DBCP-356:
--------------------------------------

This is probably because of a bug in the IBM JDK, see http://www-01.ibm.com/support/docview.wss?uid=swg1IZ96415

For a "dirty" workaround you can create a copy of TransactionRegistry in your local project (so it does overwrite the DBCP class) and change the WeakHashMap to HashMap. For short lived tests it should be ok, but don't run anything serious on this (it should eat up connections ...)



> ManagedDataSource doesn't work with an active transaction in progress on IBM JDK 6+
> -----------------------------------------------------------------------------------
>
>                 Key: DBCP-356
>                 URL: https://issues.apache.org/jira/browse/DBCP-356
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.3, 1.4
>         Environment: IBM JDK 6
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwa6460sr9fp1-20110208_03(SR9 FP1))
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 amd64-64 jvmwa6460sr9-20110203_74623 (JIT enabled, AOT enabled)
> J9VM - 20110203_074623
> JIT  - r9_20101028_17488ifx3
> GC   - 20101027_AA)
> JCL  - 20110203_01
> commons-dbcp of version 1.3 / 1.4
>            Reporter: an envy guest
>              Labels: ibm, xaresource
>             Fix For: 1.3.1, 1.4.1
>
>
> When using IBM JDK 6+ and trying to build commons-dbcp, these tests fail:
> org.apache.commons.dbcp.managed.TestBasicManagedDataSource
> org.apache.commons.dbcp.managed.TestManagedDataSourceInTx
> with error:
> java.sql.SQLException: Connection does not have a registered XAResource null, UserName=null, null
> at org.apache.commons.dbcp.managed.TransactionRegistry.getXAResource(TransactionRegistry.java:81)
> at org.apache.commons.dbcp.managed.TransactionContext.setSharedConnection(TransactionContext.java:88)
> at org.apache.commons.dbcp.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:131)
> at org.apache.commons.dbcp.managed.ManagedConnection.<init>(ManagedConnection.java:55)
> at org.apache.commons.dbcp.managed.ManagedDataSource.getConnection(ManagedDataSource.java:76)
> at org.apache.commons.dbcp.managed.TestManagedDataSource.getConnection(TestManagedDataSource.java:53)
> at org.apache.commons.dbcp.TestConnectionPool.newConnection(TestConnectionPool.java:81)
> at org.apache.commons.dbcp.managed.TestManagedDataSourceInTx.testMaxActive(TestManagedDataSourceInTx.java:102)
> When used in conjunction with OpenEJB 3.1.4 examples, the error is the same.
> The problem disappears when switched to Oracle JDK 1.6.24 (so, all tests are passed and OpenEJB examples are working).
> I beleive this has something to do with differences in java.lang.ref.WeakReference implementations between IBM and Oracle JDKs, which was already discussed here:
> http://www.mail-archive.com/dev@.../msg13107.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (DBCP-356) ManagedDataSource doesn't work with an active transaction in progress on IBM JDK 6+

David Mollitor (Jira)
In reply to this post by David Mollitor (Jira)

    [ https://issues.apache.org/jira/browse/DBCP-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032825#comment-13032825 ]

an envy guest commented on DBCP-356:
------------------------------------

@Michael: I confirm your workaround is ok.
Basically, I faced this issue when running embedded OpenEJB container in unit tests, and I ended up with exactly what you are proposing: getting DBCP source, replacing WeakHashMap with HashMap and building my custom 'distribution' :-) For my purposes that sufficed since that were just unit tests and I didn't need solid rock stability in terms of connections leak.
However, that of course would be nice to have issue fixed.

> ManagedDataSource doesn't work with an active transaction in progress on IBM JDK 6+
> -----------------------------------------------------------------------------------
>
>                 Key: DBCP-356
>                 URL: https://issues.apache.org/jira/browse/DBCP-356
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.3, 1.4
>         Environment: IBM JDK 6
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwa6460sr9fp1-20110208_03(SR9 FP1))
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 amd64-64 jvmwa6460sr9-20110203_74623 (JIT enabled, AOT enabled)
> J9VM - 20110203_074623
> JIT  - r9_20101028_17488ifx3
> GC   - 20101027_AA)
> JCL  - 20110203_01
> commons-dbcp of version 1.3 / 1.4
>            Reporter: an envy guest
>              Labels: ibm, xaresource
>             Fix For: 1.3.1, 1.4.1
>
>
> When using IBM JDK 6+ and trying to build commons-dbcp, these tests fail:
> org.apache.commons.dbcp.managed.TestBasicManagedDataSource
> org.apache.commons.dbcp.managed.TestManagedDataSourceInTx
> with error:
> java.sql.SQLException: Connection does not have a registered XAResource null, UserName=null, null
> at org.apache.commons.dbcp.managed.TransactionRegistry.getXAResource(TransactionRegistry.java:81)
> at org.apache.commons.dbcp.managed.TransactionContext.setSharedConnection(TransactionContext.java:88)
> at org.apache.commons.dbcp.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:131)
> at org.apache.commons.dbcp.managed.ManagedConnection.<init>(ManagedConnection.java:55)
> at org.apache.commons.dbcp.managed.ManagedDataSource.getConnection(ManagedDataSource.java:76)
> at org.apache.commons.dbcp.managed.TestManagedDataSource.getConnection(TestManagedDataSource.java:53)
> at org.apache.commons.dbcp.TestConnectionPool.newConnection(TestConnectionPool.java:81)
> at org.apache.commons.dbcp.managed.TestManagedDataSourceInTx.testMaxActive(TestManagedDataSourceInTx.java:102)
> When used in conjunction with OpenEJB 3.1.4 examples, the error is the same.
> The problem disappears when switched to Oracle JDK 1.6.24 (so, all tests are passed and OpenEJB examples are working).
> I beleive this has something to do with differences in java.lang.ref.WeakReference implementations between IBM and Oracle JDKs, which was already discussed here:
> http://www.mail-archive.com/dev@.../msg13107.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (DBCP-356) ManagedDataSource doesn't work with an active transaction in progress on IBM JDK 6+

David Mollitor (Jira)
In reply to this post by David Mollitor (Jira)

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

Balazs Zsoldos updated DBCP-356:
--------------------------------

    Attachment: TransactionRegistry.java.patch
                TransactionRegistry.java.patch

I experienced this problem on JDK 1.6_30. I managed to solve it by applying the patch (not hacking equals or any other function just being sure that the same object is used during getting the XAResource from the weakhashmap)
               

> ManagedDataSource doesn't work with an active transaction in progress on IBM JDK 6+
> -----------------------------------------------------------------------------------
>
>                 Key: DBCP-356
>                 URL: https://issues.apache.org/jira/browse/DBCP-356
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.3, 1.4
>         Environment: IBM JDK 6
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwa6460sr9fp1-20110208_03(SR9 FP1))
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 amd64-64 jvmwa6460sr9-20110203_74623 (JIT enabled, AOT enabled)
> J9VM - 20110203_074623
> JIT  - r9_20101028_17488ifx3
> GC   - 20101027_AA)
> JCL  - 20110203_01
> commons-dbcp of version 1.3 / 1.4
>            Reporter: an envy guest
>              Labels: ibm, xaresource
>             Fix For: 1.3.1, 1.4.1
>
>         Attachments: TransactionRegistry.java.patch, TransactionRegistry.java.patch
>
>
> When using IBM JDK 6+ and trying to build commons-dbcp, these tests fail:
> org.apache.commons.dbcp.managed.TestBasicManagedDataSource
> org.apache.commons.dbcp.managed.TestManagedDataSourceInTx
> with error:
> java.sql.SQLException: Connection does not have a registered XAResource null, UserName=null, null
> at org.apache.commons.dbcp.managed.TransactionRegistry.getXAResource(TransactionRegistry.java:81)
> at org.apache.commons.dbcp.managed.TransactionContext.setSharedConnection(TransactionContext.java:88)
> at org.apache.commons.dbcp.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:131)
> at org.apache.commons.dbcp.managed.ManagedConnection.<init>(ManagedConnection.java:55)
> at org.apache.commons.dbcp.managed.ManagedDataSource.getConnection(ManagedDataSource.java:76)
> at org.apache.commons.dbcp.managed.TestManagedDataSource.getConnection(TestManagedDataSource.java:53)
> at org.apache.commons.dbcp.TestConnectionPool.newConnection(TestConnectionPool.java:81)
> at org.apache.commons.dbcp.managed.TestManagedDataSourceInTx.testMaxActive(TestManagedDataSourceInTx.java:102)
> When used in conjunction with OpenEJB 3.1.4 examples, the error is the same.
> The problem disappears when switched to Oracle JDK 1.6.24 (so, all tests are passed and OpenEJB examples are working).
> I beleive this has something to do with differences in java.lang.ref.WeakReference implementations between IBM and Oracle JDKs, which was already discussed here:
> http://www.mail-archive.com/dev@.../msg13107.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (DBCP-356) ManagedDataSource doesn't work with an active transaction in progress on IBM JDK 6+

David Mollitor (Jira)
In reply to this post by David Mollitor (Jira)

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

Allan Saddi updated DBCP-356:
-----------------------------

    Attachment: commons-dbcp-TransactionRegistry.diff

Running into this issue with Apple's JDK 1.6.0_31, OpenEJB, and the PostgreSQL 9.1 JDBC4 driver. (Though it works fine with the PostgreSQL 8.4 JDBC4 driver.) Balazs' patch also fixes it in DBCP 1.4 -- the version that OpenEJB 4.0.0 uses. However, I had to tweak the patch a bit because the TestBasicManagedDataSource.testReallyClose unit test was failing.
               

> ManagedDataSource doesn't work with an active transaction in progress on IBM JDK 6+
> -----------------------------------------------------------------------------------
>
>                 Key: DBCP-356
>                 URL: https://issues.apache.org/jira/browse/DBCP-356
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.3, 1.4
>         Environment: IBM JDK 6
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwa6460sr9fp1-20110208_03(SR9 FP1))
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 amd64-64 jvmwa6460sr9-20110203_74623 (JIT enabled, AOT enabled)
> J9VM - 20110203_074623
> JIT  - r9_20101028_17488ifx3
> GC   - 20101027_AA)
> JCL  - 20110203_01
> commons-dbcp of version 1.3 / 1.4
>            Reporter: an envy guest
>              Labels: ibm, xaresource
>             Fix For: 1.3.1, 1.4.1
>
>         Attachments: TransactionRegistry.java.patch, TransactionRegistry.java.patch, commons-dbcp-TransactionRegistry.diff
>
>
> When using IBM JDK 6+ and trying to build commons-dbcp, these tests fail:
> org.apache.commons.dbcp.managed.TestBasicManagedDataSource
> org.apache.commons.dbcp.managed.TestManagedDataSourceInTx
> with error:
> java.sql.SQLException: Connection does not have a registered XAResource null, UserName=null, null
> at org.apache.commons.dbcp.managed.TransactionRegistry.getXAResource(TransactionRegistry.java:81)
> at org.apache.commons.dbcp.managed.TransactionContext.setSharedConnection(TransactionContext.java:88)
> at org.apache.commons.dbcp.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:131)
> at org.apache.commons.dbcp.managed.ManagedConnection.<init>(ManagedConnection.java:55)
> at org.apache.commons.dbcp.managed.ManagedDataSource.getConnection(ManagedDataSource.java:76)
> at org.apache.commons.dbcp.managed.TestManagedDataSource.getConnection(TestManagedDataSource.java:53)
> at org.apache.commons.dbcp.TestConnectionPool.newConnection(TestConnectionPool.java:81)
> at org.apache.commons.dbcp.managed.TestManagedDataSourceInTx.testMaxActive(TestManagedDataSourceInTx.java:102)
> When used in conjunction with OpenEJB 3.1.4 examples, the error is the same.
> The problem disappears when switched to Oracle JDK 1.6.24 (so, all tests are passed and OpenEJB examples are working).
> I beleive this has something to do with differences in java.lang.ref.WeakReference implementations between IBM and Oracle JDKs, which was already discussed here:
> http://www.mail-archive.com/dev@.../msg13107.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira