db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-2498) NullPointerException on ClientDataSource.getConnection() when ds.setdatabaseName was invalid
Date Tue, 04 Nov 2008 15:00:44 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren resolved DERBY-2498.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.5.0.0
       Derby Info:   (was: [Patch Available])

Committed the patch with revision 711266. I don't think this merits a release note, the behavior
has only changed in that we now get an appropriate SQLException where before we'd get a NullPointerException.

> NullPointerException on ClientDataSource.getConnection() when ds.setdatabaseName was
invalid 
> ---------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2498
>                 URL: https://issues.apache.org/jira/browse/DERBY-2498
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.3.1.4
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>             Fix For: 10.5.0.0
>
>         Attachments: DERBY-2498.diff
>
>
> The following code snippet:
>                ClientDataSource ds = 
>                     (ClientDataSource)JDBCDataSource.getDataSource();
>                 // invalid database string
>                 ds.setDatabaseName("jdbc:derby:wombat");
>                 ds.getConnection();
> results (with jdk14) in this stack trace:
> java.lang.NullPointerException
> 	at org.apache.derby.client.am.ProductLevel.<init>(ProductLevel.java:41)
> 	at org.apache.derby.client.net.NetDatabaseMetaData.<init>(NetDatabaseMetaData.java:40)
> 	at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetDatabaseMetaData(ClientJDBCObjectFactoryImpl.java:276)
> 	at org.apache.derby.client.net.NetConnection.newDatabaseMetaData_(NetConnection.java:1144)
> 	at org.apache.derby.client.am.Connection.completeConnect(Connection.java:1803)
> 	at org.apache.derby.client.net.NetConnection.completeConnect(NetConnection.java:412)
> 	at org.apache.derby.client.net.NetConnection.initialize(NetConnection.java:297)
> 	at org.apache.derby.client.net.NetConnection.<init>(NetConnection.java:231)
> 	at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(ClientJDBCObjectFactoryImpl.java:213)
> 	at org.apache.derby.jdbc.ClientDataSource.getConnection(ClientDataSource.java:186)
> 	at org.apache.derby.jdbc.ClientDataSource.getConnection(ClientDataSource.java:163)
> 	at org.apache.derbyTesting.functionTests.tests.jdbcapi.DataSourceTest.testJira95ds(DataSourceTest.java:808)
> This is a similar situation as described for EmbeddedDataSource in DERBY-95.
> This bug was found when converting the test for DERBY-95 to junit - the old test was
explicitly creating an EmbeddedDataSource, so, this was never tested for Client (even when
running with network server).
> Note, that the similar test for XADataSource, even for client, does not result in an
NPE. 
> I have not tested PooledDataSource, but it should be checked.

-- 
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