[
http://mifosforge.jira.com/browse/MIFOSBI-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
johnwoodlock resolved MIFOSBI-310.
----------------------------------
Resolution: Fixed
The ETLs are not getting this commmunication error any more since Jakub
rescheduled them to not have the prod and test ETL's overlapping.
> ETLs Failing when communicating with RDS Instances
> --------------------------------------------------
>
> Key: MIFOSBI-310
> URL: http://mifosforge.jira.com/browse/MIFOSBI-310
> Project: mifos business intelligence
> Issue Type: Bug
> Components: Data Warehouse
> Reporter: johnwoodlock
> Assignee: johnwoodlock
> Priority: Major
>
> All Prod and Test ETLs have failed intermittently with the following error
> which starts
> "Couldn't get row from result set
> Communications link failure due to underlying exception:
> ** BEGIN NESTED EXCEPTION **
> javax.net.ssl.SSLException
> MESSAGE: SSL peer shut down incorrectly"
> It has affected ETL BI versions 1.1 and 1.2 (didn't go back to check 1.0).
> Typically, it occurs in "Load DW Trxn Table" job. Has also occurred during
> the "Load stg_customer_and_account_updates For Accounts" Transformation.
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
