I'm using Postgres 7.1rc3 with 'the most recent Orion build' ;)
I'm going to upgrade both overnight to see if it makes any difference, but I
think what I really need is a tool to see:
a) the threads Orion is running and what method they're stuck in (JPDA
should do this)
b) the current connections to postgres and the query that's being run - any
idea how to get this info?
Heavy load is very heavy, real life load. (if that helps)
-mike
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Adam Cassar
> Sent: Thursday, April 19, 2001 12:24 PM
> To: Orion-Interest
> Subject: Re: PostgresJDBC Driver w/ Orion under load
>
>
> What version's r u using?
>
> We use postgres + orion here with no problems.
>
> What do you classify as 'heavy load'? Is it testing or real life load?
>
> On 19 Apr 2001 10:27:02 +1000, Mike Cannon-Brookes wrote:
> > Has anyone used Postgres + JDBC + Orion under heavy load?
> >
> > We're having a problem on one of our production machines that on some
> > occasions under heavy load Postgres JDBC connections seem to be dying /
> > locking up as do Orion threads and we're not sure where to
> start looking.
> >
> > Has anyone used this combo and has experience with this sort of thing?
> >
> > Here's an example trace:
> >
> > An I/O error occured while reading from backend - Exception:
> > java.net.SocketException: Connection reset by peer: Connection
> reset by peer
> > Stack Trace:
> > java.net.SocketException: Connection reset by peer: Connection
> reset by peer
> > at java.net.SocketInputStream.socketRead(Native Method)
> > at java.net.SocketInputStream.read(SocketInputStream.java:86)
> > at
> java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
> > at
> java.io.BufferedInputStream.read(BufferedInputStream.java:204)
> > at org.postgresql.PG_Stream.ReceiveChar(PG_Stream.java:181)
> > at org.postgresql.Connection.openConnection(Connection.java:160)
> > at org.postgresql.Driver.connect(Driver.java:122)
> >
> > or
> >
> > An I/O error occured while reading from backend - Exception:
> > java.net.SocketException: Broken pipe: Broken pipe
> > Stack Trace:
> > java.net.SocketException: Broken pipe: Broken pipe
> > at java.net.SocketInputStream.socketRead(Native Method)
> > at java.net.SocketInputStream.read(SocketInputStream.java:86)
> > at
> java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
> > at
> java.io.BufferedInputStream.read(BufferedInputStream.java:204)
> > at org.postgresql.PG_Stream.ReceiveChar(PG_Stream.java:181)
> > at org.postgresql.Connection.openConnection(Connection.java:160)
> > at org.postgresql.Driver.connect(Driver.java:122)
> > ...
> > at org.postgresql.PG_Stream.ReceiveChar(PG_Stream.java:184)
> > at org.postgresql.Connection.openConnection(Connection.java:160)
> > at org.postgresql.Driver.connect(Driver.java:122)
> >
> > any ideas where to start looking?
> >
> > -mike
> >
> >
> >
> >
>
>
>
> --
>
> Adam Cassar
> Technical Development Manager
> ___________________________________________
> NetRegistry http://www.netregistry.au.com
> Tel: +61 2 9641 8609 | Fax: +61 2 9699 6088
> PO Box 270 Broadway NSW 2007 Australia
>
>
>
