Troubleshooting
Problem
Agentservers are not starting up no errors system management console not loading cannot start agent server or access system management console
Symptom
PART: Platform Framework 5.0 SP2 Platform
PRODUCT: Distributed Order
Management
COMPONENT: API
WEB BROWSER: Internet Explorer - 6.0
sp1
Agentservers are not starting up;
No errors;
System management console not loading;
Cannot start agent server or
access system management console
Cause
Resolving The Problem
Check the agent server log for errors during startup. When the Agent is
completely started it should log the following messages ..
2003-12-28 17:28:28,936:DEBUG : Context Intialized : YFCRemoteManager
2003-12-28 17:28:28,936:DEBUG : Registring IntegrationServer with id Server_1 :
YIFServerManager
2003-12-28 17:28:28,936:DEBUG : Initial Context creation
: YFCRemoteManager
2003-12-28 17:28:28,938:DEBUG : Jndi Context obtained
: YFCRemoteManager
2003-12-28 17:28:28,949:DEBUG : SubContext created...
: YFCRemoteManager
2003-12-28 17:28:28,949:DEBUG : Checking if this
instance is connected.....Server_1 : YFCRemoteManager
2003-12-28
17:28:28,956:DEBUG : Mediator will start the services :
ServiceContextMediatorBase
2003-12-28 17:28:28,957:INFO : Starting
Service[ 0] For RuntimeId: SCHEDULE_AGENT : ServiceContextMediatorBase
If you do not see any errors but the agent does not start up check if
the JNDI registry / tree is fine. One way to confirm that is to check if the
System Managemtn console loads up correctly and if you can stop/start servers
from there. If the page is not loading or if you cannot manage the agents then
the problem is most likely with the JNDI tree.
For weblogic App
server there is a JNDI clean up script released as a part of HF on 5.0 SP2 to
remove stale entries. For websphere or if you dont have the script the only way
to clean up the entries is to bring down the agent servers and restart the
application server. Make sure that you bring down all agent servers before
restarting the app server.
You should be able to restart the agent server
after the application server is up.
If there are still problems
in getting the agent to work you can use Soln 13997 to submit the agent and
process the task_q records without JNDI tree, MQ or JMS queue etc.
Historical Number
PRI49265
Product Synonym
[<p><b>]Fact[</b><p>];
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21545774