Archived
This forum has been archived. Please start a new discussion on GitHub.
can't destroy topic , why?
Ice 3.1.1 Copyright 2003-2006 ZeroC, Inc.
>>> help
help Print this message.
exit, quit Exit this program.
create TOPICS Add TOPICS.
destroy TOPICS Remove TOPICS.
link FROM TO COST Link FROM to TO with the given COST.
unlink FROM TO Unlink TO from FROM.
graph DATA COST Construct the link graph as described in DATA with COST
list [TOPICS] Display information on TOPICS or all topics.
>>> list
>>> create test
>>> list
test
>>> destroy test
error: Reference.cpp:1124: Ice::NoEndpointException:
no suitable endpoint available for proxy `test -t @ Simple.Config.TopicManager'
>>>
why can't destroy topic ??
>>> help
help Print this message.
exit, quit Exit this program.
create TOPICS Add TOPICS.
destroy TOPICS Remove TOPICS.
link FROM TO COST Link FROM to TO with the given COST.
unlink FROM TO Unlink TO from FROM.
graph DATA COST Construct the link graph as described in DATA with COST
list [TOPICS] Display information on TOPICS or all topics.
>>> list
>>> create test
>>> list
test
>>> destroy test
error: Reference.cpp:1124: Ice::NoEndpointException:
no suitable endpoint available for proxy `test -t @ Simple.Config.TopicManager'
>>>
why can't destroy topic ??
0
Comments
-
Can you fix the organization name in your profile information please? To help you with this problem we also need more information.
- Version of Ice you are using.
- Operating system.
- The IceStorm and admin configuration files.0 -
- Version of Ice you are using.
ICE-3.1.1
- Operating system.
Slackware 10.1
- The IceStorm and admin configuration files.
i use icestorm in icegrid:
<service-template id="IceStorm">
<parameter name="instance-name" default="${application}.IceStorm"/>
<parameter name="index" default=""/>
<parameter name="topic-manager-endpoints"/>
<parameter name="publish-endpoints"/>
<parameter name="flush-timeout" default="1000"/>
<service name="IceStorm${index}" entry="IceStormService,31:createIceStorm">
<dbenv name="${service}"/>
<adapter name="${service}.TopicManager" id="${instance-name}.TopicManager" endpoints="${topic-manager-endpoints}" register-p
rocess="true">
<object identity="${instance-name}/TopicManager" type="::IceStorm::TopicManager"/>
</adapter>
<adapter name="${service}.Publish" id="${instance-name}.Publish" endpoints="${publish-endpoints}">
<properties>
<property name="${service}.InstanceName" value="${instance-name}"/>
<property name="${service}.Flush.Timeout" value="${flush-timeout}"/>
</properties>
</adapter>
<property name="${service}.Trace.TopicManager" value="1"/>
<property name="${service}.Trace.Topic" value="2"/>
<property name="${service}.Trace.Flush" value="1"/>
<property name="${service}.Trace.Subscriber" value="1"/>
<property name="${service}.Trace.TopicManager" value="1"/>
</service>
</service-template>
<server-template id="IceStorm">
<parameter name="instance-name" default="${application}.IceStorm"/>
<parameter name="topic-manager-endpoints" default="default"/>
<parameter name="publish-endpoints" default="default"/>
<parameter name="flush-timeout" default="1000"/>
<icebox id="${instance-name}" exe="icebox" activation="on-demand">
<service-instance template="IceStorm"
instance-name="${instance-name}"
topic-manager-endpoints="${topic-manager-endpoints}"
publish-endpoints="${publish-endpoints}"
flush-timeout="${flush-timeout}"/>
</icebox>
</server-template>
<node name="config">
<server-instance template="IceStorm"
instance-name="${application}.Config"
topic-manager-endpoints="tcp -h 172.16.28.79 -p 46000"
publish-endpoints="tcp -h 172.16.28.79 -p 47000"
flush-timeout="2000"/>
</node>0 -
Hi,
The Ice::NoEndpointException indicates that the IceStorm server isn't reachable anymore at the time you try to destroy the topic. You need to figure out why this is the case.
This could be because the IceGrid node managing the IceStorm server isn't running anymore, because the IceStorm server is not running anymore and can't be restarted on-demand, etc.
To investigate this I would recommend to enable the following trace on the IceGrid registry:IceGrid.Registry.Trace.Locator=1
This should give you some insights on the reason why the locate request failed when you destroy the topic.
Cheers,
Benoit.0 -
I set
IceGrid.Registry.Trace.Locator=2
but registry has no any output
btw: IceStorm still running
why?0 -
i have resolve the problem, i have not set Ice.Default.Locator. when i use icestormadmin bellow:
icestormadmin --Ice.Default.Locator=DMQQIceGrid/Locator:tcp -h 10.2.75.77 -p 12000 --IceStorm.TopicManager.Proxy="Dmqq.Config/TopicManager:tcp -h 10.2.75.77 -p 40000"
, it's ok!0
