Topic:   Getting following error in the webMethods IS
Aug 13, 2013 15:35 3 Replies 2565 Views hvreddy
Prev Next
Topic Replies (3)
  1. 1
    idnkx user

    hvreddy

    Am getting following error in the IS. Can anyone help me in fixing it.................




    Adapter Runtime (Connection): Unable to get a connection to resource JDBC_Implementation.JDBCConnection:LocalType_Connection. Resource not available.
    [386]2013-08-13 11:35:38 IST [SCC.0126.9999C] Unable to add ServiceCompletionListener for Transaction Manager
    [385]2013-08-13 11:35:38 IST [ART.0116.3038E] Adapter Runtime (Notification): Error in Notification Callback:initCallback notification JDBC_Implementation.Notifications:customerBasicNoti.
    [384]2013-08-13 11:35:38 IST [ART.0114.1007E] Adapter Runtime: Error Logged. See Error log for details. Error: [ADA.1.311] The connection is not available for " initCallBack() ".
    [383]2013-08-13 11:35:38 IST [SCC.0126.9999C] Unable to add ServiceCompletionListener for Transaction Manager
    [382]2013-08-13 11:35:38 IST [SCC.0126.9999C] Unable to add ServiceCompletionListener for Transaction Manager
    [381]2013-08-13 11:35:38 IST [ART.0118.5046E] Adapter Runtime (Connection): Unable to get a connection to resource JDBC_Implementation.JDBCConnection:LocalType_Connection. Resource not available.
    [380]2013-08-13 11:35:38 IST [SCC.0126.9999C] Unable to add ServiceCompletionListener for Transaction Manager
    [379]2013-08-13 11:35:38 IST [ART.0116.3038E] Adapter Runtime (Notification): Error in Notification Callback:initCallback notification JDBC_Implementation.Notifications:insertCustomerNoti.
    [378]2013-08-13 11:35:38 IST [ART.0114.1007E] Adapter Runtime: Error Logged. See Error log for details. Error: [ADA.1.311] The connection is not available for " initCallBack() ".
    [377]2013-08-13 11:35:38 IST [SCC.0126.9999C] Unable to add ServiceCompletionListener for Transaction Manager
    [376]2013-08-13 11:35:38 IST [SCC.0126.9999C] Unable to add ServiceCompletionListener for Transaction Manager
    [375]2013-08-13 11:35:38 IST [ART.0118.5046E] Adapter Runtime (Connection): Unable to get a connection to resource JDBC_Implementation.JDBCConnection:LocalType_Connection. Resource not available.
    [374]2013-08-13 11:35:38 IST [SCC.0126.9999C] Unable to add ServiceCompletionListener for Transaction Manager
    [373]2013-08-13 11:35:38 IST [ART.0116.3038E] Adapter Runtime (Notification): Error in Notification Callback:initCallback notification JDBC_Implementation.Notifications:deleteItemsNoti.
    [372]2013-08-13 11:35:38 IST [ART.0114.1007E] Adapter Runtime: Error Logged. See Error log for details. Error: [ADA.1.311] The connection is not available for " initCallBack() ".
    [371]2013-08-13 11:35:37 IST [SCC.0126.9999C] Unable to add ServiceCompletionListener for Transaction Manager
    [370]2013-08-13 11:35:35 IST [ISS.0025.0016I] Config File Directory Saved
    [369]2013-08-13 11:35:34 IST [ISS.0014.0002C] Initialization completed in 252 seconds.
    [368]2013-08-13 11:35:34 IST [ISS.0025.0025I] Broker Synchronizer initialized
    [367]2013-08-13 11:35:34 IST [ISS.0036.9998E] Exception --> com.wm.app.b2b.client.DeliveryException: [ISC.0063.9154] [Tx] The ISInternal functional alias is not configured properly on the JDBC Pools page. Assign a valid database pool and restart the Integration Server. ()
    [366]2013-08-13 11:35:34 IST [ISC.0037.0001E] Unable to Initialize [ISC.0063.9154] [Tx] The ISInternal functional alias is not configured properly on the JDBC Pools page. Assign a valid database pool and restart the Integration Server. ()
    [365]2013-08-13 11:35:34 IST [ISS.0025.0013I] Cache Sweeper started
    [364]2013-08-13 11:35:34 IST [ISS.0025.0005I] Port Manager started
    [363]2013-08-13 11:35:34 IST [ISS.0025.0036I] Dispatcher started
    [362]2013-08-13 11:35:33 IST [ISS.0098.0027I] PersistenceManager started all Stores
    [361]2013-08-13 11:35:33 IST [ISS.0098.0034I] webM IS RequestReplyHandler starting execution.
    [360]2013-08-13 11:35:33 IST [ISS.0098.0021I] Exactly Once Trigger Output Dispatcher started
    [359]2013-08-13 11:35:33 IST [ISS.0098.0021I] Persistent Trigger Output Dispatcher started
    [358]2013-08-13 11:35:33 IST [ISP.0046.0012I] Enabling HTTP Listener on port 5555
    [357]2013-08-13 11:35:33 IST [ISP.0046.0012I] Enabling HTTP Listener on port 7777
    [356]2013-08-13 11:35:33 IST [ISP.0046.0012I] Enabling HTTP Listener on port 9999
    [355]2013-08-13 11:35:32 IST [ISS.0028.0012I] WmTaskClient: Startup service (wm.task.taskclient:init)
    [354]2013-08-13 11:35:32 IST [ART.0114.1100I] Adapter Runtime: Facility 680 - JMSAdapter registered with bundle com.wm.adapter.wmjms.JMSAdapterResourceBundle.
    [353]2013-08-13 11:35:32 IST [ISS.0028.0012I] WmJMSAdapter: Startup service (wm.adapter.wmjms.admin:startUp)
    [352]2013-08-13 11:35:31 IST [ISS.0028.0012I] WmLogUtil: Startup service (wm.loggingUtility:start)
    [351]2013-08-13 11:35:30 IST [ISS.0028.0012I] WmDeployer: Startup service (wm.deployer.Util:verifyPlugins)

    1
    idnkx user

    rambo

    Hi


    We could see 2 errors mainly notifications are throwing errors and Jdbc pool errors.

    1)please check if the jdbc pools are configured correctly or not .Test them.

    2)See whether wmjdbc package is enabled partially ? If it is partial check for the missouts and add them.

    If it is full check whether there is any issue connections and notifications.

    regards

    1
    idnkx user

    Akash

    Is your issue resolved?

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