segmentation violation

[rolson-alister]

Hi!

In my application, the same request is executed in a loop within the same connection.

After some time, he panics "invalid memory address".

The request code and the error itself are attached below.

Do you have any ideas or tips where to look, and what could be wrong?

[rolson-alister]

@sijms

I have created a repository with my code in which you can view a part of my technology that I developed to reconnect to Oracle, based on your library.

https://github.com/rolson-alister/go-ora-reconnect-example

The essence of my application is that it works 24/7 and constantly communicates with Oracle. And at some point, during the next request, a random error may occur, including about a suddenly closed connection.

In order not to constantly restart my application when such errors occur, I have developed a small functionality that allows you to reconnect to Oracle on the fly.

But now I sometimes have panics, the cause of which I cannot find out.

In my repository, you can fully run and test my development. In the "possible_errors" folder, there are screenshots of errors, both from my "production" application and from the test one, which you can run for debag.

Perhaps you will understand the reason and tell me how I can better refine my idea.

Thanks!
I am very much waiting for your answer.

[rolson-alister]

Figured it out on my own. The problem was multithreading. There was an appeal from different threads to a single connection instance. I modified my code with the help of a synchronization package and everything started working fine.