FYI - the postgres JDBC driver connects to
the database via TCP/IP.
You can test that your client machine
can access the database over
TCP/IP with psql:
% psql --host hostname --port port -U whatever
Good luck!
Reuben
>>> Christian Voelker <[EMAIL PROTECTED]> 3/19/2008 3:33 PM >>>
Hello,
Am 19.03.2008 um 17:35 schrieb Thornton, Susan M. (LARC-B702)[NCI
INFORMATION SYSTEMS]:
> We are trying to bring up a new machine with Dspace 1.4.2 and
> PostgreSQL 8.2 (Solaris 10). It looks like DSpace is configured
> correctly (the web page will come up, but it gets an Internal
> Error). We can query the database at the command line level, but
> cannot get to the database in PGAdminIII.
I dont use Solaris and I dont know for sure whether Postgres JDBC
driver accesses the database via Unix socket connection or TCP
(port 5432 IIRC), but this is where I would start my search for
problems. If you can connect via psql, than you have the proper
account information. Connecting by PgAdmin seems to go a different
way, probably the same way the JDBC driver tries without success.
You should be able to determine that by consulting your pg_hba.conf
file. I guess connection to localhost:5432 should be allowed for
All All which means every user to every db, but it would be
sufficient if it were allowed for the account you are using
accessing the dspace db. Maybe, localhost does not resolve
properly and you have to use the qualified host name?
If this is the wrong place, I would check whether your firewall
refuses permission. If access fails because of rules defined in
the pg_hba.conf, then the connection attempts should be visible
in the postgres logs. If they are not, then access might be
blocked before postgres can see it at all. Third thing to
double check is the version of the JDBC driver version in use.
If this does not help, post back your findings to the list.
Hope this helps, bye, Christian
> Here is the error we are getting. Does anyone have any ideas?
> Thanks,
> Sue
>
> p.s. We also are not using Tomcat – we’re using Sun’s
Webserver7.
>
> ****ERROR****
> 2008-03-19 12:27:01,215 INFO org.dspace.core.ConfigurationManager @
> DSpace logging installed using log4j.properties
> 2008-03-19 12:27:13,780 WARN org.dspace.jsp @
> anonymous:no_context:database_error:org
> .apache.commons.dbcp.SQLNestedException:Cannot get a connection,
> pool exhausted
> org.apache.commons.dbcp.SQLNestedException: Cannot get a connection,
> pool exhausted
> at
>
org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:183)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
