Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-tck-dev] database derbyDB was not found error during Platform TCK run 


On 6/16/20 4:45 AM, Steve Millidge (Payara) wrote:

I’ve had a look at the logs and my quick view is;
The javax references in the email below are just logger names and I know some of those haven’t been changed over yet. However that shouldn’t impact functionally. 

Thanks, this is helpful!



Line 1087 derby.dbName=derbyDB

Line 1453 derby.dbName.ri=derbyDBri
Line 4568 whitebox-mdcomplete.rar fails to deploy but a few other rars before succeed.
The jakartaee-tck/src/com/sun/ts/tests/common/connector/whitebox/mdcomplete/ra-md-complete.xml is using https://jakarta.ee/xml/ns/jakartaee/connector_2_0.xsd and right schema version (2.0).
Just a guess but I wonder if it would help if we updated (command.testExecute) to have tools.jar at the end of the classpath. 




Line 5006 configure.RI.backend:

      [echo] DB URL: jdbc:derby://localhost:1527/derbyDBri;create=true

Line 5114 configure.interop:

      [echo] DB URL: jdbc:derby://localhost:1527/derbyDBri;create=true
Line 5624    [runcts] OUT => [javatest.batch] 7198: RAR5038:Unexpected exception while creating resource for pool cts-derby-pool. Exception : jakarta.resource.spi.ResourceAllocationException: Connection could not be allocated because: The connection was refused because the database derbyDB was not found.]] 

Line 5630 deployment fails because the database derbyDB is not found.
Two databases URLs are set up however the configure.interop  and the configure.RI.backend both use the ri database URL is that intentional? I would guess the configure.RI.backend task should be configuring the derbyDB database.
https://github.com/eclipse-ee4j/jakartaee-tck/issues/333 is for removing the configure.interop + related *ddl.interop.sql scripts, as they aren't needed in EE 9. 

Scott



Steve
*From:*jakartaee-tck-dev-bounces@xxxxxxxxxxx <jakartaee-tck-dev-bounces@xxxxxxxxxxx> *On Behalf Of *Ed Bratt 
*Sent:* 15 June 2020 23:50
*To:* jakartaee-tck developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>; Scott Marlow <smarlow@xxxxxxxxxx> *Subject:* Re: [jakartaee-tck-dev] database derbyDB was not found error during Platform TCK run
The stand-alone persistence TCK is passing at 100% (yay that!). A successful log is at [1] below.
It looks like the resource adapter code might not yet be fully Jakartafied. It also appears there are still a few javax references in some of the TCK XML definition files. (I saw a separate note about that. Maybe this is being addressed?)
Looking at the console log for the puservlet stage [2] (be careful before you download this too many times, this is a 175MB log file), one will see deployment failures, just ahead of the JPA failure listed in this issue. I think we can ignore the stop-domain failures.
deploy.all.rars target seems to fail, leading to BUILD FAILED (Line 4591) but I don't know if that's relevant. 

At line 5497, we see the jpa_core_annotations deployment failures

Backing up a little, at line 5462, the following is reported:
   [runcts] OUT => [javatest.batch] 7197: [2020-06-14T11:04:55.697+0000] [glassfish 6.0] [WARNING] 
    [poolmgr.create_resource_error]
    [javax.enterprise.resource.resourceadapter.com.sun.enterprise.resource.allocator]
    [tid: _ThreadID=53 _ThreadName=AutoDeployer] [timeMillis:
    1592132695697] [levelValue: 900] [[

Note, the reference to _javax_.enterprise.resource.resourceadapter. ...
Further down, in the snippet of the GlassFish Domain log, you can see several references to javax.enterprise.system.tools. These start at line 5622.
Looking backward, I see javax in several command arguments for the ant run command (line 5278).
Also, one line up from the first  RAR5038 error, on line 5652, you can also see another javax.enterprise.resource .... "create_resource_error." 

I'd check to be sure these javax references are intentional.

Maybe this helps?

Log files referenced:
[1] https://ci.eclipse.org/jakartaee-tck/blue/rest/organizations/jenkins/pipelines/jakartaee-tck/branches/master/runs/697/nodes/70/steps/294/log/?start=0
[2] https://ci.eclipse.org/jakartaee-tck/blue/rest/organizations/jenkins/pipelines/jakartaee-tck/branches/master/runs/695/nodes/148/steps/1138/log/?start=0 

On 6/15/2020 11:49 AM, Scott Marlow wrote:

    Hi,

    We are getting JPA TCK failures connecting to Derby [1].

    The Derby classes + version information is shown in the start of the
    TCK run, we seem to successfully run the init.derby task.

    The test failure is shown at [2].  Any idea why we are getting this
    error?

    Scott

    [1] RAR5038:Unexpected exception while creating resource for pool
    cts-derby-pool. Exception :
    jakarta.resource.spi.ResourceAllocationException: Connection could
    not be allocated because: The connection was refused because the
    database derbyDB was not found.

    [2]
    https://ci.eclipse.org/jakartaee-tck/job/jakartaeetck-nightly-run-master/43/junit-reports-with-handlebars/test-summary/943fb33e-51f1-4e34-9fbe-36d3c392e056.html



    _______________________________________________

    jakartaee-tck-dev mailing list

    jakartaee-tck-dev@xxxxxxxxxxx  <mailto:jakartaee-tck-dev@xxxxxxxxxxx>

    To unsubscribe from this list, visithttps://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev


_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev

Back to the top