• Denis BOURDON
  • NEWBIE
  • 25 Points
  • Member since 2015

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 1
    Questions
  • 18
    Replies
Hello

For a few days (since Thursday 8th, but not on Saturday and Sunday, and never during the night), we encounter exceptions we never had before when creating Attachements using the API. We have 2 different exceptions that occur :
 
BlobField : U#15f.3fffffff (Attachment) U#15f.aff (Body) got exception Request timed out waiting for connection: [config 200ms, actual 215ms] - SERVER_UNAVAILABLE: Request timed out waiting for connection: [config 200ms, actual 236ms]

BlobField : U#15f.3fffffff (Attachment) U#15f.aff (Body) got exception Exception by writeBlob: BlobField: Attachment 00PD000000glfYF 

It is to be noticed that we have the first one during several hours, then the second one during several hours, and back to the first, and so on.
And during peak hours, these exceptions are totally random. If we regenerate the same query, it works fine.

It seems that there is a problem with the Oracle database of SF. The fact that it occurs on peak hours/days makes us think there is something of a degradation performance ? We are on EU1.

Thanks for the dedicated team of Salesforce for their help with that issue.

Regards,
When will be Winter 16 release notes available
Hello

For a few days (since Thursday 8th, but not on Saturday and Sunday, and never during the night), we encounter exceptions we never had before when creating Attachements using the API. We have 2 different exceptions that occur :
 
BlobField : U#15f.3fffffff (Attachment) U#15f.aff (Body) got exception Request timed out waiting for connection: [config 200ms, actual 215ms] - SERVER_UNAVAILABLE: Request timed out waiting for connection: [config 200ms, actual 236ms]

BlobField : U#15f.3fffffff (Attachment) U#15f.aff (Body) got exception Exception by writeBlob: BlobField: Attachment 00PD000000glfYF 

It is to be noticed that we have the first one during several hours, then the second one during several hours, and back to the first, and so on.
And during peak hours, these exceptions are totally random. If we regenerate the same query, it works fine.

It seems that there is a problem with the Oracle database of SF. The fact that it occurs on peak hours/days makes us think there is something of a degradation performance ? We are on EU1.

Thanks for the dedicated team of Salesforce for their help with that issue.

Regards,