If you’re using BizTalk to connect to an Oracle database via a WCF-Custom port, you might encounter a suspended message with this error. It’s a simple Oracle timeout error, but it’s not always obvious where/how to extend the timeout.
ORA-01013: user requested cancel of current operation
The error simply means that BizTalk gave up waiting for a response from the database. But sometimes large databases are slow, and you might want to extend the timeout.
First, identify the port you need. You should have a suspended Messaging instance with this error, and its Service Name will match the send port name.
If you go to the offending Send Port and hit the Configure button, you can swing by the Binding tab to set the connection settings. So far, so easy…
The tricky part is that you have 4 timeouts specified here (at the bottom), and it’s not always clear which one you need.
Long story short, it’s the sendTimeout (hightlighted) which seems to relate to this error. It’s not necessarily the one you’d think, but I tested it extensively (will explain how in a future post), and so far it’s the only one that’s had any effect whenever I’ve encountered this problem.
So there you go, if you want to stop seeing that error when your database is feeling a little slow, extend the sendTimeout on the port.