db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lily Wei (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4715) Write jvm information and path of derby.jar to derby.log
Date Wed, 14 Jul 2010 16:14:49 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888412#action_12888412

Lily Wei commented on DERBY-4715:

Thank you, Knut. Yeah! Suites.all and derbyall seem to run fine except:
1) ttestSetPortPriority(org.apache.derbyTesting.functionTests.tests.derbynet.Serve
rPropertiesTest)junit.framework.AssertionFailedError: Port 1537 exceeeds expected
maximum. You may need to update TestConfiguration.MAX_PORTS_USED and the Wiki page
 at http://wiki.apache.org/db-derby/DerbyJUnitTesting if test runs now require mor
e available ports
        at org.apache.derbyTesting.junit.TestConfiguration.getNextAvailablePort(Te
        at org.apache.derbyTesting.functionTests.tests.derbynet.ServerPropertiesTe
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso
        at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:10
        at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)

This failure is a known issue by the group.

DERBY-4715-5.diff is ready to submit.

> Write jvm information and path of derby.jar to derby.log
> --------------------------------------------------------
>                 Key: DERBY-4715
>                 URL: https://issues.apache.org/jira/browse/DERBY-4715
>             Project: Derby
>          Issue Type: Bug
>          Components: Miscellaneous
>    Affects Versions:
>            Reporter: Lily Wei
>            Assignee: Lily Wei
>            Priority: Minor
>             Fix For:
>         Attachments: DERBY-4715-1.diff, DERBY-4715-2.diff, DERBY-4715-3.diff, DERBY-4715-4.diff,
DERBY-4715-5.diff, derby.log
> The bug is part of DERBY-1272. In production environment, derby.jar can be located different
than the derbyclient.jar It can be easier if we have jvm version information and path of derby.jar
are in the derby.log

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message