Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 67198 invoked from network); 23 Aug 2002 18:52:49 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 23 Aug 2002 18:52:49 -0000 Received: (qmail 12796 invoked by uid 97); 23 Aug 2002 18:52:43 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 12610 invoked by uid 97); 23 Aug 2002 18:52:41 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 12383 invoked by uid 98); 23 Aug 2002 18:52:37 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Date: Fri, 23 Aug 2002 13:51:49 -0500 From: Jacob Kjome X-Mailer: The Bat! (v1.54/10) Personal Reply-To: Jacob Kjome Organization: Springfield Nuclear Plant X-Priority: 3 (Normal) Message-Id: <13291918451.20020823135149@visi.com> To: "Tomcat Users List" Subject: Re: Tomcat 4.1.9 beta, Postgresql jndi / jdbc problem In-Reply-To: <3D666F04.7080401@webformation.com> References: <3D666F04.7080401@webformation.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hello Peter, I reported this bug earlier this week and it was fixed the same day. Current CVS and Tomcat-4.1.10 will have the fix. is the old syntax. It is supposed to be for the DBCP stuff. The admin was still assuming that it was "user". Here's the bug report: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11775 Jake Friday, August 23, 2002, 12:21:08 PM, you wrote: PY> I would be interested in any comments on the following problem I PY> encountered setting up a jdbc datasource to Postgresql on Tomcat 4.1.9 beta. PY> os - RedHat Linux 7.1 i386 PY> db - Postgresql 7.1.3 PY> driver - jdbc7.1-1.2.jar (jdbc driver for pg 7.1, java2) PY> tc - Tomcat 4.1.9 beta. PY> The problem arose after I used the new web admin interface to set up a PY> jdbc datasource to my Postgresql database (although the web admin PY> doesn't seem to be the problem). I received the error: PY> "org.apache.jasper.JasperException: The user property is missing. It is PY> mandatory." PY> However, the user property was not in fact missing. PY> The web admin inserted the following resource parameters into my PY> server.xml (abridged): PY> PY> user PY> postgres PY> PY> PY> url PY> jdbc:postgresql:testdb1 PY> PY> PY> password PY> password_here PY> PY> The part above is identical to the corresponding parts in my 4.0.x PY> jndi/jdbc setup(s), which work fine. PY> I discovered the following workarounds in server.xml: PY> (1) attach the user parameter to the end of the jdbc url (e.g., PY> jdbc:postgresql:testdb1?user=postgres), or PY> (2) change the parameter named "user" to "username", as in PY> PY> username PY> postgres PY> PY> The Postgresql documentation clearly states that the property in PY> questions is "name". PY> Any comments are appreciated. PY> Thanks, PY> Peter Yellman PY> -- PY> To unsubscribe, e-mail: PY> For additional commands, e-mail: -- Best regards, Jacob mailto:hoju@visi.com -- To unsubscribe, e-mail: For additional commands, e-mail: