Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • Ibm Support: Ibm Filenet P8 Content Engine (Ce) Is Slow, Sometimes Hangs, and Produces Datasource Errors

    Uploaded by

    srikanth jeripothula
    259 views1 page
    This document provides troubleshooting steps for slow performance and hangs when saving or searching in an IBM FileNet P8 Content Engine. The issue is caused by too few connections in the datasource connection pool. The solution is to increase the number of connections by accessing the WebSphere console, navigating to the data sources, increasing the connection pool property value for each datasource, saving the changes, and restarting WebSphere.

    Original Description:

    datacap

    Original Title

    1.1.1

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document provides troubleshooting steps for slow performance and hangs when saving or searching in an IBM FileNet P8 Content Engine. The issue is caused by too few connections in the datasource connection pool. The solution is to increase the number of connections by accessing the WebSphere console, navigating to the data sources, increasing the connection pool property value for each datasource, saving the changes, and restarting WebSphere.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    259 views1 page

    Ibm Support: Ibm Filenet P8 Content Engine (Ce) Is Slow, Sometimes Hangs, and Produces Datasource Errors

    Uploaded by

    srikanth jeripothula
    This document provides troubleshooting steps for slow performance and hangs when saving or searching in an IBM FileNet P8 Content Engine. The issue is caused by too few connections in the datasource connection pool. The solution is to increase the number of connections by accessing the WebSphere console, navigating to the data sources, increasing the connection pool property value for each datasource, saving the changes, and restarting WebSphere.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    of 1

    Support Downloads Documentation Forums Cases Monitoring Manage support account

    IBM Support
    Search support or find a product 

    Contact and feedback


    IBM FileNet P8 Content Engine (CE) is slow, sometimes hangs, and produces
    datasource errors

    Troubleshooting Document Information

    More support for:


    Problem FileNet P8 Platform

    Attempting to save or search in IBM FileNet P8 Content Engine (CE) is slow and sometimes hangs. Software version:
    4.5.1, 5.0, 5.1, 5.2, 5.2.1
    Symptom
    Operating system(s):
    CE exhibits slow performance and hangs. Datasource errors appear in the logs, but the database is fine and the datasources test out ok in the WAS console.
    AIX, HP-UX, Linux, Solaris,
    Windows
    Cause
    Document number:
    Too few connections in the datasource connection pool
    265125

    Environment
    Modified date:
    WebSphere Application Server 17 June 2018

    Diagnosing The Problem

    Errors such as this appear in the logs:


    2015-05-19T08:12:21.412 1F7122D0 CSTG FNRCE0024E - ERROR
    executeRollFwdCommand threw an exception
    com.filenet.api.exception.EngineRuntimeException: FNRCE0024E:
    E_FAILED_TO_GET_DATASOURCE: The server cannot get the data source
    <name>. Message was: CWTE_NORMAL_J2CA1009

    Resolving The Problem

    Increase the number of connections in the Connection pool:

    1. Access the WebSphere Integrated Console:


    http://server_name:9060/ibm/console (default) where server_name is the name of your CE server.

    2. Navigate to Resources -> JDBC -> Data sources.

    3. Click each data source and check the Connection pool properties value,
    which is on the right side of the page.

    4. Increase the Connection pool based on your system resources and needs. A suggested maximum value is 100.

    5. Click OK.

    6. Click Save directly to the master configuration.

    7. Restart WebSphere

    Cookie Preferences
    Contact IBM Privacy Terms of use Accessibility United States — English

    You might also like