Hi Thomas,
No there are no other clients involved, however I am using multiple statements
in the same transactions. All connections are made from the application running
inside the same VM. There are no remote connections.
Thanks for taking a look. I am a little confused myself as this only seems to
happen with recent versions of the driver.
Kind regards
Alex
On 29/03/2012, at 03:07 , Thomas Mueller wrote:
> Hi,
>
> I don't know what the problem could be. There are two thread on the
> server side that are waiting for a client, here:
>
> private void process() throws IOException {
> int operation = transfer.readInt(); <<== server
> switch (operation) {
>
> case SessionRemote.SESSION_PREPARE: {
> int id = transfer.readInt();
> String sql = transfer.readString(); <<== server
>
> and there is only one client, here:
>
> at org.h2.value.Transfer.readInt(Transfer.java:147)
> at org.h2.engine.SessionRemote.done(SessionRemote.java:558)
> at org.h2.command.CommandRemote.executeQuery(CommandRemote.java:151)
> at org.h2.jdbc.JdbcConnection.getQueryTimeout(JdbcConn
>
> This doesn't make much sense. Is there another client, running in a
> different process?
>
> I don't know why this would hang.
>
> Regards,
> Thomas
>
>
> On Wed, Mar 28, 2012 at 8:07 PM, Alexander Hartner
> <lostinspace2...@googlemail.com> wrote:
>> Hi Thomas,
>>
>> Were you able to take a look at this issue ?
>>
>> Kind regards
>> Alex
>>
>> Begin forwarded message:
>>
>> From: Alexander Hartner <a...@j2anywhere.com>
>> Subject: Fwd: Query hung / stuck with Version 1.3.164 (2012-02-03)
>> Date: 21 March 2012 00:52:26 AWST
>> To: Thomas Mueller <thomas.tom.muel...@gmail.com>
>>
>> Hi Thomas
>>
>> I was able to reproduce this problem on both OSX and Linux running JDK
>> 1.6.0.31
>>
>> Alex
>>
>> Begin forwarded message:
>>
>> From: Alexander Hartner <lostinspace2...@gmail.com>
>> Subject: Re: Query hung / stuck with Version 1.3.164 (2012-02-03)
>> Date: 21 March 2012 00:44:55 AWST
>> To: Thomas Mueller <thomas.tom.muel...@gmail.com>
>>
>> Hi Thomas,
>>
>> Attached please find the thread dump. H2 is run embedded tcp server inside
>> tomcat in a single JVM with the application.
>>
>> The application uses tcp to connect to the server on the following URL :
>>
>> jdbc:h2:tcp://localhost:28081/AddressBookDB;LOCK_TIMEOUT=60000
>>
>> I have also run into the same problem using the latest build.
>>
>> Looking at the thread dump I didn't see anything obvious. Most threads were
>> in a runnable state.
>>
>> Please let me know if there is anything else I can provide you to resolve
>> this issue.
>>
>>
>>
>>
>>
>>
>> On 20/03/2012, at 03:58 , Thomas Mueller wrote:
>>
>> Hi,
>>
>>
>> I replied to the Google Group -
>>
>> https://groups.google.com/forum/?fromgroups#!searchin/h2-database/Query$20hung/h2-database/zMQOdTxbyVk/9ntD_4YyIQEJ
>>
>>
>> Hi,
>>
>>
>> I don't know what it could be. What version of H2 do you use on the
>>
>> server side? New clients should be compatible with old servers (and
>>
>> vice versa) but maybe there is a bug somewhere... If this is not the
>>
>> problem, what does the stack trace look like on the server (a full
>>
>> thread dump, created using kill -QUIT or jps -l / jstack -l <pid>)?
>>
>>
>> Regards,
>>
>>
>>
>>
>>
>> On Sun, Mar 18, 2012 at 3:36 PM, Alexander Hartner
>>
>> <lostinspace2...@googlemail.com> wrote:
>>
>> Hi Thomas,
>>
>>
>> Sorry to email you directly. I haven't had any response on the forum and
>>
>> this seems like a major issue I ran into. It only seem to happen with the
>>
>> latest version.
>>
>>
>> Kind regards
>>
>> Alex
>>
>>
>>
>> Begin forwarded message:
>>
>>
>> From: Alexander Hartner <lostinspace2...@googlemail.com>
>>
>> Subject: Query hung / stuck with Version 1.3.164 (2012-02-03)
>>
>> Date: 8 March 2012 13:22:07 AWST
>>
>> To: h2-database@googlegroups.com
>>
>>
>> In my application one (possibly more) query never returns a result. This
>>
>> happened since I upgraded to the latest available release. I tried to debug
>>
>> it, and got the following stack trace. I switched back to an older release
>>
>> and did not encounter this issue.
>>
>>
>> java.net.SocketInputStream.socketRead0(SocketInputStream.java)
>>
>> java.net.SocketInputStream.read(SocketInputStream.java:129)
>>
>> java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>>
>> java.io.BufferedInputStream.read(BufferedInputStream.java:237)
>>
>> java.io.DataInputStream.readInt(DataInputStream.java:370)
>>
>> org.h2.value.Transfer.readInt(Transfer.java:147)
>>
>> org.h2.engine.SessionRemote.done(SessionRemote.java:558)
>>
>> org.h2.command.CommandRemote.executeQuery(CommandRemote.java:151)
>>
>> org.h2.jdbc.JdbcConnection.getQueryTimeout(JdbcConnection.java:719)
>>
>> org.h2.jdbc.JdbcStatement.getQueryTimeout(JdbcStatement.java:552)
>>
>> org.apache.tomcat.dbcp.dbcp.DelegatingStatement.getQueryTimeout(DelegatingStatement.java:246)
>>
>> org.apache.tomcat.dbcp.dbcp.DelegatingStatement.getQueryTimeout(DelegatingStatement.java:246)
>>
>> org.hibernate.jdbc.AbstractBatcher.closeQueryStatement(AbstractBatcher.java:299)
>>
>> org.hibernate.jdbc.AbstractBatcher.closeQueryStatement(AbstractBatcher.java:234)
>>
>> org.hibernate.loader.Loader.doQuery(Loader.java:749)
>>
>> org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259)
>>
>> org.hibernate.loader.Loader.doList(Loader.java:2232)
>>
>> org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2129)
>>
>> org.hibernate.loader.Loader.list(Loader.java:2124)
>>
>> org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:401)
>>
>> org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:363)
>>
>> org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196)
>>
>> org.hibernate.impl.SessionImpl.list(SessionImpl.java:1149)
>>
>> org.hibernate.impl.QueryImpl.list(QueryImpl.java:102)
>>
>> org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:67)
>>
>> com.abc.SyncService.fetchRecords(SyncService.java:217)
>>
>>
>> Feel free to contact me if you require any further details on this.
>>
>>
>> Kind regards
>>
>> Alex
>>
>>
>>
>>
>>
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups "H2
> Database" group.
> To post to this group, send email to h2-database@googlegroups.com.
> To unsubscribe from this group, send email to
> h2-database+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/h2-database?hl=en.
>
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to h2-database@googlegroups.com.
To unsubscribe from this group, send email to
h2-database+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
