[
https://issues.jboss.org/browse/TEIIDDES-2041?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-2041:
----------------------------------------
The stack trace indicates you are trying to connect from the Eclipse Data Source Explorer
and it appears it's an Eclipse Data Tools issue ?
The issue will have to be logged at:
https://bugs.eclipse.org/bugs/
In the meantime, you might have more luck changing your connection profile type. There
are specific JDBC connection profiles for DB2. You could try using that profile instead of
"Generic JDBC" profile.
For my DB2 connections I use the driver jar: *db2jcc4.jar*
Null Pointer Exception creating DB2 JDBC Connection
---------------------------------------------------
Key: TEIIDDES-2041
URL:
https://issues.jboss.org/browse/TEIIDDES-2041
Project: Teiid Designer
Issue Type: Bug
Environment: Designer 8.3.1.Final-v20140122-1920-B21. Running in eclipse Kepler
on Windows 7 with jdk1.7.0_45
Reporter: Jim Riley
When trying to Make a JDBC connection to DB2 Database a Null Pointer Exception is
encountered. The Ping to test the connection is successful.
I tried connecting to a AIX DB2 instance and a Mainframe instance. The result was the
same.
The detailed messages is:
Could not connect to New Generic JDBC.
Error creating SQL Model Connection connection to New Generic JDBC. (Error: null)
java.lang.NullPointerException
OK
The log file contains:
!ENTRY org.eclipse.datatools.connectivity 4 -1 2014-02-06 10:18:14.869
!MESSAGE Could not connect to DMS Net Driver JDBC.
!SUBENTRY 1 org.eclipse.datatools.connectivity 4 -1 2014-02-06 10:18:14.869
!MESSAGE Error creating SQL Model Connection connection to DMS Net Driver JDBC. (Error:
null)
!STACK 0
java.lang.NullPointerException
at
org.eclipse.datatools.connectivity.sqm.internal.core.util.DatabaseProviderHelper.getCatalogDatabase(DatabaseProviderHelper.java:37)
at
org.eclipse.datatools.connectivity.sqm.internal.core.util.DatabaseProviderHelper.setDatabase(DatabaseProviderHelper.java:47)
at
org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.initializeJDBCConnection(ConnectionInfoImpl.java:718)
at
org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.<init>(ConnectionInfoImpl.java:690)
at
org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:38)
at
org.eclipse.datatools.connectivity.sqm.core.SQMConnectionFactory.createConnection(SQMConnectionFactory.java:45)
at
org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:59)
at
org.eclipse.datatools.connectivity.internal.ConnectionFactoryAdapterProvider.createConnection(ConnectionFactoryAdapterProvider.java:114)
at
org.eclipse.datatools.connectivity.internal.ManagedConnection.createConnection(ManagedConnection.java:163)
at
org.eclipse.datatools.connectivity.internal.CreateConnectionJob.run(CreateConnectionJob.java:56)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
!SUBENTRY 1 unknown 0 0 2014-02-06 10:18:14.869
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira