Re: Postgresql connection issue

[Pascal Robert]

Since when OS X became "a economic deployment environment" ?

- Mail original -
De: "Daniel D CIV NAVAIR Beatty, 474300D" 
À: "WebObjects-Dev List" 
Envoyé: Lundi 18 Novembre 2013 13:28:01
Objet: RE: Postgresql connection issue

Hi,
I have one stupid question.  So is this supposed to be a recipe to use the 
native Postgresql is now in OSX?  I remember back Tiger through Snow Leopard 
that the one blessing that came with MySQL was the fact that it was native to 
the system.

While I could make environment I did chose in my academic days, I still had to 
eat and sell the idea grant sources.   Despite popularity of Linux, OSX made a 
good out of the box case for minimalist deployment and low maintenance.  For 
small organizations, this was that had to content with big brother this was 
appealing for many reasons.  Apple provided support far cheaper than the 
employment of multiple men/women per organization, the distribution was cheap, 
and the student labor was cheap.

Postgresql was highly evangelized even then.  Now that it is native DB in the 
server,  is just as good to from a simplicity stand point to make the recipe 
use the native?  I noticed the Postgresql.app approach in the chain also.

Thus, I could use some expertise on both approaches.  Often we deploy with 
Linux or whatever we can ship to the cloud, economically.  If OSX happens to be 
a economic deployment or development environment, then what are pros and cons.  
Bottom line, I have been out of the loop for a while.  It would be helpful for 
the keep-up issue, and that kind of thing is a blessing.

V/R,

Daniel D. Beatty, Ph.D.
Senior Computer Scientist,
Detonation Sciences Branch- NAWCWD
1 Adminstration Circle M/S 1109
China Lake, CA 93555
(760)939-7097
daniel.bea...@navy.mil




From: webobjects-dev-bounces+daniel.beatty=navy@lists.apple.com 
[webobjects-dev-bounces+daniel.beatty=navy@lists.apple.com] on behalf of 
Joe Kramer [jkmarti...@gmail.com]
Sent: Sunday, November 17, 2013 1:13 AM
To: Theodore Petrosky
Cc: WebObjects Development
Subject: Re: Postgresql connection issue

Hello all,

Thank you to everyone, especially Ted, for all the help to get my dev 
environment set up. Some combination of re-installing PostgreSQL, adjusting my 
PATH variable, grumbling/shaking my fists in anger, setting default DB 
connection variables in my properties file, and/or re-adding all the necessary 
frameworks to my build path has done the trick and things seem to be in order. 
Personally I think it was all the grumbling. But in all seriousness, I can't 
say enough good things about the fine folks on this list. I have been lurking 
on the list for years with very little opportunity to use WO, but I always know 
I can come to this list if (when) I get into a bind. Thanks so much!

Regards,

Joe



On Fri, Nov 15, 2013 at 7:52 AM, Theodore Petrosky 
mailto:tedp...@yahoo.com>> wrote:
well yes and no!   ARD uses postgresql on all versions of OS X. this is what 
causes the conflict as it listens on port 5432 also.

although this link refers to Lion, I found the same issue on Mountain Lion

http://joneslee85.wordpress.com/2011/10/27/fix-postgres-permission-denied-issue-on-osx-lion/





On Nov 15, 2013, at 10:03 AM, Þór Sigurðsson 
mailto:th...@samgongustofa.is>> wrote:

> Only 10.8 server has a postgres installation - not the client.
>
> The path isn't required for connectivity - only that the machine is listening 
> on localhost:5432 (which is the default for Postgres93.app )
>
> On 15.11.2013, at 14:58, Theodore Petrosky 
> mailto:tedp...@yahoo.com>> wrote:
>
>> one of the problems I ran into with Postgresql and 10.8 os x was the path. 
>> OS X has an installation of postgresql so you need to make sure the path to 
>> the Postgresql.app is the first in the environment.
>>
>>
>>
>> export PATH=/Applications/Postgres93.app/Contents/MacOS/bin:$PATH
>>
>> copy and paste this into a terminal session and see if it helps. if yes, add 
>> this to your .bash_profile.
>>
>> Ted
>>
>>
>> On Nov 13, 2013, at 3:11 AM, Þór Sigurðsson 
>> mailto:th...@samgongustofa.is>> wrote:
>>
>>>
>>> Exactly as Ramsey said - although if your database IS in fact on a remote 
>>> machine, you would not want "trust", since that would imply anybody could
>>> connect as anybody to any database.
>>>
>>> If your database is "mybase" and your database user is "myuser" and your 
>>> development machine is 192.168.0.100, then your line ought to be something 
>>> like:
>>>
>>> hostmybase  myuser  192.168.0.100/32<http://192.168.0.100/32>  md5
>>>
>>> Only use a trust relationship if the server doesn't allo

Re: Postgresql connection issue

[Ramsey Gurley]

Just a few days ago, this happened

http://aws.amazon.com/rds/postgresql/

:-)

On Nov 18, 2013, at 11:28 AM, Beatty, Daniel D CIV NAVAIR, 474300D 
 wrote:

> Hi,
> I have one stupid question.  So is this supposed to be a recipe to use the 
> native Postgresql is now in OSX?  I remember back Tiger through Snow Leopard 
> that the one blessing that came with MySQL was the fact that it was native to 
> the system.
> 
> While I could make environment I did chose in my academic days, I still had 
> to eat and sell the idea grant sources.   Despite popularity of Linux, OSX 
> made a good out of the box case for minimalist deployment and low 
> maintenance.  For small organizations, this was that had to content with big 
> brother this was appealing for many reasons.  Apple provided support far 
> cheaper than the employment of multiple men/women per organization, the 
> distribution was cheap, and the student labor was cheap.
> 
> Postgresql was highly evangelized even then.  Now that it is native DB in the 
> server,  is just as good to from a simplicity stand point to make the recipe 
> use the native?  I noticed the Postgresql.app approach in the chain also.
> 
> Thus, I could use some expertise on both approaches.  Often we deploy with 
> Linux or whatever we can ship to the cloud, economically.  If OSX happens to 
> be a economic deployment or development environment, then what are pros and 
> cons.  Bottom line, I have been out of the loop for a while.  It would be 
> helpful for the keep-up issue, and that kind of thing is a blessing.
> 
> V/R,
> 
> Daniel D. Beatty, Ph.D.
> Senior Computer Scientist,
> Detonation Sciences Branch- NAWCWD
> 1 Adminstration Circle M/S 1109
> China Lake, CA 93555
> (760)939-7097
> daniel.bea...@navy.mil
> 
> 
> 
> 
> From: webobjects-dev-bounces+daniel.beatty=navy@lists.apple.com 
> [webobjects-dev-bounces+daniel.beatty=navy@lists.apple.com] on behalf of 
> Joe Kramer [jkmarti...@gmail.com]
> Sent: Sunday, November 17, 2013 1:13 AM
> To: Theodore Petrosky
> Cc: WebObjects Development
> Subject: Re: Postgresql connection issue
> 
> Hello all,
> 
> Thank you to everyone, especially Ted, for all the help to get my dev 
> environment set up. Some combination of re-installing PostgreSQL, adjusting 
> my PATH variable, grumbling/shaking my fists in anger, setting default DB 
> connection variables in my properties file, and/or re-adding all the 
> necessary frameworks to my build path has done the trick and things seem to 
> be in order. Personally I think it was all the grumbling. But in all 
> seriousness, I can't say enough good things about the fine folks on this 
> list. I have been lurking on the list for years with very little opportunity 
> to use WO, but I always know I can come to this list if (when) I get into a 
> bind. Thanks so much!
> 
> Regards,
> 
> Joe
> 
> 
> 
> On Fri, Nov 15, 2013 at 7:52 AM, Theodore Petrosky 
> mailto:tedp...@yahoo.com>> wrote:
> well yes and no!   ARD uses postgresql on all versions of OS X. this is what 
> causes the conflict as it listens on port 5432 also.
> 
> although this link refers to Lion, I found the same issue on Mountain Lion
> 
> http://joneslee85.wordpress.com/2011/10/27/fix-postgres-permission-denied-issue-on-osx-lion/
> 
> 
> 
> 
> 
> On Nov 15, 2013, at 10:03 AM, Þór Sigurðsson 
> mailto:th...@samgongustofa.is>> wrote:
> 
>> Only 10.8 server has a postgres installation - not the client.
>> 
>> The path isn't required for connectivity - only that the machine is 
>> listening on localhost:5432 (which is the default for Postgres93.app )
>> 
>> On 15.11.2013, at 14:58, Theodore Petrosky 
>> mailto:tedp...@yahoo.com>> wrote:
>> 
>>> one of the problems I ran into with Postgresql and 10.8 os x was the path. 
>>> OS X has an installation of postgresql so you need to make sure the path to 
>>> the Postgresql.app is the first in the environment.
>>> 
>>> 
>>> 
>>> export PATH=/Applications/Postgres93.app/Contents/MacOS/bin:$PATH
>>> 
>>> copy and paste this into a terminal session and see if it helps. if yes, 
>>> add this to your .bash_profile.
>>> 
>>> Ted
>>> 
>>> 
>>> On Nov 13, 2013, at 3:11 AM, Þór Sigurðsson 
>>> mailto:th...@samgongustofa.is>> wrote:
>>> 
>>>> 
>>>> Exactly as Ramsey said - although if your database IS in fact on a remote 
>>>> machine, you would not want "trust", since that would imply anybody could
>>>> connect as anybody to any database.
&

RE: Postgresql connection issue

[Beatty, Daniel D CIV NAVAIR, 474300D]

Hi,
I have one stupid question.  So is this supposed to be a recipe to use the 
native Postgresql is now in OSX?  I remember back Tiger through Snow Leopard 
that the one blessing that came with MySQL was the fact that it was native to 
the system.

While I could make environment I did chose in my academic days, I still had to 
eat and sell the idea grant sources.   Despite popularity of Linux, OSX made a 
good out of the box case for minimalist deployment and low maintenance.  For 
small organizations, this was that had to content with big brother this was 
appealing for many reasons.  Apple provided support far cheaper than the 
employment of multiple men/women per organization, the distribution was cheap, 
and the student labor was cheap.

Postgresql was highly evangelized even then.  Now that it is native DB in the 
server,  is just as good to from a simplicity stand point to make the recipe 
use the native?  I noticed the Postgresql.app approach in the chain also.

Thus, I could use some expertise on both approaches.  Often we deploy with 
Linux or whatever we can ship to the cloud, economically.  If OSX happens to be 
a economic deployment or development environment, then what are pros and cons.  
Bottom line, I have been out of the loop for a while.  It would be helpful for 
the keep-up issue, and that kind of thing is a blessing.

V/R,

Daniel D. Beatty, Ph.D.
Senior Computer Scientist,
Detonation Sciences Branch- NAWCWD
1 Adminstration Circle M/S 1109
China Lake, CA 93555
(760)939-7097
daniel.bea...@navy.mil




From: webobjects-dev-bounces+daniel.beatty=navy@lists.apple.com 
[webobjects-dev-bounces+daniel.beatty=navy@lists.apple.com] on behalf of 
Joe Kramer [jkmarti...@gmail.com]
Sent: Sunday, November 17, 2013 1:13 AM
To: Theodore Petrosky
Cc: WebObjects Development
Subject: Re: Postgresql connection issue

Hello all,

Thank you to everyone, especially Ted, for all the help to get my dev 
environment set up. Some combination of re-installing PostgreSQL, adjusting my 
PATH variable, grumbling/shaking my fists in anger, setting default DB 
connection variables in my properties file, and/or re-adding all the necessary 
frameworks to my build path has done the trick and things seem to be in order. 
Personally I think it was all the grumbling. But in all seriousness, I can't 
say enough good things about the fine folks on this list. I have been lurking 
on the list for years with very little opportunity to use WO, but I always know 
I can come to this list if (when) I get into a bind. Thanks so much!

Regards,

Joe



On Fri, Nov 15, 2013 at 7:52 AM, Theodore Petrosky 
mailto:tedp...@yahoo.com>> wrote:
well yes and no!   ARD uses postgresql on all versions of OS X. this is what 
causes the conflict as it listens on port 5432 also.

although this link refers to Lion, I found the same issue on Mountain Lion

http://joneslee85.wordpress.com/2011/10/27/fix-postgres-permission-denied-issue-on-osx-lion/





On Nov 15, 2013, at 10:03 AM, Þór Sigurðsson 
mailto:th...@samgongustofa.is>> wrote:

> Only 10.8 server has a postgres installation - not the client.
>
> The path isn't required for connectivity - only that the machine is listening 
> on localhost:5432 (which is the default for Postgres93.app )
>
> On 15.11.2013, at 14:58, Theodore Petrosky 
> mailto:tedp...@yahoo.com>> wrote:
>
>> one of the problems I ran into with Postgresql and 10.8 os x was the path. 
>> OS X has an installation of postgresql so you need to make sure the path to 
>> the Postgresql.app is the first in the environment.
>>
>>
>>
>> export PATH=/Applications/Postgres93.app/Contents/MacOS/bin:$PATH
>>
>> copy and paste this into a terminal session and see if it helps. if yes, add 
>> this to your .bash_profile.
>>
>> Ted
>>
>>
>> On Nov 13, 2013, at 3:11 AM, Þór Sigurðsson 
>> mailto:th...@samgongustofa.is>> wrote:
>>
>>>
>>> Exactly as Ramsey said - although if your database IS in fact on a remote 
>>> machine, you would not want "trust", since that would imply anybody could
>>> connect as anybody to any database.
>>>
>>> If your database is "mybase" and your database user is "myuser" and your 
>>> development machine is 192.168.0.100, then your line ought to be something 
>>> like:
>>>
>>> hostmybase  myuser  192.168.0.100/32<http://192.168.0.100/32>  md5
>>>
>>> Only use a trust relationship if the server doesn't allow user logins or 
>>> the users logging in are truly trusted, and then only for 
>>> 127.0.0.1/8<http://127.0.0.1/8> :)
>>>
>>> - however
>>>
>>> If your database happens to be on your _local_ machine (same 

Re: Postgresql connection issue

[Joe Kramer]

Hello all,

Thank you to everyone, especially Ted, for all the help to get my dev
environment set up. Some combination of re-installing PostgreSQL, adjusting
my PATH variable, grumbling/shaking my fists in anger, setting default DB
connection variables in my properties file, and/or re-adding all the
necessary frameworks to my build path has done the trick and things seem to
be in order. Personally I think it was all the grumbling. But in all
seriousness, I can't say enough good things about the fine folks on this
list. I have been lurking on the list for years with very little
opportunity to use WO, but I always know I can come to this list if (when)
I get into a bind. Thanks so much!

Regards,

Joe



On Fri, Nov 15, 2013 at 7:52 AM, Theodore Petrosky wrote:

> well yes and no!   ARD uses postgresql on all versions of OS X. this is
> what causes the conflict as it listens on port 5432 also.
>
> although this link refers to Lion, I found the same issue on Mountain Lion
>
>
> http://joneslee85.wordpress.com/2011/10/27/fix-postgres-permission-denied-issue-on-osx-lion/
>
>
>
>
>
> On Nov 15, 2013, at 10:03 AM, Þór Sigurðsson 
> wrote:
>
> > Only 10.8 server has a postgres installation - not the client.
> >
> > The path isn't required for connectivity - only that the machine is
> listening on localhost:5432 (which is the default for Postgres93.app )
> >
> > On 15.11.2013, at 14:58, Theodore Petrosky  wrote:
> >
> >> one of the problems I ran into with Postgresql and 10.8 os x was the
> path. OS X has an installation of postgresql so you need to make sure the
> path to the Postgresql.app is the first in the environment.
> >>
> >>
> >>
> >> export PATH=/Applications/Postgres93.app/Contents/MacOS/bin:$PATH
> >>
> >> copy and paste this into a terminal session and see if it helps. if
> yes, add this to your .bash_profile.
> >>
> >> Ted
> >>
> >>
> >> On Nov 13, 2013, at 3:11 AM, Þór Sigurðsson 
> wrote:
> >>
> >>>
> >>> Exactly as Ramsey said - although if your database IS in fact on a
> remote machine, you would not want "trust", since that would imply anybody
> could
> >>> connect as anybody to any database.
> >>>
> >>> If your database is "mybase" and your database user is "myuser" and
> your development machine is 192.168.0.100, then your line ought to be
> something like:
> >>>
> >>> hostmybase  myuser  192.168.0.100/32  md5
> >>>
> >>> Only use a trust relationship if the server doesn't allow user logins
> or the users logging in are truly trusted, and then only for 127.0.0.1/8:)
> >>>
> >>> - however
> >>>
> >>> If your database happens to be on your _local_ machine (same as your
> development/deployment) - like the Postgres.app for Mac OS X, then
> something else is amuck.
> >>>
> >>> One thing that comes to mind - does your database actually exist?
> >>>
> >>> psql -l
> >>>
> >>> lists the databases
> >>>
> >>> IF the database you expect to use doesn't exist, of course there will
> be no connection - so, if the database doesn't exist, I'll presume that the
> user doesn't exist either. In that case, you'll need to create both.
> >>>
> >>> As the user running the postgres database (logged-in user if
> "Postgres.app" or "postgres","psql" or other db-centric user of the OS the
> DB is running on:
> >>>
> >>> $ psql
> >>> # create user myuser password 'reallySecret2013';
> >>> ...
> >>> # create database myuser owner myuser encoding='UTF8';
> >>> ...
> >>> # exit
> >>>
> >>> Then try connecting again.
> >>>
> >>> Hope this helps :)
> >>>
> >>> /Þór
> >>>
> >>> On 12.11.2013, at 21:19, Ramsey Gurley  > wrote:
> >>>
> >>> Is the db on the same machine as the app? If not, this won’t work. You
> need to add the IP of your app server. Something like...
> >>>
> >>> hostall all 192.168.0.100trust
> >>>
> >>>
> >>> On Nov 12, 2013, at 1:41 PM, Joe Kramer  jkmarti...@gmail.com>> wrote:
> >>>
> >>> Thanks for the reply. Here is my config in pg_hba.conf. It seems like
> this should not be causing the issue. Any other thoughts or something I am
> missing in this config?
> >>>
> >>> Thanks,
> >>>
> >>> Joe
> >>>
> >>> # TYPE  DATABASEUSERADDRESS METHOD
> >>>
> >>> # "local" is for Unix domain socket connections only
> >>> local   all all trust
> >>> # IPv4 local connections:
> >>> hostall all 127.0.0.1/32<
> http://127.0.0.1/32>trust
> >>> # IPv6 local connections:
> >>> hostall all ::1/128 trust
> >>>
> >>>
> >>> On Tue, Nov 12, 2013 at 2:36 AM, Þór Sigurðsson <
> th...@samgongustofa.is> wrote:
> >>>
> >>> Have you given the user permission to connect to the database ?
> >>>
> >>> Take a look at pg_hba.conf. Add a line for the user. If you _want_ the
> user to use a password, then the last column should be "password" or better
> yet "md5". If you want 

Re: Postgresql connection issue

[Theodore Petrosky]

well yes and no!   ARD uses postgresql on all versions of OS X. this is what 
causes the conflict as it listens on port 5432 also.

although this link refers to Lion, I found the same issue on Mountain Lion

http://joneslee85.wordpress.com/2011/10/27/fix-postgres-permission-denied-issue-on-osx-lion/





On Nov 15, 2013, at 10:03 AM, Þór Sigurðsson  wrote:

> Only 10.8 server has a postgres installation - not the client.
> 
> The path isn't required for connectivity - only that the machine is listening 
> on localhost:5432 (which is the default for Postgres93.app )
> 
> On 15.11.2013, at 14:58, Theodore Petrosky  wrote:
> 
>> one of the problems I ran into with Postgresql and 10.8 os x was the path. 
>> OS X has an installation of postgresql so you need to make sure the path to 
>> the Postgresql.app is the first in the environment.
>> 
>> 
>> 
>> export PATH=/Applications/Postgres93.app/Contents/MacOS/bin:$PATH
>> 
>> copy and paste this into a terminal session and see if it helps. if yes, add 
>> this to your .bash_profile.
>> 
>> Ted
>> 
>> 
>> On Nov 13, 2013, at 3:11 AM, Þór Sigurðsson  wrote:
>> 
>>> 
>>> Exactly as Ramsey said - although if your database IS in fact on a remote 
>>> machine, you would not want "trust", since that would imply anybody could
>>> connect as anybody to any database.
>>> 
>>> If your database is "mybase" and your database user is "myuser" and your 
>>> development machine is 192.168.0.100, then your line ought to be something 
>>> like:
>>> 
>>> hostmybase  myuser  192.168.0.100/32  md5
>>> 
>>> Only use a trust relationship if the server doesn't allow user logins or 
>>> the users logging in are truly trusted, and then only for 127.0.0.1/8 :)
>>> 
>>> - however
>>> 
>>> If your database happens to be on your _local_ machine (same as your 
>>> development/deployment) - like the Postgres.app for Mac OS X, then 
>>> something else is amuck.
>>> 
>>> One thing that comes to mind - does your database actually exist?
>>> 
>>> psql -l
>>> 
>>> lists the databases
>>> 
>>> IF the database you expect to use doesn't exist, of course there will be no 
>>> connection - so, if the database doesn't exist, I'll presume that the user 
>>> doesn't exist either. In that case, you'll need to create both.
>>> 
>>> As the user running the postgres database (logged-in user if "Postgres.app" 
>>> or "postgres","psql" or other db-centric user of the OS the DB is running 
>>> on:
>>> 
>>> $ psql
>>> # create user myuser password 'reallySecret2013';
>>> ...
>>> # create database myuser owner myuser encoding='UTF8';
>>> ...
>>> # exit
>>> 
>>> Then try connecting again.
>>> 
>>> Hope this helps :)
>>> 
>>> /Þór
>>> 
>>> On 12.11.2013, at 21:19, Ramsey Gurley 
>>> mailto:rgur...@smarthealth.com>> wrote:
>>> 
>>> Is the db on the same machine as the app? If not, this won’t work. You need 
>>> to add the IP of your app server. Something like...
>>> 
>>> hostall all 192.168.0.100trust
>>> 
>>> 
>>> On Nov 12, 2013, at 1:41 PM, Joe Kramer 
>>> mailto:jkmarti...@gmail.com>> wrote:
>>> 
>>> Thanks for the reply. Here is my config in pg_hba.conf. It seems like this 
>>> should not be causing the issue. Any other thoughts or something I am 
>>> missing in this config?
>>> 
>>> Thanks,
>>> 
>>> Joe
>>> 
>>> # TYPE  DATABASEUSERADDRESS METHOD
>>> 
>>> # "local" is for Unix domain socket connections only
>>> local   all all trust
>>> # IPv4 local connections:
>>> hostall all 127.0.0.1/32   
>>>  trust
>>> # IPv6 local connections:
>>> hostall all ::1/128 trust
>>> 
>>> 
>>> On Tue, Nov 12, 2013 at 2:36 AM, Þór Sigurðsson 
>>> mailto:th...@samgongustofa.is>> wrote:
>>> 
>>> Have you given the user permission to connect to the database ?
>>> 
>>> Take a look at pg_hba.conf. Add a line for the user. If you _want_ the user 
>>> to use a password, then the last column should be "password" or better yet 
>>> "md5". If you want a trust-level connection, set it to "trust".
>>> 
>>> On 12.11.2013, at 09:58, Joe Kramer 
>>> mailto:jkmarti...@gmail.com>> wrote:
>>> 
 Hi all,
 
 It has been some time since I have done any WebObjects development and I 
 am trying to resurrect an old project on a new machine. I went through all 
 the steps to get WebObjects/Wonder installed and I can run HelloWorld. The 
 problem appears to be with my Postgresql JDBC connection. I am running 
 Postgres93.app. I added the postgresql-9.3-1100.jdbc3.jar to my project's 
 Resources folder and added that jar to the build path. When I run and try 
 to bootstrap my database, I cannot connect and I get the following error. 
 Is there something that I missed in the setup process? Any help would be 
 appreciated.
 
 Thanks,
 
 Joe Kramer
 
 Nov 12 01:49:37 GA

Re: Postgresql connection issue

[Theodore Petrosky]

one of the problems I ran into with Postgresql and 10.8 os x was the path. OS X 
has an installation of postgresql so you need to make sure the path to the 
Postgresql.app is the first in the environment.



export PATH=/Applications/Postgres93.app/Contents/MacOS/bin:$PATH

copy and paste this into a terminal session and see if it helps. if yes, add 
this to your .bash_profile.

Ted


On Nov 13, 2013, at 3:11 AM, Þór Sigurðsson  wrote:

> 
> Exactly as Ramsey said - although if your database IS in fact on a remote 
> machine, you would not want "trust", since that would imply anybody could
> connect as anybody to any database.
> 
> If your database is "mybase" and your database user is "myuser" and your 
> development machine is 192.168.0.100, then your line ought to be something 
> like:
> 
> hostmybase  myuser  192.168.0.100/32  md5
> 
> Only use a trust relationship if the server doesn't allow user logins or the 
> users logging in are truly trusted, and then only for 127.0.0.1/8 :)
> 
> - however
> 
> If your database happens to be on your _local_ machine (same as your 
> development/deployment) - like the Postgres.app for Mac OS X, then something 
> else is amuck.
> 
> One thing that comes to mind - does your database actually exist?
> 
> psql -l
> 
> lists the databases
> 
> IF the database you expect to use doesn't exist, of course there will be no 
> connection - so, if the database doesn't exist, I'll presume that the user 
> doesn't exist either. In that case, you'll need to create both.
> 
> As the user running the postgres database (logged-in user if "Postgres.app" 
> or "postgres","psql" or other db-centric user of the OS the DB is running on:
> 
> $ psql
> # create user myuser password 'reallySecret2013';
> ...
> # create database myuser owner myuser encoding='UTF8';
> ...
> # exit
> 
> Then try connecting again.
> 
> Hope this helps :)
> 
> /Þór
> 
> On 12.11.2013, at 21:19, Ramsey Gurley 
> mailto:rgur...@smarthealth.com>> wrote:
> 
> Is the db on the same machine as the app? If not, this won’t work. You need 
> to add the IP of your app server. Something like...
> 
> hostall all 192.168.0.100trust
> 
> 
> On Nov 12, 2013, at 1:41 PM, Joe Kramer 
> mailto:jkmarti...@gmail.com>> wrote:
> 
> Thanks for the reply. Here is my config in pg_hba.conf. It seems like this 
> should not be causing the issue. Any other thoughts or something I am missing 
> in this config?
> 
> Thanks,
> 
> Joe
> 
> # TYPE  DATABASEUSERADDRESS METHOD
> 
> # "local" is for Unix domain socket connections only
> local   all all trust
> # IPv4 local connections:
> hostall all 127.0.0.1/32 
>trust
> # IPv6 local connections:
> hostall all ::1/128 trust
> 
> 
> On Tue, Nov 12, 2013 at 2:36 AM, Þór Sigurðsson 
> mailto:th...@samgongustofa.is>> wrote:
> 
> Have you given the user permission to connect to the database ?
> 
> Take a look at pg_hba.conf. Add a line for the user. If you _want_ the user 
> to use a password, then the last column should be "password" or better yet 
> "md5". If you want a trust-level connection, set it to "trust".
> 
> On 12.11.2013, at 09:58, Joe Kramer 
> mailto:jkmarti...@gmail.com>> wrote:
> 
>> Hi all,
>> 
>> It has been some time since I have done any WebObjects development and I am 
>> trying to resurrect an old project on a new machine. I went through all the 
>> steps to get WebObjects/Wonder installed and I can run HelloWorld. The 
>> problem appears to be with my Postgresql JDBC connection. I am running 
>> Postgres93.app. I added the postgresql-9.3-1100.jdbc3.jar to my project's 
>> Resources folder and added that jar to the build path. When I run and try to 
>> bootstrap my database, I cannot connect and I get the following error. Is 
>> there something that I missed in the setup process? Any help would be 
>> appreciated.
>> 
>> Thanks,
>> 
>> Joe Kramer
>> 
>> Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - An exception occurred 
>> while trying to open a channel: N/A
>> Nov 12 01:49:37 GALApplication[9199] INFO  er.transaction.adaptor.Exceptions 
>>  - Database Exception occured: java.lang.IllegalStateException: 
>> _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext 
>> com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open database 
>> channel.  Check your connection dictionary, and ensure your database is 
>> correctly configured.
>> Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn 
>> 'PostgresqlPlugIn' for JDBCAdaptor@1767199109
>> Nov 12 01:49:37 GALApplication[9199] INFO  
>> er.extensions.eof.ERXDatabaseContextDelegate  - GALDatabase: {plugin = 
>> "PostgresqlPlugIn"; username = "jkramer"; driver = "org.postgresql.Driver"; 
>> password = ""; URL = 
>> "jdbc:postgresql://localhost/gal_database?useBundl

Re: Postgresql connection issue

[Þór Sigurðsson]

Exactly as Ramsey said - although if your database IS in fact on a remote 
machine, you would not want "trust", since that would imply anybody could
connect as anybody to any database.

If your database is "mybase" and your database user is "myuser" and your 
development machine is 192.168.0.100, then your line ought to be something like:

hostmybase  myuser  192.168.0.100/32  md5

Only use a trust relationship if the server doesn't allow user logins or the 
users logging in are truly trusted, and then only for 127.0.0.1/8 :)

- however

If your database happens to be on your _local_ machine (same as your 
development/deployment) - like the Postgres.app for Mac OS X, then something 
else is amuck.

One thing that comes to mind - does your database actually exist?

psql -l

lists the databases

IF the database you expect to use doesn't exist, of course there will be no 
connection - so, if the database doesn't exist, I'll presume that the user 
doesn't exist either. In that case, you'll need to create both.

As the user running the postgres database (logged-in user if "Postgres.app" or 
"postgres","psql" or other db-centric user of the OS the DB is running on:

$ psql
# create user myuser password 'reallySecret2013';
...
# create database myuser owner myuser encoding='UTF8';
...
# exit

Then try connecting again.

Hope this helps :)

/Þór

On 12.11.2013, at 21:19, Ramsey Gurley 
mailto:rgur...@smarthealth.com>> wrote:

Is the db on the same machine as the app? If not, this won’t work. You need to 
add the IP of your app server. Something like...

hostall all 192.168.0.100trust


On Nov 12, 2013, at 1:41 PM, Joe Kramer 
mailto:jkmarti...@gmail.com>> wrote:

Thanks for the reply. Here is my config in pg_hba.conf. It seems like this 
should not be causing the issue. Any other thoughts or something I am missing 
in this config?

Thanks,

Joe

# TYPE  DATABASEUSERADDRESS METHOD

# "local" is for Unix domain socket connections only
local   all all trust
# IPv4 local connections:
hostall all 127.0.0.1/32   
 trust
# IPv6 local connections:
hostall all ::1/128 trust


On Tue, Nov 12, 2013 at 2:36 AM, Þór Sigurðsson 
mailto:th...@samgongustofa.is>> wrote:

Have you given the user permission to connect to the database ?

Take a look at pg_hba.conf. Add a line for the user. If you _want_ the user to 
use a password, then the last column should be "password" or better yet "md5". 
If you want a trust-level connection, set it to "trust".

On 12.11.2013, at 09:58, Joe Kramer 
mailto:jkmarti...@gmail.com>> wrote:

> Hi all,
>
> It has been some time since I have done any WebObjects development and I am 
> trying to resurrect an old project on a new machine. I went through all the 
> steps to get WebObjects/Wonder installed and I can run HelloWorld. The 
> problem appears to be with my Postgresql JDBC connection. I am running 
> Postgres93.app. I added the postgresql-9.3-1100.jdbc3.jar to my project's 
> Resources folder and added that jar to the build path. When I run and try to 
> bootstrap my database, I cannot connect and I get the following error. Is 
> there something that I missed in the setup process? Any help would be 
> appreciated.
>
> Thanks,
>
> Joe Kramer
>
> Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - An exception occurred 
> while trying to open a channel: N/A
> Nov 12 01:49:37 GALApplication[9199] INFO  er.transaction.adaptor.Exceptions  
> - Database Exception occured: java.lang.IllegalStateException: 
> _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext 
> com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open database 
> channel.  Check your connection dictionary, and ensure your database is 
> correctly configured.
> Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn 
> 'PostgresqlPlugIn' for JDBCAdaptor@1767199109
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.extensions.eof.ERXDatabaseContextDelegate  - GALDatabase: {plugin = 
> "PostgresqlPlugIn"; username = "jkramer"; driver = "org.postgresql.Driver"; 
> password = ""; URL = 
> "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Checking JDBC connection with 
> information {plugin = "PostgresqlPlugIn"; username = "jkramer"; driver = 
> "org.postgresql.Driver"; password = ""; URL = 
> "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Trying to create JDBCAdaptor...
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Successfully created adaptor 
> com.webobjects.jdbcadaptor.JDBCAdaptor
> Nov 12 01:49:37 GALAppl

Re: Postgresql connection issue

[Theodore Petrosky]

http://jdbc.postgresql.org/download.html

Go check the jdbc version that they recommend. It does not match what yor error 
messages point to.

Ted


Sent from my iPad

> On Nov 12, 2013, at 5:35 PM, Ramsey Gurley  wrote:
> 
> For what it’s worth, I needed my local machine in the file under its 
> 192.168.x.x address for everything to work. May be because the database is 
> dedicated? Don’t know. Here’s what I have though:
> 
> postgresql.conf
>listen_addresses = 'localhost,192.168.100.96’
> pg_hba.conf
>host all all 192.168.100.96/32 md5
> 
> 
>> On Nov 12, 2013, at 3:23 PM, Joe Kramer  wrote:
>> 
>> The DB is on the same machine, so not sure why I would need another host 
>> entry.
>> 
>> Sent from my iPhone
>> 
>>> On Nov 12, 2013, at 1:50 PM, Theodore Petrosky  wrote:
>>> 
>>> btw, did you read this  in the pg_hba.conf file:
>>> 
>>> #
>>> # If you want to allow non-local connections, you need to add more
>>> # "host" records.  In that case you will also need to make PostgreSQL
>>> # listen on a non-local interface via the listen_addresses
>>> # configuration parameter, or via the -i or -h command line switches.
>>> 
>>> # CAUTION: Configuring the system for local "trust" authentication
>>> # allows any local user to connect as any PostgreSQL user, including
>>> # the database superuser.  If you do not trust all your local users,
>>> # use another authentication method.
>>> 
>>> and from postgresql.conf
>>> 
>>> #--
>>> # CONNECTIONS AND AUTHENTICATION
>>> #--
>>> 
>>> # - Connection Settings -
>>> 
>>> listen_addresses = '*'# what IP address(es) to listen on;
>>># comma-separated list of addresses;
>>># defaults to 'localhost'; use '*' for all
>>># (change requires restart)
>>> 
>>> 
>>> 
>>> 
 On Nov 12, 2013, at 4:19 PM, Ramsey Gurley  wrote:
 
 Is the db on the same machine as the app? If not, this won’t work. You 
 need to add the IP of your app server. Something like...
 
 hostall all 192.168.0.100trust
 
 
> On Nov 12, 2013, at 1:41 PM, Joe Kramer  wrote:
> 
> Thanks for the reply. Here is my config in pg_hba.conf. It seems like 
> this should not be causing the issue. Any other thoughts or something I 
> am missing in this config?
> 
> Thanks,
> 
> Joe
> 
> # TYPE  DATABASEUSERADDRESS METHOD
> 
> # "local" is for Unix domain socket connections only
> local   all all trust
> # IPv4 local connections:
> hostall all 127.0.0.1/32trust
> # IPv6 local connections:
> hostall all ::1/128 trust
> 
> 
> On Tue, Nov 12, 2013 at 2:36 AM, Þór Sigurðsson  
> wrote:
> 
> Have you given the user permission to connect to the database ?
> 
> Take a look at pg_hba.conf. Add a line for the user. If you _want_ the 
> user to use a password, then the last column should be "password" or 
> better yet "md5". If you want a trust-level connection, set it to "trust".
> 
>> On 12.11.2013, at 09:58, Joe Kramer  wrote:
>> 
>> Hi all,
>> 
>> It has been some time since I have done any WebObjects development and I 
>> am trying to resurrect an old project on a new machine. I went through 
>> all the steps to get WebObjects/Wonder installed and I can run 
>> HelloWorld. The problem appears to be with my Postgresql JDBC 
>> connection. I am running Postgres93.app. I added the 
>> postgresql-9.3-1100.jdbc3.jar to my project's Resources folder and added 
>> that jar to the build path. When I run and try to bootstrap my database, 
>> I cannot connect and I get the following error. Is there something that 
>> I missed in the setup process? Any help would be appreciated.
>> 
>> Thanks,
>> 
>> Joe Kramer
>> 
>> Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - An exception 
>> occurred while trying to open a channel: N/A
>> Nov 12 01:49:37 GALApplication[9199] INFO  
>> er.transaction.adaptor.Exceptions  - Database Exception occured: 
>> java.lang.IllegalStateException: _obtainOpenChannel -- 
>> com.webobjects.eoaccess.EODatabaseContext 
>> com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open 
>> database channel.  Check your connection dictionary, and ensure your 
>> database is correctly configured.
>> Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn 
>> 'PostgresqlPlugIn' for JDBCAdaptor@1767199109
>> Nov 12 01:49:37 GALApplication[9199] INFO  
>> er.extensions.eof.ERXDatabaseContextDelegate  - GALDat

Re: Postgresql connection issue

[Ramsey Gurley]

For what it’s worth, I needed my local machine in the file under its 
192.168.x.x address for everything to work. May be because the database is 
dedicated? Don’t know. Here’s what I have though:

postgresql.conf
listen_addresses = 'localhost,192.168.100.96’
pg_hba.conf
host all all 192.168.100.96/32 md5


On Nov 12, 2013, at 3:23 PM, Joe Kramer  wrote:

> The DB is on the same machine, so not sure why I would need another host 
> entry.
> 
> Sent from my iPhone
> 
> On Nov 12, 2013, at 1:50 PM, Theodore Petrosky  wrote:
> 
>> btw, did you read this  in the pg_hba.conf file:
>> 
>> #
>> # If you want to allow non-local connections, you need to add more
>> # "host" records.  In that case you will also need to make PostgreSQL
>> # listen on a non-local interface via the listen_addresses
>> # configuration parameter, or via the -i or -h command line switches.
>> 
>> # CAUTION: Configuring the system for local "trust" authentication
>> # allows any local user to connect as any PostgreSQL user, including
>> # the database superuser.  If you do not trust all your local users,
>> # use another authentication method.
>> 
>> and from postgresql.conf
>> 
>> #--
>> # CONNECTIONS AND AUTHENTICATION
>> #--
>> 
>> # - Connection Settings -
>> 
>> listen_addresses = '*'   # what IP address(es) to listen on;
>>  # comma-separated list of addresses;
>>  # defaults to 'localhost'; use '*' for 
>> all
>>  # (change requires restart)
>> 
>> 
>> 
>> 
>> On Nov 12, 2013, at 4:19 PM, Ramsey Gurley  wrote:
>> 
>>> Is the db on the same machine as the app? If not, this won’t work. You need 
>>> to add the IP of your app server. Something like...
>>> 
>>> hostall all 192.168.0.100trust
>>> 
>>> 
>>> On Nov 12, 2013, at 1:41 PM, Joe Kramer  wrote:
>>> 
 Thanks for the reply. Here is my config in pg_hba.conf. It seems like this 
 should not be causing the issue. Any other thoughts or something I am 
 missing in this config?
 
 Thanks,
 
 Joe
 
 # TYPE  DATABASEUSERADDRESS METHOD
 
 # "local" is for Unix domain socket connections only
 local   all all trust
 # IPv4 local connections:
 hostall all 127.0.0.1/32trust
 # IPv6 local connections:
 hostall all ::1/128 trust
 
 
 On Tue, Nov 12, 2013 at 2:36 AM, Þór Sigurðsson  
 wrote:
 
 Have you given the user permission to connect to the database ?
 
 Take a look at pg_hba.conf. Add a line for the user. If you _want_ the 
 user to use a password, then the last column should be "password" or 
 better yet "md5". If you want a trust-level connection, set it to "trust".
 
 On 12.11.2013, at 09:58, Joe Kramer  wrote:
 
 > Hi all,
 >
 > It has been some time since I have done any WebObjects development and I 
 > am trying to resurrect an old project on a new machine. I went through 
 > all the steps to get WebObjects/Wonder installed and I can run 
 > HelloWorld. The problem appears to be with my Postgresql JDBC 
 > connection. I am running Postgres93.app. I added the 
 > postgresql-9.3-1100.jdbc3.jar to my project's Resources folder and added 
 > that jar to the build path. When I run and try to bootstrap my database, 
 > I cannot connect and I get the following error. Is there something that 
 > I missed in the setup process? Any help would be appreciated.
 >
 > Thanks,
 >
 > Joe Kramer
 >
 > Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - An exception 
 > occurred while trying to open a channel: N/A
 > Nov 12 01:49:37 GALApplication[9199] INFO  
 > er.transaction.adaptor.Exceptions  - Database Exception occured: 
 > java.lang.IllegalStateException: _obtainOpenChannel -- 
 > com.webobjects.eoaccess.EODatabaseContext 
 > com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open 
 > database channel.  Check your connection dictionary, and ensure your 
 > database is correctly configured.
 > Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn 
 > 'PostgresqlPlugIn' for JDBCAdaptor@1767199109
 > Nov 12 01:49:37 GALApplication[9199] INFO  
 > er.extensions.eof.ERXDatabaseContextDelegate  - GALDatabase: {plugin = 
 > "PostgresqlPlugIn"; username = "jkramer"; driver = 
 > "org.postgresql.Driver"; password = ""; URL = 
 > "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
 > Nov 12 01:49:37 GALApplication[9199] INFO  

Re: Postgresql connection issue

[Joe Kramer]

The DB is on the same machine, so not sure why I would need another host entry.

Sent from my iPhone

> On Nov 12, 2013, at 1:50 PM, Theodore Petrosky  wrote:
> 
> btw, did you read this  in the pg_hba.conf file:
> 
> #
> # If you want to allow non-local connections, you need to add more
> # "host" records.  In that case you will also need to make PostgreSQL
> # listen on a non-local interface via the listen_addresses
> # configuration parameter, or via the -i or -h command line switches.
> 
> # CAUTION: Configuring the system for local "trust" authentication
> # allows any local user to connect as any PostgreSQL user, including
> # the database superuser.  If you do not trust all your local users,
> # use another authentication method.
> 
> and from postgresql.conf
> 
> #--
> # CONNECTIONS AND AUTHENTICATION
> #--
> 
> # - Connection Settings -
> 
> listen_addresses = '*'# what IP address(es) to listen on;
>   # comma-separated list of addresses;
>   # defaults to 'localhost'; use '*' for 
> all
>   # (change requires restart)
> 
> 
> 
> 
>> On Nov 12, 2013, at 4:19 PM, Ramsey Gurley  wrote:
>> 
>> Is the db on the same machine as the app? If not, this won’t work. You need 
>> to add the IP of your app server. Something like...
>> 
>> hostall all 192.168.0.100trust
>> 
>> 
>>> On Nov 12, 2013, at 1:41 PM, Joe Kramer  wrote:
>>> 
>>> Thanks for the reply. Here is my config in pg_hba.conf. It seems like this 
>>> should not be causing the issue. Any other thoughts or something I am 
>>> missing in this config?
>>> 
>>> Thanks,
>>> 
>>> Joe
>>> 
>>> # TYPE  DATABASEUSERADDRESS METHOD
>>> 
>>> # "local" is for Unix domain socket connections only
>>> local   all all trust
>>> # IPv4 local connections:
>>> hostall all 127.0.0.1/32trust
>>> # IPv6 local connections:
>>> hostall all ::1/128 trust
>>> 
>>> 
 On Tue, Nov 12, 2013 at 2:36 AM, Þór Sigurðsson  
 wrote:
 
 Have you given the user permission to connect to the database ?
 
 Take a look at pg_hba.conf. Add a line for the user. If you _want_ the 
 user to use a password, then the last column should be "password" or 
 better yet "md5". If you want a trust-level connection, set it to "trust".
 
 On 12.11.2013, at 09:58, Joe Kramer  wrote:
 
 > Hi all,
 >
 > It has been some time since I have done any WebObjects development and I 
 > am trying to resurrect an old project on a new machine. I went through 
 > all the steps to get WebObjects/Wonder installed and I can run 
 > HelloWorld. The problem appears to be with my Postgresql JDBC 
 > connection. I am running Postgres93.app. I added the 
 > postgresql-9.3-1100.jdbc3.jar to my project's Resources folder and added 
 > that jar to the build path. When I run and try to bootstrap my database, 
 > I cannot connect and I get the following error. Is there something that 
 > I missed in the setup process? Any help would be appreciated.
 >
 > Thanks,
 >
 > Joe Kramer
 >
 > Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - An exception 
 > occurred while trying to open a channel: N/A
 > Nov 12 01:49:37 GALApplication[9199] INFO  
 > er.transaction.adaptor.Exceptions  - Database Exception occured: 
 > java.lang.IllegalStateException: _obtainOpenChannel -- 
 > com.webobjects.eoaccess.EODatabaseContext 
 > com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open 
 > database channel.  Check your connection dictionary, and ensure your 
 > database is correctly configured.
 > Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn 
 > 'PostgresqlPlugIn' for JDBCAdaptor@1767199109
 > Nov 12 01:49:37 GALApplication[9199] INFO  
 > er.extensions.eof.ERXDatabaseContextDelegate  - GALDatabase: {plugin = 
 > "PostgresqlPlugIn"; username = "jkramer"; driver = 
 > "org.postgresql.Driver"; password = ""; URL = 
 > "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
 > Nov 12 01:49:37 GALApplication[9199] INFO  
 > er.transaction.adaptor.ConnectionAnalyzer  - Checking JDBC connection 
 > with information {plugin = "PostgresqlPlugIn"; username = "jkramer"; 
 > driver = "org.postgresql.Driver"; password = ">>> > log>"; URL = 
 > "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
 > Nov 12 01:49:37 GALApplication[9199] INFO  
 > er.transaction.adaptor.ConnectionAnalyzer  - Trying to create 
 > JDBCA

Re: Postgresql connection issue

[Theodore Petrosky]

btw, did you read this  in the pg_hba.conf file:

#
# If you want to allow non-local connections, you need to add more
# "host" records.  In that case you will also need to make PostgreSQL
# listen on a non-local interface via the listen_addresses
# configuration parameter, or via the -i or -h command line switches.

# CAUTION: Configuring the system for local "trust" authentication
# allows any local user to connect as any PostgreSQL user, including
# the database superuser.  If you do not trust all your local users,
# use another authentication method.

and from postgresql.conf

#--
# CONNECTIONS AND AUTHENTICATION
#--

# - Connection Settings -

listen_addresses = '*'  # what IP address(es) to listen on;
# comma-separated list of addresses;
# defaults to 'localhost'; use '*' for 
all
# (change requires restart)




On Nov 12, 2013, at 4:19 PM, Ramsey Gurley  wrote:

> Is the db on the same machine as the app? If not, this won’t work. You need 
> to add the IP of your app server. Something like...
> 
> hostall all 192.168.0.100trust
> 
> 
> On Nov 12, 2013, at 1:41 PM, Joe Kramer  wrote:
> 
>> Thanks for the reply. Here is my config in pg_hba.conf. It seems like this 
>> should not be causing the issue. Any other thoughts or something I am 
>> missing in this config?
>> 
>> Thanks,
>> 
>> Joe
>> 
>> # TYPE  DATABASEUSERADDRESS METHOD
>> 
>> # "local" is for Unix domain socket connections only
>> local   all all trust
>> # IPv4 local connections:
>> hostall all 127.0.0.1/32trust
>> # IPv6 local connections:
>> hostall all ::1/128 trust
>> 
>> 
>> On Tue, Nov 12, 2013 at 2:36 AM, Þór Sigurðsson  
>> wrote:
>> 
>> Have you given the user permission to connect to the database ?
>> 
>> Take a look at pg_hba.conf. Add a line for the user. If you _want_ the user 
>> to use a password, then the last column should be "password" or better yet 
>> "md5". If you want a trust-level connection, set it to "trust".
>> 
>> On 12.11.2013, at 09:58, Joe Kramer  wrote:
>> 
>> > Hi all,
>> >
>> > It has been some time since I have done any WebObjects development and I 
>> > am trying to resurrect an old project on a new machine. I went through all 
>> > the steps to get WebObjects/Wonder installed and I can run HelloWorld. The 
>> > problem appears to be with my Postgresql JDBC connection. I am running 
>> > Postgres93.app. I added the postgresql-9.3-1100.jdbc3.jar to my project's 
>> > Resources folder and added that jar to the build path. When I run and try 
>> > to bootstrap my database, I cannot connect and I get the following error. 
>> > Is there something that I missed in the setup process? Any help would be 
>> > appreciated.
>> >
>> > Thanks,
>> >
>> > Joe Kramer
>> >
>> > Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - An exception occurred 
>> > while trying to open a channel: N/A
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.transaction.adaptor.Exceptions  - Database Exception occured: 
>> > java.lang.IllegalStateException: _obtainOpenChannel -- 
>> > com.webobjects.eoaccess.EODatabaseContext 
>> > com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open 
>> > database channel.  Check your connection dictionary, and ensure your 
>> > database is correctly configured.
>> > Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn 
>> > 'PostgresqlPlugIn' for JDBCAdaptor@1767199109
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.extensions.eof.ERXDatabaseContextDelegate  - GALDatabase: {plugin = 
>> > "PostgresqlPlugIn"; username = "jkramer"; driver = 
>> > "org.postgresql.Driver"; password = ""; URL = 
>> > "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.transaction.adaptor.ConnectionAnalyzer  - Checking JDBC connection with 
>> > information {plugin = "PostgresqlPlugIn"; username = "jkramer"; driver = 
>> > "org.postgresql.Driver"; password = ""; URL = 
>> > "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.transaction.adaptor.ConnectionAnalyzer  - Trying to create 
>> > JDBCAdaptor...
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.transaction.adaptor.ConnectionAnalyzer  - Successfully created adaptor 
>> > com.webobjects.jdbcadaptor.JDBCAdaptor
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.transaction.adaptor.ConnectionAnalyzer  - Trying to create plugin...
>> > Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Us

Re: Postgresql connection issue

[Theodore Petrosky]

like ramsey said:

# TYPE  DATABASEUSERADDRESS METHOD
# IPv4 local connections:
hostall admin   10.1.5.100/32   trust

the line above is on my database machine (10.1.2.10). it allows 10.1.5.100 to 
talk to the database in a trust setting. these are local on my internal network.

Ted



On Nov 12, 2013, at 4:19 PM, Ramsey Gurley  wrote:

> Is the db on the same machine as the app? If not, this won’t work. You need 
> to add the IP of your app server. Something like...
> 
> hostall all 192.168.0.100trust
> 
> 
> On Nov 12, 2013, at 1:41 PM, Joe Kramer  wrote:
> 
>> Thanks for the reply. Here is my config in pg_hba.conf. It seems like this 
>> should not be causing the issue. Any other thoughts or something I am 
>> missing in this config?
>> 
>> Thanks,
>> 
>> Joe
>> 
>> # TYPE  DATABASEUSERADDRESS METHOD
>> 
>> # "local" is for Unix domain socket connections only
>> local   all all trust
>> # IPv4 local connections:
>> hostall all 127.0.0.1/32trust
>> # IPv6 local connections:
>> hostall all ::1/128 trust
>> 
>> 
>> On Tue, Nov 12, 2013 at 2:36 AM, Þór Sigurðsson  
>> wrote:
>> 
>> Have you given the user permission to connect to the database ?
>> 
>> Take a look at pg_hba.conf. Add a line for the user. If you _want_ the user 
>> to use a password, then the last column should be "password" or better yet 
>> "md5". If you want a trust-level connection, set it to "trust".
>> 
>> On 12.11.2013, at 09:58, Joe Kramer  wrote:
>> 
>> > Hi all,
>> >
>> > It has been some time since I have done any WebObjects development and I 
>> > am trying to resurrect an old project on a new machine. I went through all 
>> > the steps to get WebObjects/Wonder installed and I can run HelloWorld. The 
>> > problem appears to be with my Postgresql JDBC connection. I am running 
>> > Postgres93.app. I added the postgresql-9.3-1100.jdbc3.jar to my project's 
>> > Resources folder and added that jar to the build path. When I run and try 
>> > to bootstrap my database, I cannot connect and I get the following error. 
>> > Is there something that I missed in the setup process? Any help would be 
>> > appreciated.
>> >
>> > Thanks,
>> >
>> > Joe Kramer
>> >
>> > Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - An exception occurred 
>> > while trying to open a channel: N/A
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.transaction.adaptor.Exceptions  - Database Exception occured: 
>> > java.lang.IllegalStateException: _obtainOpenChannel -- 
>> > com.webobjects.eoaccess.EODatabaseContext 
>> > com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open 
>> > database channel.  Check your connection dictionary, and ensure your 
>> > database is correctly configured.
>> > Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn 
>> > 'PostgresqlPlugIn' for JDBCAdaptor@1767199109
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.extensions.eof.ERXDatabaseContextDelegate  - GALDatabase: {plugin = 
>> > "PostgresqlPlugIn"; username = "jkramer"; driver = 
>> > "org.postgresql.Driver"; password = ""; URL = 
>> > "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.transaction.adaptor.ConnectionAnalyzer  - Checking JDBC connection with 
>> > information {plugin = "PostgresqlPlugIn"; username = "jkramer"; driver = 
>> > "org.postgresql.Driver"; password = ""; URL = 
>> > "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.transaction.adaptor.ConnectionAnalyzer  - Trying to create 
>> > JDBCAdaptor...
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.transaction.adaptor.ConnectionAnalyzer  - Successfully created adaptor 
>> > com.webobjects.jdbcadaptor.JDBCAdaptor
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.transaction.adaptor.ConnectionAnalyzer  - Trying to create plugin...
>> > Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn 
>> > 'PostgresqlPlugIn' for JDBCAdaptor@1616586953
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.transaction.adaptor.ConnectionAnalyzer  - Created plugin 
>> > com.webobjects.jdbcadaptor.PostgresqlPlugIn
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.transaction.adaptor.ConnectionAnalyzer  - Trying to load JDBC driver 
>> > org.postgresql.Driver...
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.transaction.adaptor.ConnectionAnalyzer  - Successfully loaded JDBC 
>> > driver org.postgresql.Driver
>> > Nov 12 01:49:37 GALApplication[9199] INFO  
>> > er.transaction.adaptor.ConnectionAnalyzer  - JDBC driver and plugin are 
>> > loaded, trying to connect...
>> > Nov 12 01:49:37 GALApplication[9199] INFO 

Re: Postgresql connection issue

[Ramsey Gurley]

Is the db on the same machine as the app? If not, this won’t work. You need to 
add the IP of your app server. Something like...

hostall all 192.168.0.100trust


On Nov 12, 2013, at 1:41 PM, Joe Kramer  wrote:

> Thanks for the reply. Here is my config in pg_hba.conf. It seems like this 
> should not be causing the issue. Any other thoughts or something I am missing 
> in this config?
> 
> Thanks,
> 
> Joe
> 
> # TYPE  DATABASEUSERADDRESS METHOD
> 
> # "local" is for Unix domain socket connections only
> local   all all trust
> # IPv4 local connections:
> hostall all 127.0.0.1/32trust
> # IPv6 local connections:
> hostall all ::1/128 trust
> 
> 
> On Tue, Nov 12, 2013 at 2:36 AM, Þór Sigurðsson  
> wrote:
> 
> Have you given the user permission to connect to the database ?
> 
> Take a look at pg_hba.conf. Add a line for the user. If you _want_ the user 
> to use a password, then the last column should be "password" or better yet 
> "md5". If you want a trust-level connection, set it to "trust".
> 
> On 12.11.2013, at 09:58, Joe Kramer  wrote:
> 
> > Hi all,
> >
> > It has been some time since I have done any WebObjects development and I am 
> > trying to resurrect an old project on a new machine. I went through all the 
> > steps to get WebObjects/Wonder installed and I can run HelloWorld. The 
> > problem appears to be with my Postgresql JDBC connection. I am running 
> > Postgres93.app. I added the postgresql-9.3-1100.jdbc3.jar to my project's 
> > Resources folder and added that jar to the build path. When I run and try 
> > to bootstrap my database, I cannot connect and I get the following error. 
> > Is there something that I missed in the setup process? Any help would be 
> > appreciated.
> >
> > Thanks,
> >
> > Joe Kramer
> >
> > Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - An exception occurred 
> > while trying to open a channel: N/A
> > Nov 12 01:49:37 GALApplication[9199] INFO  
> > er.transaction.adaptor.Exceptions  - Database Exception occured: 
> > java.lang.IllegalStateException: _obtainOpenChannel -- 
> > com.webobjects.eoaccess.EODatabaseContext 
> > com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open database 
> > channel.  Check your connection dictionary, and ensure your database is 
> > correctly configured.
> > Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn 
> > 'PostgresqlPlugIn' for JDBCAdaptor@1767199109
> > Nov 12 01:49:37 GALApplication[9199] INFO  
> > er.extensions.eof.ERXDatabaseContextDelegate  - GALDatabase: {plugin = 
> > "PostgresqlPlugIn"; username = "jkramer"; driver = "org.postgresql.Driver"; 
> > password = ""; URL = 
> > "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
> > Nov 12 01:49:37 GALApplication[9199] INFO  
> > er.transaction.adaptor.ConnectionAnalyzer  - Checking JDBC connection with 
> > information {plugin = "PostgresqlPlugIn"; username = "jkramer"; driver = 
> > "org.postgresql.Driver"; password = ""; URL = 
> > "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
> > Nov 12 01:49:37 GALApplication[9199] INFO  
> > er.transaction.adaptor.ConnectionAnalyzer  - Trying to create JDBCAdaptor...
> > Nov 12 01:49:37 GALApplication[9199] INFO  
> > er.transaction.adaptor.ConnectionAnalyzer  - Successfully created adaptor 
> > com.webobjects.jdbcadaptor.JDBCAdaptor
> > Nov 12 01:49:37 GALApplication[9199] INFO  
> > er.transaction.adaptor.ConnectionAnalyzer  - Trying to create plugin...
> > Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn 
> > 'PostgresqlPlugIn' for JDBCAdaptor@1616586953
> > Nov 12 01:49:37 GALApplication[9199] INFO  
> > er.transaction.adaptor.ConnectionAnalyzer  - Created plugin 
> > com.webobjects.jdbcadaptor.PostgresqlPlugIn
> > Nov 12 01:49:37 GALApplication[9199] INFO  
> > er.transaction.adaptor.ConnectionAnalyzer  - Trying to load JDBC driver 
> > org.postgresql.Driver...
> > Nov 12 01:49:37 GALApplication[9199] INFO  
> > er.transaction.adaptor.ConnectionAnalyzer  - Successfully loaded JDBC 
> > driver org.postgresql.Driver
> > Nov 12 01:49:37 GALApplication[9199] INFO  
> > er.transaction.adaptor.ConnectionAnalyzer  - JDBC driver and plugin are 
> > loaded, trying to connect...
> > Nov 12 01:49:37 GALApplication[9199] INFO  
> > er.transaction.adaptor.ConnectionAnalyzer  - Error: Exception thrown while 
> > connecting.
> > Check exception message carefully.
> > Nov 12 01:49:37 GALApplication[9199] ERROR 
> > er.transaction.adaptor.ConnectionAnalyzer  - No connection.
> > Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - A fatal exception 
> > occurred: _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext 
> > com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open database 
> > channel.  Check your connecti

Re: Postgresql connection issue

[Joe Kramer]

Using PGAdmin to connect and the DB is up and running.


On Tue, Nov 12, 2013 at 1:09 PM, Theodore Petrosky wrote:

> did you confirm that the database is running?
>
> what do you use to talk directly to the database? psql, pgadmin?
>
> Ted
>
>
> On Nov 12, 2013, at 4:58 AM, Joe Kramer  wrote:
>
> > Hi all,
> >
> > It has been some time since I have done any WebObjects development and I
> am trying to resurrect an old project on a new machine. I went through all
> the steps to get WebObjects/Wonder installed and I can run HelloWorld. The
> problem appears to be with my Postgresql JDBC connection. I am running
> Postgres93.app. I added the postgresql-9.3-1100.jdbc3.jar to my project's
> Resources folder and added that jar to the build path. When I run and try
> to bootstrap my database, I cannot connect and I get the following error.
> Is there something that I missed in the setup process? Any help would be
> appreciated.
> >
> > Thanks,
> >
> > Joe Kramer
> >
> > Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - An exception
> occurred while trying to open a channel: N/A
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.Exceptions  - Database Exception occured:
> java.lang.IllegalStateException: _obtainOpenChannel --
> com.webobjects.eoaccess.EODatabaseContext
> com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open
> database channel.  Check your connection dictionary, and ensure your
> database is correctly configured.
> > Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn
> 'PostgresqlPlugIn' for JDBCAdaptor@1767199109
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.extensions.eof.ERXDatabaseContextDelegate  - GALDatabase: {plugin =
> "PostgresqlPlugIn"; username = "jkramer"; driver = "org.postgresql.Driver";
> password = ""; URL =
> "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Checking JDBC connection with
> information {plugin = "PostgresqlPlugIn"; username = "jkramer"; driver =
> "org.postgresql.Driver"; password = ""; URL =
> "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Trying to create
> JDBCAdaptor...
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Successfully created adaptor
> com.webobjects.jdbcadaptor.JDBCAdaptor
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Trying to create plugin...
> > Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn
> 'PostgresqlPlugIn' for JDBCAdaptor@1616586953
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Created plugin
> com.webobjects.jdbcadaptor.PostgresqlPlugIn
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Trying to load JDBC driver
> org.postgresql.Driver...
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Successfully loaded JDBC
> driver org.postgresql.Driver
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - JDBC driver and plugin are
> loaded, trying to connect...
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Error: Exception thrown while
> connecting.
> > Check exception message carefully.
> > Nov 12 01:49:37 GALApplication[9199] ERROR
> er.transaction.adaptor.ConnectionAnalyzer  - No connection.
> > Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - A fatal exception
> occurred: _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext
> com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open
> database channel.  Check your connection dictionary, and ensure your
> database is correctly configured.
> > [2013-11-12 1:49:37 PST]  java.lang.IllegalStateException:
> _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext
> com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open
> database channel.  Check your connection dictionary, and ensure your
> database is correctly configured.
> >   at
> com.webobjects.eoaccess.EODatabaseContext._obtainOpenChannel(EODatabaseContext.java:1967)
> >   at
> com.webobjects.eoaccess.EODatabaseContext._objectsWithFetchSpecificationEditingContext(EODatabaseContext.java:3054)
> >   at
> com.webobjects.eoaccess.EODatabaseContext.objectsWithFetchSpecification(EODatabaseContext.java:3195)
> >   at
> com.webobjects.eocontrol.EOObjectStoreCoordinator.objectsWithFetchSpecification(EOObjectStoreCoordinator.java:488)
> >   at
> com.webobjects.eocontrol.EOEditingContext.objectsWithFetchSpecification(EOEditingContext.java:4069)
> >   at
> er.extensions.eof.ERXEC.objectsWithFetchSpecification(ERXEC.java:1308)
> >   at
> com.webobjects.eocontrol.EOEdit

Re: Postgresql connection issue

[Theodore Petrosky]

did you confirm that the database is running?

what do you use to talk directly to the database? psql, pgadmin?

Ted


On Nov 12, 2013, at 4:58 AM, Joe Kramer  wrote:

> Hi all,
> 
> It has been some time since I have done any WebObjects development and I am 
> trying to resurrect an old project on a new machine. I went through all the 
> steps to get WebObjects/Wonder installed and I can run HelloWorld. The 
> problem appears to be with my Postgresql JDBC connection. I am running 
> Postgres93.app. I added the postgresql-9.3-1100.jdbc3.jar to my project's 
> Resources folder and added that jar to the build path. When I run and try to 
> bootstrap my database, I cannot connect and I get the following error. Is 
> there something that I missed in the setup process? Any help would be 
> appreciated.
> 
> Thanks,
> 
> Joe Kramer
> 
> Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - An exception occurred 
> while trying to open a channel: N/A
> Nov 12 01:49:37 GALApplication[9199] INFO  er.transaction.adaptor.Exceptions  
> - Database Exception occured: java.lang.IllegalStateException: 
> _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext 
> com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open database 
> channel.  Check your connection dictionary, and ensure your database is 
> correctly configured.
> Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn 
> 'PostgresqlPlugIn' for JDBCAdaptor@1767199109
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.extensions.eof.ERXDatabaseContextDelegate  - GALDatabase: {plugin = 
> "PostgresqlPlugIn"; username = "jkramer"; driver = "org.postgresql.Driver"; 
> password = ""; URL = 
> "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Checking JDBC connection with 
> information {plugin = "PostgresqlPlugIn"; username = "jkramer"; driver = 
> "org.postgresql.Driver"; password = ""; URL = 
> "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Trying to create JDBCAdaptor...
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Successfully created adaptor 
> com.webobjects.jdbcadaptor.JDBCAdaptor
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Trying to create plugin...
> Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn 
> 'PostgresqlPlugIn' for JDBCAdaptor@1616586953
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Created plugin 
> com.webobjects.jdbcadaptor.PostgresqlPlugIn
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Trying to load JDBC driver 
> org.postgresql.Driver...
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Successfully loaded JDBC driver 
> org.postgresql.Driver
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - JDBC driver and plugin are 
> loaded, trying to connect...
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Error: Exception thrown while 
> connecting.
> Check exception message carefully.
> Nov 12 01:49:37 GALApplication[9199] ERROR 
> er.transaction.adaptor.ConnectionAnalyzer  - No connection.
> Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - A fatal exception 
> occurred: _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext 
> com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open database 
> channel.  Check your connection dictionary, and ensure your database is 
> correctly configured.
> [2013-11-12 1:49:37 PST]  java.lang.IllegalStateException: 
> _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext 
> com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open database 
> channel.  Check your connection dictionary, and ensure your database is 
> correctly configured.
>   at 
> com.webobjects.eoaccess.EODatabaseContext._obtainOpenChannel(EODatabaseContext.java:1967)
>   at 
> com.webobjects.eoaccess.EODatabaseContext._objectsWithFetchSpecificationEditingContext(EODatabaseContext.java:3054)
>   at 
> com.webobjects.eoaccess.EODatabaseContext.objectsWithFetchSpecification(EODatabaseContext.java:3195)
>   at 
> com.webobjects.eocontrol.EOObjectStoreCoordinator.objectsWithFetchSpecification(EOObjectStoreCoordinator.java:488)
>   at 
> com.webobjects.eocontrol.EOEditingContext.objectsWithFetchSpecification(EOEditingContext.java:4069)
>   at 
> er.extensions.eof.ERXEC.objectsWithFetchSpecification(ERXEC.java:1308)
>   at 
> com.webobjects.eocontrol.EOEditingContext.objectsWithFetchSpecification(EOEditingContext.java:)
>   at 
> er.extensions.eof.ERXFetchSpecification.fetchObjects(ERXFe

Re: Postgresql connection issue

[Joe Kramer]

Thanks for the reply. Here is my config in pg_hba.conf. It seems like this
should not be causing the issue. Any other thoughts or something I am
missing in this config?

Thanks,

Joe

# TYPE  DATABASEUSERADDRESS METHOD

# "local" is for Unix domain socket connections only
local   all all trust
# IPv4 local connections:
hostall all 127.0.0.1/32trust
# IPv6 local connections:
hostall all ::1/128 trust


On Tue, Nov 12, 2013 at 2:36 AM, Þór Sigurðsson wrote:

>
> Have you given the user permission to connect to the database ?
>
> Take a look at pg_hba.conf. Add a line for the user. If you _want_ the
> user to use a password, then the last column should be "password" or better
> yet "md5". If you want a trust-level connection, set it to "trust".
>
> On 12.11.2013, at 09:58, Joe Kramer  wrote:
>
> > Hi all,
> >
> > It has been some time since I have done any WebObjects development and I
> am trying to resurrect an old project on a new machine. I went through all
> the steps to get WebObjects/Wonder installed and I can run HelloWorld. The
> problem appears to be with my Postgresql JDBC connection. I am running
> Postgres93.app. I added the postgresql-9.3-1100.jdbc3.jar to my project's
> Resources folder and added that jar to the build path. When I run and try
> to bootstrap my database, I cannot connect and I get the following error.
> Is there something that I missed in the setup process? Any help would be
> appreciated.
> >
> > Thanks,
> >
> > Joe Kramer
> >
> > Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - An exception
> occurred while trying to open a channel: N/A
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.Exceptions  - Database Exception occured:
> java.lang.IllegalStateException: _obtainOpenChannel --
> com.webobjects.eoaccess.EODatabaseContext
> com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open
> database channel.  Check your connection dictionary, and ensure your
> database is correctly configured.
> > Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn
> 'PostgresqlPlugIn' for JDBCAdaptor@1767199109
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.extensions.eof.ERXDatabaseContextDelegate  - GALDatabase: {plugin =
> "PostgresqlPlugIn"; username = "jkramer"; driver = "org.postgresql.Driver";
> password = ""; URL =
> "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Checking JDBC connection with
> information {plugin = "PostgresqlPlugIn"; username = "jkramer"; driver =
> "org.postgresql.Driver"; password = ""; URL =
> "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Trying to create
> JDBCAdaptor...
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Successfully created adaptor
> com.webobjects.jdbcadaptor.JDBCAdaptor
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Trying to create plugin...
> > Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn
> 'PostgresqlPlugIn' for JDBCAdaptor@1616586953
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Created plugin
> com.webobjects.jdbcadaptor.PostgresqlPlugIn
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Trying to load JDBC driver
> org.postgresql.Driver...
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Successfully loaded JDBC
> driver org.postgresql.Driver
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - JDBC driver and plugin are
> loaded, trying to connect...
> > Nov 12 01:49:37 GALApplication[9199] INFO
>  er.transaction.adaptor.ConnectionAnalyzer  - Error: Exception thrown while
> connecting.
> > Check exception message carefully.
> > Nov 12 01:49:37 GALApplication[9199] ERROR
> er.transaction.adaptor.ConnectionAnalyzer  - No connection.
> > Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - A fatal exception
> occurred: _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext
> com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open
> database channel.  Check your connection dictionary, and ensure your
> database is correctly configured.
> > [2013-11-12 1:49:37 PST]  java.lang.IllegalStateException:
> _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext
> com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open
> database channel.  Check your connection dictionary, and ensure your
> database is correctly configured.
> >   at
> com.webobjects.eoaccess.EODatabaseContext

Re: Postgresql connection issue

[Þór Sigurðsson]

Have you given the user permission to connect to the database ?

Take a look at pg_hba.conf. Add a line for the user. If you _want_ the user to 
use a password, then the last column should be "password" or better yet "md5". 
If you want a trust-level connection, set it to "trust".

On 12.11.2013, at 09:58, Joe Kramer  wrote:

> Hi all,
>
> It has been some time since I have done any WebObjects development and I am 
> trying to resurrect an old project on a new machine. I went through all the 
> steps to get WebObjects/Wonder installed and I can run HelloWorld. The 
> problem appears to be with my Postgresql JDBC connection. I am running 
> Postgres93.app. I added the postgresql-9.3-1100.jdbc3.jar to my project's 
> Resources folder and added that jar to the build path. When I run and try to 
> bootstrap my database, I cannot connect and I get the following error. Is 
> there something that I missed in the setup process? Any help would be 
> appreciated.
>
> Thanks,
>
> Joe Kramer
>
> Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - An exception occurred 
> while trying to open a channel: N/A
> Nov 12 01:49:37 GALApplication[9199] INFO  er.transaction.adaptor.Exceptions  
> - Database Exception occured: java.lang.IllegalStateException: 
> _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext 
> com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open database 
> channel.  Check your connection dictionary, and ensure your database is 
> correctly configured.
> Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn 
> 'PostgresqlPlugIn' for JDBCAdaptor@1767199109
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.extensions.eof.ERXDatabaseContextDelegate  - GALDatabase: {plugin = 
> "PostgresqlPlugIn"; username = "jkramer"; driver = "org.postgresql.Driver"; 
> password = ""; URL = 
> "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Checking JDBC connection with 
> information {plugin = "PostgresqlPlugIn"; username = "jkramer"; driver = 
> "org.postgresql.Driver"; password = ""; URL = 
> "jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Trying to create JDBCAdaptor...
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Successfully created adaptor 
> com.webobjects.jdbcadaptor.JDBCAdaptor
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Trying to create plugin...
> Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn 
> 'PostgresqlPlugIn' for JDBCAdaptor@1616586953
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Created plugin 
> com.webobjects.jdbcadaptor.PostgresqlPlugIn
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Trying to load JDBC driver 
> org.postgresql.Driver...
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Successfully loaded JDBC driver 
> org.postgresql.Driver
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - JDBC driver and plugin are 
> loaded, trying to connect...
> Nov 12 01:49:37 GALApplication[9199] INFO  
> er.transaction.adaptor.ConnectionAnalyzer  - Error: Exception thrown while 
> connecting.
> Check exception message carefully.
> Nov 12 01:49:37 GALApplication[9199] ERROR 
> er.transaction.adaptor.ConnectionAnalyzer  - No connection.
> Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - A fatal exception 
> occurred: _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext 
> com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open database 
> channel.  Check your connection dictionary, and ensure your database is 
> correctly configured.
> [2013-11-12 1:49:37 PST]  java.lang.IllegalStateException: 
> _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext 
> com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open database 
> channel.  Check your connection dictionary, and ensure your database is 
> correctly configured.
>   at 
> com.webobjects.eoaccess.EODatabaseContext._obtainOpenChannel(EODatabaseContext.java:1967)
>   at 
> com.webobjects.eoaccess.EODatabaseContext._objectsWithFetchSpecificationEditingContext(EODatabaseContext.java:3054)
>   at 
> com.webobjects.eoaccess.EODatabaseContext.objectsWithFetchSpecification(EODatabaseContext.java:3195)
>   at 
> com.webobjects.eocontrol.EOObjectStoreCoordinator.objectsWithFetchSpecification(EOObjectStoreCoordinator.java:488)
>   at 
> com.webobjects.eocontrol.EOEditingContext.objectsWithFetchSpecification(EOEditingContext.java:4069)
>   at 
> er.extensions.eof.ERXEC.objectsWithFetchSpecification(ERXEC.java:1308)
>   at 
> com.webobjects.

Postgresql connection issue

[Joe Kramer]

Hi all,

It has been some time since I have done any WebObjects development and I am
trying to resurrect an old project on a new machine. I went through all the
steps to get WebObjects/Wonder installed and I can run HelloWorld. The
problem appears to be with my Postgresql JDBC connection. I am running
Postgres93.app. I added the postgresql-9.3-1100.jdbc3.jar to my project's
Resources folder and added that jar to the build path. When I run and try
to bootstrap my database, I cannot connect and I get the following error.
Is there something that I missed in the setup process? Any help would be
appreciated.

Thanks,

Joe Kramer

Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - An exception occurred
while trying to open a channel: N/A
Nov 12 01:49:37 GALApplication[9199] INFO
 er.transaction.adaptor.Exceptions  - Database Exception occured:
java.lang.IllegalStateException: _obtainOpenChannel --
com.webobjects.eoaccess.EODatabaseContext
com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open database
channel.  Check your connection dictionary, and ensure your database is
correctly configured.
Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn
'PostgresqlPlugIn' for JDBCAdaptor@1767199109
Nov 12 01:49:37 GALApplication[9199] INFO
 er.extensions.eof.ERXDatabaseContextDelegate  - GALDatabase: {plugin =
"PostgresqlPlugIn"; username = "jkramer"; driver = "org.postgresql.Driver";
password = ""; URL =
"jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
Nov 12 01:49:37 GALApplication[9199] INFO
 er.transaction.adaptor.ConnectionAnalyzer  - Checking JDBC connection with
information {plugin = "PostgresqlPlugIn"; username = "jkramer"; driver =
"org.postgresql.Driver"; password = ""; URL =
"jdbc:postgresql://localhost/gal_database?useBundledJdbcInfo=true"; }
Nov 12 01:49:37 GALApplication[9199] INFO
 er.transaction.adaptor.ConnectionAnalyzer  - Trying to create
JDBCAdaptor...
Nov 12 01:49:37 GALApplication[9199] INFO
 er.transaction.adaptor.ConnectionAnalyzer  - Successfully created adaptor
com.webobjects.jdbcadaptor.JDBCAdaptor
Nov 12 01:49:37 GALApplication[9199] INFO
 er.transaction.adaptor.ConnectionAnalyzer  - Trying to create plugin...
Nov 12 01:49:37 GALApplication[9199] DEBUG NSLog  - Using JDBCPlugIn
'PostgresqlPlugIn' for JDBCAdaptor@1616586953
Nov 12 01:49:37 GALApplication[9199] INFO
 er.transaction.adaptor.ConnectionAnalyzer  - Created plugin
com.webobjects.jdbcadaptor.PostgresqlPlugIn
Nov 12 01:49:37 GALApplication[9199] INFO
 er.transaction.adaptor.ConnectionAnalyzer  - Trying to load JDBC driver
org.postgresql.Driver...
Nov 12 01:49:37 GALApplication[9199] INFO
 er.transaction.adaptor.ConnectionAnalyzer  - Successfully loaded JDBC
driver org.postgresql.Driver
Nov 12 01:49:37 GALApplication[9199] INFO
 er.transaction.adaptor.ConnectionAnalyzer  - JDBC driver and plugin are
loaded, trying to connect...
Nov 12 01:49:37 GALApplication[9199] INFO
 er.transaction.adaptor.ConnectionAnalyzer  - Error: Exception thrown while
connecting.
Check exception message carefully.
Nov 12 01:49:37 GALApplication[9199] ERROR
er.transaction.adaptor.ConnectionAnalyzer  - No connection.
Nov 12 01:49:37 GALApplication[9199] WARN  NSLog  - A fatal exception
occurred: _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext
com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open database
channel.  Check your connection dictionary, and ensure your database is
correctly configured.
[2013-11-12 1:49:37 PST]  java.lang.IllegalStateException:
_obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext
com.webobjects.eoaccess.EODatabaseContext@105585dc: failed to open database
channel.  Check your connection dictionary, and ensure your database is
correctly configured.
 at
com.webobjects.eoaccess.EODatabaseContext._obtainOpenChannel(EODatabaseContext.java:1967)
at
com.webobjects.eoaccess.EODatabaseContext._objectsWithFetchSpecificationEditingContext(EODatabaseContext.java:3054)
 at
com.webobjects.eoaccess.EODatabaseContext.objectsWithFetchSpecification(EODatabaseContext.java:3195)
at
com.webobjects.eocontrol.EOObjectStoreCoordinator.objectsWithFetchSpecification(EOObjectStoreCoordinator.java:488)
 at
com.webobjects.eocontrol.EOEditingContext.objectsWithFetchSpecification(EOEditingContext.java:4069)
at er.extensions.eof.ERXEC.objectsWithFetchSpecification(ERXEC.java:1308)
 at
com.webobjects.eocontrol.EOEditingContext.objectsWithFetchSpecification(EOEditingContext.java:)
at
er.extensions.eof.ERXFetchSpecification.fetchObjects(ERXFetchSpecification.java:155)
 at org.luth.eo._Product.fetchProducts(_Product.java:207)
at org.luth.eo._Product.fetchAllProducts(_Product.java:201)
 at org.luth.eo._Product.fetchAllProducts(_Product.java:197)
at org.luth.Application.migrateDbaseDB(Application.java:72)
 at org.luth.Application.(Application.java:65)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at
sun.reflect.NativeConstructorAccessorImpl.newInstance(N