You must be careful to distinguish the two different users involved. The OS user would determine whether there is a permissions problem with the JAR containing the PostgreSQL JDBC driver, but be insignificant in actually connecting to the DBMS. Ensuring that the JAR is world-readable should eliminate this as a source of trouble.
The PostgreSQL user (I think it was "testmanager") partially determines which entry in pg_hba is used to authorize the connection -- the other determinant is the type of connection (local or network socket, and (for network socket) the client host address). The OS user is not involved in this unless the DBMS is configured to pass credentials through to e.g. PAM. You might check the PostgreSQL monitor log for clues. You may have to adjust the logging configuration to be sure you get enough information to be useful. If you see no connection attempted, it wouldn't appear to be a problem with the database user. -- Mark H. Wood, Lead System Programmer [EMAIL PROTECTED] Typically when a software vendor says that a product is "intuitive" he means the exact opposite.
pgpotqU5kaI4g.pgp
Description: PGP signature
