[
https://issues.apache.org/jira/browse/DERBY-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen closed DERBY-4904.
-
Resolution: Fixed
Fix Version/s: 10.8.0.0
10.7.1.1
All the
Myrna van Lunteren wrote:
On Mon, Nov 15, 2010 at 1:42 PM, Kathey Marsden
kmarsdende...@sbcglobal.net wrote:
On 11/15/2010 1:31 PM, Myrna van Lunteren wrote:
If this artifact doesn't change much, would it make sense to check it
into
the Derby codeline?
I don't have a hard
Issue Subscription
Filter: Derby: JIRA issues with patch available (5 issues)
Subscriber: derby-dev
Key Summary
DERBY-4741 Make Derby work reliably in the presence of thread interrupts
https://issues.apache.org/jira/browse/DERBY-4741
DERBY-4897 Get rid of warning for
[
https://issues.apache.org/jira/browse/DERBY-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932464#action_12932464
]
Knut Anders Hatlen commented on DERBY-4874:
---
Thanks for making the changes,
[
https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-2573:
-
Attachment: derby-2573-12-aa-eclipse_ui_doc_plugin.diff
Attaching
[
https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932485#action_12932485
]
Rick Hillegas commented on DERBY-2573:
--
Backported 1035647 from trunk to 10.7 branch
On 16.11.10 14:47, Bergquist, Brett wrote:
I am using Derby as a database as part of a Glassfish installation. I
am processing JMS messages with each one causing access to the Derby
database via Eclipselink. After about 80K to 100K messages processed,
I have a hung system.
I run jstack
[
https://issues.apache.org/jira/browse/DERBY-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-4771:
---
Component/s: Store
SQL
Issue fix info: [Patch Available]
[
https://issues.apache.org/jira/browse/DERBY-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-4771:
---
Attachment: derby-4771-2d-prototype_lcc_code_dump.diff
Attached patch 2d: 18 files changed,
Okay, thanks for the feedback. Just a little more info. I was using the XA
client driver. I am now trying try reproduce with just the standard local
client driver to see if this makes a difference. I don't actually need the
distributed transaction support at this time.
Also, here is the
On 16.11.10 16:27, Bergquist, Brett wrote:
Okay, thanks for the feedback. Just a little more info. I was using the XA
client driver. I am now trying try reproduce with just the standard local
client driver to see if this makes a difference. I don't actually need the
distributed
Thanks again. The network server trace was after I could not connect with any
client and I did not look closely at it ;) Before that point, there was a
thread that looked like:
NetworkServerThread_2 prio=6 tid=0x030fc800 nid=0x121c runnable
[0x0357f000..0x0357fa94]
java.lang.Thread.State:
[Auto-generated mail]
*Daily* 1035352/2010-11-15 18:00:27 MET
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
lin
01308413084 0 1383.92% suitesAll
01313 0 .% jdbcapiAutoLoad
0
[
https://issues.apache.org/jira/browse/DERBY-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-4855:
-
Attachment: derby-4855-05-aa-cliXconf.diff
Attaching derby-4855-05-aa-cliXconf.diff. This patch
[
https://issues.apache.org/jira/browse/DERBY-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932543#action_12932543
]
Rick Hillegas edited comment on DERBY-4855 at 11/16/10 12:26 PM:
[
https://issues.apache.org/jira/browse/DERBY-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932546#action_12932546
]
Rick Hillegas commented on DERBY-4855:
--
Ported 1035700 from trunk to 10.7 branch at
test failure in teardown (removeDir) related to testSQLRoles
Key: DERBY-4905
URL: https://issues.apache.org/jira/browse/DERBY-4905
Project: Derby
Issue Type: Bug
A follow up. The only change that I made to the system was to replace
org.apache.derby.jdbc.ClientXADataSource ass the Datasource Classname and
javax.sql.XADataSource to org.apache.derby.jdbc.ClientDataSource and
javax.sql.DataSource respectively through the Glassfish Application Server's
[
https://issues.apache.org/jira/browse/DERBY-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Closson closed DERBY-4697.
--
Resolution: Not A Problem
We switched from derby to another database. So its not a problem
On 11/12/2010 7:53 AM, Rick Hillegas wrote:
Thank you Rick for your work on the release and Derby in general and
sharing your thoughts on testing and releases. I've been thinking about
what you said and thought I would share a few of my own thoughts below.
Buddy-testing = Integration test
[
https://issues.apache.org/jira/browse/DERBY-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lily Wei updated DERBY-4856:
Attachment: derby.log
derby-4856-1a.diff
Thanks to Kathey. I am able to construct first
[
https://issues.apache.org/jira/browse/DERBY-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932806#action_12932806
]
Lily Wei commented on DERBY-4856:
-
The changes included:
1. Move ThreadDump.java from
22 matches
Mail list logo
