VirtualXacute Connector to IP21OLEDB remote instance fails

[Former Member]

The following error is issued:

"SQL or RefineryXacute Failed: Site: 9 Error has occurred while processing data stream org.w3c.www.protocol.http.HttpException: Unable to contact target server xxxxx.com:50000 after 1 tries".

This comes each time after 301 seconds, so looks like a timeout. The processing on the remote target server takes more then 400 seconds and if I shorten the processing by reducing the rowcount number, it works well. I increased all connection timeouts to more then 600 secs - on the IP21OLEDB data server, and the UDS instance.

We are using xMII 12.0 and I can not see the transaction ExecutionTimeout property which was existing on 11.5 with value 300000. I added a global property with the same name with bigger value, but this did not help.

The UDS version is 4.0.3.10.

Any ideas?

[Former Member]

Some more tests revieled that the virtual xAcute query fails - timeouts within 300 seconds. Is it a way to change this timeout? It looks like somewere in the code we have:

srvrSkt.SetSocketOption(SocketOptionLevel.Socket, SocketOptionName.ReceiveTimeout, 300000);

Is this timeout exposed for configuration?

[jcgood25]

Michel,

In BLS all Data Query actions have a timeout property (default is 60 seconds), which may have been bumped up to 300 during development. It looks like the application has some error messaging convention that should point you in the right direction, but based upon the message it almost looks like a network issue where the remote NW virtual connection couldn't reach the refinery server.

Regards,

Jeremy

[Former Member]

Thank you guys, I'll try the new timeout spelling.

About the delay, Jeremy is close we are abaout to identify network bottelneck between xMII and IP21.

Vlad (I was using Michel Renard's acct before creating mine...)

[Former Member]

Sounds like a bug, Jeremy, or at least, something that should be configurable. There are definitely queries that can run a LOOOOONG time, and in some cases, they might be virtual. I have seen heavy duty queries that take upwards of an hour to run.

[Former Member]

In BLS transaction, global properties config ExecutionTimeOut in milesecounds.

I hope I have helped,

Greetings,

[Former Member]

Unfortunately ExecutionTimeOut, as ExecutionTimeout does not help, at least in our case...