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 "Deepa Remesh (JIRA)" <de...@db.apache.org> on 2006/09/13 17:37:24 UTC
[jira] Created: (DERBY-1845) OutOfMemoryError when running "All"
suite directly using JUnit
OutOfMemoryError when running "All" suite directly using JUnit
--------------------------------------------------------------
Key: DERBY-1845
URL: http://issues.apache.org/jira/browse/DERBY-1845
Project: Derby
Issue Type: Test
Components: Test
Affects Versions: 10.3.0.0
Reporter: Deepa Remesh
OutOfMemoryError when running "All" suite directly using the following command:
java -Dderby.system.home=$PWD junit.textui.TestRunner org.apache.derbyTesting.functionTests.suites.All
where $PWD is the current working directory.
Some discussion of this is in derby-dev: http://www.nabble.com/Errors-when-running-JUnit-suite-directly-tf2261860.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Commented: (DERBY-1845) OutOfMemoryError when running "All" suite directly using JUnit
Posted by Deepa Remesh <dr...@gmail.com>.
On 10/10/06, Kristian Waagan <Kr...@sun.com> wrote:
> Hello Deepa,
>
> Yes, I'm also seeing this. I think there is a bug in
> NetworkServerTestSetup.setUp(), where the path is constructed without a
> directory separator between the rundir and the filename (line 68). When
> fixing this, I got the results posted below (sorry for the long stack
> traces).
> I'll look for a suitable Jira for the bug, or create a new one if necessary.
>
Thanks Kristian for looking into this.
Deepa
Re: [jira] Commented: (DERBY-1845) OutOfMemoryError when running "All"
suite directly using JUnit
Posted by Kristian Waagan <Kr...@Sun.COM>.
Deepa Remesh wrote:
> On 10/9/06, Knut Anders Hatlen (JIRA) <de...@db.apache.org> wrote:
>> [
>> http://issues.apache.org/jira/browse/DERBY-1845?page=comments#action_12440846
>> ]
>>
>> Knut Anders Hatlen commented on DERBY-1845:
>> -------------------------------------------
>>
>> Is this still a problem after DERBY-1910?
>>
>
> I believe this issue is same as DERBY-1910 and should be resolved now.
> However, I have not been able to verify this. When I run the "All"
> suite directly using junit, I am getting a new error at the point
> where it tries to run the client tests;
> 1) AllPackagesjava.security.AccessControlException: access denied
> (java.io.FilePermission C:\deepa\j
> unit_testserverConsoleOutput.log write)
> at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
>
> at
> java.security.AccessController.checkPermission(AccessController.java:401)
> at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
> at java.lang.SecurityManager.checkWrite(SecurityManager.java:954)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:169)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:70)
> at
> org.apache.derbyTesting.junit.NetworkServerTestSetup$1.run(NetworkServerTestSetup.java:72
>
> )
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkServerTestSetup.java:65
>
> )
> at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
>
> I have not seen this error before and wondering if it is caused by
> something in my environment. Is anyone else seeing this?
Hello Deepa,
Yes, I'm also seeing this. I think there is a bug in
NetworkServerTestSetup.setUp(), where the path is constructed without a
directory separator between the rundir and the filename (line 68). When
fixing this, I got the results posted below (sorry for the long stack
traces).
I'll look for a suitable Jira for the bug, or create a new one if necessary.
Time: 280.066
There were 3 errors:
1)
grantRevokeAfterSettingSQLAuthProperty(org.apache.derbyTesting.functionTests.
tests.lang.SQLAuthorizationPropTest)java.sql.SQLException: A network
protocol er ror was encountered and the connection has been terminated:
the requested comman d encountered an unarchitected and
implementation-specific condition for which t here was no architected
message
at
org.apache.derby.client.am.SQLExceptionFactory.getSQLException(SQLExc
eptionFactory.java:46)
at
org.apache.derby.client.am.SqlException.getSQLException(SqlException.
java:345)
at org.apache.derby.client.am.Statement.execute(Statement.java:826)
at
org.apache.derbyTesting.functionTests.tests.lang.SQLAuthorizationProp
Test.grantRevokeAfterSettingSQLAuthProperty(SQLAuthorizationPropTest.java:125)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java: 76)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
Caused by: org.apache.derby.client.am.DisconnectException: A network
protocol er ror was encountered and the connection has been terminated:
the requested comman d encountered an unarchitected and
implementation-specific condition for which t here was no architected
message
at
org.apache.derby.client.net.NetConnectionReply.parseCMDCHKRM(NetConne
ctionReply.java:888)
at
org.apache.derby.client.net.NetStatementReply.parseExecuteImmediateEr
ror(NetStatementReply.java:562)
at
org.apache.derby.client.net.NetStatementReply.parseEXCSQLIMMreply(Net
StatementReply.java:210)
at
org.apache.derby.client.net.NetStatementReply.readExecuteImmediate(Ne
tStatementReply.java:58)
at
org.apache.derby.client.net.StatementReply.readExecuteImmediate(State
mentReply.java:45)
at
org.apache.derby.client.net.NetStatement.readExecuteImmediate_(NetSta
tement.java:125)
at
org.apache.derby.client.am.Statement.readExecuteImmediate(Statement.j
ava:1320)
at
org.apache.derby.client.am.Statement.flowExecute(Statement.java:2016)
at
org.apache.derby.client.am.Statement.executeX(Statement.java:831)
at org.apache.derby.client.am.Statement.execute(Statement.java:817)
... 37 more
2) junit.framework.TestSuite@4735bjava.sql.SQLException:
java.net.ConnectExcepti on : Error connecting to server localhost on
port 1527 with message Connection r efused.
at
org.apache.derby.client.am.SQLExceptionFactory.getSQLException(SQLExc
eptionFactory.java:46)
at
org.apache.derby.client.am.SqlException.getSQLException(SqlException.
java:345)
at
org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:149)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at
org.apache.derbyTesting.junit.TestConfiguration.getConnection(TestCon
figuration.java:456)
at
org.apache.derbyTesting.junit.TestConfiguration.getDefaultConnection(
TestConfiguration.java:437)
at
org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection
(TestConfiguration.java:411)
at
org.apache.derbyTesting.junit.BaseJDBCTestSetup.getConnection(BaseJDB
CTestSetup.java:74)
at
org.apache.derbyTesting.junit.CleanDatabaseTestSetup.setUp(CleanDatab
aseTestSetup.java:68)
at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
Caused by: org.apache.derby.client.am.DisconnectException:
java.net.ConnectExcep tion : Error connecting to server localhost on
port 1527 with message Connection refused.
at org.apache.derby.client.net.NetAgent.<init>(NetAgent.java:124)
at
org.apache.derby.client.net.NetConnection.newAgent_(NetConnection.jav
a:1086)
at
org.apache.derby.client.am.Connection.<init>(Connection.java:324)
at
org.apache.derby.client.net.NetConnection.<init>(NetConnection.java:2 09)
at
org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnect
ion(ClientJDBCObjectFactoryImpl.java:201)
at
org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:140)
... 29 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:178)
at
org.apache.derby.client.net.OpenSocketAction.run(OpenSocketAction.jav a:34)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.derby.client.net.NetAgent.<init>(NetAgent.java:122)
... 34 more
3) AllPackagesjava.lang.Exception: DRDA_NoIO.S:Could not connect to
Derby Networ k Server on host 127.0.0.1, port 1527.
at
org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMe
ssageWork(NetworkServerControlImpl.java:2697)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMe
ssage(NetworkServerControlImpl.java:1508)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.setUpSocket(Netwo
rkServerControlImpl.java:2087)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.shutdown(NetworkS
erverControlImpl.java:793)
at
org.apache.derby.drda.NetworkServerControl.shutdown(NetworkServerCont
rol.java:301)
at
org.apache.derbyTesting.junit.NetworkServerTestSetup.tearDown(Network
ServerTestSetup.java:106)
at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
There were 4 failures:
1)
testGrantRevokeWithoutSQLAuthProperty(org.apache.derbyTesting.functionTests.t
ests.lang.SQLAuthorizationPropTest)junit.framework.AssertionFailedError:
FAIL: G rant statement should have failed when SQL authorization is not set
at
org.apache.derbyTesting.functionTests.tests.lang.SQLAuthorizationProp
Test.testGrantRevokeWithoutSQLAuthProperty(SQLAuthorizationPropTest.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java: 76)
2)
testInertTime(org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTe
st)junit.framework.AssertionFailedError: TIME to java.sql.Timestamp does
not con tain current date 1900-01-01 07:38:05.0
at
org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.che
ckTimeValue(TimeHandlingTest.java:645)
at
org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.tes
tInertTime(TimeHandlingTest.java:198)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java: 76)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
3)
testCurrentTime(org.apache.derbyTesting.functionTests.tests.lang.TimeHandling
Test)junit.framework.AssertionFailedError: TIME to java.sql.Timestamp
does not c ontain current date 1900-01-01 14:14:06.0
at
org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.che
ckTimeValue(TimeHandlingTest.java:645)
at
org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.che
ckCurrentTimeValue(TimeHandlingTest.java:726)
at
org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.che
ckCurrentTimeMultiple(TimeHandlingTest.java:518)
at
org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.che
ckCurrentMultiple(TimeHandlingTest.java:492)
at
org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.che
ckCurrentQuery(TimeHandlingTest.java:468)
at
org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.cur
rentFunctionTests(TimeHandlingTest.java:280)
at
org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.tes
tCurrentTime(TimeHandlingTest.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java: 76)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
4)
testGrantRevokeWithoutSQLAuthProperty(org.apache.derbyTesting.functionTests.t
ests.lang.SQLAuthorizationPropTest)junit.framework.AssertionFailedError:
FAIL: G rant statement should have failed when SQL authorization is not set
at
org.apache.derbyTesting.functionTests.tests.lang.SQLAuthorizationProp
Test.testGrantRevokeWithoutSQLAuthProperty(SQLAuthorizationPropTest.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java: 76)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
FAILURES!!!
Tests run: 1760, Failures: 4, Errors: 3
--
Kristian
>
> Thanks,
> Deepa
Re: [jira] Commented: (DERBY-1845) OutOfMemoryError when running "All" suite directly using JUnit
Posted by Deepa Remesh <dr...@gmail.com>.
On 10/9/06, Knut Anders Hatlen (JIRA) <de...@db.apache.org> wrote:
> [ http://issues.apache.org/jira/browse/DERBY-1845?page=comments#action_12440846 ]
>
> Knut Anders Hatlen commented on DERBY-1845:
> -------------------------------------------
>
> Is this still a problem after DERBY-1910?
>
I believe this issue is same as DERBY-1910 and should be resolved now.
However, I have not been able to verify this. When I run the "All"
suite directly using junit, I am getting a new error at the point
where it tries to run the client tests;
1) AllPackagesjava.security.AccessControlException: access denied
(java.io.FilePermission C:\deepa\j
unit_testserverConsoleOutput.log write)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
at java.security.AccessController.checkPermission(AccessController.java:401)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
at java.lang.SecurityManager.checkWrite(SecurityManager.java:954)
at java.io.FileOutputStream.<init>(FileOutputStream.java:169)
at java.io.FileOutputStream.<init>(FileOutputStream.java:70)
at org.apache.derbyTesting.junit.NetworkServerTestSetup$1.run(NetworkServerTestSetup.java:72
)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkServerTestSetup.java:65
)
at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
I have not seen this error before and wondering if it is caused by
something in my environment. Is anyone else seeing this?
Thanks,
Deepa
[jira] Commented: (DERBY-1845) OutOfMemoryError when running "All"
suite directly using JUnit
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648350#action_12648350 ]
Kathey Marsden commented on DERBY-1845:
---------------------------------------
Can this issue be closed? I thought as a rule, you had to run with 512MB heap.
> OutOfMemoryError when running "All" suite directly using JUnit
> --------------------------------------------------------------
>
> Key: DERBY-1845
> URL: https://issues.apache.org/jira/browse/DERBY-1845
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.3.1.4
> Reporter: Deepa Remesh
>
> OutOfMemoryError when running "All" suite directly using the following command:
> java -Dderby.system.home=$PWD junit.textui.TestRunner org.apache.derbyTesting.functionTests.suites.All
> where $PWD is the current working directory.
> Some discussion of this is in derby-dev: http://www.nabble.com/Errors-when-running-JUnit-suite-directly-tf2261860.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1845) OutOfMemoryError when running "All"
suite directly using JUnit
Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1845?page=comments#action_12440846 ]
Knut Anders Hatlen commented on DERBY-1845:
-------------------------------------------
Is this still a problem after DERBY-1910?
> OutOfMemoryError when running "All" suite directly using JUnit
> --------------------------------------------------------------
>
> Key: DERBY-1845
> URL: http://issues.apache.org/jira/browse/DERBY-1845
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Deepa Remesh
>
> OutOfMemoryError when running "All" suite directly using the following command:
> java -Dderby.system.home=$PWD junit.textui.TestRunner org.apache.derbyTesting.functionTests.suites.All
> where $PWD is the current working directory.
> Some discussion of this is in derby-dev: http://www.nabble.com/Errors-when-running-JUnit-suite-directly-tf2261860.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-1845) OutOfMemoryError when running "All"
suite directly using JUnit
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden closed DERBY-1845.
---------------------------------
Resolution: Duplicate
Per comments closing as a duplicate of DERBY-1910
> OutOfMemoryError when running "All" suite directly using JUnit
> --------------------------------------------------------------
>
> Key: DERBY-1845
> URL: https://issues.apache.org/jira/browse/DERBY-1845
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.3.1.4
> Reporter: Deepa Remesh
>
> OutOfMemoryError when running "All" suite directly using the following command:
> java -Dderby.system.home=$PWD junit.textui.TestRunner org.apache.derbyTesting.functionTests.suites.All
> where $PWD is the current working directory.
> Some discussion of this is in derby-dev: http://www.nabble.com/Errors-when-running-JUnit-suite-directly-tf2261860.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.