My Oracle Support Banner

Integration Stuck in FRESH Status Due to "Connection pool DEDICATED_DBA is exhausted" Error Being Generated (Doc ID 1462779.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Transportation Management - Version 6.0 to 6.4.3 [Release 6 to 6.4]
Information in this document applies to any platform.

Symptoms

Integration being sent into Oracle Transportation Management ( OTM ) remains in a FRESH status after the following exception is generated.

2012-04-27 13:01:54.132 441503 Error Exception Connection pool DEDICATED_DBA is exhausted (capacity=[initial=1,max=3,increment=1], used=3)

at sun.reflect.GeneratedConstructorAccessor990.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at glog.util.exception.GLException.factory(GLException.java:435)
at glog.util.exception.GLException.factory(GLException.java:411)
at glog.util.exception.GLException.factory(GLException.java:407)
at glog.util.exception.GLException.factory(GLException.java:403)
at glog.util.datasource.GC3ConnectionPoolInstance.reserve(GC3ConnectionPoolInstance.java:60)
at glog.util.datasource.GC3ConnectionPool.reserve(GC3ConnectionPool.java:36)
at glog.util.datasource.DataSource.reserve(DataSource.java:143)
at glog.util.datasource.DataSource.reserve(DataSource.java:137)
at glog.util.jdbc.noserver.T2SharedConnection$ReferencedConnection.addRef(T2SharedConnection.java:301)
at glog.util.jdbc.noserver.T2SharedConnection$ReferencedConnection.addRef(T2SharedConnection.java:291)
at glog.util.jdbc.noserver.T2SharedConnection.open(T2SharedConnection.java:57)
at glog.server.synch.object.ObjectLock.insertOwnership(ObjectLock.java:635)
at glog.server.synch.object.ObjectLock$Hold.lock(ObjectLock.java:1027)
at glog.server.synch.object.ObjectLock.tryLock(ObjectLock.java:344)
at glog.server.synch.object.ObjectLock.tryLock(ObjectLock.java:294)
at glog.server.synch.object.ObjectLockMediatorID.acquire(ObjectLockMediatorID.java:120)
at glog.server.workflow.mediator.Mediator.checkAndRelease(Mediator.java:344)
at glog.server.workflow.mediator.Mediator.addItem(Mediator.java:99)
at glog.server.workflow.TopicManager.publish(TopicManager.java:104)
at glog.server.workflow.ServerPublisher.publishInternal(ServerPublisher.java:64)
at glog.server.workflow.ServerPublisher.publish(ServerPublisher.java:82)
at glog.server.workflow.Topic.publish(Topic.java:142)
at glog.server.workflow.mediator.MediationTopic.sendToMediator(MediationTopic.java:27)
at glog.server.workflow.mediator.MediationGroup.processGroup(MediationGroup.java:79)
at glog.server.workflow.transproc.NewXmlWF.execute(NewXmlWF.java:93)
at glog.server.workflow.WorkflowSessionBean.execute(WorkflowSessionBean.java:64)
at glog.server.workflow.WorkflowSessionNonTransServerSideEJBWrapper.execute(WorkflowSessionNonTransServerSideEJBWrapper.java:38)
at glog.server.workflow.WorkflowSessionNonTransServerSideEJBWrapper_t6tuwu_EOImpl.execute(WorkflowSessionNonTransServerSideEJBWrapper_t6tuwu_EOImpl.java:278)
at glog.server.workflow.WorkflowManager.execute(WorkflowManager.java:352)
at glog.server.workflow.Trigger.trigger(Trigger.java:122)
at glog.util.event.MemoryEventQueueRunnable.processEvent(MemoryEventQueueRunnable.java:146)
at glog.util.event.MemoryEventQueueRunnable.run(MemoryEventQueueRunnable.java:98)
at glog.util.event.EventThread.run(EventThread.java:82)
at java.lang.Thread.run(Thread.java:619)
[integrationMediate - 1]

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.