[
https://issues.apache.org/jira/browse/DERBY-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
V.Narayanan updated DERBY-3384:
---
Attachment: Derby_3384_v1.stat
Derby_3384_v1.diff
startMaster now unfreezes the datab
[
https://issues.apache.org/jira/browse/DERBY-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland resolved DERBY-3361.
--
Resolution: Fixed
> Specifying a non-existant slaveHost for startSlave seemingly succeeds in
>
[
https://issues.apache.org/jira/browse/DERBY-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland reopened DERBY-3383:
--
A little too eager with this one - better leave the issue open until the patch
has been committed
[
https://issues.apache.org/jira/browse/DERBY-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland reassigned DERBY-3205:
Assignee: Jørgen Løland (was: V.Narayanan)
Assigning myself to this issue since I submitte
[
https://issues.apache.org/jira/browse/DERBY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-3117:
--
Attachment: d3117-concurrent.diff
Attaching d3117-concurrent.diff. This patch compiles
[
https://issues.apache.org/jira/browse/DERBY-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566992#action_12566992
]
V.Narayanan commented on DERBY-3358:
The boot method of the service module is called on
[
https://issues.apache.org/jira/browse/DERBY-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan closed DERBY-3369.
--
Test passes in the tinderbox test runs. Closing issue.
> Extend jdbcapi.DataSourceReferenceTest to
Support min/max values for Java types float/double in real/double columns
-
Key: DERBY-3398
URL: https://issues.apache.org/jira/browse/DERBY-3398
Project: Derby
Issue Ty
[
https://issues.apache.org/jira/browse/DERBY-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan closed DERBY-3324.
--
Resolution: Fixed
Closing this issue.
If something has to be fixed, it will be dealt with in a
[
https://issues.apache.org/jira/browse/DERBY-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567023#action_12567023
]
Jørgen Løland commented on DERBY-3358:
--
I don't think the problem is best solved by mo
[
https://issues.apache.org/jira/browse/DERBY-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John H. Embretsen updated DERBY-3385:
-
Attachment: TestJMXp9.java
Attaching a simple sample program, TestJMXp9.java, demonstrati
Daniel John Debrunner wrote:
Rick Hillegas wrote:
Daniel John Debrunner wrote:
Rick Hillegas wrote:
In order to use JMX to monitor/configure Derby (and other
applications), I think that the following is true:
DerbyNet-Admin => JMX-Admin
Engine-Admin => JMX-Admin
DB-Admin => JMX-Admin
OtherA
[Auto-generated mail]
*Daily* 619506/2008-02-07 18:01:01 MET
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
lin
0271271 072.08% derbyall
01018810188 0 1485.58% suitesAll
linN+1
[
https://issues.apache.org/jira/browse/DERBY-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A B resolved DERBY-3288.
Resolution: Fixed
Fix Version/s: 10.3.2.2
Committed d3288_10_3_merge.patch to 10.3 with svn # 619932:
URL
Hi,
I've been trying to run the Derby testsuites with EMMA to measure
codecoverage, and after troubling a little I have a few questions and
comments.
I hit some problems both with the old test harness and the new junit
testsuite in relation to the securitymanager. I haven't analyzed it
full
[
https://issues.apache.org/jira/browse/DERBY-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A B updated DERBY-3288:
---
Attachment: d3288_10_3_merge.patch
I ran the "svn merge" command to port this change back to 10.3, but the command
f
Issue Subscription
Filter: Derby: JIRA issues with patch available (19 issues)
Subscriber: derby-dev
Key Summary
DERBY-3383 Replication: stopSlave boots database?
https://issues.apache.org/jira/browse/DERBY-3383
DERBY-3359 The log shipper needs to be modified to vary the shi
[
https://issues.apache.org/jira/browse/DERBY-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567080#action_12567080
]
Øystein Grøvlen commented on DERBY-3383:
Code looks good.
One minor nit is that
Daniel John Debrunner wrote:
JohnHEmbretsen wrote:
* Let's simplify things by saying that MBeans have essentially two
states: ''enabled'' or ''disabled''
* An '''enabled''' (registered) MBean is visible/accessible to any
valid JMX user.
=== SystemMBean ===
* May be enabled only if
JohnHEmbretsen wrote:
* Let's simplify things by saying that MBeans have essentially two states:
''enabled'' or ''disabled''
* An '''enabled''' (registered) MBean is visible/accessible to any valid
JMX user.
=== SystemMBean ===
* May be enabled only if system-wide authentication
[
https://issues.apache.org/jira/browse/DERBY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567109#action_12567109
]
Rick Hillegas commented on DERBY-2109:
--
Hi Martin,
I have applied the 09 patch and ru
Rick Hillegas wrote:
Daniel John Debrunner wrote:
Rick Hillegas wrote:
Daniel John Debrunner wrote:
Rick Hillegas wrote:
In order to use JMX to monitor/configure Derby (and other
applications), I think that the following is true:
DerbyNet-Admin => JMX-Admin
Engine-Admin => JMX-Admin
DB-Adm
[
https://issues.apache.org/jira/browse/DERBY-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-2969:
-
Attachment: cadminhubbkup01.html
DERBY-2969-2.diff
Thanks very much for the advice, Jørge
[
https://issues.apache.org/jira/browse/DERBY-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567112#action_12567112
]
John H. Embretsen commented on DERBY-1387:
--
I'd like to take a step back and try t
Daniel John Debrunner wrote:
John Embretsen wrote:
Daniel John Debrunner wrote:
The SystemMBean section is really talking about if an attribute or
operation is visible or useable by a specific jmx-user, not if the
bean is enabled or not.
My intention was to talk about if the entire bean is
The automatic compile path property setting for the build system should be
expanded to handle Java SE 6 virtual machines.
-
Key: DERBY-3399
URL
Manjula Kutty wrote:
The getTypeInfo Fails with ibm16 while running the UpgradeTests. Here is
junit stack trace
1)
testGetTypeInfo(org.apache.derbyTesting.functionTests.tests.jdbcapi.DatabaseMetaDataTest)junit.framework.AssertionFailedError:
Column nullability do not match for column 16 expec
Removing a ConnectionEventListener from a PooledConnection during its
connectionClosed() callback causes other ConnectionEventListener callbacks to
be missed
---
[
https://issues.apache.org/jira/browse/DERBY-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567162#action_12567162
]
Kathey Marsden commented on DERBY-3399:
---
To build with IBM 1.6 I have to set:
java16c
testgetTypeInfo Fails with ibm16 while running the UpgradeTests
---
Key: DERBY-3400
URL: https://issues.apache.org/jira/browse/DERBY-3400
Project: Derby
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/DERBY-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567182#action_12567182
]
Manjula Kutty commented on DERBY-3400:
--
And here is the answer I got when I posted the
[
https://issues.apache.org/jira/browse/DERBY-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner closed DERBY-3391.
Resolution: Fixed
Fix Version/s: 10.4.0.0
Revision: 619981 in trunk removes
[
https://issues.apache.org/jira/browse/DERBY-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567206#action_12567206
]
Kathey Marsden commented on DERBY-3310:
---
So things seem to work ok without the assert
On 2/8/08, Daniel John Debrunner (JIRA) <[EMAIL PROTECTED]> wrote:
>
>[
> https://issues.apache.org/jira/browse/DERBY-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567209#action_12567209
> ]
>
> Daniel John Debrunner commented on DERBY-3400:
> -
[
https://issues.apache.org/jira/browse/DERBY-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567211#action_12567211
]
Kathey Marsden commented on DERBY-3400:
---
Does the problem occur with JIT turned off?
[
https://issues.apache.org/jira/browse/DERBY-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567162#action_12567162
]
kmarsden edited comment on DERBY-3399 at 2/8/08 11:04 AM:
T
[
https://issues.apache.org/jira/browse/DERBY-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567209#action_12567209
]
Daniel John Debrunner commented on DERBY-3400:
--
I think it is a jvm issue. The
Myrna van Lunteren wrote:
Hi,
As I was poking at the DataSourceTest recently, I noticed it doesn't
run with JSR169.
btw - I think this is a symptom of a bigger issue where a complete set
of fixtures from a test class is not run on J2ME even though only a
handful of features actually require
John Embretsen wrote:
Daniel John Debrunner wrote:
JohnHEmbretsen wrote:
* Let's simplify things by saying that MBeans have essentially two
states: ''enabled'' or ''disabled''
* An '''enabled''' (registered) MBean is visible/accessible to
any valid JMX user.
=== SystemMBean ===
*
> Note also that as Manjula reported, that it *doesn't* occur when
> running the DatabaseMetaDataTest against 10.4, only when running it in
> the upgrade tests against an older version.
>
> Myrna
>
I meant, when upgrading from an older version.
[
https://issues.apache.org/jira/browse/DERBY-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567026#action_12567026
]
Jørgen Løland commented on DERBY-3358:
--
Hang in master server if startMaster command i
[
https://issues.apache.org/jira/browse/DERBY-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julius Stroffek updated DERBY-2871:
---
Attachment: d2871.stat
d2871.diff
Dan, Knut: Thanks for catching this. I fixe
[
https://issues.apache.org/jira/browse/DERBY-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
R VIDYA LAKSHMI reassigned DERBY-2128:
--
Assignee: R VIDYA LAKSHMI
> The wrod class appears twice for the message SIF01.V
>
[
https://issues.apache.org/jira/browse/DERBY-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567204#action_12567204
]
Myrna van Lunteren commented on DERBY-3400:
---
Although this looks like a jvm issue
[
https://issues.apache.org/jira/browse/DERBY-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567132#action_12567132
]
Kristian Waagan commented on DERBY-3379:
I had a look at this one.
After some DRDA
[
https://issues.apache.org/jira/browse/DERBY-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567058#action_12567058
]
Øystein Grøvlen commented on DERBY-3359:
Thanks, for the patch Narayanan. I think
[
https://issues.apache.org/jira/browse/DERBY-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567247#action_12567247
]
Daniel John Debrunner commented on DERBY-3310:
--
In this *specific* case a cast
Hi,
As I was poking at the DataSourceTest recently, I noticed it doesn't
run with JSR169.
I wondered if it would make sense to make a minimalized version -
either to be extended by the DataSourceTest or to be run with JSR169
only.
I played with the idea some and am attaching a patch that has the
t
[
https://issues.apache.org/jira/browse/DERBY-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567247#action_12567247
]
djd edited comment on DERBY-3310 at 2/8/08 3:56 PM:
--
I
Myrna van Lunteren wrote:
Hi,
As I was poking at the DataSourceTest recently, I noticed it doesn't
run with JSR169.
I wondered if it would make sense to make a minimalized version -
either to be extended by the DataSourceTest or to be run with JSR169
only.
I played with the idea some and am atta
My (detail) comments and a few questions below.
Daniel John Debrunner wrote:
Rick Hillegas wrote:
For this mode to be enabled some changes are needed to DERBY-2109:
- Enforce Derby's security permissions if there is a security
manager (regardless of Derby's authentication state)
Like Ric
51 matches
Mail list logo
