You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Fernanda Pizzorno (JIRA)" <de...@db.apache.org> on 2005/10/10 10:07:53 UTC
[jira] Created: (DERBY-611) Network client: updateRow() causes a commit when autoCommit = true
Network client: updateRow() causes a commit when autoCommit = true
------------------------------------------------------------------
Key: DERBY-611
URL: http://issues.apache.org/jira/browse/DERBY-611
Project: Derby
Type: Bug
Components: Network Client
Environment: Java Version: 1.5.0_01
Java Vendor: Sun Microsystems Inc.
Java home: /usr/jdk/instances/jdk1.5.0/jre
Java classpath: classes
OS name: SunOS
OS architecture: x86
OS version: 5.10
Reporter: Fernanda Pizzorno
Priority: Minor
Attachments: testCSUpdateRowCommits.java
On the network client driver, the ResultSet method updateRow makes the transaction commit, when autocommit is true. The correct behavior is to commit only when the result set is closed. This works correctly in the embedded driver.
The repro case is uploaded as an attachment "testCSUpdateRowCommits.java".
Output (repro case):
updateRow() should not commit
Value: 16, expected value 1. Should not have committed updateRow()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-611) Network client: updateRow() causes a commit when autoCommit = true
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-611?page=all ]
Dag H. Wanvik updated DERBY-611:
--------------------------------
Attachment: (was: 611.stat)
> Network client: updateRow() causes a commit when autoCommit = true
> ------------------------------------------------------------------
>
> Key: DERBY-611
> URL: http://issues.apache.org/jira/browse/DERBY-611
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0, 10.1.2.1, 10.2.0.0, 10.1.3.0, 10.1.2.2, 10.0.2.2
> Environment: Java Version: 1.5.0_01
> Java Vendor: Sun Microsystems Inc.
> Java home: /usr/jdk/instances/jdk1.5.0/jre
> Java classpath: classes
> OS name: SunOS
> OS architecture: x86
> OS version: 5.10
> Reporter: Fernanda Pizzorno
> Assignee: Dag H. Wanvik
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: testCSUpdateRowCommits.java
>
> On the network client driver, the ResultSet method updateRow makes the transaction commit, when autocommit is true. The correct behavior is to commit only when the result set is closed. This works correctly in the embedded driver.
> The repro case is uploaded as an attachment "testCSUpdateRowCommits.java".
> Output (repro case):
> updateRow() should not commit
> Value: 16, expected value 1. Should not have committed updateRow()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-611) Network client: updateRow() causes a commit when autoCommit = true
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-611?page=all ]
Dag H. Wanvik updated DERBY-611:
--------------------------------
Attachment: (was: 611.diff)
> Network client: updateRow() causes a commit when autoCommit = true
> ------------------------------------------------------------------
>
> Key: DERBY-611
> URL: http://issues.apache.org/jira/browse/DERBY-611
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0, 10.1.2.1, 10.2.0.0, 10.1.3.0, 10.1.2.2, 10.0.2.2
> Environment: Java Version: 1.5.0_01
> Java Vendor: Sun Microsystems Inc.
> Java home: /usr/jdk/instances/jdk1.5.0/jre
> Java classpath: classes
> OS name: SunOS
> OS architecture: x86
> OS version: 5.10
> Reporter: Fernanda Pizzorno
> Assignee: Dag H. Wanvik
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: 611.stat, testCSUpdateRowCommits.java
>
> On the network client driver, the ResultSet method updateRow makes the transaction commit, when autocommit is true. The correct behavior is to commit only when the result set is closed. This works correctly in the embedded driver.
> The repro case is uploaded as an attachment "testCSUpdateRowCommits.java".
> Output (repro case):
> updateRow() should not commit
> Value: 16, expected value 1. Should not have committed updateRow()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-611) Network client: updateRow() causes a commit when autoCommit = true
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-611?page=all ]
Dag H. Wanvik updated DERBY-611:
--------------------------------
Fix Version: 10.2.0.0
Version: 10.1.1.0
10.1.1.1
10.1.1.2
10.1.2.0
10.1.2.1
10.2.0.0
10.1.3.0
10.1.2.2
10.0.2.2
> Network client: updateRow() causes a commit when autoCommit = true
> ------------------------------------------------------------------
>
> Key: DERBY-611
> URL: http://issues.apache.org/jira/browse/DERBY-611
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0, 10.1.2.1, 10.2.0.0, 10.1.3.0, 10.1.2.2, 10.0.2.2
> Environment: Java Version: 1.5.0_01
> Java Vendor: Sun Microsystems Inc.
> Java home: /usr/jdk/instances/jdk1.5.0/jre
> Java classpath: classes
> OS name: SunOS
> OS architecture: x86
> OS version: 5.10
> Reporter: Fernanda Pizzorno
> Assignee: Dag H. Wanvik
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: 611.diff, 611.stat, testCSUpdateRowCommits.java
>
> On the network client driver, the ResultSet method updateRow makes the transaction commit, when autocommit is true. The correct behavior is to commit only when the result set is closed. This works correctly in the embedded driver.
> The repro case is uploaded as an attachment "testCSUpdateRowCommits.java".
> Output (repro case):
> updateRow() should not commit
> Value: 16, expected value 1. Should not have committed updateRow()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-611) Network client: updateRow() causes a commit when autoCommit = true
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-611?page=all ]
Dag H. Wanvik updated DERBY-611:
--------------------------------
Attachment: 611.diff
An updated diff, which removes a spurious blank line introduced by the
first version of the patch.
The reviewer (Bernt) asked for explanation of the removed usage of the
variable 'chainAutoCommit': It was used to be able to potentially
append an commit action onto the update/delete row action to be sent
to the server over DRDA, in the case that autocommit is in force, and
to anticipate a reply from that commit action. Since the intention of
the patch is to remove this commit, the variable is no longer in use
and has been removed.
> Network client: updateRow() causes a commit when autoCommit = true
> ------------------------------------------------------------------
>
> Key: DERBY-611
> URL: http://issues.apache.org/jira/browse/DERBY-611
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0, 10.1.2.1, 10.2.0.0, 10.1.3.0, 10.1.2.2, 10.0.2.2
> Environment: Java Version: 1.5.0_01
> Java Vendor: Sun Microsystems Inc.
> Java home: /usr/jdk/instances/jdk1.5.0/jre
> Java classpath: classes
> OS name: SunOS
> OS architecture: x86
> OS version: 5.10
> Reporter: Fernanda Pizzorno
> Assignee: Dag H. Wanvik
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: 611.diff, 611.stat, testCSUpdateRowCommits.java
>
> On the network client driver, the ResultSet method updateRow makes the transaction commit, when autocommit is true. The correct behavior is to commit only when the result set is closed. This works correctly in the embedded driver.
> The repro case is uploaded as an attachment "testCSUpdateRowCommits.java".
> Output (repro case):
> updateRow() should not commit
> Value: 16, expected value 1. Should not have committed updateRow()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-611) Network client: updateRow() causes a commit when autoCommit = true
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-611?page=comments#action_12357978 ]
Dag H. Wanvik commented on DERBY-611:
-------------------------------------
deleteRow has the same problem. In both cases (updateRow and deleteRow), there is explicit code
to make a commit happen is autocommit is on.
> Network client: updateRow() causes a commit when autoCommit = true
> ------------------------------------------------------------------
>
> Key: DERBY-611
> URL: http://issues.apache.org/jira/browse/DERBY-611
> Project: Derby
> Type: Bug
> Components: Network Client
> Environment: Java Version: 1.5.0_01
> Java Vendor: Sun Microsystems Inc.
> Java home: /usr/jdk/instances/jdk1.5.0/jre
> Java classpath: classes
> OS name: SunOS
> OS architecture: x86
> OS version: 5.10
> Reporter: Fernanda Pizzorno
> Priority: Minor
> Attachments: testCSUpdateRowCommits.java
>
> On the network client driver, the ResultSet method updateRow makes the transaction commit, when autocommit is true. The correct behavior is to commit only when the result set is closed. This works correctly in the embedded driver.
> The repro case is uploaded as an attachment "testCSUpdateRowCommits.java".
> Output (repro case):
> updateRow() should not commit
> Value: 16, expected value 1. Should not have committed updateRow()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-611) Network client: updateRow() causes a commit when autoCommit = true
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-611?page=all ]
Dag H. Wanvik updated DERBY-611:
--------------------------------
Attachment: 611.stat
611.diff
I have uploaded a fix for this problem (611.{stat,diff}), and added a
new test (look for "Positive Test34") to lang/updatableResultSet.java.
The network client driver canons are also changed in the case of three
error messages due to the changed behavior, in addition to the change
due to new test.
The patch removes the explicit (auto)commit code in the network client
driver in deleteRow and updateRow, making it behave as the embedded
driver in this respect (modulo error messages).
I have run lang/updatableResultSet.java successfully with Sun jdk 1.3,
1.4 and 1.5 (the two latter has another canon) on Solaris
10/x86. Also, there is a separate canon under j9_13 for this test,
which I have updated, but not been able to test.
I have also run derbyall successfully with jdk 1.4, also on Solaris
10/x86, albeit with some errors in unrelated tests (lang/dcl,
store/OnlineBackupTest1.java)
> Network client: updateRow() causes a commit when autoCommit = true
> ------------------------------------------------------------------
>
> Key: DERBY-611
> URL: http://issues.apache.org/jira/browse/DERBY-611
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0, 10.1.2.1, 10.2.0.0, 10.1.3.0, 10.1.2.2, 10.0.2.2
> Environment: Java Version: 1.5.0_01
> Java Vendor: Sun Microsystems Inc.
> Java home: /usr/jdk/instances/jdk1.5.0/jre
> Java classpath: classes
> OS name: SunOS
> OS architecture: x86
> OS version: 5.10
> Reporter: Fernanda Pizzorno
> Assignee: Dag H. Wanvik
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: 611.diff, 611.stat, testCSUpdateRowCommits.java
>
> On the network client driver, the ResultSet method updateRow makes the transaction commit, when autocommit is true. The correct behavior is to commit only when the result set is closed. This works correctly in the embedded driver.
> The repro case is uploaded as an attachment "testCSUpdateRowCommits.java".
> Output (repro case):
> updateRow() should not commit
> Value: 16, expected value 1. Should not have committed updateRow()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-611) Network client: updateRow() causes a commit when autoCommit = true
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-611?page=all ]
Dag H. Wanvik closed DERBY-611:
-------------------------------
> Network client: updateRow() causes a commit when autoCommit = true
> ------------------------------------------------------------------
>
> Key: DERBY-611
> URL: http://issues.apache.org/jira/browse/DERBY-611
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0, 10.1.2.1, 10.2.0.0, 10.1.3.0, 10.1.2.2, 10.0.2.2
> Environment: Java Version: 1.5.0_01
> Java Vendor: Sun Microsystems Inc.
> Java home: /usr/jdk/instances/jdk1.5.0/jre
> Java classpath: classes
> OS name: SunOS
> OS architecture: x86
> OS version: 5.10
> Reporter: Fernanda Pizzorno
> Assignee: Dag H. Wanvik
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: 611.diff.3, 611.stat.3, testCSUpdateRowCommits.java
>
> On the network client driver, the ResultSet method updateRow makes the transaction commit, when autocommit is true. The correct behavior is to commit only when the result set is closed. This works correctly in the embedded driver.
> The repro case is uploaded as an attachment "testCSUpdateRowCommits.java".
> Output (repro case):
> updateRow() should not commit
> Value: 16, expected value 1. Should not have committed updateRow()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-611) Network client: updateRow() causes a commit when autoCommit = true
Posted by "Fernanda Pizzorno (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-611?page=all ]
Fernanda Pizzorno updated DERBY-611:
------------------------------------
Attachment: testCSUpdateRowCommits.java
> Network client: updateRow() causes a commit when autoCommit = true
> ------------------------------------------------------------------
>
> Key: DERBY-611
> URL: http://issues.apache.org/jira/browse/DERBY-611
> Project: Derby
> Type: Bug
> Components: Network Client
> Environment: Java Version: 1.5.0_01
> Java Vendor: Sun Microsystems Inc.
> Java home: /usr/jdk/instances/jdk1.5.0/jre
> Java classpath: classes
> OS name: SunOS
> OS architecture: x86
> OS version: 5.10
> Reporter: Fernanda Pizzorno
> Priority: Minor
> Attachments: testCSUpdateRowCommits.java
>
> On the network client driver, the ResultSet method updateRow makes the transaction commit, when autocommit is true. The correct behavior is to commit only when the result set is closed. This works correctly in the embedded driver.
> The repro case is uploaded as an attachment "testCSUpdateRowCommits.java".
> Output (repro case):
> updateRow() should not commit
> Value: 16, expected value 1. Should not have committed updateRow()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-611) Network client: updateRow() causes a commit when autoCommit = true
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-611?page=all ]
Dag H. Wanvik updated DERBY-611:
--------------------------------
Attachment: 611.diff.3
611.stat.3
Uploaded a new version of the patch which adds an extra test case as
suggested by Mamta in this mail:
http://article.gmane.org/gmane.comp.apache.db.derby.devel/11222
> Network client: updateRow() causes a commit when autoCommit = true
> ------------------------------------------------------------------
>
> Key: DERBY-611
> URL: http://issues.apache.org/jira/browse/DERBY-611
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0, 10.1.2.1, 10.2.0.0, 10.1.3.0, 10.1.2.2, 10.0.2.2
> Environment: Java Version: 1.5.0_01
> Java Vendor: Sun Microsystems Inc.
> Java home: /usr/jdk/instances/jdk1.5.0/jre
> Java classpath: classes
> OS name: SunOS
> OS architecture: x86
> OS version: 5.10
> Reporter: Fernanda Pizzorno
> Assignee: Dag H. Wanvik
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: 611.diff.3, 611.stat.3, testCSUpdateRowCommits.java
>
> On the network client driver, the ResultSet method updateRow makes the transaction commit, when autocommit is true. The correct behavior is to commit only when the result set is closed. This works correctly in the embedded driver.
> The repro case is uploaded as an attachment "testCSUpdateRowCommits.java".
> Output (repro case):
> updateRow() should not commit
> Value: 16, expected value 1. Should not have committed updateRow()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-611) Network client: updateRow() causes a commit when autoCommit = true
Posted by "Bernt M. Johnsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-611?page=all ]
Bernt M. Johnsen resolved DERBY-611:
------------------------------------
Resolution: Fixed
> Network client: updateRow() causes a commit when autoCommit = true
> ------------------------------------------------------------------
>
> Key: DERBY-611
> URL: http://issues.apache.org/jira/browse/DERBY-611
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0, 10.1.2.1, 10.2.0.0, 10.1.3.0, 10.1.2.2, 10.0.2.2
> Environment: Java Version: 1.5.0_01
> Java Vendor: Sun Microsystems Inc.
> Java home: /usr/jdk/instances/jdk1.5.0/jre
> Java classpath: classes
> OS name: SunOS
> OS architecture: x86
> OS version: 5.10
> Reporter: Fernanda Pizzorno
> Assignee: Dag H. Wanvik
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: 611.diff.3, 611.stat.3, testCSUpdateRowCommits.java
>
> On the network client driver, the ResultSet method updateRow makes the transaction commit, when autocommit is true. The correct behavior is to commit only when the result set is closed. This works correctly in the embedded driver.
> The repro case is uploaded as an attachment "testCSUpdateRowCommits.java".
> Output (repro case):
> updateRow() should not commit
> Value: 16, expected value 1. Should not have committed updateRow()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-611) Network client: updateRow() causes a commit when autoCommit = true
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-611?page=all ]
Dag H. Wanvik reassigned DERBY-611:
-----------------------------------
Assign To: Dag H. Wanvik
> Network client: updateRow() causes a commit when autoCommit = true
> ------------------------------------------------------------------
>
> Key: DERBY-611
> URL: http://issues.apache.org/jira/browse/DERBY-611
> Project: Derby
> Type: Bug
> Components: Network Client
> Environment: Java Version: 1.5.0_01
> Java Vendor: Sun Microsystems Inc.
> Java home: /usr/jdk/instances/jdk1.5.0/jre
> Java classpath: classes
> OS name: SunOS
> OS architecture: x86
> OS version: 5.10
> Reporter: Fernanda Pizzorno
> Assignee: Dag H. Wanvik
> Priority: Minor
> Attachments: testCSUpdateRowCommits.java
>
> On the network client driver, the ResultSet method updateRow makes the transaction commit, when autocommit is true. The correct behavior is to commit only when the result set is closed. This works correctly in the embedded driver.
> The repro case is uploaded as an attachment "testCSUpdateRowCommits.java".
> Output (repro case):
> updateRow() should not commit
> Value: 16, expected value 1. Should not have committed updateRow()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-611) Network client: updateRow() causes a commit when autoCommit = true
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-611?page=all ]
Dag H. Wanvik updated DERBY-611:
--------------------------------
Attachment: (was: 611.diff)
> Network client: updateRow() causes a commit when autoCommit = true
> ------------------------------------------------------------------
>
> Key: DERBY-611
> URL: http://issues.apache.org/jira/browse/DERBY-611
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0, 10.1.2.1, 10.2.0.0, 10.1.3.0, 10.1.2.2, 10.0.2.2
> Environment: Java Version: 1.5.0_01
> Java Vendor: Sun Microsystems Inc.
> Java home: /usr/jdk/instances/jdk1.5.0/jre
> Java classpath: classes
> OS name: SunOS
> OS architecture: x86
> OS version: 5.10
> Reporter: Fernanda Pizzorno
> Assignee: Dag H. Wanvik
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: testCSUpdateRowCommits.java
>
> On the network client driver, the ResultSet method updateRow makes the transaction commit, when autocommit is true. The correct behavior is to commit only when the result set is closed. This works correctly in the embedded driver.
> The repro case is uploaded as an attachment "testCSUpdateRowCommits.java".
> Output (repro case):
> updateRow() should not commit
> Value: 16, expected value 1. Should not have committed updateRow()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira