Null pointer in connection.close

Register Lost your login? The pointer is set to NULL outside of mutexed zone, so if close and dealloc follow each other very shortly application crashes. Please see the attached patch. So why is there a mutex again each other anyway? We are getting a crash, which is only possible if dealloc is called where close is not yet done. Is this possible? Characters Remaining: Please provide feedback! Printable View.

Article Number Has only been reported with the DB2 driver. Steps to Reproduce. Clarifying Information. Error Message java. Defect Number. Are you trying to connect over SSL? See I've seen this issue before a long time ago though I cannot remember what it was. Could you post a larger code sample? I haven't had a chance to look at the code in detail within the module you're using. At least that's where I would check first. Is there any particular place where the queries stop working or does it just randomly stop within some block of executing the same query n times?

Perhaps heroku's using some addon to tell postgres to disconnect idle connections after a time? I think it could help to expose the underlying stream's end event to the client so 'scheduled' disconnects could be handled though it's hard to properly patch this without a little code snippet to reproduce.

Is there a way you can reproduce this locally on your machine without using the hater module? I really like to have a dependency free test for things if possible or at least a way to accurately reproduce them. This works fine in the beginning, but when the timeout reaches 32s I get an error. The attempt to reconnect causes a segfault. I know that 61 suggests the use of pauseDrain and resumeDrain , but I haven't figured out how to modify this example so that errors aren't raised.

By turning on logging I noticed that the connection is attempted released twice. Active 6 years, 9 months ago. Viewed 3k times.

BlackHatSamurai How on earth do you format your code? Do you just insert random whitespace for fun? Also the correct way to register a driver is Class. Class" , it is the driver's responsibility to register itself at static init. Your conn object is null. What do you expect? Add a comment.