dbTalk Databases Forums  

non-blocking socket operation could not be completed immediately

comp.databases.postgresql comp.databases.postgresql


Discuss non-blocking socket operation could not be completed immediately in the comp.databases.postgresql forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Yourdon
 
Posts: n/a

Default non-blocking socket operation could not be completed immediately - 12-30-2006 , 03:07 PM






Hello,

I experience unstable behaviour of PostgreSQL 8.1, running a Java data
import program using JDBC. It is showing the following message in the log
file: 'A non-blocking socket operation could not be completed immediately'.
The corresponding Java exception shown is: PSQLException I/O error
QueryExecutorImpl.execute.

The error message is still occurring frequently. I can replicate this error,
by having two instances of the java program running. Or, by having one java
program running and running a big select * query in the pgAdmin III SQL
window. In the pgAdmin III SQL window additional error messages show: could
not receive data from server: No buffer space available. Although at the
same time in the PostgreSQL log the non-blocking socket operation preceeds
this error.

I have removed all anti-virus (avast) and firewall software (sygate),
following suggestions from other similar postings.

I am running under Windows 2000 Server service pack 4, PostgreSQL 8.1, Java
1.5 and postgres-8.1.08.jdbc3.jar. JBoss 4.05 is running and uses the driver
org.postgresql.jdbc3.Jdbc3PoolingDataSource. The Java import program uses
the driver connectionpool org.postgresql.Driver. I used the standard
installation of PostgreSQL and have not configured database options. In
JBoss sometimes the error shows:
javax.ejb.EJBTransactionRolledbackException:
javax.persistence.PersistenceException:
org.hibernate.exception.JDBCConnectionException: could not execute query.

It seems to me, that although version 8 is supporting Windows, it is not
stable enough and not yet suitable for a production environment.

I am planning to move to a Linux environment within some time, however I
want to have a stable environment now.

Any ideas ??

I hope you can help me.

Marcel



Reply With Quote
  #2  
Old   
Laurenz Albe
 
Posts: n/a

Default Re: non-blocking socket operation could not be completed immediately - 01-03-2007 , 05:53 AM






Yourdon <marcelvanvelzen (AT) wanadoo (DOT) nl> wrote:
Quote:
I experience unstable behaviour of PostgreSQL 8.1, running a Java data
import program using JDBC. It is showing the following message in the log
file: 'A non-blocking socket operation could not be completed immediately'.
The corresponding Java exception shown is: PSQLException I/O error
QueryExecutorImpl.execute.

The error message is still occurring frequently. I can replicate this error,
by having two instances of the java program running. Or, by having one java
program running and running a big select * query in the pgAdmin III SQL
window. In the pgAdmin III SQL window additional error messages show: could
not receive data from server: No buffer space available. Although at the
same time in the PostgreSQL log the non-blocking socket operation preceeds
this error.

I have removed all anti-virus (avast) and firewall software (sygate),
following suggestions from other similar postings.

I am running under Windows 2000 Server service pack 4, PostgreSQL 8.1, Java
1.5 and postgres-8.1.08.jdbc3.jar. JBoss 4.05 is running and uses the driver
org.postgresql.jdbc3.Jdbc3PoolingDataSource. The Java import program uses
the driver connectionpool org.postgresql.Driver. I used the standard
installation of PostgreSQL and have not configured database options. In
JBoss sometimes the error shows:
javax.ejb.EJBTransactionRolledbackException:
javax.persistence.PersistenceException:
org.hibernate.exception.JDBCConnectionException: could not execute query.

It seems to me, that although version 8 is supporting Windows, it is not
stable enough and not yet suitable for a production environment.

I am planning to move to a Linux environment within some time, however I
want to have a stable environment now.
Since I know next to nothing about Windows, I suggest writing to
the pgsql-hackers mailing list. They can maybe help you.

It seems to be a problem with the Windows port.

Yours,
Laurenz Albe


Reply With Quote
  #3  
Old   
Yourdon
 
Posts: n/a

Default Re: non-blocking socket operation could not be completed immediately - 01-03-2007 , 12:57 PM



Thanks for your answer, however I have decided to install tomorrow Linux on
my development machine. Better environment I think for these kind of things.

"Laurenz Albe" <invite (AT) spam (DOT) to.invalid> schreef in bericht
news:1167821578.435990 (AT) proxy (DOT) dienste.wien.at...
Quote:
Yourdon <marcelvanvelzen (AT) wanadoo (DOT) nl> wrote:
I experience unstable behaviour of PostgreSQL 8.1, running a Java data
import program using JDBC. It is showing the following message in the log
file: 'A non-blocking socket operation could not be completed
immediately'.
The corresponding Java exception shown is: PSQLException I/O error
QueryExecutorImpl.execute.

The error message is still occurring frequently. I can replicate this
error,
by having two instances of the java program running. Or, by having one
java
program running and running a big select * query in the pgAdmin III SQL
window. In the pgAdmin III SQL window additional error messages show:
could
not receive data from server: No buffer space available. Although at the
same time in the PostgreSQL log the non-blocking socket operation
preceeds
this error.

I have removed all anti-virus (avast) and firewall software (sygate),
following suggestions from other similar postings.

I am running under Windows 2000 Server service pack 4, PostgreSQL 8.1,
Java
1.5 and postgres-8.1.08.jdbc3.jar. JBoss 4.05 is running and uses the
driver
org.postgresql.jdbc3.Jdbc3PoolingDataSource. The Java import program uses
the driver connectionpool org.postgresql.Driver. I used the standard
installation of PostgreSQL and have not configured database options. In
JBoss sometimes the error shows:
javax.ejb.EJBTransactionRolledbackException:
javax.persistence.PersistenceException:
org.hibernate.exception.JDBCConnectionException: could not execute query.

It seems to me, that although version 8 is supporting Windows, it is not
stable enough and not yet suitable for a production environment.

I am planning to move to a Linux environment within some time, however I
want to have a stable environment now.

Since I know next to nothing about Windows, I suggest writing to
the pgsql-hackers mailing list. They can maybe help you.

It seems to be a problem with the Windows port.

Yours,
Laurenz Albe



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.