This forum is now out of date, for our new forum Click Here
Determining closed connections
Question Asked
I had a customer say that their reports were not working. When I checked the data source, it was listed as unavailable. I performed a test of the connection via Administration > Source Systems & Views > Connection Details, and the connection was available again.

We never disable a data source and the minimum connections in Pool Management is 1. We have 60+ client orgs/data sources so managing them is a challenge.

Is there something causing the connection to be lost - or at least a way to automatically re-test the connection to re-establish it?

Is there a way to report on the status of every data source at one time?

Is there an action in the Event log that would show when the connection was lost?

Thanks for your help!

Rob

Rob

Tue Jun 25, 2013 6:46 AM

Comment
Hi Rob,

Yellowfin has a setting called Refresh Time that causes a connection to be recycled as explained in this Wiki page.

The default configuration time is 3 hours, you could try a shorter period as this should cause the connection to be checked and recycled more requently

This is logged in the source file for that particular data source (eg. source.12345.log) as shown below:

2013-03-13 16:06:00 INFO: [58978] Connection[0] has been open for 3 h, 24 ms and will be recycled
2013-03-13 16:06:00 INFO: [58978] Connection[0] successfully reopened
2013-03-14 09:46:00 NOTICE: [58978] -----------------------------------------


What database did the connection issues occur with?
We have had clients tell us about connection loss issues such as this occurring with DB2 and also Oracle.

Also, you can configure Yellowfin to check DB connections every minute, if it finds that a connection has become corrupted it will recycle it before the refresh time has come up. This Forum post describes how to configure Yellowfin to do this connection verifying.

As well as that, Yellowfin also can be configured for volatile sources such that after a specified timeout period it will retry a connection (rather than just returning an error message to the user), and it will repeat this for a number of times that is also configurable. Please see this Forum post for a description of how to set this up.

I hope this information helps with the issue of reports not working, please let us know how it goes.

Regards,
Dave

David

Fri Jun 28, 2013 9:29 AM

Comment
Hi Dave - thanks for info. We're using MS SQL Server 2008.

The third link (..after a specified timeout period it will retry a connection...) didn't come through. Could you please repost it?

Thanks!

Rob

Rob

Fri Jun 28, 2013 1:15 AM

Comment
Hi Rob,

woops! thanks for letting me know...I've fixed the link now.

Regards,
Dave

David

Fri Jun 28, 2013 9:31 AM