[
https://issues.apache.org/jira/browse/DERBY-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-4201.
---
Resolution: Fixed
Fix Version/s: 10.9.0.0
Committed revision 1210846.
I
[
https://issues.apache.org/jira/browse/DERBY-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-5520.
---
Resolution: Duplicate
Resolving as a duplicate of DERBY-4201. Please reopen or file
[
https://issues.apache.org/jira/browse/DERBY-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-5518.
---
Resolution: Duplicate
Resolving as a duplicate of DERBY-4201. Please reopen or file
[
https://issues.apache.org/jira/browse/DERBY-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-4265.
---
Resolution: Duplicate
Resolving as a duplicate of DERBY-4201. Please reopen or file
[
https://issues.apache.org/jira/browse/DERBY-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-4914.
---
Resolution: Duplicate
Resolving as a duplicate of DERBY-4201. Please reopen or file
[
https://issues.apache.org/jira/browse/DERBY-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-5194.
---
Resolution: Duplicate
Resolving as a duplicate of DERBY-4201. Please reopen or file
[Auto-generated mail]
*tinderbox_trunk16* 1210846/2011-12-06 11:22:06 CET
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
022 0 0.00%
The JVM that derby was running in crashed with a SEGV. There application
server also went down. When I brought both up, the database shows two XA
transactions in the PREPARE state (looking at syscs_diag.transaction_table) but
the application server has no reference to these transactions to
Bergquist, Brett bbergqu...@canoga.com writes:
The JVM that derby was running in crashed with a SEGV. There
application server also went down. When I brought both up, the
database shows two XA transactions in the PREPARE state (looking at
syscs_diag.transaction_table) but the application
[
https://issues.apache.org/jira/browse/DERBY-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren reopened DERBY-1016:
---
Reopening because this check in caused a test failure in
jdbcapi/xaSimpleNegative.sql:
[
https://issues.apache.org/jira/browse/DERBY-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-866:
Attachment: UserManagement.html
Attaching a third rev of UserManagement.html. This version fills in
Document the NATIVE authentication scheme.
--
Key: DERBY-5522
URL: https://issues.apache.org/jira/browse/DERBY-5522
Project: Derby
Issue Type: Improvement
Components: Documentation
I will give this a try and that is exactly what I was just trying to write.
This is the second time in about 5 years that this has happened :( I need to
get away from using XA but the application server was bitching without it.
Thank you for your help on this. It would have taken me much
[
https://issues.apache.org/jira/browse/DERBY-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren resolved DERBY-1016.
---
Resolution: Fixed
It seems to me the diff in the failing xaSimpleNegative test was
The database has the following transactions being show from querying
syscs_diag.transaction_table:
NPCAcv# sh /opt/csem/canogaview/app/scripts/solaris/gettrans.sh
ij version 10.8
ij ij XID|GLOBAL_XID
[Auto-generated mail]
*Daily* 1210529/2011-12-05 18:00:08 MET
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.7*
lin
NA NA NANA suitesAll
NA NA NANA jdbcapiAutoLoad
NA
I need a test program to get the database into this same state. I have tried
the following in attempt to get the database into the state. If I query
syscs_diag.transaction_table, I see
but if I restart the database service, the ACTIVE transaction is no longer
present. So it seems that this
In a previous email I discussed that I have a database with 44 XA transactions
in the ACTIVE state associated with no connections. In trying to find out the
cause and a possible solution, I tried writing a test case that would put the
database into the same state. Below is the code to get the
[
https://issues.apache.org/jira/browse/DERBY-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164012#comment-13164012
]
Dag H. Wanvik commented on DERBY-4201:
--
Clean patch, looks good to me! +1.
Good to
[
https://issues.apache.org/jira/browse/DERBY-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-5519:
-
Issue fix info: Known fix (was: Patch Available,Known fix)
Fix Version/s: 10.9.0.0
[
https://issues.apache.org/jira/browse/DERBY-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik resolved DERBY-5519.
--
Resolution: Fixed
Update code in JVMInfo#derbyVMLevel to give correct results for Java 7
[
https://issues.apache.org/jira/browse/DERBY-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164035#comment-13164035
]
Dag H. Wanvik commented on DERBY-5519:
--
Committed as svn 1211257.
[
https://issues.apache.org/jira/browse/DERBY-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik resolved DERBY-5521.
--
Resolution: Fixed
Fix Version/s: 10.9.0.0
Issue fix info: (was: Patch
More testing and more information.
If using a connection with no timeout starts an XA transaction with
xaRes.start(xid, XAResource.TMNOFLAGS);
and some work is done but the application fails without calling
xaRes.end(xid, XAResource.TMSUCCESS)
then another application cannot join
[
https://issues.apache.org/jira/browse/DERBY-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-5521:
-
Attachment: derby-5521.diff
Thanks, Knut. Committed derby-5521b taking that advice as svn
[
https://issues.apache.org/jira/browse/DERBY-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-5521:
-
Attachment: (was: derby-5521.diff)
JDBCMBeanTest#testAttributeDriverLevel uses Java
[
https://issues.apache.org/jira/browse/DERBY-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-5521:
-
Attachment: derby-5521b.diff
JDBCMBeanTest#testAttributeDriverLevel uses Java assert in
[
https://issues.apache.org/jira/browse/DERBY-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164055#comment-13164055
]
Dag H. Wanvik commented on DERBY-5521:
--
Not suitable for backport, bug introduced
[
https://issues.apache.org/jira/browse/DERBY-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik closed DERBY-5521.
JDBCMBeanTest#testAttributeDriverLevel uses Java assert in lieu of JUnit
assert: no real
XA Transactions can becomes stuck if a connection from a XAResource without a
timeout terminates after performing work but before ending
Key:
[
https://issues.apache.org/jira/browse/DERBY-5523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Bergquist updated DERBY-5523:
---
Description:
If using a connection with no timeout starts an XA transaction with
[
https://issues.apache.org/jira/browse/DERBY-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164165#comment-13164165
]
Mamta A. Satoor commented on DERBY-4631:
I debugged the code to figure out what
32 matches
Mail list logo
