[ http://issues.apache.org/jira/browse/DERBY-1052?page=all ]
Myrna van Lunteren updated DERBY-1052:
--------------------------------------
Attachment: DERBY-1052_testutil_2006_03_08.diff
M java\testing\org\apache\derbyTesting\functionTests\util\TestUtil.java
I'm attaching an attempted fix for this.
I tested with remote server with insane jars, ran derbyall, and for good
measure, also ran derbyall with wctme5.7_foundation.
There were the 'known' wctme5.7 failures (bootLock, SUR*test...), the
checkDataSource and savepointJdbc30_XA tests passed with remote server, and
derbyall looked good...
Except for one mysterious failure with my change: on linux (not on windows
machine), with jars built on windows, the test derbynet/runtimeinfo.java failed
with both DerbyNet and DerbyNetClient. It's very strange, because that test
does not use datasources in any way that I can see. Also, the result is
intermittent...
I am hoping someone will have a chance to review this and run the test on linux
after applying my patch...
This is an example diff I'm seeing:
--------
....
Attempt to shutdown framework: DerbyNetClient
57a58,66
> Session # :2
> Database :wombat;create=true
> User :APP
> # Statements:2
> Prepared Statement Information:
> Stmt ID SQLText
> ------------- -----------
> SYSLH0002 VALUES(1)
> SYSLH0001 SELECT count(*) from sys.systables
61 del
< # Active Sessions : 1
61a70
> # Active Sessions : 2
Test Failed.
*** End: runtimeinfo jdk1.4.2_04 DerbyNetClient 2006-03-08 12:11:27 ***
-----------------------
> test jdbcapi/checkDataSource30 and savepointJdbc30_XA fail with remote server
> with security exceptions
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1052
> URL: http://issues.apache.org/jira/browse/DERBY-1052
> Project: Derby
> Type: Test
> Components: Regression Test Failure
> Environment: windows, server jdk13 or jdk14, client jdk14
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-1052_testutil_2006_03_08.diff
>
> The .tmp from the jdbcapi/checkDataSource30.java is:
> ----------------------
> START XA HOLDABILITY TEST
> ERROR (no SQLState): java.security.PrivilegedActionException : Error opening
> socket to server localhost on port 1527 with message : Connection refused
> Completed checkDataSource30
> ----------------------
> The .tmp from the jdbcapi/savepointJdbc30_XA.java is:
> -------------------------------------
> FAIL -- unexpected exception
> SQLSTATE(null):java.sql.SQLException: java.security.PrivilegedActionException
> : Error opening socket to server localhost on port 1527 with message :
> Connection refused
> at
> org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:285)
> at
> org.apache.derby.client.ClientPooledConnection.<init>(ClientPooledConnection.java:104)
> at
> org.apache.derby.client.ClientXAConnection.<init>(ClientXAConnection.java:47)
> at
> org.apache.derby.jdbc.ClientXADataSource.getXAConnection(ClientXADataSource.java:50)
> at
> org.apache.derby.jdbc.ClientXADataSource.getXAConnection(ClientXADataSource.java:43)
> at
> org.apache.derbyTesting.functionTests.tests.jdbcapi.savepointJdbc30_XA.main(savepointJdbc30_XA.java:58)
> Caused by: org.apache.derby.client.am.DisconnectException:
> java.security.PrivilegedActionException : Error opening socket to server
> localhost on port 1527 with message : Connection refused
> at org.apache.derby.client.net.NetAgent.<init>(NetAgent.java:113)
> at
> org.apache.derby.client.net.NetConnection.newAgent_(NetConnection.java:928)
> at
> org.apache.derby.client.am.Connection.initConnection(Connection.java:174)
> at org.apache.derby.client.am.Connection.<init>(Connection.java:144)
> at
> org.apache.derby.client.net.NetConnection.<init>(NetConnection.java:207)
> at
> org.apache.derby.client.net.NetXAConnection.<init>(NetXAConnection.java:39)
> at
> org.apache.derby.client.ClientPooledConnection.<init>(ClientPooledConnection.java:94)
> ... 4 more
> -----------------------------
--
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
