db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2435) network server boot fails indicating authentication must be set up even when authentication is fully defined in derby.properties
Date Fri, 16 Mar 2007 15:26:09 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481651
] 

Rick Hillegas commented on DERBY-2435:
--------------------------------------

Committed derby-2435-01.diff at subversion revision 519004. Derbyall and the junit tests ran
cleanly except for the DerbyNetClient run of checkDataSource30. That test failed beginning
with this error:

*** Start: checkDataSource30 jdk1.4.2_12 DerbyNetClient derbynetmats:jdk14 2007-03-15 14:31:10
***
293 del
< FAIL incorrect connection object returned for Statement.getConnection()
293a293,296
> FAIL incorrect connection object returneException in thread "main" org.apache.derby.client.am.XaException:
XAER_NOTA : Error executing a XAResource.start(), server returned XAER_NOTA.
> Caused by: org.apache.derby.client.am.SqlException: Error executing a XAResource.start(),
server returned XAER_NOTA.
> 	... 4 more

I re-ran the test against the classtree and against the jar files and was unable to reproduce
the failure. I think it is unlikely that my changes introduced this heisenbug into this test.


> network server boot fails indicating authentication must be set up even when authentication
is fully defined in derby.properties
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2435
>                 URL: https://issues.apache.org/jira/browse/DERBY-2435
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server, Security
>    Affects Versions: 10.3.0.0
>            Reporter: Daniel John Debrunner
>         Assigned To: Rick Hillegas
>            Priority: Critical
>         Attachments: derby-2435-01.diff
>
>
> Booting the server using the default to install a security manager fails even when the
derby.properties is in the current directory with these contents.
> derby.connection.requireAuthentication=true
> derby.authentication.provider=BUILTIN
> derby.user.SA=sapwd
> derby.user.MARY=marypwd
> The documentation on authentication indicates this is the preferred way to setup authentication
for a server machine.

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


Mime
View raw message