Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 64335 invoked from network); 2 Apr 2007 22:13:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Apr 2007 22:13:55 -0000 Received: (qmail 57828 invoked by uid 500); 2 Apr 2007 22:14:01 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 57598 invoked by uid 500); 2 Apr 2007 22:14:00 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 57587 invoked by uid 99); 2 Apr 2007 22:14:00 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2007 15:14:00 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2007 15:13:52 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4349A71403B for ; Mon, 2 Apr 2007 15:13:32 -0700 (PDT) Message-ID: <22414000.1175552012245.JavaMail.jira@brutus> Date: Mon, 2 Apr 2007 15:13:32 -0700 (PDT) From: "David Jencks (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Commented: (GERONIMO-3051) DB Viewer portlet error In-Reply-To: <28399985.1175282425143.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486156 ] David Jencks commented on GERONIMO-3051: ---------------------------------------- Before any changes get committed can we verify that system-database is a parent of the app we're having problems with? the derby classes should be coming from system-database, not from including the jars directly. In any case we've seen similar problems in the past when a second copy of derby classes is loaded: this definitely is a problem with the embedded driver and possibly with the network driver. > DB Viewer portlet error > ----------------------- > > Key: GERONIMO-3051 > URL: https://issues.apache.org/jira/browse/GERONIMO-3051 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console, databases > Affects Versions: 2.0-M4 > Environment: embedded Derby databases > Reporter: Hernan Cunico > Attachments: GERONIMO-3051.patch > > > There is a problem when trying to view an embedded Derby database. > I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error. > When I check the logs I get this: > 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception > javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver" > ... > 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception > javax.servlet.ServletException > ... > 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet. > javax.portlet.PortletException > ... > With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.