Resolution:
Description:
============
The following error is seen in the HawkAgent.log file after the previous machine reboot.

2011 Feb 26 22:08:29:207 GMT -5 Error [DBEntityStore] AESDKJ-0000 [TsmSyncTibcoServers]  TibrvException[error=21,message=Not connected to daemon]
     at com.tibco.tibrv.TibrvImplTPortC.natCreate(Native Method)
     at com.tibco.tibrv.TibrvImplTPortC.create(TibrvImplTPortC.java:40)
     at com.tibco.tibrv.TibrvRvdTransport.init(TibrvRvdTransport.java:77)
     at com.tibco.tibrv.TibrvRvdTransport.&ltinit>(TibrvRvdTransport.java:50)
     at com.tibco.pof.rendezvous.impl.TibrvRvdTransportConfigImpl.getTibrvRvdTransport(TibrvRvdTransportConfigImpl.java:62)
     at com.tibco.pof.entitystore.rvtransactionnotifier.RVTransactionNotifier.init(RVTransactionNotifier.java:149)
     at com.tibco.pof.entitystore.AbstractEntityStore.initTransactionNotifier(AbstractEntityStore.java:498)
     at com.tibco.pof.entitystore.db.DBEntityStore.init(DBEntityStore.java:564)
     at com.tibco.pof.entitystore.EntityStoreManager.a(EntityStoreManager.java:221)
     at com.tibco.pof.entitystore.EntityStoreManager.getEntityStore(EntityStoreManager.java:202)
     at com.tibco.pof.entitystore.EntityStoreManager.getReadOnlyEntityDomain(EntityStoreManager.java:333)
     at com.tibco.pof.entitystore.EntityStoreManager.getReadOnlyEntityDomain(EntityStoreManager.java:327)
     at com.tibco.pof.entitystore.EntityStoreManager.getReadOnlyEntityDomain(EntityStoreManager.java:312)
     at com.tibco.pof.admindomain.AdministrationDomain.instance(AdministrationDomain.java:181)
     at com.tibco.tra.tsm.TSM.getBindings(TSM.java:3967)
     at com.tibco.tra.tsm.TSM.syncTIBCOServers(TSM.java:3842)
     at com.tibco.tra.tsm.TsmSyncTibcoServers.run(TsmSyncTibcoServers.java:30)

Envionment:
===========
All

Resolution:
===========

1). If the Hawkagent is using a local RVD, when Hawkagent starts it starts the RV daemon if it's not already running. It will then  try to connect to the daemon.  If the daemon is not fully started, the Hawkagent will fail with the "Not connected to daemon" error.  The Hawkagent cannot connect to the daemon when an RVD/RVRD is not running. Also, daemon start-up requires getting the hostname/IP address. If it takes too long to get the hostname/IP resolved (which can happen sometime after restart), daemon start-up will be delayed and Hawkagnet will fail to connect to it and throw the “Not connected to daemon” error.

A possible workaround is to start “rvd” manually before starting other TIBCO applications (including Hawk, BW, …). On Windows platforms, you can create an RVD Windows service and let the Hawkagent depend upon the service to start the daemon.

2). If the Hawkagent is trying to connect to a remote daemon and that daemon is terminated, then Hawkagent will get the “Not connected to daemon” error.  The remote daemon needs to be started before any RV clients as the applications cannot start a remote daemon automatically.

An RV error [TibrvException[error=21,message=Not connected to daemon] is seen in the HawkAgent.log file after the previous machine reboot.