[jira] Updated: (DERBY-3541) quit; on ij with authentication enabled does not shutdown the derby modules that are loaded
[ https://issues.apache.org/jira/browse/DERBY-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lily Wei updated DERBY-3541: Urgency: Normal Labels: derby_triage10_8 (was: ) > quit; on ij with authentication enabled does not shutdown the derby modules > that are loaded > --- > > Key: DERBY-3541 > URL: https://issues.apache.org/jira/browse/DERBY-3541 > Project: Derby > Issue Type: Bug > Components: Tools >Affects Versions: 10.4.1.3 >Reporter: V.Narayanan >Priority: Minor > Labels: derby_triage10_8 > Attachments: PrintStackTrace.diff, > WithoutAuthentication_StackTrace.txt, derby.properties > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-3541) quit; on ij with authentication enabled does not shutdown the derby modules that are loaded
[ https://issues.apache.org/jira/browse/DERBY-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tiago R. Espinha updated DERBY-3541: Triaged for 10.5.2. No changes made. > quit; on ij with authentication enabled does not shutdown the derby modules > that are loaded > --- > > Key: DERBY-3541 > URL: https://issues.apache.org/jira/browse/DERBY-3541 > Project: Derby > Issue Type: Bug > Components: Tools >Affects Versions: 10.4.1.3 >Reporter: V.Narayanan >Priority: Minor > Attachments: derby.properties, PrintStackTrace.diff, > WithoutAuthentication_StackTrace.txt > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3541) quit; on ij with authentication enabled does not shutdown the derby modules that are loaded
[ https://issues.apache.org/jira/browse/DERBY-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-3541: - Component/s: Tools > quit; on ij with authentication enabled does not shutdown the derby modules > that are loaded > --- > > Key: DERBY-3541 > URL: https://issues.apache.org/jira/browse/DERBY-3541 > Project: Derby > Issue Type: Bug > Components: Tools >Affects Versions: 10.4.1.3 >Reporter: V.Narayanan >Priority: Minor > Attachments: derby.properties, PrintStackTrace.diff, > WithoutAuthentication_StackTrace.txt > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3541) quit; on ij with authentication enabled does not shutdown the derby modules that are loaded
[ https://issues.apache.org/jira/browse/DERBY-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3541: --- Priority: Minor (was: Major) > quit; on ij with authentication enabled does not shutdown the derby modules > that are loaded > --- > > Key: DERBY-3541 > URL: https://issues.apache.org/jira/browse/DERBY-3541 > Project: Derby > Issue Type: Bug > Components: Security >Affects Versions: 10.4.0.0 >Reporter: V.Narayanan >Priority: Minor > Attachments: derby.properties, PrintStackTrace.diff, > WithoutAuthentication_StackTrace.txt > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3541) quit; on ij with authentication enabled does not shutdown the derby modules that are loaded
[ https://issues.apache.org/jira/browse/DERBY-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3541: --- Attachment: derby.properties WithoutAuthentication_StackTrace.txt PrintStackTrace.diff I modified the derby codebase to print a stack trace (new Throwable().printStackTrace();) in the TopService#shutdown() method (pls find patch attached.) I then tried getting a connection *with* authentication enabled (pls find derby.properties attached) with the following connection url ij> connect 'jdbc:derby:replicationdb2;create=true;user=oystein;password=pass'; ij> quit; [EMAIL PROTECTED]:~/work/workspaces/PrintStackTrace/trials$ There was no stack trace printed. I then tried a connection *without* authentication enabled There was a stack trace printed (pls find attached stack trace) ij> connect 'jdbc:derby:replicationdb1;create=true'; ij> quit; java.lang.Throwable at org.apache.derby.impl.services.monitor.TopService.shutdown(TopService.java:327) at org.apache.derby.impl.services.monitor.BaseMonitor.shutdown(BaseMonitor.java:237) at org.apache.derby.impl.services.monitor.BaseMonitor.shutdown(BaseMonitor.java:203) at org.apache.derby.jdbc.InternalDriver.connect(InternalDriver.java:231) at org.apache.derby.jdbc.AutoloadedDriver.connect(AutoloadedDriver.java:119) at java.sql.DriverManager.getConnection(DriverManager.java:582) at java.sql.DriverManager.getConnection(DriverManager.java:207) at org.apache.derby.impl.tools.ij.utilMain.cleanupGo(utilMain.java:416) at org.apache.derby.impl.tools.ij.utilMain.go(utilMain.java:249) at org.apache.derby.impl.tools.ij.Main.go(Main.java:215) at org.apache.derby.impl.tools.ij.Main.mainCore(Main.java:181) at org.apache.derby.impl.tools.ij.Main.main(Main.java:73) at org.apache.derby.tools.ij.main(ij.java:59) ... and so on (attached is the full stack trace) Not shutting down the modules when authentication is enabled I believe is not correct. > quit; on ij with authentication enabled does not shutdown the derby modules > that are loaded > --- > > Key: DERBY-3541 > URL: https://issues.apache.org/jira/browse/DERBY-3541 > Project: Derby > Issue Type: Bug > Components: Security >Affects Versions: 10.4.0.0 >Reporter: V.Narayanan > Attachments: derby.properties, PrintStackTrace.diff, > WithoutAuthentication_StackTrace.txt > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
