db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-2066) DisconnectException: The DDM object 0x1232 is not supported following shutdown of embedded engine while network server is running
Date Mon, 04 Apr 2011 11:45:05 GMT

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

Knut Anders Hatlen commented on DERBY-2066:
-------------------------------------------

Hi Rick,

It sounds reasonable to me to change this code so that the SQLExceptions have an SQLState.
Perhaps not 08002, though, as that's reserved for "connection name in use", if I read my copy
of SQL:2003 correctly.

Would it make sense to use Util.generateCsSQLException() instead of constructing a new SQLException
directly? Then we'd go through the exception factory and get the correct sub-class of SQLException.

> DisconnectException: The DDM object 0x1232 is not supported following shutdown of embedded
engine while network server is running
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2066
>                 URL: https://issues.apache.org/jira/browse/DERBY-2066
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client, Network Server
>    Affects Versions: 10.3.1.4
>         Environment: JDK 142 windows
>            Reporter: Daniel John Debrunner
>              Labels: derby_triage10_5_2
>         Attachments: Test_2066.java, derby-2066-01-aa-makeMessageIDaSQLState.diff, derby-2066-01-ab-makeMessageIDaSQLState.diff
>
>
> Running all within the same JVM.
> start network server using api
> connect to database using client
> close connection
> shutdown engine (not network server) using jdbc:derby:;shutdown=true
> connect to database using client - FAILS
> Caused by: org.apache.derby.client.am.DisconnectException: The DDM object 0x1232 is not
supported.  The connection has been terminated.
> 	at org.apache.derby.client.net.NetConnectionReply.doObjnsprmSemantics(Unknown Source)
> 	at org.apache.derby.client.net.NetConnectionReply.parseCommonError(Unknown Source)
> 	at org.apache.derby.client.net.NetConnectionReply.parseSecurityCheckError(Unknown Source)
> 	at org.apache.derby.client.net.NetConnectionReply.parseSECCHKreply(Unknown Source)
> 	at org.apache.derby.client.net.NetConnectionReply.readSecurityCheck(Unknown Source)
> 	at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(Unknown Source)
> 	at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(Unknown Source)
> 	at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unknown Source)
> 	at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source)
> 	at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
> 	at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown
Source)
> 	... 33 more

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message