Error occurring when running parallel Threads / connections to the DB2 database -- CLI0106E Connection is closed. SQLSTATE=08003

Posted by: raghuveerp77 on 3 August 2017, 3:20 pm EST

  • Posted 3 August 2017, 3:20 pm EST

    Error: An unexpected error occurred. Additional information: ' CLI0106E Connection is closed. SQLSTATE=08003'



    I am newbie,

    We are trying to run the DDR reports using the multithreaded application (.Net 3.5 framework). DDR report rendering engine is accessing the DB2 data base in order to generate the results. Each thread opens the connection, fetches the results and closes connection. We are running maximum 4 threads







    var _renderingExtension = new DataDynamics.Reports.Rendering.Xml.XmlRenderingExtension();



    //using memory instead of file

    var _streamProvider = new DataDynamics.Reports.Rendering.IO.MemoryStreamProvider();



    runtime.Render(_renderingExtension, _streamProvider);



    Throwing the error when running render method



    Report Definition has the Connection properties



    ReportDefinition definition;



    string rdlxName = Constants.rdlxAndXslFilePath + gr.StructureFileName;



    definition = new ReportDefinition(new FileInfo(rdlxName));



    definition.Report.DataSources[0].DataSourceReference = null;

    definition.Report.DataSources[0].ConnectionProperties.ConnectString = Constants.connectionString;

    definition.Report.DataSources[0].ConnectionProperties.IntegratedSecurity = true;

    definition.Report.DataSources[0].ConnectionProperties.DataProvider = "OLEDB";



    Any ideas or suggestions?
  • Replied 3 August 2017, 3:20 pm EST

    Hello,

    This seems to be a generic error and I am not sure if it is specifically related to Data Dynamics Reports. I would suggest you to test the issue without using Data Dynamics Reports, you might try creating a multi threaded environment while binding the DB2 to a windows component and see if the issue persists.

    Please share your observations with me as it would help me to debug the issue further at my end. However, if you still face the same issue I would request you to provide me with a sample application depicting your issue so that I can replicate the issue at my end and debug it further.

    Thanks,
    Manpreet Kaur
  • Replied 3 August 2017, 3:20 pm EST

    Hi Manpreet.,



    Thank you very much; we did figured it out; its connection string with IBM Db2; ( we are using OLEDB type connection string.;



    regards

    Raghuveer
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels