Hello Francisco,
As long as the destination remains stable and is not changed, you will not experience such an issue. If it needs to be reconfigured, and you use a cached RfcDestination instance, you will experience this situation. A good countermeasure is not to cache the RfcDestination instance, but to always use the RfcDestinationManager to get the destination when needed.
Best regards,
Markus