Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebSphere Application Server Access PostgreSQL throuth JDBC #272

Closed
mushixun opened this issue Apr 3, 2015 · 2 comments
Closed

WebSphere Application Server Access PostgreSQL throuth JDBC #272

mushixun opened this issue Apr 3, 2015 · 2 comments

Comments

@mushixun
Copy link

mushixun commented Apr 3, 2015

My Application is deploy on WebSphere Application Server ,config a JDBC Datasource pool to connect PostgreSQL ,JDBC Version is 9.3,PostgreSQL version is 9.3,my problem is my app query a table(using preparedstatement) that contain TIMESTAMP type,the first 4 times access is OK,later access is fail,if I set binaryTransfer=false,All access is OK.

@sehrope
Copy link
Member

sehrope commented Apr 3, 2015

Please provide the actual error message you're receiving and if possible the stack trace of the error. If you can reproduce the error with a self-contained example that would be even more helpful.

Just guessing based on the "...the first 4 times..." part of the comment, I'd say this is related to the prepared statement being converted to a server side prepared statement. It might be effecting the way the timestamp parameter for your statement is being sent/bound.

The driver switches to (more efficient) server side prepared statements after 4 executions of the same Java prepared statement. You can read more about it here.

@vlsi
Copy link
Member

vlsi commented Aug 12, 2016

I think timestamp handling was fixed in several commits, so it should be just fine in 9.4.1209+

@vlsi vlsi closed this as completed Aug 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants