Skip to Content
author's profile photo Former Member
Former Member

RFC_FAILURE affects Connection Pool

Using VB.NET (2003) with .Net Connector 2.0.

An intermittent problem causes a RFC Call to fail, and an exception is raised in the .NET code. The Exception message is:

See RFC trace file or SAP system log for more details

The Trace file shows:

  • ERROR file opened at 20051115 131423 GMT Standard

T, SAP-REL 640,0,78 RFC-VER 3 759904 MT-SL

<b>T:2844 Could not send rfc container 0x130

T:2844 <* RfcCall [1] : returns 1:RFC_FAILURE

T:2844 <* RfcCallReceive [1] : returns 1:RFC_FAILURE

>TS> Tue Nov 15 13:14:24 2005

T:2844 <* RfcCleanupContext [1] : returns


T:2844 <* RfcCleanupContext [1] : returns


This error adversely affects the Connection Pool – as calls to other RFCs are now prone to similar intermittent errors…

Is there any way to prevent the problem causing problems with Connection Pool ?

Is there any way of removing a “faulty” connection from the pool ? (NB Close and Dispose on the connection does not help)

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Nov 16, 2005 at 08:34 AM

    Thanks, this sounds interesting. I think I get the point, but perhaps you could isolate the problem to a code snipped. Where exactly does the exeption happen? I assume this is in a call after you took a connection from pool.

    Wouldn't it help just to catch the exception and prevent that this connection to put back to pool? e.g.

    proxy.Connection = Connection.GetConnectionFromPool(...)



    Catch e As RfcException


    proxy.Connection = Nothing

    End Catch


    if proxy.Connection <> Nothing then


    end if

    End Finally

    (sorry if my VB is not correct)

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.