IBM Support

PI67832: FFDC created when a feature is removed from server.xml.

Fixes are available

16.0.0.3: WebSphere Application Server Liberty 16.0.0.3
16.0.0.4: WebSphere Application Server Liberty 16.0.0.4
17.0.0.1: WebSphere Application Server Liberty 17.0.0.1
17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An FFDC occurs when a feature is removed from server.xml
    while the server is running.
    
    FFDC exception:
    Exception = javax.resource.spi.ResourceAllocationException
    >Source =
    com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection
    >probeid = 299
    >Stack Dump =
    javax.resource.spi.ResourceAllocationException: Pool
    requests blocked for
    dataSource[db2]/connectionManager[default-0], connection
    pool is being shut down.
    >	at
    com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2632)
    >	at
    com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2335)
    etc....
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty - Web Container              *
    ****************************************************************
    * PROBLEM DESCRIPTION: FFDC created when a feature is removed  *
    *                      from server.xml.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An FFDC occurs on a application request after a feature is
    removed from server.xml while the server is running.
    
    FFDC exception:
    Exception = javax.resource.spi.ResourceAllocationException
    >Source =
    com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection
    >probeid = 299
    >Stack Dump = javax.resource.spi.ResourceAllocationException:
    Pool requests blocked for
    dataSource[db2]/connectionManager[default-0], connection pool is
    being shut down.
    >	at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2632)
    >	at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2335)
    etc....
    

Problem conclusion

  • The problem was caused by the way the webcontainer stops an
    application during a configuration update which means that the
    application was not fully destroyed and  resources from the
    stopped version of the application may then be re-used for the
    restarted application. The problem reported for this APAR is
    just one example of an error which could happen.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 16.0.0.3.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Stop the server before making config updates and the re-start
    the server.
    

Comments

APAR Information

  • APAR number

    PI67832

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-19

  • Closed date

    2016-08-22

  • Last modified date

    2016-08-22

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

  • RCD0 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
14 October 2021