Thread: What does this mean?
What does it mean when your process is stuck in the following: "AWT-EventQueue-0" prio=10 tid=0x09821400 nid=0x1370 runnable [0xb51b5000..0xb51b70b0] java.lang.Thread.State: RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) - locked <0x8160ffa8> (a java.io.BufferedInputStream) at org.postgresql.core.PGStream.ReceiveChar(PGStream.java:256) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1163) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:188) - locked <0x8160fd50> (a org.postgresql.core.v3.QueryExecutorImpl) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:354) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:258) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.postgresql.ds.common.PooledConnectionImpl$StatementHandler.invoke(PooledConnectionImpl.java:474) at $Proxy1.executeQuery(Unknown Source) at com.kodak.ei.assetmanager.database.DBVenueID.getVenueID(DBVenueID.java:153) - locked <0x90309d40> (a java.lang.Class for com.kodak.ei.assetmanager.database.DBVenueID) at com.kodak.ei.assetmanager.database.DBPerformance.parseResultSet(DBPerformance.java:161) at com.kodak.ei.assetmanager.database.DBPerformance.getPerformancesForVenue(DBPerformance.java:346) - locked <0x90333040> (a java.lang.Class for com.kodak.ei.assetmanager.database.DBPerformance) at kodak.dcms.DBShowList.getScheduleDay(DBShowList.java:204) at kodak.dcms.DBScreenDay.reloadFromDB(DBScreenDay.java:1202) - locked <0x80140178> (a kodak.dcms.DBScreenDay) at kodak.dcms.DBScreenDay.<init>(DBScreenDay.java:118) at kodak.dcms.DBTheatreDayCache.get(DBTheatreDayCache.java:139) at kodak.cms.scheduler.TheatreDay.getDBScreenDay(TheatreDay.java:1713) at kodak.cms.scheduler.ScreenDay.loadSchedule(ScreenDay.java:308) at kodak.cms.scheduler.TheatreDay.loadSchedule(TheatreDay.java:716) at kodak.cms.scheduler.TheatreDay.dateChanged(TheatreDay.java:685) at kodak.cms.scheduler.TheatreDay$12.propertyChange(TheatreDay.java:1180) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339) -- House: "Because it doesn't hurt here. Because I don't want to be in pain, I don't want to be miserable." Amber: "Well...You can't always get what you want."
Paul Tomblin wrote: > What does it mean when your process is stuck in the following: It's waiting for a query result. -O
On Thu, Jul 10, 2008 at 9:50 AM, Oliver Jowett <oliver@opencloud.com> wrote: > Paul Tomblin wrote: >> >> What does it mean when your process is stuck in the following: > > It's waiting for a query result. Yeah, but this is a very small query on a very small table. The query in question is "SELECT " + columns + "FROM venue " + "WHERE venueid = ?"); where the table "venue" has 15 rows in it, and it's indexed on venueid. Hmmm. Looks like something isn't getting committed before the nightly vacuum. -- House: "Because it doesn't hurt here. Because I don't want to be in pain, I don't want to be miserable." Amber: "Well...You can't always get what you want."
Paul Tomblin wrote: > >> What does it mean when your process is stuck in the following: > > > > It's waiting for a query result. > > Yeah, but this is a very small query on a very small table. The query > in question is > > "SELECT " + columns + > "FROM venue " + > "WHERE venueid = ?"); > > where the table "venue" has 15 rows in it, and it's indexed > on venueid. > > Hmmm. Looks like something isn't getting committed before > the nightly vacuum. I'd trace on the server to see what's going on. What happens if you run the query in psql? If you thing that there is a problem with VACUUM, try to run "VACUUM VERBOSE venue" in psql and see what it says. Yours, Laurenz Albe