[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.dtp] Re: TransientConnectionException: No current connection

Hi Chris...

This definitely seems like a bug to me.

Can you write up a bugzilla with what you have here and we can take a look 
at it for 1.7.1?

--Fitz

"Chris Giblin" <cgi@xxxxxxxxxxxxxx> wrote in message 
news:h039rh$ubo$1@xxxxxxxxxxxxxxxxxxxx
> Hi,
> I obtain a jdbc connection from the ProfileConnectionManager and use it to 
> successfully import 3700 rows.
>
> Next, I go to the Data Source Explorer and click on the "Schemas" folder 
> of the database but the folder does not expand. In my Eclipse development 
> environment, I see the above-mentioned exceptionin the console. I 
> disconnect and connect the database. Then I can navigate into the 
> "Schemas" folder again and edit the desired table.
>
> I have attached the stack trace at the very end of this message.
>
> Did I take the one and only connection for this database? If so, can I 
> return it? I have tried closing the connection, nulling it but I get the 
> same error. I do not see a method on the ProfileConnectionManager for 
> returning a connection.
>
> I am using a ganymede birt build from eclipse.org with these versions:
>   BIRT 2.3.2
>   DTP 1.6.2
>   Eclipse 3.4.2
>   EMF 2.4.2
>
> My db driver is the Derby 10.2 Embedded JDBC driver.
>
> Any suggestions what is wrong?
>
> Thanks,
> chris
>
> Stack trace:
>
> java.sql.SQLTransientConnectionException: No current connection.
> at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown 
> Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.checkIfClosed(Unknown 
> Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.getMetaData(Unknown Source)
> at 
> org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionAdapter.getMetaData(ConnectionAdapter.java:98)
> at 
> org.eclipse.datatools.connectivity.sqm.loader.JDBCCatalogLoader.createResultSet(JDBCCatalogLoader.java:175)
> at 
> org.eclipse.datatools.connectivity.sqm.loader.JDBCCatalogLoader.loadCatalogs(JDBCCatalogLoader.java:108)
> at 
> org.eclipse.datatools.connectivity.sqm.core.rte.jdbc.JDBCDatabase.loadCatalogs(JDBCDatabase.java:101)
> at 
> org.eclipse.datatools.connectivity.sqm.core.rte.jdbc.JDBCDatabase.getCatalogs(JDBCDatabase.java:63)
> at 
> org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.vnode.ServerExplorerVNodeContentProviderNav.displayDatabaseChildren(ServerExplorerVNodeContentProviderNav.java:366)
> at 
> org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.AbstractOnDemandContentProviderNav.getChildren(AbstractOnDemandContentProviderNav.java:116)
> at 
> org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.AbstractOnDemandContentProviderNav.getChildren(AbstractOnDemandContentProviderNav.java:239)
> at 
> org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.AbstractLayoutProviderNav.getChildren(AbstractLayoutProviderNav.java:85)
> at 
> org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.impl.ServerExplorerContentProviderNav.load(ServerExplorerContentProviderNav.java:153)
> at 
> org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.loading.LoadingJob.run(LoadingJob.java:43)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.sql.SQLException: No current connection.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown 
> Source)
> at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown 
> Source)
> ... 18 more
>