The workaround really does work around the problem. I have changed all my queues to dynamic allocation and deallocation, and so far I haven't encountered any problems any more. I'll have to put in another 8 queues over the next couple of days. If anything new comes up, I'll let you know...
Got another problem now. To give you some more background let me say that the queues I am using are accessed through components in a data module.
What happens is that I open a connection to a remote database and start dequeueing objects waiting in a queue (if any). TOracleSession.NullValue is...
Not meaning to be impolite, I still have a couple of questions:
- do you have any plans for a fix for the problem with dequeueing messages when having TOracleSession.NullValue set to nvNull?
- do you have any plans for a fix for the problem with "TOracleObject: Invalid handle"?
Any answers...
The value for the TOracleSession.NullValue property is nvNull. I just went and changed it to nvUnAssigned in order to try out what happens then. Things started to work immediately. However, the "Invalid handle" exception on closing is still there. :confused:
By the way, I don't recall having...
I have an object queue which works fine with PL/SQL code on Oracle 9.2.0.5 both ways (enqueue and dequeue). Connecting to the same schema as before using Delphi 6 and DOA 4.0.6.2 and attempting a Dequeue from the Queue, I get an EVariantTypeCastError for a conversion from null to integer...