OCI_GetTimeout() always returns 0 since v4.7.0 about ocilib HOT 11 CLOSED

Hi,

I found the issue, a bug introduced few versions ago :(
I will fix this asap in a v4.7.6 branch.

Regards,

Vincent

from ocilib.

Hi,

v4.7.6 released.

I am waiting for feedback from Oracle about the receive timeout retrieval that does not work with 21C.

Regards,

Vincent

from ocilib.

Hi,

can you report the return values of the following calls ?

Environment::GetCompileMajorVersion()
Environment::GetRuntimeMajorVersion()
con.GetServerMajorVersion()
con.GetServerMinorVersion()
con.GetServerRevisionVersion()
con.GetVersion()

Regards,

Vincent

from ocilib.

And also :

Environment::GetCompileVersion()
Environment::GetRuntimeVersion()

from ocilib.

Hi
here is the result:

GetCompileMajorVersion: 18
GetRuntimeMajorVersion: 18
GetCompileVersion: 180100
GetRuntimeVersion: 180300
con.GetServerMajorVersion: 19
con.GetServerMinorVersion: 11
con.GetServerRevisionVersion: 0
con.GetVersion: 180300

from ocilib.

I fixed my bug and I was testing the different timeout types (send, receive and call)
It works now with send and call types (oracle returns the correct value previously set) but for receive type the oracle client does not fill input the variable content that should receive the value ....
I have to determine if the value for receive type is taken into account when set and if its just the oracle client getter call for this attribute that has a bug. In this case, I can store theses values in the connection object instead of relying solely on the oracle client.
.
I will reach out to this weird behavior by with 21c client to oracle folks.

from ocilib.

regression introduced in v4.7.0
Fix will be committed this evening in v4.7.6 branch
Still investigating weird OCI client behavior when getting the receive timeout

from ocilib.

Did some more testing and it seems that there is an issue in the Oracle client (at least, the one I am using windows 64bit 21.3)

from ocilib.

Thank you Vincent, I appreciate your efforts.

from ocilib.

@inPhraZ If you initialize OCILIB in threaded mode ( Environment::Initialize(Environment::Threaded) ), then retrieving receive timeout works.
It seems that OCI client returns the receive timeout only if it has been initialized in threaded mode, while for other timeouts, it makes no difference.
I have send some pure OCI test case demoing the issue to Oracle. So, for me, the issue is still on the OCI client side.
I will update this issue once I get feedback from Oracle.

Regards,

Vincent

from ocilib.

If you initialize OCILIB in threaded mode ( Environment::Initialize(Environment::Threaded) ), then retrieving receive timeout works.

yes. both send and receive are working well in v4.7.6. (we did test the TimeoutCall and it also works in OCI_18_1)
but it does not apply on previous branches, cause we have been initialized with Environment::Initialize(Environment::Default | Environment::Threaded); since v4.7.4.

from ocilib.