You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2011/03/02 18:17:36 UTC
[jira] Created: (DERBY-5085) After specifying deregister=false on
the engine shutdown URL, Derby forgets that the default behavior is
deregister=true
After specifying deregister=false on the engine shutdown URL, Derby forgets that the default behavior is deregister=true
------------------------------------------------------------------------------------------------------------------------
Key: DERBY-5085
URL: https://issues.apache.org/jira/browse/DERBY-5085
Project: Derby
Issue Type: Bug
Components: JDBC
Affects Versions: 10.8.0.0
Reporter: Rick Hillegas
If you shutdown the engine specifying deregister=false, then get a new connection, then shutdown the engine again without specifying any value for the deregister attribute, Derby acts as though you specified deregister=false again. I will attach a test program which shows this problem.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-5085) After specifying deregister=false on
the engine shutdown URL, Derby forgets that the default behavior is
deregister=true
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lily Wei resolved DERBY-5085.
-----------------------------
Resolution: Fixed
Fix Version/s: 10.8.0.0
Issue & fix info: [Patch Available, Repro attached] (was: [Repro attached])
Suites.all and derbyall run clean with the patch. I've committed with revision 1076499. Thanks Rick.
> After specifying deregister=false on the engine shutdown URL, Derby forgets that the default behavior is deregister=true
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5085
> URL: https://issues.apache.org/jira/browse/DERBY-5085
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.8.0.0
> Reporter: Rick Hillegas
> Assignee: Lily Wei
> Labels: derby_triage10_8
> Fix For: 10.8.0.0
>
> Attachments: DERBY-5085_1.diff, y.java
>
>
> If you shutdown the engine specifying deregister=false, then get a new connection, then shutdown the engine again without specifying any value for the deregister attribute, Derby acts as though you specified deregister=false again. I will attach a test program which shows this problem.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-5085) After specifying deregister=false on
the engine shutdown URL, Derby forgets that the default behavior is
deregister=true
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001603#comment-13001603 ]
Rick Hillegas commented on DERBY-5085:
--------------------------------------
Thanks, Lily. I can confirm that after applying this patch, the repro behaves correctly. Thanks.
> After specifying deregister=false on the engine shutdown URL, Derby forgets that the default behavior is deregister=true
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5085
> URL: https://issues.apache.org/jira/browse/DERBY-5085
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.8.0.0
> Reporter: Rick Hillegas
> Assignee: Lily Wei
> Labels: derby_triage10_8
> Attachments: DERBY-5085_1.diff, y.java
>
>
> If you shutdown the engine specifying deregister=false, then get a new connection, then shutdown the engine again without specifying any value for the deregister attribute, Derby acts as though you specified deregister=false again. I will attach a test program which shows this problem.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-5085) After specifying deregister=false on
the engine shutdown URL, Derby forgets that the default behavior is
deregister=true
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lily Wei updated DERBY-5085:
----------------------------
Attachment: DERBY-5085_1.diff
Thanks, Rick. Upload patch DERBY-5085_1.diff. With this patch, derby will keep the default behavior deregister=true after shutdown derby with deregister=false.
> After specifying deregister=false on the engine shutdown URL, Derby forgets that the default behavior is deregister=true
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5085
> URL: https://issues.apache.org/jira/browse/DERBY-5085
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.8.0.0
> Reporter: Rick Hillegas
> Assignee: Lily Wei
> Labels: derby_triage10_8
> Attachments: DERBY-5085_1.diff, y.java
>
>
> If you shutdown the engine specifying deregister=false, then get a new connection, then shutdown the engine again without specifying any value for the deregister attribute, Derby acts as though you specified deregister=false again. I will attach a test program which shows this problem.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-5085) After specifying deregister=false on
the engine shutdown URL, Derby forgets that the default behavior is
deregister=true
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001609#comment-13001609 ]
Lily Wei commented on DERBY-5085:
---------------------------------
Thanks Rick. It passed AutoloadTest and my other DERBY-2905 tests as well. I am running regression tests now. Once there is no issue on the regression test suites. I will commit the fix.
> After specifying deregister=false on the engine shutdown URL, Derby forgets that the default behavior is deregister=true
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5085
> URL: https://issues.apache.org/jira/browse/DERBY-5085
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.8.0.0
> Reporter: Rick Hillegas
> Assignee: Lily Wei
> Labels: derby_triage10_8
> Attachments: DERBY-5085_1.diff, y.java
>
>
> If you shutdown the engine specifying deregister=false, then get a new connection, then shutdown the engine again without specifying any value for the deregister attribute, Derby acts as though you specified deregister=false again. I will attach a test program which shows this problem.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-5085) After specifying deregister=false on
the engine shutdown URL, Derby forgets that the default behavior is
deregister=true
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lily Wei reassigned DERBY-5085:
-------------------------------
Assignee: Lily Wei
> After specifying deregister=false on the engine shutdown URL, Derby forgets that the default behavior is deregister=true
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5085
> URL: https://issues.apache.org/jira/browse/DERBY-5085
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.8.0.0
> Reporter: Rick Hillegas
> Assignee: Lily Wei
> Labels: derby_triage10_8
> Attachments: y.java
>
>
> If you shutdown the engine specifying deregister=false, then get a new connection, then shutdown the engine again without specifying any value for the deregister attribute, Derby acts as though you specified deregister=false again. I will attach a test program which shows this problem.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-5085) After specifying deregister=false on
the engine shutdown URL, Derby forgets that the default behavior is
deregister=true
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-5085:
---------------------------------
Labels: derby_triage10_8 (was: )
> After specifying deregister=false on the engine shutdown URL, Derby forgets that the default behavior is deregister=true
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5085
> URL: https://issues.apache.org/jira/browse/DERBY-5085
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.8.0.0
> Reporter: Rick Hillegas
> Labels: derby_triage10_8
> Attachments: y.java
>
>
> If you shutdown the engine specifying deregister=false, then get a new connection, then shutdown the engine again without specifying any value for the deregister attribute, Derby acts as though you specified deregister=false again. I will attach a test program which shows this problem.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-5085) After specifying deregister=false on
the engine shutdown URL, Derby forgets that the default behavior is
deregister=true
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-5085:
---------------------------------
Attachment: y.java
Attaching y.java, a repro for this problem. Here is the output from this program:
java y true
Connection is a org.apache.derby.impl.jdbc.EmbedConnection40
Saw SQLState XJ015 after trying to shutdown with this url: jdbc:derby:;shutdown=true;deregister=false
Connection is a org.apache.derby.impl.jdbc.EmbedConnection40
Saw SQLState XJ015 after trying to shutdown with this url: jdbc:derby:;shutdown=true;deregister=true
As expected, could not get a connection after an ordinary orderly shutdown.
Connection is a org.apache.derby.impl.jdbc.EmbedConnection40
Success!
java y false
Connection is a org.apache.derby.impl.jdbc.EmbedConnection40
Saw SQLState XJ015 after trying to shutdown with this url: jdbc:derby:;shutdown=true;deregister=false
Connection is a org.apache.derby.impl.jdbc.EmbedConnection40
Saw SQLState XJ015 after trying to shutdown with this url: jdbc:derby:;shutdown=true
Connection is a org.apache.derby.impl.jdbc.EmbedConnection40
Oops! Did not expect to be able to get a connection!
The above tests were run on Java 6. Note that you can also run this test on JDK 1.4 and see the same behavior there:
java -Djdbc.drivers=org.apache.derby.jdbc.EmbeddedDriver y true
Connection is a org.apache.derby.impl.jdbc.EmbedConnection30
Saw SQLState XJ015 after trying to shutdown with this url: jdbc:derby:;shutdown=true;deregister=false
Connection is a org.apache.derby.impl.jdbc.EmbedConnection30
Saw SQLState XJ015 after trying to shutdown with this url: jdbc:derby:;shutdown=true;deregister=true
As expected, could not get a connection after an ordinary orderly shutdown.
Connection is a org.apache.derby.impl.jdbc.EmbedConnection30
Success!
java -Djdbc.drivers=org.apache.derby.jdbc.EmbeddedDriver y false
Connection is a org.apache.derby.impl.jdbc.EmbedConnection30
Saw SQLState XJ015 after trying to shutdown with this url: jdbc:derby:;shutdown=true;deregister=false
Connection is a org.apache.derby.impl.jdbc.EmbedConnection30
Saw SQLState XJ015 after trying to shutdown with this url: jdbc:derby:;shutdown=true
Connection is a org.apache.derby.impl.jdbc.EmbedConnection30
Oops! Did not expect to be able to get a connection!
> After specifying deregister=false on the engine shutdown URL, Derby forgets that the default behavior is deregister=true
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5085
> URL: https://issues.apache.org/jira/browse/DERBY-5085
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.8.0.0
> Reporter: Rick Hillegas
> Attachments: y.java
>
>
> If you shutdown the engine specifying deregister=false, then get a new connection, then shutdown the engine again without specifying any value for the deregister attribute, Derby acts as though you specified deregister=false again. I will attach a test program which shows this problem.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira