Hi Bonnie, ----- Original Message ----- From: "Bonnie MacKellar" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Friday, March 28, 2003 9:38 PM Subject: RE: regression test errors
> OK, I figured out how to run the tests with SequenceManagerInMemoryImpl. > I still get the messages > ----------------------- > JTurbo 3.0.2 JDBC 2.1 Driver]: Communication Link Failure. Socket Closed > [org.apache.ojb.broker.util.sequence.SequenceManagerHelper] WARN: Cannot > lookup max value from table SM_KEY for column STRING_KEY, PB was > ----------------------- > This is what I got before with the default sequence manager. ** Before the sequence manager first time assign a new id for a (primary key) field, SequenceManagerHelper try to figure out the current max value of the field (select max...). This does not work in your case. > > I notice that these messages are marked WARN. There are also messages marked > ERROR and 2 marked FAILURE. What is the difference between these levels? Do > I need to worry about WARN messages? Yes, this means you should watch what's going on. OJB try to ignore the problems or to go an alternative way. ERROR was used if something definite goes wrong and there is no way to bypass the problem. > > One FAIL message looks like this > ---------------------- > Testcase: testMaxKeySearch1 took 0.11 sec > FAILED > Expected 131, something goes wrong when try to identify max PK id in the > prepared database tables - Check the ...SMMAX... database tables for id 131, > if id was found in one of the tables, test fails expected:<131> but was:<0> > ---------------------- Result of ** > > The other looks like this > ---------------------- > Testcase: testIterator took 0.01 sec > FAILED > org.apache.ojb.broker.PersistenceBrokerSQLException: > java.net.SocketException: Socket Closed AFAIK there some other postings on the list report the same problem with MSSQL server / jdbc driver. But I think there some people using OJB and MSSQL server with success (sorry, I use hsql/sapDB only). regards, Armin > junit.framework.AssertionFailedError: > org.apache.ojb.broker.PersistenceBrokerSQLException: > java.net.SocketException: Socket Closed > at > org.apache.ojb.broker.RsIteratorTest.testIterator(RsIteratorTest.java:59 ) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39 > ) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl > .java:25) > -------------------- > > I have not a clue what either failure means. > > thanks, > Bonnie MacKellar > -----Original Message----- > From: Armin Waibel [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 26, 2003 6:42 PM > To: OJB Users List > Subject: Re: regression test errors > > > Hi Bonnie, > > ----- Original Message ----- > From: "Bonnie MacKellar" <[EMAIL PROTECTED]> > To: "OJB Users List" <[EMAIL PROTECTED]> > Sent: Wednesday, March 26, 2003 11:27 PM > Subject: regression test errors > > > > > > OK, now that I have a build, how do I go about understanding > > and fixing errors in the regressions tests? > > > > My environment : built with JSDK1.4.0_03 > > DBMS is MSSqlServer2000 > > JDBC driver is JTurbo 3.0.2 JDBC 2.1 Driver > > > > I get several errors in the broker tests : > > Testsuite: org.apache.ojb.broker.AllTests > > Tests run: 187, Failures: 2, Errors: 10, Time elapsed: 50.583 sec > > > > Most of these errors seem to be socket failures > > JTurbo 3.0.2 JDBC 2.1 Driver]: Communication Link Failure. Socket > Closed > > [org.apache.ojb.broker.util.sequence.SequenceManagerHelper] WARN: > Cannot > > lookup max value from table SM_TAB_BB for column SM_ID, PB was > > [EMAIL PROTECTED], using > > jdbc-descriptor > > [EMAIL PROTECTED] > > > > Seems a problem with the used sequence manager > (SequenceManagerHighLowImpl). > Try to run the test cases with SequenceManagerInMemoryImpl > Do you get the same results? > > > or connection problems > > > > Error getting Connection from DriverManager with url > > (jdbc:JTurbo://W2KBMACKELL/ActiveBill) and driver > > (com.newatlanta.jturbo.driver.Driver): Login failed for user > '!!TestCase: > > This should fail!!'. > > Used ConnectionManager instance could not obtain a connection: Could > not > > borrow connection from pool - > > org.apache.ojb.broker.metadata.JdbcConnectionDescriptor: > > [EMAIL PROTECTED] > > This test case have to fail, ignore the error message. > > > > > Now, I have successfully used JTurbo and this DBMS in the past to do > > connection pooling under Weblogic, so I don't think there is a DBMS > > configuration problem. > > > > What is the best way to attack this sort of problem? What files should > I be > > looking at? > > All ;-) > > OK, good initial point are the ConnectionFactory implementation > classes (default is ConnectionFactoryPooledImpl) manage the connections. > > ConnectionManagerImpl does the connection tx/life cycle handling. > > regards, > Armin > > > > > thanks, > > Bonnie MacKellar > > [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
