[
https://issues.apache.org/jira/browse/DERBY-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3431:
---
Attachment: derby-3431-2a-test.diff
Patch 2a adds a new test to J2EEDataSourceTest. It
[
https://issues.apache.org/jira/browse/DERBY-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3431:
---
Derby Info: [Patch Available]
DatabaseMetaData.getConnection returns the wrong connection
[
https://issues.apache.org/jira/browse/DERBY-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590854#action_12590854
]
Bassel Kh commented on DERBY-2475:
--
Hello again,
1- I'm using only one class loader for
[
https://issues.apache.org/jira/browse/DERBY-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590858#action_12590858
]
Knut Anders Hatlen commented on DERBY-3087:
---
This could be the same problem as
[
https://issues.apache.org/jira/browse/DERBY-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590859#action_12590859
]
Knut Anders Hatlen commented on DERBY-2677:
---
This could be the same problem as
[
https://issues.apache.org/jira/browse/DERBY-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590861#action_12590861
]
Knut Anders Hatlen commented on DERBY-2475:
---
You mentioned that you have tested
[
https://issues.apache.org/jira/browse/DERBY-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590865#action_12590865
]
Kristian Waagan commented on DERBY-3397:
I'm running the existing regression tests,
Testresults for 10.4.1.2 are published at
http://dbtg.thresher.com/derby/test/
Tests have been run with jvm1.4, jvm1.5 and jvm1.6 on up to 28 different
OS platforms.
A summary-report will be published here:
http://dbtg.thresher.com/derby/test/10.4.1.2_RC/PublicTestReport.html
I have also
[
https://issues.apache.org/jira/browse/DERBY-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590894#action_12590894
]
Knut Anders Hatlen commented on DERBY-3619:
---
Committed lob.diff with revision
[
https://issues.apache.org/jira/browse/DERBY-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590896#action_12590896
]
Kristian Waagan commented on DERBY-3397:
All tests ran without failures (revision
[
https://issues.apache.org/jira/browse/DERBY-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590907#action_12590907
]
Michael Lossos commented on DERBY-3397:
---
FYI I wrote the repro case in a way that
Docs for attribute slaveHost should say what the attribute means when used with
startSlave=true
---
Key: DERBY-3637
URL: https://issues.apache.org/jira/browse/DERBY-3637
[
https://issues.apache.org/jira/browse/DERBY-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590921#action_12590921
]
John H. Embretsen commented on DERBY-3417:
--
During buddy testing I noticed a
[
https://issues.apache.org/jira/browse/DERBY-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590922#action_12590922
]
Tomohito Nakayama commented on DERBY-3402:
--
After 2 monthes, those png files seem
[
https://issues.apache.org/jira/browse/DERBY-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590926#action_12590926
]
Tomohito Nakayama commented on DERBY-3402:
--
Committed.
[EMAIL
[
https://issues.apache.org/jira/browse/DERBY-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590929#action_12590929
]
Tomohito Nakayama commented on DERBY-3402:
--
Updated.
[EMAIL PROTECTED]
java/testing/Readme.htm location of derbyTesting.jar
Key: DERBY-3638
URL: https://issues.apache.org/jira/browse/DERBY-3638
Project: Derby
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/DERBY-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svein Erik Løvland updated DERBY-3638:
--
Attachment: patch_tstjardir_jardir.txt
Hope I made the patch correctly.
[
https://issues.apache.org/jira/browse/DERBY-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590936#action_12590936
]
Tomohito Nakayama commented on DERBY-3402:
--
The latest version manuals seem to be
Issue Subscription
Filter: Derby: JIRA issues with patch available (6 issues)
Subscriber: derby-dev
Key Summary
DERBY-3638 java/testing/Readme.htm location of derbyTesting.jar
https://issues.apache.org/jira/browse/DERBY-3638
DERBY-3397 Derby 10.3.1.4 and 10.3.2.1 break
[
https://issues.apache.org/jira/browse/DERBY-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590945#action_12590945
]
Tomohito Nakayama commented on DERBY-3402:
--
Done.
[EMAIL PROTECTED]
[Auto-generated mail]
*Daily* 649942/2008-04-20 18:01:01 MEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
lin
0269269 080.97% derbyall
099119911 0 1328.38% suitesAll
sles
NA
I don't know if this is a problem or not. The NetworkServer-ping()
operation through jconsole does not work with the
default security manager. The error you see in the network server
console is below. Is this a problem (Should the default
security policy allow the operation)? or is it
On Windows I am working my way through
http://wiki.apache.org/db-derby/DerbyJMXQuickStart
I am on the example
Example: Enabling Remote JMX, password authentication, no SSL
I found that to get the server to get the start command to work cleanly
I needed to change the permissions on
Kathey Marsden wrote:
On Windows I am working my way through
http://wiki.apache.org/db-derby/DerbyJMXQuickStart
I am on the example
Example: Enabling Remote JMX, password authentication, no SSL
I found that to get the server to get the start command to work
cleanly I needed to
[
https://issues.apache.org/jira/browse/DERBY-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-1201:
--
Derby Info: [Patch Available]
ResultSet.updateRow() in network client should not throw an
Thanks for trying out the new feature, Kathey!
Kathey Marsden wrote:
I don't know if this is a problem or not. The NetworkServer-ping()
operation through jconsole does not work with the
default security manager. The error you see in the network server
console is below. Is this a problem
John H. Embretsen wrote:
the permission will have to be
set for a wildcard address (*) even if it is only pinging itself on the
loopback interface.
I'd say leave it as is then. It's not worth opening up a potential
security hole.
Kathey
Kathey Marsden wrote:
Kathey Marsden wrote:
On Windows I am working my way through
http://wiki.apache.org/db-derby/DerbyJMXQuickStart
I am on the example
Example: Enabling Remote JMX, password authentication, no SSL
I found that to get the server to get the start command to work
[
https://issues.apache.org/jira/browse/DERBY-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tiago R. Espinha updated DERBY-3623:
Attachment: (was: DeadlockModeTest.java)
Convert deadlockMode.java to JUnit
[
https://issues.apache.org/jira/browse/DERBY-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tiago R. Espinha updated DERBY-3623:
Attachment: derby3623.patch
Convert deadlockMode.java to JUnit
[
https://issues.apache.org/jira/browse/DERBY-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591030#action_12591030
]
Tiago R. Espinha commented on DERBY-3623:
-
Added a patch for the following:
-
On Fri, Apr 18, 2008 at 10:56 AM, Mamta Satoor [EMAIL PROTECTED] wrote:
Hope this is not confusing and some one can tell me why Jira is not is
sync with subversion.
Because revprop changes are not applied as a new commit, I believe
that changes to old revision log statements will not appear
Thanks for your reply, Andrew.
Mamta
On 4/21/08, Andrew McIntyre [EMAIL PROTECTED] wrote:
On Fri, Apr 18, 2008 at 10:56 AM, Mamta Satoor [EMAIL PROTECTED] wrote:
Hope this is not confusing and some one can tell me why Jira is not is
sync with subversion.
Because revprop changes are
Hi.
I'm working on *DERBY-3618https://issues.apache.org/jira/browse/DERBY-3618
* and I can't figure out how to print to derby.log. Is there an easy way to
get hold of the PrintWriter for the log?
Thanks.
-Erlend
**
Hi Erlend,
I'm not sure about this, but I believe you can do so with the following
code:
PrintWriter logWriter = Monitor.getStream().getPrintWriter();
and you need this:
import org.apache.derby.iapi.services.monitor.Monitor;
Regards,
Tiago
On Mon, Apr 21, 2008 at 9:59 PM, Erlend Birkenes
[
https://issues.apache.org/jira/browse/DERBY-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591071#action_12591071
]
Kathey Marsden commented on DERBY-1201:
---
I verified your fix with the repro, but am
[
https://issues.apache.org/jira/browse/DERBY-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton reassigned DERBY-3613:
--
Assignee: Bryan Pendleton
SELECT DISTINCT field FROM TABLE_NAME GROUP BY field,
[
https://issues.apache.org/jira/browse/DERBY-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591082#action_12591082
]
Kathey Marsden commented on DERBY-3623:
---
Need to remove master/deadlockMode.out.
[
https://issues.apache.org/jira/browse/DERBY-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591089#action_12591089
]
Kathey Marsden commented on DERBY-3623:
---
The core exception seems to be:
[
https://issues.apache.org/jira/browse/DERBY-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591082#action_12591082
]
kmarsden edited comment on DERBY-3623 at 4/21/08 3:57 PM:
[
https://issues.apache.org/jira/browse/DERBY-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-3623:
--
Attachment: ThreadTest.java
I made this quick test to see what happens with asserts in spawned
[
https://issues.apache.org/jira/browse/DERBY-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-3613:
---
Derby Info: [Patch Available]
SELECT DISTINCT field FROM TABLE_NAME GROUP BY field, field2
[
https://issues.apache.org/jira/browse/DERBY-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-3613:
---
Attachment: dontGenerateForDistinct.diff
Attached is 'dontGenerateForDistinct.diff', a patch
I am taking the liberty to copy Dyre's email on Feb 29th '08 about how
to print into log file
On the server, you can use the Monitor.logMessage system to write
messages directly to derby.log. You can also use the
SanityManager.DEBUG_ON(mydebugflag) predicate if you only want to/need
to see the
[
https://issues.apache.org/jira/browse/DERBY-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591205#action_12591205
]
Mamta A. Satoor commented on DERBY-1201:
It will be great if someone else can also
46 matches
Mail list logo
