• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Error: No more data available to read

New Here ,
Jan 28, 2020 Jan 28, 2020

Copy link to clipboard

Copied

Hi everyone,

 

We just recently migrated from ColdFusion 2011 to 2018. Pages on the site frequently encounter the following error:

 

Error Executing Database Query.[Macromedia][Oracle JDBC Driver]No more data available to read.

 

This is usually generated when a page is initally loaded or access after having been idle for an indeterminate time frame. This error was never an issue with our CF 2011 installation.

 

We are using an Oracle backend datasource which is situated in another physcial location from our CF servers. This setup is new to us but I cannot imagine it be the cause of the error.

 

I see that this error has been posted in the past by it was never fully resolved/explained.

 

Any advice/suggestion would be greatly appreciated.

 

TOPICS
Database access

Views

774

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jan 30, 2020 Jan 30, 2020

Copy link to clipboard

Copied

Are you saying that having the database in a separate location is new, as well as your CF upgrade? Because that certainly sounds like a viable cause for your problem. And in general, it's not a good idea.

 

Dave Watts, Eidolon LLC

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 30, 2020 Jan 30, 2020

Copy link to clipboard

Copied

LATEST

Thanks the response Dave.

 

Our host provider was able to help identify the crux of the issue. As they had explained:

 

  • We have seen this happen when the datasource timeout and interval is set too high. By default, the timeout is 20min and the interval is 7min. The datasources we saw, that had problems, were going through a proxy and the login timeout was 300 seconds. The interval had to be less than that to work. I just set your datasource to use a timeout of 3min and interval of 1min. That should keep the connection open and not timeout the read.

 

This seemed to have resolved the issue.

 

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Documentation