On Friday 18 March 2005 5:31 am, ganapatiram wrote:
> Hi Mr. Steeve,
>
> I really thank for your detailed reply. I worked on the
> four points what you mentioned. I am sure it worked. But when i
> went for testing i saw a different error this time. It says:
>
> org.jboss.util.NestedSQLE
I had the same problem a few weeks ago.
Was happening that our developers using Tomcat, were using connection
pools, and stoping and restarting their aplications which causes to
leave these connection opened and opening some new.
Look in the servlet engine (or what they use) for the number of
c
>I work with postgresql 8.0 version. I have a team of 14
> developers. When all the team connects the DB i see this error very
> very frequently which is a severe problem for me and team all the
> day. The error is:
>
> Please report this exception: java.sql.SQLException: FATAL: sorry,
Well, first of all, max_connections can only be set at server start.
Are you restarting postgres when you do "trial and error changes"?
Secondly, 5 users can still manage to make multiple connections. You
can use ps to see how many connections are active at any given time.
http://www.postgresql
Hi Experts,
I work with
postgresql 8.0 version. I have a team of 14 developers. When all the team
connects the DB i see this error very very frequently which is a severe problem
for me and team all the day. The error is:
Please report this exception: java.sql.SQLException: FAT
