Skip to content
This repository has been archived by the owner on May 19, 2023. It is now read-only.

[common_tools] Same node name problem when concert checker is running. #76

Open
2 tasks
dwlee opened this issue Jul 13, 2015 · 0 comments
Open
2 tasks

Comments

@dwlee
Copy link
Contributor

dwlee commented Jul 13, 2015

Symptom
ConcertChecker is wrapping for easily searching concert information. It get concert information via creating ros node and subscribing specific topic and then ros node created this process is shutdown after getting concert infomation. However, if some error( especially timeout error) is happened in this process, ros node can not be terminated and Concert checker is received following error when it again tried to getting concert information.

I/Registrar﹕ MasterXmlRpcEndpoint URI: http://192.168.10.32:11311
I/Registrar﹕ Registering publisher: Publisher<PublisherDefinition<PublisherIdentifier<NodeIdentifier</master_info_node, http://192.168.10.51:42322/>, TopicIdentifier</rosout>>, Topic<TopicIdentifier</rosout>, TopicDescription<rosgraph_msgs/Log, acffd30cd6b6de30f120938c17c593fb>>>>
I/Registrar﹕ Response<Success, Registered [/master_info_node] as publisher of [/rosout], [http://192.168.10.32:55680/]>
I/DefaultPublisher﹕ Publisher registered: Publisher<PublisherDefinition<PublisherIdentifier<NodeIdentifier</master_info_node, http://192.168.10.51:42322/>, TopicIdentifier</rosout>>, Topic<TopicIdentifier</rosout>, TopicDescription<rosgraph_msgs/Log, acffd30cd6b6de30f120938c17c593fb>>>>

Solution

  • Adding finally after try-catch
  • Launching ros node with anonymous
@dwlee dwlee mentioned this issue Jul 16, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant