TcpInitiator is not running - java.lang.IllegalStateException

Question

This is the first time we have seen this exception on our Extend-client side in the past 6 months. What is the reason we are getting this? How can this be fixed? Do we need to do some autostart some where?
java.lang.IllegalStateException: XYZ-tcpProxy:TcpInitiator is not running
     at com.tangosol.coherence.component.util.daemon.queueProcessor.service.peer.Initiator.ensureConnection(Initiator.CDB:5)
     at com.tangosol.coherence.component.net.extend.remoteService.RemoteCacheService.openChannel(RemoteCacheService.CDB:5)
     at com.tangosol.coherence.component.net.extend.RemoteService.ensureChannel(RemoteService.CDB:6)
     at com.tangosol.coherence.component.net.extend.remoteService.RemoteCacheService.createRemoteNamedCache(RemoteCacheService.CDB:12)
     at com.tangosol.coherence.component.net.extend.remoteService.RemoteCacheService.ensureCache(RemoteCacheService.CDB:39)
     at com.tangosol.coherence.component.util.safeService.SafeCacheService.ensureCache$Router(SafeCacheService.CDB:1)
     at com.tangosol.coherence.component.util.safeService.SafeCacheService.ensureCache(SafeCacheService.CDB:46)
     at com.barcap.edt.flow.core.impl.cache.CoherenceCacheFactory$1.doTry(CoherenceCacheFactory.java:87)
     at com.barcap.edt.flow.core.impl.cache.CoherenceCacheFactory$1.doTry(CoherenceCacheFactory.java:1)
     at com.barcap.edt.flow.core.util.retry.RetryUtil.tryIt(RetryUtil.java:65)
     ... 2 more
Edited by: A.G. on Mar 10, 2010 5:55 PM

Answer 1

Dave,
Thanks for looking at the issue we encountered. Our Extend client config is as follows. Unfortunately I do not have the full log from the extend client vm as in this case extend client runs on our client's desktop.
<?xml version='1.0'?>
<cache-config>
<caching-scheme-mapping>
<cache-mapping>
<cache-name>xyz</cache-name>
<scheme-name>xyz-tcpProxy</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<remote-cache-scheme>
<scheme-name>xyz-tcpProxy</scheme-name>
<service-name>xyz-tcpProxy</service-name>
<initiator-config>
<tcp-initiator>
<remote-addresses>
<socket-address>
<address>proxy-host-address-01</address>
<port>22001</port>
</socket-address>
<socket-address>
<address>proxy-host-address-nn</address>
<port>22001</port>
</socket-address>
<connect-timeout>10000</connect-timeout>
</remote-addresses>
</tcp-initiator>
<outgoing-message-handler>
<request-timeout>30000</request-timeout>
</outgoing-message-handler>
</initiator-config>
</remote-cache-scheme>
<remote-invocation-scheme>
<scheme-name>xyz-remoteInvocation</scheme-name>
<service-name>xyz-remoteInvocation</service-name>
<initiator-config>
<tcp-initiator>
<remote-addresses>
<socket-address>
<address>proxy-host-address-01</address>
<port>22001</port>
</socket-address>
<socket-address>
<address>proxy-host-address-nn</address>
<port>22001</port>
</socket-address>
<connect-timeout>10000</connect-timeout>
</remote-addresses>
</tcp-initiator>
<outgoing-message-handler>
<request-timeout>30000</request-timeout>
</outgoing-message-handler>
</initiator-config>
</remote-invocation-scheme>
</caching-schemes>
</cache-config>
Regards
/A.G.