[ http://issues.apache.org/jira/browse/DERBY-285?page=comments#action_12312662 ]
Kathey Marsden commented on DERBY-285: -------------------------------------- The offending characters appear for severe error messages where the client cannot call the server to retrieve the message text. So my planned solution is to not send message arguments in the sqlerrmc for severe messages, but rather send the full message text localized according the the server locale. This will make the error messages more readable and eliminate the offending characters. > Network Client should not print non-ascii token separators in message when it > cannot connect to the server to retrieve the error message > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-285 > URL: http://issues.apache.org/jira/browse/DERBY-285 > Project: Derby > Type: Improvement > Components: Network Client > Versions: 10.1.0.0 > Reporter: Kathey Marsden > Assignee: Kathey Marsden > > If Network Client cannot connect to the database to retrieve an error > message, it will print only the message tokens, the non-ascii token > separators, and derby log location. It would be good if at least the message > could be formatted to present a better message to the user without the > non-ascii characters. > To reproduce try a database shutdown. Because the database is shutdown, the > client cannot retrieve the actual message from the server. It therefore just > prints the tokens. > Start network server > java org.apache.derby.drda.NetworkServerControl start > $ java org.apache.derby.tools.ij > ij version 10.1 > ij> connect 'jdbc:derby://localhost:1527/wombat;create=true'; > ij> connect 'jdbc:derby://localhost:1527/wombat;shutdown=true'; > ERROR 08006: DERBY SQL error: SQLCODE: -1, SQLSTATE: 08006, SQLERRMC: > wombat[]08006.D[]Database 'wombat' shutdown.[](server log:derby.log) > ij> > Note: The actual offending characters have been replaced in the output in > this bug by []. This is because they break Jira XML retrieval! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
