Topic:   ServerError: (com.wm.pkg.art.error.DetailedServiceException: [ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service- [ART.118.5053] Adapter Runtime (Connection): Unable to
Sep 27, 2012 15:04 2 Replies 7736 Views George
Prev Next
Topic Replies (2)
  1. 1
    idnkx user

    George

    Hi Xperts,

    We are using wM 6.1 version with JDBC adapter 6.5 version and connecting to our oracle database, while connecting sometimes we get the below exceptions:


    ServerError: (com.wm.pkg.art.error.DetailedServiceException: [ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service testFramework.scheduler:testList

    com.wm.pkg.art.error.DetailedServiceException: [ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service testFramework.scheduler:testList.
    [ART.117.4012] Adapter Runtime (Adapter Service): Unable to run adapter service. Error occurred when connecting to resource testFramework.connections:testDB.
    [ART.118.5053] Adapter Runtime (Connection): Unable to get a connection to resource testFramework.connections:testDB.
    A connection was not available for request in pool
    at com.wm.pkg.art.error.DetailedServiceException.create(DetailedServiceException.java:125)


    at java.lang.Thread.run(Thread.java:619)
    Caused by: com.wm.adk.error.AdapterServiceException: [ART.117.4012] Adapter Runtime (Adapter Service): Unable to run adapter service. Error occurred when connecting to resource testFramework.connections:testDB.
    [ART.118.5053] Adapter Runtime (Connection): Unable to get a connection to resource testFramework.connections:testDB.
    A connection was not available for request in pool testFramework.connections:testDB
    at com.wm.adk.error.AdapterException.(AdapterException.java:427)
    at com.wm.pkg.art.error.DetailedException.(DetailedException.java:91)
    at com.wm.pkg.art.transaction.ConnectionState.getConnection(ConnectionState.java:230)
    at com.wm.pkg.art.ns.AdapterServiceNode.getConnection(AdapterServiceNode.java:611)
    at com.wm.pkg.art.ns.AdapterServiceNode.invokeService(AdapterServiceNode.java:301)
    ... 34 more
    Caused by: com.wm.pkg.art.error.DetailedException: [ART.118.5053] Adapter Runtime (Connection): Unable to get a connection to resource testFramework.connections:testDB.
    A connection was not available for request in pool testFramework.connections:testDB
    at com.wm.pkg.art.ns.ConnectionResource.createConnection(ConnectionResource.java:437)
    at com.wm.pkg.art.transaction.ConnectionState.getConnection(ConnectionState.java:210)
    ... 36 more


    Any replies to resolve this issue highly appreciated.

    Regards,
    George

    1
    idnkx user

    Pavan

    Hi,

    Check Your Adapter configuration and connection pool settings. Seems you were exceeding the maximum no of connections specified at connection pool.

    [ART.118.5053] Adapter Runtime (Connection): Unable to get a connection to resource testFramework.connections:testDB. [b]A connection was not available for request in pool [/b]testFramework.connections:testDB


    If you still face problems after increasing the maximum connections, if it would be a problem with hanging services then it needs to be investigated differently, IS restart may resolve hanging services problem and needs to find out why the services were hanging.


    [b]Connection Pools:[/b]
    The Integration Server includes a connection management service that dynamically manages connections and connection pools based on configuration settings that you specify for the connection. All adapter services use connection pooling. A connection pool is a collection of connections with the same set of attributes. The Integration Server maintains connection pools in memory. Connection pools improve
    performance by enabling adapter services to reuse open connections instead of opening new connections.

    [b]Run-Time Behavior of Connection Pools:[/b]
    When you enable a connection, the Integration Server initializes the connection pool, creating the number of connection instances you specified in the connection’s Minimum Pool Size field when you configured the connection. Whenever an adapter service needs a connection, the Integration Server provides a connection from the pool. If no connections are available in the pool, and the maximum pool size has not been reached, the server creates one or more new connections (according to the number specified in the Pool Increment Size field) and adds them to the connection pool. If the pool is full (as specified in Maximum Pool Size field), the requesting service will wait for the Integration Server to obtain a connection, up to the length of time specified in the [b]Block Timeout field[/b], until a
    connection becomes available. Periodically, the Integration Server inspects the pool and removes inactive connections that have exceeded the expiration period that you specified in the [b]Expire Timeout [/b]field.

    If the connection pool initialization fails because of a network connection failure or some other type of exception, you can enable the system to retry the initialization any number of times [b]Startup Retry Count[/b], at specified intervals. The time system should wait between attempts to initialize a connections will be [b]Startup Backoff Timeout[/b]. For information about configuring connections Refer..[url=http://documentation.softwareag.com/webmethods/adapters_estandards/Adapters/JDBC/JDBC_6-0-3/JDBC%20Adapter%206.0.3/webMethods%20JDBC%20Adapter%20User%27s%20Guide%206.0.3.pdf]wM JDBC Adapter users guide[/url].

Leave a Reply
Guest User

Not sure what course is right for you?

Choose the right course for you.
Get the help of our experts and find a course that best suits your needs.


Let`s Connect