Thread Pool Problelm in Weblogic during server startup

if u find below problem during server startup in weblogic

#### <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <1309892506466> <|I |00:31:46 |1 |omsAdminServer |Starting service 'Thread Pool'>

#### <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <1309892506520> <|W |00:31:46 |1 |omsAdminServer |Failed to lookup the WorkManager 'java:comp/env/wm/log' for ThreadPool 'log'. Make sure that this WorkManager is defined in the application server. In addition, if a new ThreadPool was added, it will be necessary to rebuild the project for the necessary resource references to be added to the deployment file ejb-jar.xml. <>

amdocs.epi.error.EpiIllegalArgumentException: Failed to lookup the WorkManager 'java:comp/env/wm/log' for ThreadPool 'log'. Make sure that this WorkManager is defined in the application server. In addition, if a new ThreadPool was added, it will be necessary to rebuild the project for the necessary resource references to be added to the deployment file ejb-jar.xml. <>

at amdocs.epi.appserver.AppServerInfoBase.initThreadPoolImpl(AppServerInfoBase.java:207)

at amdocs.epi.appserver.weblogic_10.AppServerInfoCls.initThreadPool(AppServerInfoCls.java:94)

at amdocs.epi.concurrent.ThreadPoolCls.(ThreadPoolCls.java:240)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

at amdocs.epi.management.services.RegistryAgent.initServiceFromHashMap(RegistryAgent.java:418)

at amdocs.epi.management.services.RegistryAgent.initServices(RegistryAgent.java:319)

at amdocs.epi.management.services.JmxRegistryAgent.init(JmxRegistryAgent.java:130)

at amdocs.epi.management.Bootstrap.startServicesFromConfig(Bootstrap.java:799)

at amdocs.epi.management.Bootstrap.startServices(Bootstrap.java:493)

Caused by: java.lang.reflect.InvocationTargetException

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

at amdocs.epi.management.services.RegistryAgent.initServiceFromHashMap(RegistryAgent.java:418)

at amdocs.epi.management.services.RegistryAgent.initServices(RegistryAgent.java:319)

... 43 more

Caused by: amdocs.epi.error.EpiIllegalArgumentException: Failed to lookup the WorkManager 'java:comp/env/wm/log' for ThreadPool 'log'. Make sure that this WorkManager is defined in the application server. In addition, if a new ThreadPool was added, it will be necessary to rebuild the project for the necessary resource references to be added to the deployment file ejb-jar.xml. <>

at amdocs.epi.appserver.AppServerInfoBase.initThreadPoolImpl(AppServerInfoBase.java:207)

at amdocs.epi.appserver.weblogic_10.AppServerInfoCls.initThreadPool(AppServerInfoCls.java:94)

at amdocs.epi.concurrent.ThreadPoolCls.(ThreadPoolCls.java:240)

... 49 more

Caused by: javax.naming.NameNotFoundException: While trying to look up comp/env/wm/log in /app/ejb/AmdocsProcMgrEjbDesc.jar#epi-mgmt-bootstrap.; remaining name 'comp/env/wm/log'

at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)

at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:144)

at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)

at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)

at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:45)

at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:130)

at javax.naming.InitialContext.lookup(InitialContext.java:392)

at amdocs.epi.appserver.AppServerInfoBase.lookupJndi(AppServerInfoBase.java:240)

at amdocs.epi.appserver.AppServerInfoBase.initThreadPoolImpl(AppServerInfoBase.java:161)

... 51 more

Then below is the solution

Your are missing with log thread pool entry in the weblogic config file :-

Go to weblogic >> C:\bea103\user_projects\domains\omsDomain\config

config.xml

wm/omsThreadPool

omsAdminServer

true

wm/log

omsAdminServer

false