Skip site navigation (1) Skip section navigation (2)

Re: thread hang on execute call

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Pavan Kumar <pavan(at)netcore(dot)co(dot)in>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: thread hang on execute call
Date: 2006-04-06 12:07:14
Message-ID: F15E259F-E167-4A88-A10B-36615450A4FD@fastcrypt.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
Pavan,

I'd have to see the rest of the code to be helpful here. It certainly  
sounds like the driver is getting confused.

Candidly though the driver is used by probably 1000's of people  
without this happening, so I'd be hard pressed to believe it was the  
driver.

I'm certainly open to being proven wrong though.

Dave
On 6-Apr-06, at 7:31 AM, Pavan Kumar wrote:

> hi
>  again i stuck to same problem.
> i restarted my program. After 36 hour all thread got stuck with
> postgresql call.
> both java thread and  postgresql are stuck on recv call....i couldn't
> understand whats problem.why did it happen.
> threads perform database intensive operation. there more then 60000
> record in table.
> could you tell me if i need to do any performance tuning things. like
> increasing cache size.
> each postgresql process taking 21-23 MB of memory.
>
>
> here is the stack trace of postgresql process.
>
> 0  0x003437a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> #1  0x00424451 in recv () from /lib/tls/libc.so.6
> #2  0x08145aae in secure_read ()
> #3  0x0814c062 in pq_recvbuf ()
> #4  0x0814c121 in pq_getbyte ()
> #5  0x081ad5fc in PostgresMain ()
> #6  0x0818765d in ServerLoop ()
> #7  0x0818904f in PostmasterMain ()
> #8  0x0814dd18 in main ()
>
>
>
>
>
> following is the stack trace of one of java thread.
>
> Thread 618: (state = IN_NATIVE)
>  - java.net.SocketInputStream.socketRead0(java.io.FileDescriptor,
> byte[], int, int, int) @bci=0 (Co
> mpiled frame; information may be imprecise)
>  - java.net.SocketInputStream.read(byte[], int, int) @bci=84, line=129
> (Compiled frame)
>  - java.io.BufferedInputStream.fill() @bci=175, line=218 (Compiled
> frame)
>  - java.io.BufferedInputStream.read() @bci=12, line=235 (Compiled  
> frame)
>  - org.postgresql.core.PGStream.ReceiveChar() @bci=4, line=254  
> (Compiled
> frame)
>  -
> org.postgresql.core.v3.QueryExecutorImpl.execute 
> (org.postgresql.core.Query, org.postgresql.core.
> ParameterList, org.postgresql.core.ResultHandler, int, int, int)
> @bci=129, line=188 (Interpreted fr
> ame)
>  -
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute 
> (org.postgresql.core.Query, org.postgresql.co
> re.ParameterList, int) @bci=199, line=430 (Interpreted frame)
>  - org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(int)
> @bci=14, line=346 (Compiled fr
> ame)
>  - org.postgresql.jdbc2.AbstractJdbc2Statement.execute() @bci=2,
> line=339 (Interpreted frame)
>  - org.apache.commons.dbcp.DelegatingPreparedStatement.execute()  
> @bci=8,
> line=168 (Interpreted fram
> e)
>
> On Tue, 2006-04-04 at 09:40 -0400, Tom Lane wrote:
>> Dave Cramer <pg(at)fastcrypt(dot)com> writes:
>>> Is it possible the query does not return ? Try adding a large
>>> statement timeout to the server.
>>
>> The stack traces say that the client and server are each waiting for
>> input from the other ... so somebody's confused about something.
>>
>> 			regards, tom lane
>>
>> ---------------------------(end of  
>> broadcast)---------------------------
>> TIP 4: Have you searched our list archives?
>>
>>                http://archives.postgresql.org
>
>
> ---------------------------------------------------------------------- 
> --
> Netcore Solutions Pvt. Ltd.
> Website:  http://www.netcore.co.in
> Spamtraps: http://cleanmail.netcore.co.in/directory.html
>
> Support FAQ : http://support.netcore.co.in/
>
> This e-mail contains confidential and/or privileged information. If
>   you are not the intended recipient (or have received this e-mail in
>   error)  please notify the sender immediately and delete this e- 
> mail. Any
>   unauthorized copying, disclosure, use or distribution of the  
> material in
>   this e-mail is strictly forbidden.
>
> ---------------------------------------------------------------------- 
> --
>
>


In response to

pgsql-jdbc by date

Next:From: João Paulo RibeiroDate: 2006-04-06 12:16:22
Subject: Re: thread hang on execute call
Previous:From: Oliver JowettDate: 2006-04-06 11:57:31
Subject: Re: thread hang on execute call

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group