Description:
Description:
============
If the IP address of the host changes after installation, which commonly happens using DHCP, the error below will be seen when executing the asg-engine program (the ActiveMatrix Service Gateway engine)

2012 Aug 09 16:19:37:675 GMT +2 asg-caching-core Info [main] - [com.tibco.cep.runtime.service.dao.impl.tibas.ASDaoProvider] Initializing [ASDaoProvider]
2012 Aug 09 16:19:37:677 GMT +2 asg-caching-core Info [main] - [com.tibco.cep.runtime.service.dao.impl.tibas.ASDaoProvider] Connecting to [Metaspace:ASG] on ports[tcp://10.98.32.48:6000-*/] and [tcp://127.0.0.1:6000/]
2012 Aug 09 16:19:38:298 GMT +2 asg-caching-core Warning [main] - [com.tibco.cep.runtime.service.dao.impl.tibas.ASDaoProvider] Failed connecting to [Metaspace:ASG] with error TIBAS_SYS_ERROR (no_port_available - ip=10.98.32.48:6000-65535). Retrying in [10] seconds

Workaround:
===========

Edit the file asg_core.cdd to either use the new public IP address or just the loopback value and restart the engine.

e.g.:-


&ltproperty-group comment="" name="cluster">
&ltproperty name="be.engine.cluster.as.discover.url" value="tcp://127.0.0.1:6000/"/>
&ltproperty name="be.engine.cluster.as.listen.url" value="tcp://127.0.0.1:6000-*/"/>
&ltproperty name="be.mm.cluster.as.listen.url" value="tcp://127.0.0.1:6000-*/"/>
</property-group>




Environment:
===========
   o TIBCO ActiveMatrix® Service Gateway 1.2.0


Attachment:
===========
   o N/A


Reference:
==========
   o N/A

Known Issue in TIBCO ActiveMatrix Service Gateway version 1.2.0