Opentalk Request Broker Connection Closed ignoring timeout?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Opentalk Request Broker Connection Closed ignoring timeout?

Karyn Hurley
I have some code to move data around via an opentalk server.  I am streaming the data to avoid using anonymous ftp since the file sizes may be very large (open to suggestions here) and there are some access issues related to using ftp that we're trying to avoid.

I'm getting connection closed errors even though I'm setting ridiculously high timeouts and always getting a timeout after 20 minutes.  

Here is a code snippet, does anyone have experience with this?

broker := RequestBroker newStstTcpAtPort: someNum

and then set a ridiculously high timeout:

client broker requestTimeout: 144000000

Here is the error:

an Opentalk.OtEServerError{Connection Closed}...  

the error is coming from Opentalk.RemoteRequest.waitForReply:  and if I look at the instance variables I do see my timeout as 144000000.  

Karyn Hurley
Reply | Threaded
Open this post in threaded view
|

Re: Opentalk Request Broker Connection Closed ignoring timeout?

Karyn Hurley
I have also set the object adaptor timeouts:

broker objectAdaptor connectionTimeout: 7200000.
broker objectAdaptor connectingTimeout: 7200000.

This doesn't seem to be helping either.  

I have also tried using the broker handleErrors, showErrors, passErrors methods in the  Basic Request Broker to no avail.  

Thanks,
Karyn
Karyn Hurley