Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 98310 invoked from network); 3 May 2010 20:02:17 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 May 2010 20:02:17 -0000 Received: (qmail 63535 invoked by uid 500); 3 May 2010 20:02:17 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 63507 invoked by uid 500); 3 May 2010 20:02:17 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 63500 invoked by uid 99); 3 May 2010 20:02:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 20:02:17 +0000 X-ASF-Spam-Status: No, hits=-1381.7 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 20:02:16 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o43K1ucI001102 for ; Mon, 3 May 2010 20:01:56 GMT Message-ID: <8088989.21031272916916342.JavaMail.jira@thor> Date: Mon, 3 May 2010 16:01:56 -0400 (EDT) From: "Jira (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-159) When Derby runs in Network Server mode, client does not receive warnings generated by Derby - should get documented In-Reply-To: <426955246.1109960986942.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jira updated DERBY-159: ----------------------- Attachment: screen_nps.png > When Derby runs in Network Server mode, client does not receive warnings generated by Derby - should get documented > ------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-159 > URL: https://issues.apache.org/jira/browse/DERBY-159 > Project: Derby > Issue Type: Bug > Components: Documentation, Network Server > Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1 > Reporter: Mamta A. Satoor > Assignee: Kim Haase > Attachments: d159.java > > > A simple code below will demonstrate that warnings generated by Derby running in Server mode do not make their way to client. The client code below is trying to create the database db1drda which already exsits. Server generates a warning for that but the client cde below does not print it. > con = DriverManager.getConnection("jdbc:derby:net://localhost:1527/db1drda;create=true:retrieveMessagesFromServerOnGetMessage=true;", "app", "app"); > SQLWarning warnings1 = con.getWarnings(); > System.out.println("database exists, should get warning"); > while (warnings1 != null) > { > System.out.println("warnings on connection = " + warnings1); > warnings1 = warnings1.getNextWarning(); > } -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.