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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2010/08/30 15:21:54 UTC
[jira] Created: (DERBY-4785) Remove JCC tests and references to JCC
in test code
Remove JCC tests and references to JCC in test code
---------------------------------------------------
Key: DERBY-4785
URL: https://issues.apache.org/jira/browse/DERBY-4785
Project: Derby
Issue Type: Sub-task
Components: Test
Affects Versions: 10.6.1.0, 10.5.1.1
Reporter: Kathey Marsden
Priority: Minor
I received a request to remove JCC testing from the derby suite. The user had a very old jcc version in their classpath 2.4 and 10.5 tests were failing with:
com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -1, SQLSTATE: XJ040, SQLERRMC: Failed to start database '/results/axxon/58712/laka10a-derby-m101-20100830-003810/derbyall/derbynetmats/DerbyNet/derbynetmats/dblook_test_net_territory//wombat', see the next exception for details.::SQLSTATE: XJ001Java exception: 'Access denied (java.util.PropertyPermission com.ibm.crypto.provider.FIPSMODE read): java.security.AccessControlException'.
at com.ibm.db2.jcc.c.o.a(o.java:3219)
at com.ibm.db2.jcc.a.cb.q(cb.java:653)
at com.ibm.db2.jcc.a.cb.p(cb.java:541)
at com.ibm.db2.jcc.a.cb.l(cb.java:363)
at com.ibm.db2.jcc.a.cb.d(cb.java:145)
at com.ibm.db2.jcc.a.b.Sb(b.java:1274)
at com.ibm.db2.jcc.a.b.a(b.java:1166)
at com.ibm.db2.jcc.a.b.q(b.java:934)
at com.ibm.db2.jcc.a.b.a(b.java:702)
at com.ibm.db2.jcc.a.b.(b.java:305)
at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:162)
at java.sql.DriverManager.getConnection(DriverManager.java:322)
at java.sql.DriverManager.getConnection(DriverManager.java:273)
at org.apache.derby.tools.dblook.go(Unknown Source)
at org.apache.derby.tools.dblook.(Unknown Source)
at org.apache.derbyTesting.functionTests.tests.tools.dblook_test.lookThree(dblook_test.java:417)
at org.apache.derbyTesting.functionTests.tests.tools.dblook_test.runTest(dblook_test.java:283)
at org.apache.derbyTesting.functionTests.tests.derbynet.dblook_test_net_territory.doTest(dblook_test_net_territory.java:65)
at org.apache.derbyTesting.functionTests.tests.derbynet.dblook_test_net_territory.main(dblook_test_net_territory.java:41)
Now that I look at it more closely, their actual problem might be on the server side and JCC just reporting it but good to get the JCC tests out of the mix when people accidentally have it in their classpath anyway.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Posted by Myrna van Lunteren <m....@gmail.com>.
On Thu, Dec 2, 2010 at 8:44 PM, Jayaram Subramanian <rs...@gmail.com> wrote:
> Hi All,
> When i tried running java
> org.apache.derbyTesting.functionTests.harness.RunSuite derbyall i saw
> the following error in derbyall.sum file. Could you please help me and
> let me know how to work around this
>
> ERROR XJ041: Failed to create database 'wombat', see the next
> exception for details.
> ERROR XSLAT: The log directory 'extinout\wierdlog\log' exists. The
> directory might belong to another database. Check that the location
> specified for the logDevice attribute is correct.
>
> With Regards
> Jayaram
>
Hi Jayaram,
The .sum file isn't a good indication of success or fail; it's more of
a running commentary. Did any test actually fail?
That said, I don't see that diff. I think maybe you didn't start the
test in a clean directory? Although the tests should try to remove old
files, it doesn't do this properly.
If you did start in a clean directory, please tell us which test
failed (in derbyall_fail.txt)?
Myrna
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references
to JCC in test code
Posted by Kathey Marsden <km...@sbcglobal.net>.
On 12/27/2010 10:27 AM, Jayaram Subramanian wrote:
> Thanks all for your reply. When i try running "
> java org.apache.derbyTesting.functionTests.harness.RunTest
> unit/T_RawStoreFactory.unit", i see the following in derby.log
>
> With Regards
> Jayaram
>
>
> [main] FAIL - org.apache.derby.shared.common.sanity.AssertFailure:
> ASSERT FAILED There should be 0 observers, but we still have 1
> observers.
> org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED
> There should be 0 observers, but we still have 1 observers.
> at
Yes that loks like DERBY-3993. It is fine to go ahead and post your patch.
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Posted by Jayaram Subramanian <rs...@gmail.com>.
Thanks all for your reply. When i try running "
java org.apache.derbyTesting.functionTests.harness.RunTest
unit/T_RawStoreFactory.unit", i see the following in derby.log
With Regards
Jayaram
[main] FAIL - org.apache.derby.shared.common.sanity.AssertFailure:
ASSERT FAILED There should be 0 observers, but we still have 1
observers.
org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED
There should be 0 observers, but we still have 1 observers.
at org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:162)
at org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:147)
at org.apache.derby.impl.store.raw.xact.Xact.doComplete(Xact.java:1969)
at org.apache.derby.impl.store.raw.xact.Xact.preComplete(Xact.java:1925)
at org.apache.derby.impl.store.raw.xact.Xact.prepareCommit(Xact.java:769)
at org.apache.derby.impl.store.raw.xact.Xact.commit(Xact.java:882)
at org.apache.derby.impl.store.raw.xact.Xact.commit(Xact.java:679)
at org.apache.derbyTesting.unitTests.store.T_Util.t_commit(T_Util.java:840)
at org.apache.derbyTesting.unitTests.store.T_RawStoreFactory.TC001(T_RawStoreFactory.java:7310)
at org.apache.derbyTesting.unitTests.store.T_RawStoreFactory.runTempTests(T_RawStoreFactory.java:417)
at org.apache.derbyTesting.unitTests.store.T_RawStoreFactory.runTestSet(T_RawStoreFactory.java:248)
at org.apache.derbyTesting.unitTests.harness.T_MultiIterations.runTests(T_MultiIterations.java:95)
at org.apache.derbyTesting.unitTests.harness.T_MultiThreadedIterations.runTests(T_MultiThreadedIterations.java:92)
at org.apache.derbyTesting.unitTests.harness.T_Generic.Execute(T_Generic.java:118)
at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.runATest(BasicUnitTestManager.java:184)
at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.runTests(BasicUnitTestManager.java:246)
at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.boot(BasicUnitTestManager.java:93)
at org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java:2021)
at org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:333)
at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1858)
at org.apache.derby.impl.services.monitor.BaseMonitor.startServices(BaseMonitor.java:997)
at org.apache.derby.impl.services.monitor.BaseMonitor.runWithState(BaseMonitor.java:429)
at org.apache.derby.impl.services.monitor.FileMonitor.<init>(FileMonitor.java:60)
at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:289)
at org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:51)
---------------
Stack traces for all live threads:
Thread name=derby.rawStoreDaemon id=15 priority=5 state=TIMED_WAITING
isdaemon=true
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:196)
org.apache.derby.impl.services.daemon.BasicDaemon.rest(BasicDaemon.java:571)
org.apache.derby.impl.services.daemon.BasicDaemon.run(BasicDaemon.java:388)
java.lang.Thread.run(Thread.java:736)
Thread name=JIT Compilation Thread id=4 priority=10 state=RUNNABLE isdaemon=true
Thread name=Finalizer thread id=9 priority=5 state=RUNNABLE isdaemon=true
Thread name=Attach handler id=6 priority=6 state=RUNNABLE isdaemon=true
com.ibm.tools.attach.javaSE.IPC.waitSemaphore(Native Method)
com.ibm.tools.attach.javaSE.CommonDirectory.waitSemaphore(CommonDirectory.java:252)
com.ibm.tools.attach.javaSE.AttachHandler.waitForNotification(AttachHandler.java:282)
com.ibm.tools.attach.javaSE.AttachHandler.run(AttachHandler.java:203)
Thread name=derby.antiGC id=8 priority=1 state=WAITING isdaemon=true
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:167)
org.apache.derby.impl.services.monitor.AntiGC.run(BaseMonitor.java:2219)
java.lang.Thread.run(Thread.java:736)
Thread name=Signal Dispatcher id=2 priority=5 state=RUNNABLE isdaemon=true
com.ibm.misc.SignalDispatcher.waitForSignal(Native Method)
com.ibm.misc.SignalDispatcher.run(SignalDispatcher.java:54)
Thread name=Thread-4 id=10 priority=5 state=WAITING isdaemon=true
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:167)
java.util.Timer$TimerImpl.run(Timer.java:226)
Thread name=Thread-8 id=14 priority=5 state=TIMED_WAITING isdaemon=true
java.lang.Thread.sleep(Native Method)
java.lang.Thread.sleep(Thread.java:851)
org.apache.derbyTesting.unitTests.harness.T_Bomb.run(T_Bomb.java:105)
java.lang.Thread.run(Thread.java:736)
Thread name=Gc Slave Thread id=5 priority=5 state=RUNNABLE isdaemon=true
Thread name=main id=1 priority=5 state=RUNNABLE isdaemon=false
java.lang.Thread.getStackTraceImpl(Native Method)
java.lang.Thread.getStackTrace(Thread.java:1042)
java.lang.Thread.getAllStackTraces(Thread.java:1070)
org.apache.derby.shared.common.sanity.ThreadDump.getStackDumpString(ThreadDump.java:34)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:600)
org.apache.derby.shared.common.sanity.AssertFailure$1.run(AssertFailure.java:165)
java.security.AccessController.doPrivileged(AccessController.java:251)
org.apache.derby.shared.common.sanity.AssertFailure.dumpThreads(AssertFailure.java:159)
org.apache.derby.shared.common.sanity.AssertFailure.<init>(AssertFailure.java:72)
org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:162)
org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:147)
org.apache.derby.impl.store.raw.xact.Xact.doComplete(Xact.java:1969)
org.apache.derby.impl.store.raw.xact.Xact.preComplete(Xact.java:1925)
org.apache.derby.impl.store.raw.xact.Xact.prepareCommit(Xact.java:769)
org.apache.derby.impl.store.raw.xact.Xact.commit(Xact.java:882)
org.apache.derby.impl.store.raw.xact.Xact.commit(Xact.java:679)
org.apache.derbyTesting.unitTests.store.T_Util.t_commit(T_Util.java:840)
org.apache.derbyTesting.unitTests.store.T_RawStoreFactory.TC001(T_RawStoreFactory.java:7310)
org.apache.derbyTesting.unitTests.store.T_RawStoreFactory.runTempTests(T_RawStoreFactory.java:417)
org.apache.derbyTesting.unitTests.store.T_RawStoreFactory.runTestSet(T_RawStoreFactory.java:248)
org.apache.derbyTesting.unitTests.harness.T_MultiIterations.runTests(T_MultiIterations.java:95)
org.apache.derbyTesting.unitTests.harness.T_MultiThreadedIterations.runTests(T_MultiThreadedIterations.java:92)
org.apache.derbyTesting.unitTests.harness.T_Generic.Execute(T_Generic.java:118)
org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.runATest(BasicUnitTestManager.java:184)
org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.runTests(BasicUnitTestManager.java:246)
org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.boot(BasicUnitTestManager.java:93)
org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java:2021)
org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:333)
org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1858)
org.apache.derby.impl.services.monitor.BaseMonitor.startServices(BaseMonitor.java:997)
org.apache.derby.impl.services.monitor.BaseMonitor.runWithState(BaseMonitor.java:429)
org.apache.derby.impl.services.monitor.FileMonitor.<init>(FileMonitor.java:60)
org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:289)
org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:51)
Thread name=MemoryPoolMXBean notification dispatcher id=12 priority=6
state=RUNNABLE isdaemon=true
com.ibm.lang.management.MemoryNotificationThread.processNotificationLoop(Native
Method)
com.ibm.lang.management.MemoryNotificationThread.run(MemoryNotificationThread.java:55)
---------------
On Mon, Dec 20, 2010 at 7:57 AM, Kathey Marsden
<km...@sbcglobal.net> wrote:
> On 12/11/2010 8:02 AM, Jayaram Subramanian wrote:
>>
>> Hi All,
>> Thanks for your reply.. When i run DerbyAll from a clean folder I dont
>> see any errors in derbyall.sum file..
>>
>> But in derbyall.fail file i see the following
>> ----------------------------------------------------------
>> derbyall/storeall/storeall.fail:unit/T_RawStoreFactory.unit
>
> Hello Jayaram,
>
> If you look at the derby.log, does it look like this failure?
>
> https://issues.apache.org/jira/browse/DERBY-3993
>
>
>
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references
to JCC in test code
Posted by Kathey Marsden <km...@sbcglobal.net>.
On 12/11/2010 8:02 AM, Jayaram Subramanian wrote:
> Hi All,
> Thanks for your reply.. When i run DerbyAll from a clean folder I dont
> see any errors in derbyall.sum file..
>
> But in derbyall.fail file i see the following
> ----------------------------------------------------------
> derbyall/storeall/storeall.fail:unit/T_RawStoreFactory.unit
Hello Jayaram,
If you look at the derby.log, does it look like this failure?
https://issues.apache.org/jira/browse/DERBY-3993
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references
to JCC in test code
Posted by Bryan Pendleton <bp...@gmail.com>.
> standalone file called RawStoreFactory.unit.. and when i try running
> java org.apache.derbyTesting.functionTests.harness.RunTestunit/T_RawStoreFactory.unit,
> I am getting a classnotfound exception
Was that the exact statement you tried? If so, there is a space missing
between "RunTest" (the name of the class to run), and "unit/..." (the argument
to that class).
Try:
java org.apache.derbyTesting.functionTests.harness.RunTest unit/T_RawStoreFactory.unit
thanks,
bryan
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Posted by Jayaram Subramanian <rs...@gmail.com>.
Hi,
Thanks for your reply.. But unfortunately i couldnt find any
standalone file called RawStoreFactory.unit.. and when i try running
java org.apache.derbyTesting.functionTests.harness.RunTestunit/T_RawStoreFactory.unit,
I am getting a classnotfound exception
Wit Regards
Jayaram
On Wed, Dec 15, 2010 at 12:29 PM, Myrna van Lunteren
<m....@gmail.com> wrote:
> On Tue, Dec 14, 2010 at 7:36 PM, Jayaram Subramanian
> <rs...@gmail.com> wrote:
>> Hi All,
>> I see the following in the T_RawStoreFactory.diff file.. Please let me
>> know any corrective actions if required in my setup..
>> *** Start: T_RawStoreFactory jdk1.6.0 storeall:storeunit 2010-12-06 23:08:36 ***
>> 2 del
>> < -- Unit Test T_RawStoreFactory finished
>> 2 add
>>> Shutting down due to unit test failure.
>> Test Failed.
>> *** End: T_RawStoreFactory jdk1.6.0 storeall:storeunit 2010-12-06 23:09:12 ***
>>
>>
>> With Regards
>> Jayaram
>>
>>
>> On Sat, Dec 11, 2010 at 10:24 AM, Bryan Pendleton
>> <bp...@gmail.com> wrote:
>>> On 12/11/2010 08:02 AM, Jayaram Subramanian wrote:
>>>>
>>>> Thanks for your reply.. When i run DerbyAll from a clean folder I dont
>>>> see any errors in derbyall.sum file..
>>>>
>>>> But in derbyall.fail file i see the following
>>>> ----------------------------------------------------------
>>>> derbyall/storeall/storeall.fail:unit/T_RawStoreFactory.unit
>>>
>>> This test seems to intermittently fail, in a variety of environments, for
>>> example see https://issues.apache.org/jira/browse/DERBY-3993
>>>
>>> It is possible that the test failure you are seeing is due to
>>> this intermittent failure.
>>>
>>> In your folder where you ran the tests, are there any other
>>> files which contain more information about the T_RawStoreFactory failure?
>>>
>>> In particular, look for a 'storeunit' directory, and look for a file
>>> such as storeunit/T_RawStoreFactory.diff
>>>
>>> If you have a file like that, what are the contents?
>>>
>>> thanks,
>>>
>>> bryan
>>>
>>>
>>
>
> Hi,
>
> As Bryan said, this test fails intermittently in a variety of
> environments. There's probably some timing issue somewhere in the
> tests (or in the Derby source code). As you can tell from the
> 'probably', we don't know exactly how to get around this; so, you need
> to figure out if this failure is due to a change you made, or similar
> to the other failures reported.
>
> There are a couple of things you can do to figure out if you need to
> worry about this (or any) failure:
> - run the test again, by itself (this particular old harness can be
> run so: java org.apache.derbyTesting.functionTests.harness.RunTest
> unit/T_RawStoreFactory.unit) ; or make a script to run it 20 times.
> Unfortunately, with an intermittent and likely timing-related issue,
> this result is not really anything conclusive, merely an info-point.
> - look at all other test files. These 'old harness' tests leave all
> relevant files behind if the test fails. So, you should be able to
> find a .tmp (actual output) .out (modified output), .tmpmstr (expected
> output) files, and a derby.log file.
> If comparing tmpmstr and .tmp, nor the derby.log file seem related
> to your changes, than it's likely that you're running into something
> similar to DERBY-3993.
>
> HTH
> Myrna
>
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Posted by Myrna van Lunteren <m....@gmail.com>.
On Tue, Dec 14, 2010 at 7:36 PM, Jayaram Subramanian
<rs...@gmail.com> wrote:
> Hi All,
> I see the following in the T_RawStoreFactory.diff file.. Please let me
> know any corrective actions if required in my setup..
> *** Start: T_RawStoreFactory jdk1.6.0 storeall:storeunit 2010-12-06 23:08:36 ***
> 2 del
> < -- Unit Test T_RawStoreFactory finished
> 2 add
>> Shutting down due to unit test failure.
> Test Failed.
> *** End: T_RawStoreFactory jdk1.6.0 storeall:storeunit 2010-12-06 23:09:12 ***
>
>
> With Regards
> Jayaram
>
>
> On Sat, Dec 11, 2010 at 10:24 AM, Bryan Pendleton
> <bp...@gmail.com> wrote:
>> On 12/11/2010 08:02 AM, Jayaram Subramanian wrote:
>>>
>>> Thanks for your reply.. When i run DerbyAll from a clean folder I dont
>>> see any errors in derbyall.sum file..
>>>
>>> But in derbyall.fail file i see the following
>>> ----------------------------------------------------------
>>> derbyall/storeall/storeall.fail:unit/T_RawStoreFactory.unit
>>
>> This test seems to intermittently fail, in a variety of environments, for
>> example see https://issues.apache.org/jira/browse/DERBY-3993
>>
>> It is possible that the test failure you are seeing is due to
>> this intermittent failure.
>>
>> In your folder where you ran the tests, are there any other
>> files which contain more information about the T_RawStoreFactory failure?
>>
>> In particular, look for a 'storeunit' directory, and look for a file
>> such as storeunit/T_RawStoreFactory.diff
>>
>> If you have a file like that, what are the contents?
>>
>> thanks,
>>
>> bryan
>>
>>
>
Hi,
As Bryan said, this test fails intermittently in a variety of
environments. There's probably some timing issue somewhere in the
tests (or in the Derby source code). As you can tell from the
'probably', we don't know exactly how to get around this; so, you need
to figure out if this failure is due to a change you made, or similar
to the other failures reported.
There are a couple of things you can do to figure out if you need to
worry about this (or any) failure:
- run the test again, by itself (this particular old harness can be
run so: java org.apache.derbyTesting.functionTests.harness.RunTest
unit/T_RawStoreFactory.unit) ; or make a script to run it 20 times.
Unfortunately, with an intermittent and likely timing-related issue,
this result is not really anything conclusive, merely an info-point.
- look at all other test files. These 'old harness' tests leave all
relevant files behind if the test fails. So, you should be able to
find a .tmp (actual output) .out (modified output), .tmpmstr (expected
output) files, and a derby.log file.
If comparing tmpmstr and .tmp, nor the derby.log file seem related
to your changes, than it's likely that you're running into something
similar to DERBY-3993.
HTH
Myrna
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Posted by Jayaram Subramanian <rs...@gmail.com>.
Hi All,
I see the following in the T_RawStoreFactory.diff file.. Please let me
know any corrective actions if required in my setup..
*** Start: T_RawStoreFactory jdk1.6.0 storeall:storeunit 2010-12-06 23:08:36 ***
2 del
< -- Unit Test T_RawStoreFactory finished
2 add
> Shutting down due to unit test failure.
Test Failed.
*** End: T_RawStoreFactory jdk1.6.0 storeall:storeunit 2010-12-06 23:09:12 ***
With Regards
Jayaram
On Sat, Dec 11, 2010 at 10:24 AM, Bryan Pendleton
<bp...@gmail.com> wrote:
> On 12/11/2010 08:02 AM, Jayaram Subramanian wrote:
>>
>> Thanks for your reply.. When i run DerbyAll from a clean folder I dont
>> see any errors in derbyall.sum file..
>>
>> But in derbyall.fail file i see the following
>> ----------------------------------------------------------
>> derbyall/storeall/storeall.fail:unit/T_RawStoreFactory.unit
>
> This test seems to intermittently fail, in a variety of environments, for
> example see https://issues.apache.org/jira/browse/DERBY-3993
>
> It is possible that the test failure you are seeing is due to
> this intermittent failure.
>
> In your folder where you ran the tests, are there any other
> files which contain more information about the T_RawStoreFactory failure?
>
> In particular, look for a 'storeunit' directory, and look for a file
> such as storeunit/T_RawStoreFactory.diff
>
> If you have a file like that, what are the contents?
>
> thanks,
>
> bryan
>
>
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references
to JCC in test code
Posted by Bryan Pendleton <bp...@gmail.com>.
On 12/11/2010 08:02 AM, Jayaram Subramanian wrote:
> Thanks for your reply.. When i run DerbyAll from a clean folder I dont
> see any errors in derbyall.sum file..
>
> But in derbyall.fail file i see the following
> ----------------------------------------------------------
> derbyall/storeall/storeall.fail:unit/T_RawStoreFactory.unit
This test seems to intermittently fail, in a variety of environments, for
example see https://issues.apache.org/jira/browse/DERBY-3993
It is possible that the test failure you are seeing is due to
this intermittent failure.
In your folder where you ran the tests, are there any other
files which contain more information about the T_RawStoreFactory failure?
In particular, look for a 'storeunit' directory, and look for a file
such as storeunit/T_RawStoreFactory.diff
If you have a file like that, what are the contents?
thanks,
bryan
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Posted by Jayaram Subramanian <rs...@gmail.com>.
Hi All,
Thanks for your reply.. When i run DerbyAll from a clean folder I dont
see any errors in derbyall.sum file..
But in derbyall.fail file i see the following
----------------------------------------------------------
derbyall/storeall/storeall.fail:unit/T_RawStoreFactory.unit
In DerbyAll.pass i see the following
--------------------------------------------------
derbyall/derbyall.pass:lang/DB2IsolationLevels.sql
derbyall/derbyall.pass:lang/LOBDB2compatibility.sql
derbyall/derbyall.pass:lang/aggregateOptimization.sql
derbyall/derbyall.pass:lang/compressTable.sql
derbyall/derbyall.pass:lang/consistencyChecker.sql
derbyall/derbyall.pass:lang/currentSchema.sql
derbyall/derbyall.pass:lang/cursorerrors.sql
derbyall/derbyall.pass:lang/db2Compatibility.sql
derbyall/derbyall.pass:lang/ddlTableLockMode.sql
derbyall/derbyall.pass:lang/desc_index.sql
derbyall/derbyall.pass:lang/emptyStatistics.sql
derbyall/derbyall.pass:lang/fk_nonSPS.sql
derbyall/derbyall.pass:lang/holdCursorIJ.sql
derbyall/derbyall.pass:lang/infostreams.sql
derbyall/derbyall.pass:lang/isolationLevels.sql
derbyall/derbyall.pass:lang/joinDeadlock.sql
derbyall/derbyall.pass:lang/langUnitTests.sql
derbyall/derbyall.pass:lang/lockTable.sql
derbyall/derbyall.pass:lang/lojreorder.sql
derbyall/derbyall.pass:lang/maxMemPerTab.java
derbyall/derbyall.pass:lang/nestedCommit.sql
derbyall/derbyall.pass:lang/openScans.sql
derbyall/derbyall.pass:lang/orderbyElimination.sql
derbyall/derbyall.pass:lang/outparams.java
derbyall/derbyall.pass:lang/paramij.sql
derbyall/derbyall.pass:lang/partdml.sql
derbyall/derbyall.pass:lang/predicatesIntoViews.sql
derbyall/derbyall.pass:lang/refActions.sql
derbyall/derbyall.pass:lang/refActions2.sql
derbyall/derbyall.pass:lang/refActions3.sql
derbyall/derbyall.pass:lang/reopenScan.sql
derbyall/derbyall.pass:lang/setOpPlan.sql
derbyall/derbyall.pass:lang/specjPlans.sql
derbyall/derbyall.pass:lang/subquery.sql
derbyall/derbyall.pass:lang/subquery2.sql
derbyall/derbyall.pass:lang/subqueryFlattening.sql
derbyall/derbyall.pass:lang/triggerBeforeTrig.sql
derbyall/derbyall.pass:lang/triggerGeneral.sql
derbyall/derbyall.pass:lang/triggerRecursion.sql
derbyall/derbyall.pass:lang/triggerRefClause.sql
derbyall/derbyall.pass:lang/wisconsin.java
derbyall/derbyall.pass:jdbcapi/xaAnotherTest.sql
derbyall/derbyall.pass:jdbcapi/xaSimpleNegative.sql
derbyall/derbyall.pass:store/xaOffline1.sql
derbyall/derbyall.pass:store/xab2354.sql
derbyall/derbyall.pass:unit/T_XA.unit
derbyall/derbyall.pass:tools/dblook_test.java
derbyall/derbyall.pass:tools/dblook_test_territory.java
derbyall/derbyall.pass:tools/derbyrunjartest.java
derbyall/derbyall.pass:tools/ij.sql
derbyall/derbyall.pass:tools/ij2.sql
derbyall/derbyall.pass:tools/ij3.sql
derbyall/derbyall.pass:tools/ij4.sql
derbyall/derbyall.pass:tools/ij5.sql
derbyall/derbyall.pass:tools/ij6.sql
derbyall/derbyall.pass:tools/ijConnName.sql
derbyall/derbyall.pass:tools/URLCheck.sql
derbyall/derbyall.pass:jdbcapi/getCurConnJdbc20.sql
derbyall/derbyall.pass:jdbcapi/derbyStress.java
derbyall/derbynetclientmats/derbynetclientmats.pass:junitTests/derbyNet/CompatibilityTest.java
derbyall/derbynetclientmats/derbynetmats.pass:derbynet/dblook_test_net.java
derbyall/derbynetclientmats/derbynetmats.pass:derbynet/dblook_test_net_territory.java
derbyall/derbynetclientmats/derbynetmats.pass:derbynet/DerbyNetAutoStart.java
derbyall/derbynetclientmats/derbynetmats.pass:derbynet/testProtocol.java
derbyall/derbynetclientmats/derbynetmats.pass:lang/holdCursorIJ.sql
derbyall/derbynetclientmats/derbynetmats.pass:lang/wisconsin.java
derbyall/derbynetclientmats/derbynetmats.pass:lang/ShutdownDatabase.java
derbyall/derbynetclientmats/derbynetmats.pass:jdbcapi/derbyStress.java
derbyall/derbynetclientmats/derbynetmats.pass:jdbcapi/getCurConnJdbc20.sql
derbyall/encryptionAll/encryptionAll.pass:store/encryptParams.sql
derbyall/encryptionAll/encryptionAll.pass:store/encryptDatabaseTest1.sql
derbyall/encryptionAll/encryptionAll.pass:store/encryptDatabaseTest2.sql
derbyall/encryptionAll/encryptionAll.pass:store/encryptDatabaseTest3.sql
derbyall/storeall/storeall.pass:store/cisco.sql
derbyall/storeall/storeall.pass:store/connectDisconnect.sql
derbyall/storeall/storeall.pass:store/databaseProperties.sql
derbyall/storeall/storeall.pass:store/longRow.sql
derbyall/storeall/storeall.pass:store/logDevice.sql
derbyall/storeall/storeall.pass:store/Rllmodule1.sql
derbyall/storeall/storeall.pass:store/Rllmodule2.sql
derbyall/storeall/storeall.pass:store/Rllmodule3.sql
derbyall/storeall/storeall.pass:store/Rllmodule4.sql
derbyall/storeall/storeall.pass:store/RowLockIso.sql
derbyall/storeall/storeall.pass:store/rlliso1multi.sql
derbyall/storeall/storeall.pass:store/rlliso2multi.sql
derbyall/storeall/storeall.pass:store/rlliso3multi.sql
derbyall/storeall/storeall.pass:store/TransactionTable.sql
derbyall/storeall/storeall.pass:store/SpaceTable.sql
derbyall/storeall/storeall.pass:store/testsqldecimal.sql
derbyall/storeall/storeall.pass:store/heapscan.sql
derbyall/storeall/storeall.pass:store/removeStubs.sql
derbyall/storeall/storeall.pass:store/lockTableVti.sql
derbyall/storeall/storeall.pass:store/rollForwardBackup.sql
derbyall/storeall/storeall.pass:store/rollForwardRecovery.sql
derbyall/storeall/storeall.pass:store/readlocks.sql
derbyall/storeall/storeall.pass:store/backupRestore.sql
derbyall/storeall/storeall.pass:store/backupRestore1.java
derbyall/storeall/storeall.pass:store/bug3498.sql
derbyall/storeall/storeall.pass:store/Beetle6038.java
derbyall/storeall/storeall.pass:store/TestDurabilityProperty.java
derbyall/storeall/storeall.pass:store/OnlineCompressTest.java
derbyall/storeall/storeall.pass:store/OnlineBackupTest1.java
derbyall/storeall/storeall.pass:store/onlineBackupTest2.sql
derbyall/storeall/storeall.pass:store/OnlineBackupTest3.java
derbyall/storeall/storeall.pass:store/onlineBackupTest4.sql
derbyall/storeall/storeall.pass:store/BackupPathTests.java
derbyall/storeall/storeall.pass:store/LogDeviceTest.java
derbyall/storeall/storeall.pass:storetests/st_schema.sql
derbyall/storeall/storeall.pass:storetests/st_derby1939.java
derbyall/storeall/storeall.pass:storetests/st_derby1189.sql
derbyall/storeall/storeall.pass:storetests/st_reclaim_longcol.java
derbyall/storeall/storeall.pass:storetests/st_derby715.java
derbyall/storeall/storeall.pass:storetests/st_1.sql
derbyall/storeall/storeall.pass:storetests/st_b5772.sql
derbyall/storeall/storeall.pass:storetests/derby94.sql
derbyall/storeall/storeall.pass:unit/T_FileSystemData.unit
derbyall/storeall/storeall.pass:unit/T_StreamFile.unit
derbyall/storeall/storeall.pass:unit/T_AccessFactory.unit
derbyall/storeall/storeall.pass:unit/T_Heap.unit
derbyall/storeall/storeall.pass:unit/T_b2i.unit
derbyall/storeall/storeall.pass:unit/T_SortController.unit
derbyall/storeall/storeall.pass:unit/TLockFactory.unit
derbyall/storeall/storeall.pass:unit/TUUIDFactory.unit
derbyall/storeall/storeall.pass:unit/recoverySetup.unit
derbyall/storeall/storeall.pass:unit/recoveryTest.unit
derbyall/storeall/storeall.pass:unit/recoverBadLogSetup.unit
derbyall/storeall/storeall.pass:unit/recoverBadLog1.unit
derbyall/storeall/storeall.pass:unit/recoverBadLog2.unit
derbyall/storeall/storeall.pass:unit/recoverBadLog3.unit
derbyall/storeall/storeall.pass:unit/recoverBadLog4.unit
derbyall/storeall/storeall.pass:unit/recoverBadLog5.unit
derbyall/storeall/storeall.pass:unit/recoverBadLog6.unit
Please let me know your thougts
With Regards
Jayaram
On Fri, Dec 3, 2010 at 12:38 AM, Kristian Waagan
<kr...@oracle.com> wrote:
> On 03.12.10 05:44, Jayaram Subramanian wrote:
>>
>> Hi All,
>> When i tried running java
>> org.apache.derbyTesting.functionTests.harness.RunSuite derbyall i saw
>> the following error in derbyall.sum file. Could you please help me and
>> let me know how to work around this
>>
>> ERROR XJ041: Failed to create database 'wombat', see the next
>> exception for details.
>> ERROR XSLAT: The log directory 'extinout\wierdlog\log' exists. The
>> directory might belong to another database. Check that the location
>> specified for the logDevice attribute is correct.
>
> Hi Jayaram,
>
> Did you run the tests from a clean directory, or did you reuse a directory
> where you had run the tests already?
>
>
>
> Regards,
> --
> Kristian
>
>> With Regards
>> Jayaram
>>
>>
>>
>> 19
>> On Wed, Nov 17, 2010 at 7:40 AM, Jayaram Subramanian
>> <rs...@gmail.com> wrote:
>>>
>>> Hi All,
>>> Thanks for your help. After i removed the files reported with "?", the
>>> ant all went through without issues.. Now i will be able to proceed
>>> with the JCC testing
>>>
>>> With Regards
>>> Jayaram
>>>
>> On Sun, Nov 7, 2010 at 8:17 AM, Kathey Marsden
>>>
>>> <km...@sbcglobal.net> wrote:
>>>>
>>>> On 11/5/2010 7:13 PM, Dag H. Wanvik wrote:
>>>>>>>
>>>>>>> ________________________________
>>>>>>> From: Jayaram Subramanian<rs...@gmail.com>
>>>>>>> To: derby-dev@db.apache.org
>>>>>>> Sent: Thu, November 4, 2010 8:35:54 PM
>>>>>>> Subject: Re: [jira] Commented: (DERBY-4785) Remove JCC tests and
>>>>>>> references
>>>>>>> to JCC in test code
>>>>>>>
>>>>>>> Thanks all,
>>>>>>> I made the suggested changes to derbynetclientmats etc.. and then
>>>>>>> tried building using ant all... But i am getting the following error
>>>>>>> compile\SQLParser.java:3632: cannot find symbol
>>>>>>>
>>>>>>> [javac] symbol : class ParseException
>>>>>>> [javac] location: class
>>>>>>> org.apache.derby.impl.sql.compile.SQLParser
>>>>>>> [javac] final public DataTypeDescriptor numericType() throws
>>>>>>> ParseExceptio
>>>>>>> n, StandardException {
>>>>>>>
>>>> Hi Jararam,
>>>>
>>>> It is likely because you did a svn update before ant clobber, there are
>>>> still some private files around that need to be cleaned up manually. so
>>>> run
>>>> svn status and remove any private files that you did not intentionally
>>>> create.. You may also want to refer to this comment when I hit the
>>>> problem
>>>> myself:
>>>>
>>>> https://issues.apache.org/jira/browse/DERBY-3986?focusedCommentId=12914102&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12914102
>>>>
>>>>
>>>>
>
>
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references
to JCC in test code
Posted by Kristian Waagan <kr...@oracle.com>.
On 03.12.10 05:44, Jayaram Subramanian wrote:
> Hi All,
> When i tried running java
> org.apache.derbyTesting.functionTests.harness.RunSuite derbyall i saw
> the following error in derbyall.sum file. Could you please help me and
> let me know how to work around this
>
> ERROR XJ041: Failed to create database 'wombat', see the next
> exception for details.
> ERROR XSLAT: The log directory 'extinout\wierdlog\log' exists. The
> directory might belong to another database. Check that the location
> specified for the logDevice attribute is correct.
Hi Jayaram,
Did you run the tests from a clean directory, or did you reuse a
directory where you had run the tests already?
Regards,
--
Kristian
> With Regards
> Jayaram
>
>
>
> 19
> On Wed, Nov 17, 2010 at 7:40 AM, Jayaram Subramanian
> <rs...@gmail.com> wrote:
>> Hi All,
>> Thanks for your help. After i removed the files reported with "?", the
>> ant all went through without issues.. Now i will be able to proceed
>> with the JCC testing
>>
>> With Regards
>> Jayaram
>>
> On Sun, Nov 7, 2010 at 8:17 AM, Kathey Marsden
>> <km...@sbcglobal.net> wrote:
>>> On 11/5/2010 7:13 PM, Dag H. Wanvik wrote:
>>>>>> ________________________________
>>>>>> From: Jayaram Subramanian<rs...@gmail.com>
>>>>>> To: derby-dev@db.apache.org
>>>>>> Sent: Thu, November 4, 2010 8:35:54 PM
>>>>>> Subject: Re: [jira] Commented: (DERBY-4785) Remove JCC tests and
>>>>>> references
>>>>>> to JCC in test code
>>>>>>
>>>>>> Thanks all,
>>>>>> I made the suggested changes to derbynetclientmats etc.. and then
>>>>>> tried building using ant all... But i am getting the following error
>>>>>> compile\SQLParser.java:3632: cannot find symbol
>>>>>>
>>>>>> [javac] symbol : class ParseException
>>>>>> [javac] location: class org.apache.derby.impl.sql.compile.SQLParser
>>>>>> [javac] final public DataTypeDescriptor numericType() throws
>>>>>> ParseExceptio
>>>>>> n, StandardException {
>>>>>>
>>> Hi Jararam,
>>>
>>> It is likely because you did a svn update before ant clobber, there are
>>> still some private files around that need to be cleaned up manually. so run
>>> svn status and remove any private files that you did not intentionally
>>> create.. You may also want to refer to this comment when I hit the problem
>>> myself:
>>> https://issues.apache.org/jira/browse/DERBY-3986?focusedCommentId=12914102&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12914102
>>>
>>>
>>>
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Posted by Jayaram Subramanian <rs...@gmail.com>.
Hi All,
When i tried running java
org.apache.derbyTesting.functionTests.harness.RunSuite derbyall i saw
the following error in derbyall.sum file. Could you please help me and
let me know how to work around this
ERROR XJ041: Failed to create database 'wombat', see the next
exception for details.
ERROR XSLAT: The log directory 'extinout\wierdlog\log' exists. The
directory might belong to another database. Check that the location
specified for the logDevice attribute is correct.
With Regards
Jayaram
19
On Wed, Nov 17, 2010 at 7:40 AM, Jayaram Subramanian
<rs...@gmail.com> wrote:
> Hi All,
> Thanks for your help. After i removed the files reported with "?", the
> ant all went through without issues.. Now i will be able to proceed
> with the JCC testing
>
> With Regards
> Jayaram
>
On Sun, Nov 7, 2010 at 8:17 AM, Kathey Marsden
> <km...@sbcglobal.net> wrote:
>> On 11/5/2010 7:13 PM, Dag H. Wanvik wrote:
>>>
>>>>>
>>>>> ________________________________
>>>>> From: Jayaram Subramanian<rs...@gmail.com>
>>>>> To: derby-dev@db.apache.org
>>>>> Sent: Thu, November 4, 2010 8:35:54 PM
>>>>> Subject: Re: [jira] Commented: (DERBY-4785) Remove JCC tests and
>>>>> references
>>>>> to JCC in test code
>>>>>
>>>>> Thanks all,
>>>>> I made the suggested changes to derbynetclientmats etc.. and then
>>>>> tried building using ant all... But i am getting the following error
>>>>> compile\SQLParser.java:3632: cannot find symbol
>>>>>
>>>>> [javac] symbol : class ParseException
>>>>> [javac] location: class org.apache.derby.impl.sql.compile.SQLParser
>>>>> [javac] final public DataTypeDescriptor numericType() throws
>>>>> ParseExceptio
>>>>> n, StandardException {
>>>>>
>> Hi Jararam,
>>
>> It is likely because you did a svn update before ant clobber, there are
>> still some private files around that need to be cleaned up manually. so run
>> svn status and remove any private files that you did not intentionally
>> create.. You may also want to refer to this comment when I hit the problem
>> myself:
>> https://issues.apache.org/jira/browse/DERBY-3986?focusedCommentId=12914102&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12914102
>>
>>
>>
>
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Posted by Jayaram Subramanian <rs...@gmail.com>.
Hi All,
Thanks for your help. After i removed the files reported with "?", the
ant all went through without issues.. Now i will be able to proceed
with the JCC testing
With Regards
Jayaram
On Sun, Nov 7, 2010 at 8:17 AM, Kathey Marsden
<km...@sbcglobal.net> wrote:
> On 11/5/2010 7:13 PM, Dag H. Wanvik wrote:
>>
>>>>
>>>> ________________________________
>>>> From: Jayaram Subramanian<rs...@gmail.com>
>>>> To: derby-dev@db.apache.org
>>>> Sent: Thu, November 4, 2010 8:35:54 PM
>>>> Subject: Re: [jira] Commented: (DERBY-4785) Remove JCC tests and
>>>> references
>>>> to JCC in test code
>>>>
>>>> Thanks all,
>>>> I made the suggested changes to derbynetclientmats etc.. and then
>>>> tried building using ant all... But i am getting the following error
>>>> compile\SQLParser.java:3632: cannot find symbol
>>>>
>>>> [javac] symbol : class ParseException
>>>> [javac] location: class org.apache.derby.impl.sql.compile.SQLParser
>>>> [javac] final public DataTypeDescriptor numericType() throws
>>>> ParseExceptio
>>>> n, StandardException {
>>>>
> Hi Jararam,
>
> It is likely because you did a svn update before ant clobber, there are
> still some private files around that need to be cleaned up manually. so run
> svn status and remove any private files that you did not intentionally
> create.. You may also want to refer to this comment when I hit the problem
> myself:
> https://issues.apache.org/jira/browse/DERBY-3986?focusedCommentId=12914102&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12914102
>
>
>
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references
to JCC in test code
Posted by Kathey Marsden <km...@sbcglobal.net>.
On 11/5/2010 7:13 PM, Dag H. Wanvik wrote:
>
>>>
>>> ________________________________
>>> From: Jayaram Subramanian<rs...@gmail.com>
>>> To: derby-dev@db.apache.org
>>> Sent: Thu, November 4, 2010 8:35:54 PM
>>> Subject: Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references
>>> to JCC in test code
>>>
>>> Thanks all,
>>> I made the suggested changes to derbynetclientmats etc.. and then
>>> tried building using ant all... But i am getting the following error
>>> compile\SQLParser.java:3632: cannot find symbol
>>>
>>> [javac] symbol : class ParseException
>>> [javac] location: class org.apache.derby.impl.sql.compile.SQLParser
>>> [javac] final public DataTypeDescriptor numericType() throws
>>> ParseExceptio
>>> n, StandardException {
>>>
Hi Jararam,
It is likely because you did a svn update before ant clobber, there are
still some private files around that need to be cleaned up manually. so
run svn status and remove any private files that you did not
intentionally create.. You may also want to refer to this comment when
I hit the problem myself:
https://issues.apache.org/jira/browse/DERBY-3986?focusedCommentId=12914102&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12914102
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references to JCC in test code
Posted by "Dag H. Wanvik" <da...@oracle.com>.
I saw something similar, Rick just fixed somethign in the build so maybe
a svn update will set you straight. If not, try clobber between each
compile-time error you correct.
Thanks,
Dag
Jayaram Subramanian <rs...@gmail.com> writes:
> Hi All,
> Thanks for the reply. I did the ant clobber before starting out ant
> all... I had also done svn update before making my JCC changes.. So i
> am wondering if something is wrong with my classpath.. The issue seems
> to be occuring around "parseexception".. Is there any class reference
> which is getting missed here?
>
> With Regards
> Jayaram
>
>
> On Thu, Nov 4, 2010 at 11:14 PM, Lily Wei <li...@yahoo.com> wrote:
>> Hi Jayaram:
>> It is nice to see your email.
>>
>> The build environment change lately.
>> If you do 'ant clobber' then 'ant all', it should fix your problem.
>> Before 'ant all', you can also do svn status to see whether you have any
>> temporary files that should be manually remove.
>>
>>
>> Hope this help,
>> Lily
>>
>>
>> ________________________________
>> From: Jayaram Subramanian <rs...@gmail.com>
>> To: derby-dev@db.apache.org
>> Sent: Thu, November 4, 2010 8:35:54 PM
>> Subject: Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references
>> to JCC in test code
>>
>> Thanks all,
>> I made the suggested changes to derbynetclientmats etc.. and then
>> tried building using ant all... But i am getting the following error
>> compile\SQLParser.java:3632: cannot find symbol
>>
>> [javac] symbol : class ParseException
>> [javac] location: class org.apache.derby.impl.sql.compile.SQLParser
>> [javac] final public DataTypeDescriptor numericType() throws
>> ParseExceptio
>> n, StandardException {
>>
>> StandardException {
>> [javac] ^
>> [javac]
>> C:\java\derby\source\trunk\generated\java\org\apache\derby\impl\sql\
>> ompile\SQLParser.java:3883: cannot find symbol
>> [javac] symbol : class ParseException
>> [javac] location: class org.apache.derby.impl.sql.compile.SQLParser
>>
>>
>> my classpath is
>> C:/java/Derby/source/trunk/jars/sane/derby/derbyLocale_cs.jar;C:/java/Derby/sour
>> ce/trunk/tools/java/junit.jar;C:/java/Derby/source/trunk/jars/sane/derbyclient.j
>> ar;C:/java/Derby/source/trunk/jars/sane/derbynet.jar;C:/java/Derby/source/trunk/
>> jars/sane/derbyrun.jar;C:/java/Derby/source/trunk/jars/sane/derbytesting.jar;C:/
>> java/Derby/source/trunk/jars/sane/derbytools.jar;C:/java/Derby/source/trunk/jars
>>
>> Please let me know if i am doing something wrong
>>
>> With Regards
>> Jayaram
>>
>>
>>
>> On Wed, Nov 3, 2010 at 3:50 AM, Knut Anders Hatlen
>> <kn...@oracle.com> wrote:
>>> Jayaram Subramanian <rs...@gmail.com> writes:
>>>
>>>> Hi All,
>>>> Thanks for your reply. As suggested i made the changes to
>>>> derbyall.properties derbynetclientmats.runall and
>>>> derbynetclientmats.properties.
>>>>
>>>> I tried testing the changes by running All.java and Allpackages.java
>>>> as junit tests. But no output appeared on the console.. Should i do
>>>> something different
>>>
>>> Hi Jayaram,
>>>
>>> The tests you've changed are not part of the JUnit test suite, but run
>>> in the old test harness. To run them, add derbyrun.jar,
>>> derbyTesting.jar, jakarta-oro-2.0.8.jar and junit.jar to the classpath,
>>> and execute this command:
>>>
>>> java org.apache.derbyTesting.functionTests.harness.RunSuite derbyall
>>>
>>> If everything goes well, you'll find a test report in
>>> derbyall_report.txt when the command has completed.
>>>
>>> --
>>> Knut Anders
>>>
>>
>>
>
--
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Posted by Jayaram Subramanian <rs...@gmail.com>.
Hi All,
Thanks for the reply. I did the ant clobber before starting out ant
all... I had also done svn update before making my JCC changes.. So i
am wondering if something is wrong with my classpath.. The issue seems
to be occuring around "parseexception".. Is there any class reference
which is getting missed here?
With Regards
Jayaram
On Thu, Nov 4, 2010 at 11:14 PM, Lily Wei <li...@yahoo.com> wrote:
> Hi Jayaram:
> It is nice to see your email.
>
> The build environment change lately.
> If you do 'ant clobber' then 'ant all', it should fix your problem.
> Before 'ant all', you can also do svn status to see whether you have any
> temporary files that should be manually remove.
>
>
> Hope this help,
> Lily
>
>
> ________________________________
> From: Jayaram Subramanian <rs...@gmail.com>
> To: derby-dev@db.apache.org
> Sent: Thu, November 4, 2010 8:35:54 PM
> Subject: Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references
> to JCC in test code
>
> Thanks all,
> I made the suggested changes to derbynetclientmats etc.. and then
> tried building using ant all... But i am getting the following error
> compile\SQLParser.java:3632: cannot find symbol
>
> [javac] symbol : class ParseException
> [javac] location: class org.apache.derby.impl.sql.compile.SQLParser
> [javac] final public DataTypeDescriptor numericType() throws
> ParseExceptio
> n, StandardException {
>
> StandardException {
> [javac] ^
> [javac]
> C:\java\derby\source\trunk\generated\java\org\apache\derby\impl\sql\
> ompile\SQLParser.java:3883: cannot find symbol
> [javac] symbol : class ParseException
> [javac] location: class org.apache.derby.impl.sql.compile.SQLParser
>
>
> my classpath is
> C:/java/Derby/source/trunk/jars/sane/derby/derbyLocale_cs.jar;C:/java/Derby/sour
> ce/trunk/tools/java/junit.jar;C:/java/Derby/source/trunk/jars/sane/derbyclient.j
> ar;C:/java/Derby/source/trunk/jars/sane/derbynet.jar;C:/java/Derby/source/trunk/
> jars/sane/derbyrun.jar;C:/java/Derby/source/trunk/jars/sane/derbytesting.jar;C:/
> java/Derby/source/trunk/jars/sane/derbytools.jar;C:/java/Derby/source/trunk/jars
>
> Please let me know if i am doing something wrong
>
> With Regards
> Jayaram
>
>
>
> On Wed, Nov 3, 2010 at 3:50 AM, Knut Anders Hatlen
> <kn...@oracle.com> wrote:
>> Jayaram Subramanian <rs...@gmail.com> writes:
>>
>>> Hi All,
>>> Thanks for your reply. As suggested i made the changes to
>>> derbyall.properties derbynetclientmats.runall and
>>> derbynetclientmats.properties.
>>>
>>> I tried testing the changes by running All.java and Allpackages.java
>>> as junit tests. But no output appeared on the console.. Should i do
>>> something different
>>
>> Hi Jayaram,
>>
>> The tests you've changed are not part of the JUnit test suite, but run
>> in the old test harness. To run them, add derbyrun.jar,
>> derbyTesting.jar, jakarta-oro-2.0.8.jar and junit.jar to the classpath,
>> and execute this command:
>>
>> java org.apache.derbyTesting.functionTests.harness.RunSuite derbyall
>>
>> If everything goes well, you'll find a test report in
>> derbyall_report.txt when the command has completed.
>>
>> --
>> Knut Anders
>>
>
>
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references to JCC in test code
Posted by Lily Wei <li...@yahoo.com>.
Hi Jayaram:
It is nice to see your email.
The build environment change lately.
If you do 'ant clobber' then 'ant all', it should fix your problem.
Before 'ant all', you can also do svn status to see whether you have any
temporary files that should be manually remove.
Hope this help,
Lily
________________________________
From: JayaramSubramanian <rs...@gmail.com>
To: derby-dev@db.apache.org
Sent: Thu, November 4, 2010 8:35:54 PM
Subject: Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Thanks all,
I made the suggested changes to derbynetclientmats etc.. and then
tried building using ant all... But i am getting the following error
compile\SQLParser.java:3632: cannot find symbol
[javac] symbol : class ParseException
[javac] location: class org.apache.derby.impl.sql.compile.SQLParser
[javac] final public DataTypeDescriptornumericType() throws ParseExceptio
n, StandardException {
StandardException {
[javac] ^
[javac] C:\java\derby\source\trunk\generated\java\org\apache\derby\impl\sql\
ompile\SQLParser.java:3883: cannot find symbol
[javac] symbol : class ParseException
[javac] location: class org.apache.derby.impl.sql.compile.SQLParser
my classpath is
C:/java/Derby/source/trunk/jars/sane/derby/derbyLocale_cs.jar;C:/java/Derby/sour
ce/trunk/tools/java/junit.jar;C:/java/Derby/source/trunk/jars/sane/derbyclient.j
ar;C:/java/Derby/source/trunk/jars/sane/derbynet.jar;C:/java/Derby/source/trunk/
jars/sane/derbyrun.jar;C:/java/Derby/source/trunk/jars/sane/derbytesting.jar;C:/
java/Derby/source/trunk/jars/sane/derbytools.jar;C:/java/Derby/source/trunk/jars
Please let me know if i am doing something wrong
With Regards
Jayaram
On Wed, Nov 3, 2010 at 3:50 AM, Knut Anders Hatlen
<kn...@oracle.com> wrote:
> JayaramSubramanian <rs...@gmail.com> writes:
>
>> Hi All,
>> Thanks for your reply. As suggested i made the changes to
>> derbyall.properties derbynetclientmats.runall and
>> derbynetclientmats.properties.
>>
>> I tried testing the changes by running All.java and Allpackages.java
>> as junit tests. But no output appeared on the console.. Should i do
>> something different
>
> Hi Jayaram,
>
> The tests you've changed are not part of the JUnit test suite, but run
> in the old test harness. To run them, add derbyrun.jar,
> derbyTesting.jar, jakarta-oro-2.0.8.jar and junit.jar to the classpath,
> and execute this command:
>
> java org.apache.derbyTesting.functionTests.harness.RunSuite derbyall
>
> If everything goes well, you'll find a test report in
> derbyall_report.txt when the command has completed.
>
> --
> Knut Anders
>
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Posted by Jayaram Subramanian <rs...@gmail.com>.
Thanks all,
I made the suggested changes to derbynetclientmats etc.. and then
tried building using ant all... But i am getting the following error
compile\SQLParser.java:3632: cannot find symbol
[javac] symbol : class ParseException
[javac] location: class org.apache.derby.impl.sql.compile.SQLParser
[javac] final public DataTypeDescriptor numericType() throws ParseExceptio
n, StandardException {
StandardException {
[javac] ^
[javac] C:\java\derby\source\trunk\generated\java\org\apache\derby\impl\sql\
ompile\SQLParser.java:3883: cannot find symbol
[javac] symbol : class ParseException
[javac] location: class org.apache.derby.impl.sql.compile.SQLParser
my classpath is
C:/java/Derby/source/trunk/jars/sane/derby/derbyLocale_cs.jar;C:/java/Derby/sour
ce/trunk/tools/java/junit.jar;C:/java/Derby/source/trunk/jars/sane/derbyclient.j
ar;C:/java/Derby/source/trunk/jars/sane/derbynet.jar;C:/java/Derby/source/trunk/
jars/sane/derbyrun.jar;C:/java/Derby/source/trunk/jars/sane/derbytesting.jar;C:/
java/Derby/source/trunk/jars/sane/derbytools.jar;C:/java/Derby/source/trunk/jars
Please let me know if i am doing something wrong
With Regards
Jayaram
On Wed, Nov 3, 2010 at 3:50 AM, Knut Anders Hatlen
<kn...@oracle.com> wrote:
> Jayaram Subramanian <rs...@gmail.com> writes:
>
>> Hi All,
>> Thanks for your reply. As suggested i made the changes to
>> derbyall.properties derbynetclientmats.runall and
>> derbynetclientmats.properties.
>>
>> I tried testing the changes by running All.java and Allpackages.java
>> as junit tests. But no output appeared on the console.. Should i do
>> something different
>
> Hi Jayaram,
>
> The tests you've changed are not part of the JUnit test suite, but run
> in the old test harness. To run them, add derbyrun.jar,
> derbyTesting.jar, jakarta-oro-2.0.8.jar and junit.jar to the classpath,
> and execute this command:
>
> java org.apache.derbyTesting.functionTests.harness.RunSuite derbyall
>
> If everything goes well, you'll find a test report in
> derbyall_report.txt when the command has completed.
>
> --
> Knut Anders
>
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references to JCC in test code
Posted by Knut Anders Hatlen <kn...@oracle.com>.
Jayaram Subramanian <rs...@gmail.com> writes:
> Hi All,
> Thanks for your reply. As suggested i made the changes to
> derbyall.properties derbynetclientmats.runall and
> derbynetclientmats.properties.
>
> I tried testing the changes by running All.java and Allpackages.java
> as junit tests. But no output appeared on the console.. Should i do
> something different
Hi Jayaram,
The tests you've changed are not part of the JUnit test suite, but run
in the old test harness. To run them, add derbyrun.jar,
derbyTesting.jar, jakarta-oro-2.0.8.jar and junit.jar to the classpath,
and execute this command:
java org.apache.derbyTesting.functionTests.harness.RunSuite derbyall
If everything goes well, you'll find a test report in
derbyall_report.txt when the command has completed.
--
Knut Anders
Re: [jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Posted by Jayaram Subramanian <rs...@gmail.com>.
Hi All,
Thanks for your reply. As suggested i made the changes to
derbyall.properties derbynetclientmats.runall and
derbynetclientmats.properties.
I tried testing the changes by running All.java and Allpackages.java
as junit tests. But no output appeared on the console.. Should i do
something different
With Regards
Jayaram
On Thu, Oct 28, 2010 at 5:32 PM, Kathey Marsden (JIRA) <ji...@apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/DERBY-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925973#action_12925973 ]
>
> Kathey Marsden commented on DERBY-4785:
> ---------------------------------------
>
> Good point. Thanks Myrna I didn't notice those were linked up.
>
>
>> Remove JCC tests and references to JCC in test code
>> ---------------------------------------------------
>>
>> Key: DERBY-4785
>> URL: https://issues.apache.org/jira/browse/DERBY-4785
>> Project: Derby
>> Issue Type: Sub-task
>> Components: Test
>> Affects Versions: 10.5.1.1, 10.6.1.0
>> Reporter: Kathey Marsden
>> Priority: Minor
>>
>> I received a request to remove JCC testing from the derby suite. The user had a very old jcc version in their classpath 2.4 and 10.5 tests were failing with:
>> com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -1, SQLSTATE: XJ040, SQLERRMC: Failed to start database '/results/axxon/58712/laka10a-derby-m101-20100830-003810/derbyall/derbynetmats/DerbyNet/derbynetmats/dblook_test_net_territory//wombat', see the next exception for details.::SQLSTATE: XJ001Java exception: 'Access denied (java.util.PropertyPermission com.ibm.crypto.provider.FIPSMODE read): java.security.AccessControlException'.
>> at com.ibm.db2.jcc.c.o.a(o.java:3219)
>> at com.ibm.db2.jcc.a.cb.q(cb.java:653)
>> at com.ibm.db2.jcc.a.cb.p(cb.java:541)
>> at com.ibm.db2.jcc.a.cb.l(cb.java:363)
>> at com.ibm.db2.jcc.a.cb.d(cb.java:145)
>> at com.ibm.db2.jcc.a.b.Sb(b.java:1274)
>> at com.ibm.db2.jcc.a.b.a(b.java:1166)
>> at com.ibm.db2.jcc.a.b.q(b.java:934)
>> at com.ibm.db2.jcc.a.b.a(b.java:702)
>> at com.ibm.db2.jcc.a.b.(b.java:305)
>> at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:162)
>> at java.sql.DriverManager.getConnection(DriverManager.java:322)
>> at java.sql.DriverManager.getConnection(DriverManager.java:273)
>> at org.apache.derby.tools.dblook.go(Unknown Source)
>> at org.apache.derby.tools.dblook.(Unknown Source)
>> at org.apache.derbyTesting.functionTests.tests.tools.dblook_test.lookThree(dblook_test.java:417)
>> at org.apache.derbyTesting.functionTests.tests.tools.dblook_test.runTest(dblook_test.java:283)
>> at org.apache.derbyTesting.functionTests.tests.derbynet.dblook_test_net_territory.doTest(dblook_test_net_territory.java:65)
>> at org.apache.derbyTesting.functionTests.tests.derbynet.dblook_test_net_territory.main(dblook_test_net_territory.java:41)
>> Now that I look at it more closely, their actual problem might be on the server side and JCC just reporting it but good to get the JCC tests out of the mix when people accidentally have it in their classpath anyway.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
[jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925940#action_12925940 ]
Kathey Marsden commented on DERBY-4785:
---------------------------------------
On the mailing list Jayaram asked for first steps on this issue.
I think a good first step would be to remove the derbynetmats suite from derbyall.
Basically all that would need to be done for this first patch would be to remove derbynetmats from
java/testing/org/apache/derbyTesting/functionTests/suites/derbyall.properties and remove the erbynetmats.properties derbynetmats.runall and run tests to make sure there is no unexpected mpact.
Then as Dag suggest we can do the bare minimum in RunTest, RunSuite etc to make sure it doesn't get loaded and finally do a more careful removal of the jcc references in the JUnit test infrastructure, but I think the first step would be just to remove derbynetmats from the suite.
> Remove JCC tests and references to JCC in test code
> ---------------------------------------------------
>
> Key: DERBY-4785
> URL: https://issues.apache.org/jira/browse/DERBY-4785
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Affects Versions: 10.5.1.1, 10.6.1.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> I received a request to remove JCC testing from the derby suite. The user had a very old jcc version in their classpath 2.4 and 10.5 tests were failing with:
> com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -1, SQLSTATE: XJ040, SQLERRMC: Failed to start database '/results/axxon/58712/laka10a-derby-m101-20100830-003810/derbyall/derbynetmats/DerbyNet/derbynetmats/dblook_test_net_territory//wombat', see the next exception for details.::SQLSTATE: XJ001Java exception: 'Access denied (java.util.PropertyPermission com.ibm.crypto.provider.FIPSMODE read): java.security.AccessControlException'.
> at com.ibm.db2.jcc.c.o.a(o.java:3219)
> at com.ibm.db2.jcc.a.cb.q(cb.java:653)
> at com.ibm.db2.jcc.a.cb.p(cb.java:541)
> at com.ibm.db2.jcc.a.cb.l(cb.java:363)
> at com.ibm.db2.jcc.a.cb.d(cb.java:145)
> at com.ibm.db2.jcc.a.b.Sb(b.java:1274)
> at com.ibm.db2.jcc.a.b.a(b.java:1166)
> at com.ibm.db2.jcc.a.b.q(b.java:934)
> at com.ibm.db2.jcc.a.b.a(b.java:702)
> at com.ibm.db2.jcc.a.b.(b.java:305)
> at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:162)
> at java.sql.DriverManager.getConnection(DriverManager.java:322)
> at java.sql.DriverManager.getConnection(DriverManager.java:273)
> at org.apache.derby.tools.dblook.go(Unknown Source)
> at org.apache.derby.tools.dblook.(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.tools.dblook_test.lookThree(dblook_test.java:417)
> at org.apache.derbyTesting.functionTests.tests.tools.dblook_test.runTest(dblook_test.java:283)
> at org.apache.derbyTesting.functionTests.tests.derbynet.dblook_test_net_territory.doTest(dblook_test_net_territory.java:65)
> at org.apache.derbyTesting.functionTests.tests.derbynet.dblook_test_net_territory.main(dblook_test_net_territory.java:41)
> Now that I look at it more closely, their actual problem might be on the server side and JCC just reporting it but good to get the JCC tests out of the mix when people accidentally have it in their classpath anyway.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925964#action_12925964 ]
Myrna van Lunteren commented on DERBY-4785:
-------------------------------------------
re removal of derbynetmats suites...You can't just remove those files; you need to add the contents of derbynetmats.runall to derbynetclientmats.runall, and replace the 'derbynetmats' suite reference in derbynetclientmats.properties with 'jdbcapi jdbc20'.
> Remove JCC tests and references to JCC in test code
> ---------------------------------------------------
>
> Key: DERBY-4785
> URL: https://issues.apache.org/jira/browse/DERBY-4785
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Affects Versions: 10.5.1.1, 10.6.1.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> I received a request to remove JCC testing from the derby suite. The user had a very old jcc version in their classpath 2.4 and 10.5 tests were failing with:
> com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -1, SQLSTATE: XJ040, SQLERRMC: Failed to start database '/results/axxon/58712/laka10a-derby-m101-20100830-003810/derbyall/derbynetmats/DerbyNet/derbynetmats/dblook_test_net_territory//wombat', see the next exception for details.::SQLSTATE: XJ001Java exception: 'Access denied (java.util.PropertyPermission com.ibm.crypto.provider.FIPSMODE read): java.security.AccessControlException'.
> at com.ibm.db2.jcc.c.o.a(o.java:3219)
> at com.ibm.db2.jcc.a.cb.q(cb.java:653)
> at com.ibm.db2.jcc.a.cb.p(cb.java:541)
> at com.ibm.db2.jcc.a.cb.l(cb.java:363)
> at com.ibm.db2.jcc.a.cb.d(cb.java:145)
> at com.ibm.db2.jcc.a.b.Sb(b.java:1274)
> at com.ibm.db2.jcc.a.b.a(b.java:1166)
> at com.ibm.db2.jcc.a.b.q(b.java:934)
> at com.ibm.db2.jcc.a.b.a(b.java:702)
> at com.ibm.db2.jcc.a.b.(b.java:305)
> at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:162)
> at java.sql.DriverManager.getConnection(DriverManager.java:322)
> at java.sql.DriverManager.getConnection(DriverManager.java:273)
> at org.apache.derby.tools.dblook.go(Unknown Source)
> at org.apache.derby.tools.dblook.(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.tools.dblook_test.lookThree(dblook_test.java:417)
> at org.apache.derbyTesting.functionTests.tests.tools.dblook_test.runTest(dblook_test.java:283)
> at org.apache.derbyTesting.functionTests.tests.derbynet.dblook_test_net_territory.doTest(dblook_test_net_territory.java:65)
> at org.apache.derbyTesting.functionTests.tests.derbynet.dblook_test_net_territory.main(dblook_test_net_territory.java:41)
> Now that I look at it more closely, their actual problem might be on the server side and JCC just reporting it but good to get the JCC tests out of the mix when people accidentally have it in their classpath anyway.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925956#action_12925956 ]
Knut Anders Hatlen commented on DERBY-4785:
-------------------------------------------
For the removal from the JUnit tests, I would suggest that you go through the callers of JDBCClient.isDB2Client() and BaseJDBCTestCase.usingDB2Client(), and finally remove those two methods themselves. I think this will remove most of the JCC-specific code in the JUnit tests.
There's also a less frequently used method called DerbyJUnitTest.usingDB2Client().
> Remove JCC tests and references to JCC in test code
> ---------------------------------------------------
>
> Key: DERBY-4785
> URL: https://issues.apache.org/jira/browse/DERBY-4785
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Affects Versions: 10.5.1.1, 10.6.1.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> I received a request to remove JCC testing from the derby suite. The user had a very old jcc version in their classpath 2.4 and 10.5 tests were failing with:
> com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -1, SQLSTATE: XJ040, SQLERRMC: Failed to start database '/results/axxon/58712/laka10a-derby-m101-20100830-003810/derbyall/derbynetmats/DerbyNet/derbynetmats/dblook_test_net_territory//wombat', see the next exception for details.::SQLSTATE: XJ001Java exception: 'Access denied (java.util.PropertyPermission com.ibm.crypto.provider.FIPSMODE read): java.security.AccessControlException'.
> at com.ibm.db2.jcc.c.o.a(o.java:3219)
> at com.ibm.db2.jcc.a.cb.q(cb.java:653)
> at com.ibm.db2.jcc.a.cb.p(cb.java:541)
> at com.ibm.db2.jcc.a.cb.l(cb.java:363)
> at com.ibm.db2.jcc.a.cb.d(cb.java:145)
> at com.ibm.db2.jcc.a.b.Sb(b.java:1274)
> at com.ibm.db2.jcc.a.b.a(b.java:1166)
> at com.ibm.db2.jcc.a.b.q(b.java:934)
> at com.ibm.db2.jcc.a.b.a(b.java:702)
> at com.ibm.db2.jcc.a.b.(b.java:305)
> at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:162)
> at java.sql.DriverManager.getConnection(DriverManager.java:322)
> at java.sql.DriverManager.getConnection(DriverManager.java:273)
> at org.apache.derby.tools.dblook.go(Unknown Source)
> at org.apache.derby.tools.dblook.(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.tools.dblook_test.lookThree(dblook_test.java:417)
> at org.apache.derbyTesting.functionTests.tests.tools.dblook_test.runTest(dblook_test.java:283)
> at org.apache.derbyTesting.functionTests.tests.derbynet.dblook_test_net_territory.doTest(dblook_test_net_territory.java:65)
> at org.apache.derbyTesting.functionTests.tests.derbynet.dblook_test_net_territory.main(dblook_test_net_territory.java:41)
> Now that I look at it more closely, their actual problem might be on the server side and JCC just reporting it but good to get the JCC tests out of the mix when people accidentally have it in their classpath anyway.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4785) Remove JCC tests and references to
JCC in test code
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925973#action_12925973 ]
Kathey Marsden commented on DERBY-4785:
---------------------------------------
Good point. Thanks Myrna I didn't notice those were linked up.
> Remove JCC tests and references to JCC in test code
> ---------------------------------------------------
>
> Key: DERBY-4785
> URL: https://issues.apache.org/jira/browse/DERBY-4785
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Affects Versions: 10.5.1.1, 10.6.1.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> I received a request to remove JCC testing from the derby suite. The user had a very old jcc version in their classpath 2.4 and 10.5 tests were failing with:
> com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -1, SQLSTATE: XJ040, SQLERRMC: Failed to start database '/results/axxon/58712/laka10a-derby-m101-20100830-003810/derbyall/derbynetmats/DerbyNet/derbynetmats/dblook_test_net_territory//wombat', see the next exception for details.::SQLSTATE: XJ001Java exception: 'Access denied (java.util.PropertyPermission com.ibm.crypto.provider.FIPSMODE read): java.security.AccessControlException'.
> at com.ibm.db2.jcc.c.o.a(o.java:3219)
> at com.ibm.db2.jcc.a.cb.q(cb.java:653)
> at com.ibm.db2.jcc.a.cb.p(cb.java:541)
> at com.ibm.db2.jcc.a.cb.l(cb.java:363)
> at com.ibm.db2.jcc.a.cb.d(cb.java:145)
> at com.ibm.db2.jcc.a.b.Sb(b.java:1274)
> at com.ibm.db2.jcc.a.b.a(b.java:1166)
> at com.ibm.db2.jcc.a.b.q(b.java:934)
> at com.ibm.db2.jcc.a.b.a(b.java:702)
> at com.ibm.db2.jcc.a.b.(b.java:305)
> at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:162)
> at java.sql.DriverManager.getConnection(DriverManager.java:322)
> at java.sql.DriverManager.getConnection(DriverManager.java:273)
> at org.apache.derby.tools.dblook.go(Unknown Source)
> at org.apache.derby.tools.dblook.(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.tools.dblook_test.lookThree(dblook_test.java:417)
> at org.apache.derbyTesting.functionTests.tests.tools.dblook_test.runTest(dblook_test.java:283)
> at org.apache.derbyTesting.functionTests.tests.derbynet.dblook_test_net_territory.doTest(dblook_test_net_territory.java:65)
> at org.apache.derbyTesting.functionTests.tests.derbynet.dblook_test_net_territory.main(dblook_test_net_territory.java:41)
> Now that I look at it more closely, their actual problem might be on the server side and JCC just reporting it but good to get the JCC tests out of the mix when people accidentally have it in their classpath anyway.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4785) Remove JCC tests and references to JCC
in test code
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-4785:
--------------------------------------
Parent Issue: DERBY-4596 (was: DERBY-4597)
> Remove JCC tests and references to JCC in test code
> ---------------------------------------------------
>
> Key: DERBY-4785
> URL: https://issues.apache.org/jira/browse/DERBY-4785
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Affects Versions: 10.5.1.1, 10.6.1.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> I received a request to remove JCC testing from the derby suite. The user had a very old jcc version in their classpath 2.4 and 10.5 tests were failing with:
> com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -1, SQLSTATE: XJ040, SQLERRMC: Failed to start database '/results/axxon/58712/laka10a-derby-m101-20100830-003810/derbyall/derbynetmats/DerbyNet/derbynetmats/dblook_test_net_territory//wombat', see the next exception for details.::SQLSTATE: XJ001Java exception: 'Access denied (java.util.PropertyPermission com.ibm.crypto.provider.FIPSMODE read): java.security.AccessControlException'.
> at com.ibm.db2.jcc.c.o.a(o.java:3219)
> at com.ibm.db2.jcc.a.cb.q(cb.java:653)
> at com.ibm.db2.jcc.a.cb.p(cb.java:541)
> at com.ibm.db2.jcc.a.cb.l(cb.java:363)
> at com.ibm.db2.jcc.a.cb.d(cb.java:145)
> at com.ibm.db2.jcc.a.b.Sb(b.java:1274)
> at com.ibm.db2.jcc.a.b.a(b.java:1166)
> at com.ibm.db2.jcc.a.b.q(b.java:934)
> at com.ibm.db2.jcc.a.b.a(b.java:702)
> at com.ibm.db2.jcc.a.b.(b.java:305)
> at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:162)
> at java.sql.DriverManager.getConnection(DriverManager.java:322)
> at java.sql.DriverManager.getConnection(DriverManager.java:273)
> at org.apache.derby.tools.dblook.go(Unknown Source)
> at org.apache.derby.tools.dblook.(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.tools.dblook_test.lookThree(dblook_test.java:417)
> at org.apache.derbyTesting.functionTests.tests.tools.dblook_test.runTest(dblook_test.java:283)
> at org.apache.derbyTesting.functionTests.tests.derbynet.dblook_test_net_territory.doTest(dblook_test_net_territory.java:65)
> at org.apache.derbyTesting.functionTests.tests.derbynet.dblook_test_net_territory.main(dblook_test_net_territory.java:41)
> Now that I look at it more closely, their actual problem might be on the server side and JCC just reporting it but good to get the JCC tests out of the mix when people accidentally have it in their classpath anyway.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.