cancel
Showing results for 
Search instead for 
Did you mean: 

RfcCustomDestination stays logged in

former_member197445
Contributor
0 Kudos
155

Hi there.  We have a number of Web Applications that perform basic read-only RFC calls to SAP through the .NET Connector using a basic system user login created specifically for our web apps.  Occassionally, however, we create CustomDestinations using SSO to perform various write RFC functions using the actual user's SAP login.

This works great.  However, I am noticing in T-Code AL08 which shows all users logged on that the Custom Destinations persist.  Should we dispose of these somehow in our .NET code?  Is there a safe way of disposing of the Custom Destination after it is no longer needed?

For example, should I use the Shutdown() method after the Custom Destination is finished invoking the SSO RFC? Or RemoveDestination() possibly?

Thanks!

View Entire Topic
former_member197445
Contributor
0 Kudos

Actually, I may just use the IDLE_TIMEOUT and IDLE_CHECK_TIME to expire the connections.  That seems to work.

hynek_petrak
Active Participant
0 Kudos

Hi Case, in combination with RfcConfigParameters.PoolSize, that limits the number of idling connections.

MarkusTolksdorf
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Case,

exactly. That's the approach to take.

Best regards,

Markus