500 Connection timed out

[former_member261897]

Hello,

I have several Adaptive RFC2 Models that need a really long time to work (our abaper says that it could take up to several hours and there's no way to optimise). Naturally, I get 500 Connection timed out

Increasing timeout is not an option as modules need so much time, but maybe there's a way to call a transaction from Web Dynpro? Or some other workaround? Can't call it from portal in this particular case, sadly.

[former_member261897]

So we decided to make another module which will call a transaction in background mode (or whatever it's called in english. Hate translated interfaces...). This solution looks promising.

[former_member218672]

Hi Pavel,

Please check this thread -

Regards,

Sen

[former_member261897]

If there's no way to call a transaction, what can I do to keep connecton alive while the module is working? I already tried doing something in another thread, but it made no difference. Frankly, we're out of ideas.