[jira] [Commented] (DERBY-6711) Missing database name in error message from LogToFile.stopReplicationSlaveRole()

2017-07-24 Thread Rajitha rajasooriya (JIRA) 

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

Rajitha rajasooriya commented on DERBY-6711:


Can I have the source code for this? Which you got the issue when running it.

> Missing database name in error message from 
> LogToFile.stopReplicationSlaveRole()
> 
>
> Key: DERBY-6711
> URL: https://issues.apache.org/jira/browse/DERBY-6711
> Project: Derby
>  Issue Type: Bug
>  Components: Store
>Affects Versions: 10.11.1.1
>Reporter: Knut Anders Hatlen
>Assignee: Rajitha rajasooriya
>Priority: Minor
>
> I saw this error in derby.log after running replication tests:
> {noformat}
> ERROR 08006: Database '{0}' shutdown.
>   at 
> org.apache.derby.iapi.error.StandardException.newException(StandardException.java:290)
>   at 
> org.apache.derby.iapi.error.StandardException.newException(StandardException.java:285)
>   at 
> org.apache.derby.impl.store.raw.log.LogToFile.stopReplicationSlaveRole(LogToFile.java:5253)
>   at 
> org.apache.derby.impl.store.replication.slave.SlaveController.stopSlave(SlaveController.java:266)
>   at 
> org.apache.derby.impl.store.replication.slave.SlaveController.access$500(SlaveController.java:64)
>   at 
> org.apache.derby.impl.store.replication.slave.SlaveController$SlaveLogReceiverThread.run(SlaveController.java:526)
> {noformat}
> The database name is missing from the message.
> LogToFile.stopReplicationSlaveRole() should either call newException() with 
> the database name as argument or use another message that doesn't take a 
> database name argument.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Hey there!

2017-07-24 Thread Rajitha Rajasooriya 
About 6711 issue.

Can I have the piece of code where the error is occurred?

About DERBY-6901 issue.

2017-07-24 Thread Yeshan Tharaka 
Hello,
Where can I find the prepareCall() method in source code?
Thank you.

[jira] [Commented] (DERBY-5261) NetworkServerControl prints usage message twice on some errors

2017-07-24 Thread Rick Hillegas (JIRA) 

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

Rick Hillegas commented on DERBY-5261:
--

I think that Bryan is suggesting that you add a test case to 
NetworkServerControlClientCommandTest. The test case would call 
assertExecJavaCmdAsExpected​() just as 
NetworkServerControlClientCommandTest.assertSuccessfulPing() does.

> NetworkServerControl prints usage message twice on some errors
> --
>
> Key: DERBY-5261
> URL: https://issues.apache.org/jira/browse/DERBY-5261
> Project: Derby
>  Issue Type: Bug
>  Components: Network Server
>Affects Versions: 10.8.1.2
>Reporter: Knut Anders Hatlen
>Assignee: INDIKA KUMARA
>Priority: Minor
>  Labels: derby_triage10_9
>
> If you invoke NetworkServerControl with an invalid command, the usage message 
> will be printed twice.
> $ java -jar derbynet.jar abc
> Mon Jun 06 10:14:25 CEST 2011 : Command abc is unknown.
> Usage: NetworkServerControl  
> Commands:
> start [-h ] [-p ] [-noSecurityManager] [-ssl ]
> shutdown [-h ][-p ] [-ssl ] [-user ] 
> [-password ]
> ping [-h ][-p ] [-ssl ]
> sysinfo [-h ][-p ] [-ssl ]
> runtimeinfo [-h ][-p ] [-ssl ]
> logconnections {on|off} [-h ][-p ] [-ssl ]
> maxthreads [-h ][-p ] [-ssl ]
> timeslice [-h ][-p ] [-ssl ]
> trace {on|off} [-s ][-h ][-p ] [-ssl ]
> tracedirectory [-h ][-p ] [-ssl ]
> Mon Jun 06 10:14:25 CEST 2011 : No command given.
> Usage: NetworkServerControl  
> Commands:
> start [-h ] [-p ] [-noSecurityManager] [-ssl ]
> shutdown [-h ][-p ] [-ssl ] [-user ] 
> [-password ]
> ping [-h ][-p ] [-ssl ]
> sysinfo [-h ][-p ] [-ssl ]
> runtimeinfo [-h ][-p ] [-ssl ]
> logconnections {on|off} [-h ][-p ] [-ssl ]
> maxthreads [-h ][-p ] [-ssl ]
> timeslice [-h ][-p ] [-ssl ]
> trace {on|off} [-s ][-h ][-p ] [-ssl ]
> tracedirectory [-h ][-p ] [-ssl ]
> Printing it once should be enough.
> The same problem is seen if you don't specify a required argument for an 
> option. For example "java -jar derbynet start -p" (no port number).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (DERBY-6909) Invalid grouping by multiple columns when use function (Apache Derby 10.10.2.0)

2017-07-24 Thread Indumini Ayomi (JIRA) 

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

Indumini Ayomi updated DERBY-6909:
--
Affects Version/s: 10.13.1.1
   10.10.2.0

> Invalid grouping by multiple columns when use function (Apache Derby 
> 10.10.2.0)
> ---
>
> Key: DERBY-6909
> URL: https://issues.apache.org/jira/browse/DERBY-6909
> Project: Derby
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 10.10.2.0, 10.13.1.1
>Reporter: Boris Brinza
>Assignee: Indumini Ayomi
>Priority: Minor
>  Labels: queries
> Attachments: derby.log
>
>
> Create table TEST:
> create table TEST (name varchar(10), label varchar(10));
> insert into TEST values ('johnny', 'label_1');
> insert into TEST values ('johnny', 'label_2');
> These queries returns 2 rows 'JOHNNY':
> select upper(name) from TEST group by name, label
> select upper(name) from TEST group by upper(name), label
> When grouping is changed this way, query returns only 1 row 'JOHNNY':
> select upper(name) from TEST group by upper(name), upper(label)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)