Below is the information I can see under EventData
TaskName=ReportBroadcastTask.BroadcastTask,Error=com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after connection closed.,ScheduleSubjectCode=BROADCAST,ScheduleUnitCode=BROADCASTID,ScheduleUnitId=1668948
Below is the information I can see under EventData
TaskName=ReportBroadcastTask.BroadcastTask,Error=com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after connection closed.,ScheduleSubjectCode=BROADCAST,ScheduleUnitCode=BROADCASTID,ScheduleUnitId=1668948
Sorry, I am not sure I understand 100% so I am assuming you are looking for the reason or what the error entails?
From experience this could be related to an issue with the MYSQL database connection at this time. Does it fail if you run the scheduled broadcast manually and was this a once off or is it hapenning all the time? If you looked in the logs (yellowfin, jdbc or source logs under /yellowfininstall/appserver/logs), you will probably find a connection issue to the DB at the same time.
Let me know if this makes sense.
Regards,
Paul
Hi Shahul,
Sorry, I am not sure I understand 100% so I am assuming you are looking for the reason or what the error entails?
From experience this could be related to an issue with the MYSQL database connection at this time. Does it fail if you run the scheduled broadcast manually and was this a once off or is it hapenning all the time? If you looked in the logs (yellowfin, jdbc or source logs under /yellowfininstall/appserver/logs), you will probably find a connection issue to the DB at the same time.
My apologies as you are using version 7.3, this information is not captured in the event table. You should be able to find something in yellowfin log though, but you would need to search for it and look for "ReportBroadcastProcess" and any corresponding error that might have hapenned after that.
Thanks,
Paul
Hi Shahul,
My apologies as you are using version 7.3, this information is not captured in the event table. You should be able to find something in yellowfin log though, but you would need to search for it and look for "ReportBroadcastProcess" and any corresponding error that might have hapenned after that.
You cannot send the failure to a user the report has failed to go as such, but you can setup a failure notification to as user / group etc as per below from the Admin console / Configuration.
Let me know if this helps,
Thanks,
Paul
Hi Shahul,
You cannot send the failure to a user the report has failed to go as such, but you can setup a failure notification to as user / group etc as per below from the Admin console / Configuration.
Hi Shahul,
Some like this should work (just need to change the iporg to the correct one)
Against the YF Config DB
Let me know if you need anything else.
Regards,Paul
Hi Shahul,
Some like this should work (just need to change the iporg to the correct one)
Against the YF Config DB
Let me know if you need anything else.
Regards,Paul
Hi Shahul,
Sorry, I am not sure I understand 100% so I am assuming you are looking for the reason or what the error entails?
From experience this could be related to an issue with the MYSQL database connection at this time. Does it fail if you run the scheduled broadcast manually and was this a once off or is it hapenning all the time? If you looked in the logs (yellowfin, jdbc or source logs under /yellowfininstall/appserver/logs), you will probably find a connection issue to the DB at the same time.
Let me know if this makes sense.
Regards,
Paul
Hi Shahul,
Sorry, I am not sure I understand 100% so I am assuming you are looking for the reason or what the error entails?
From experience this could be related to an issue with the MYSQL database connection at this time. Does it fail if you run the scheduled broadcast manually and was this a once off or is it hapenning all the time? If you looked in the logs (yellowfin, jdbc or source logs under /yellowfininstall/appserver/logs), you will probably find a connection issue to the DB at the same time.
Let me know if this makes sense.
Regards,
Paul
Hi Shahul,
Just checking in on this ticket to see if you need any more help?
Thank you,
Paul
Hi Shahul,
Just checking in on this ticket to see if you need any more help?
Thank you,
Paul
Hi Paul,
Thanks for the follow up. Issue has been resolved now.
Hi Paul,
Thanks for the follow up. Issue has been resolved now.
Hi Shahul,
That's great and thank you for getting back to me.
Regards,
Paul
Hi Shahul,
That's great and thank you for getting back to me.
Regards,
Paul
Replies have been locked on this page!