Is that really how we spell retrieve in this test? in "retreiveMessagesfrom ServerOnGetServer=true"...
I'm not sure that is the current problem, but it *is* spelled wrong...
And with the derby client the property is different, retrieveMessageText, and it should be the default and thus unnecessary for a client connection...We're having a client connection according to the class in the stack, yes?
Myrna
On 11/10/05, Bernt M. Johnsen <[EMAIL PROTECTED]> wrote:
Anyone know what happens here?
derbyall/derbynetclientmats/derbynetclientmats.fail:junitTests/derbynet/CompatibilityTest.java
*** Start: CompatibilityTest jdk1.4.2_05 DerbyNetClient derbynetclientmats:derbynetclientmats 2005-11-10 14:42:50 ***
0 add
> org.apache.derby.client.am.DisconnectException: The application server rejected establishment of the connection. An attempt was made to access a database, wombat;retreiveMessagesFromServerOnGetMessage=true, which was not found.
> Exception in thread "main" java.lang.Exception: Error lookup up server info: The application server rejected establishment of the connection. An attempt was made to access a database, wombat;retreiveMessagesFromServerOnGetMessage=true, which was not found.
Test Failed.
*** End: CompatibilityTest jdk1.4.2_05 DerbyNetClient derbynetclientmats:derbynetclientmats 2005-11-10 14:42:59 ***
----------------------------------------------------------
CompatabilityTest.out looks like this:
org.apache.derby.client.am.DisconnectException: The application server rejected establishment of the connection. An attempt was made to access a database, wombat;retreiveMessagesFromServerOnGetMessage=true, which was not found.
at org.apache.derby.client.net.NetConnectionReply.parseRDBNFNRM(NetConnectionReply.java:971)
at org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(NetConnectionReply.java:434)
at org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(NetConnectionReply.java:292)
at org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(NetConnectionReply.java:119)
at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb (NetConnection.java:755)
at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(NetConnection.java:680)
at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(NetConnection.java :553)
at org.apache.derby.client.net.NetConnection.flowConnect(NetConnection.java:385)
at org.apache.derby.client.net.NetConnection.<init>(NetConnection.java:195)
at org.apache.derby.jdbc.ClientDriver.connect (ClientDriver.java:125)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilitySuite.getConnection (CompatibilitySuite.java:416)
at org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilitySuite.getConnection(CompatibilitySuite.java:400)
at org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilitySuite.findServer (CompatibilitySuite.java:304)
at org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilitySuite.main(CompatibilitySuite.java:167)
at org.apache.derbyTesting.functionTests.tests.junitTests.derbynet.CompatibilityTest.main (CompatibilityTest.java:71)
Exception in thread "main" java.lang.Exception: Error lookup up server info: The application server rejected establishment of the connection. An attempt was made to access a database, wombat;retreiveMessagesFromServerOnGetMessage=true, which was not found.
at org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilitySuite.findServer(CompatibilitySuite.java:314)
at org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilitySuite.main (CompatibilitySuite.java:167)
at org.apache.derbyTesting.functionTests.tests.junitTests.derbynet.CompatibilityTest.main(CompatibilityTest.java:71)
--
Bernt Marius Johnsen, Database Technology Group,
Sun Microsystems, Trondheim, Norway
