[
https://issues.apache.org/jira/browse/DERBY-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-5069:
----------------------------------
Attachment: TestWemeLoad.java
It is the driver.getClass() call that prevents the class from loading with
weme. If I run the attached Program TestWemeLoad.java with the driver.getClass
call as attached I get the following error verifying the class.
+ c:/cygwin/ibmsvn/ntsoftware/weme6.2/bin/j9 -jcl:foun11 -DderbyTesting.serverho
st=localhost -DderbyTesting.clienthost=localhost -Demma.active= -Xbootclasspath/
a:c:/cygwin/ibmsvn/ntsoftware/weme6.2/lib/jdbc.jar -Dbootcp=c:/cygwin/ibmsvn/nts
oftware/weme6.2/lib/jdbc.jar TestWemeLoad
Exception in thread "main" java.lang.NoClassDefFoundError: java.sql.Driver
at java.lang.J9VMInternals.verifyImpl(Native Method)
at java.lang.J9VMInternals.verify(J9VMInternals.java:88)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:150)
If I comment out the line
// System.out.println(driver.getClass());
it runs and exits gracefully with:
Not going to run because I am J2ME
I am curious if this is specific to WEME or if phoneME behaves the same way. I
am sort of surprised even with the getClass() commented out that the class
verifies with all the Driver and DriverManager references.
> Since Feb 7,2011 weme 6.2 Junit tests have failed to run completely with
> Failed to invoke suite():java.lang.reflect.InvocationTargetException
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5069
> URL: https://issues.apache.org/jira/browse/DERBY-5069
> Project: Derby
> Issue Type: Bug
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Critical
> Attachments: TestWemeLoad.java, derby-5069_diff.txt
>
>
> Since Feb 8, the weme 6.2 Junit tests have failed to run. The only output on
> the test report is:
> Failed to invoke suite():java.lang.reflect.InvocationTargetException
> Below is the list of checkins on the day it started failing. derbyall looks
> ok.
> SUBVERSION LOG FROM 1067846 TO 1068253:
> ------------------------------------------------------------------------
> r1068073 | rhillegas | 2011-02-07 11:34:02 -0800 (Mon, 07 Feb 2011) | 1 line
> DERBY-4869: Attempt to fix problem in tinderbox tests introduced by a
> previous commit today.
> ------------------------------------------------------------------------
> r1067991 | rhillegas | 2011-02-07 08:04:25 -0800 (Mon, 07 Feb 2011) | 1 line
> DERBY-4869: Always raise SQLFeatureNotSupportedException when
> Connection.get/setNetworkTimeout() is called.
> ------------------------------------------------------------------------
> r1067954 | rhillegas | 2011-02-07 06:54:31 -0800 (Mon, 07 Feb 2011) | 1 line
> DERBY-4869: Add JDBC 4.1 getParentLogger() method to Derby's implementations
> of Driver and CommonDataSource.
> ------------------------------------------------------------------------
> This should be promoted to blocker if determined to be a product regression.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
