You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2007/07/30 17:35:48 UTC

[jira] Closed: (SM-1010) net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:365)

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

Guillaume Nodet closed SM-1010.
-------------------------------

    Resolution: Won't Fix

This issue is not related to ServiceMix.
This is a SQLServer connection problem it seems.

> net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:365)
> -----------------------------------------------------------------------------
>
>                 Key: SM-1010
>                 URL: https://issues.apache.org/activemq/browse/SM-1010
>             Project: ServiceMix
>          Issue Type: Bug
>            Reporter: ashokreddy
>            Priority: Critical
>
>  23:20:14,810 WARN  [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying
>  connection that is not valid, due to the following exception: net.sourceforge.jtds.jdbc.ConnectionJDBC3@17d57
> 42f
> java.sql.SQLException: SHUTDOWN is in progress.
>         at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:365)
>         at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2781)
>         at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2224)
>         at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:628)
>         at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:525)
>         at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:487)
>         at net.sourceforge.jtds.jdbc.JtdsStatement.executeImpl(JtdsStatement.java:664)
>         at net.sourceforge.jtds.jdbc.JtdsStatement.execute(JtdsStatement.java:1114)
>         at org.jboss.resource.adapter.jdbc.CheckValidConnectionSQL.isValidConnection(CheckValidConnectionSQL.j
> ava:58)
>         at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperMa
> nagedConnectionFactory.java:389)
>         at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnectio
> n.java:231)
>         at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalMa
> nagedConnectionFactory.java:191)
>         at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedCon
> nectionPool.java:187)
>         at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManaged
> ConnectionPool.java:454)
>         at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionMana
> ger2.java:324)
>         at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConn

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