We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System Info
Bug Description
ROS2 service clients are unable to detect any available (matching) service instance.
Expected Behavior
ROS2 service clients should be able to detect available (matching) service instances.
How to Reproduce
rmw_connext_ws
rti_connext_dds-6.1.2
rti_connext_dds_micro-3.0.3.28
src/rmw_connextdds
COLCON_IGNORE
docker run -it -v $PWD:/home -w /home osrf/ros:humble-desktop in rmw_connext_ws
source ./rti_connext_dds-6.1.2/resource/scripts/rtisetenv_x64Linux4gcc7.3.0.bash
colcon build
source install/setup.bash
export RMW_IMPLEMENTATION=rmw_connextddsmicro
export RMW_CONNEXT_INITIAL_PEERS="_shmem://, 127.0.0.1"
ros2 run examples_rclcpp_minimal_service service_main & ros2 run examples_rclcpp_minimal_client client_main
This will result in this error:
Workarounds
The issues stems (at least partially) from the fact that RMW_Connext_Client::is_service_available uses
which are both only implemented as stubs in connext micro: both will usually return DDS_RETCODE_UNSUPPORTED.
Inspired by https://github.com/ros2/rmw_connext/blob/5557440c0a16dd272812587f17801975a7fa7632/rmw_connext_cpp/src/rmw_service_server_is_available.cpp#L93 I could come up with cwecht@969171a .
With that fix there is no error anymore but the service is found.
Please note that I also head to adjust the RMW_CONNEXT_LIMIT_DEFAULT_MAX to 256 (32 and 64 didn't work).
The text was updated successfully, but these errors were encountered:
asorbini
Successfully merging a pull request may close this issue.
System Info
Bug Description
ROS2 service clients are unable to detect any available (matching) service instance.
Expected Behavior
ROS2 service clients should be able to detect available (matching) service instances.
How to Reproduce
rmw_connext_ws
rti_connext_dds-6.1.2
(containing the whole Pro package as well as the micro package inrti_connext_dds_micro-3.0.3.28
)src/rmw_connextdds
COLCON_IGNORE
in rmw_connext_ws/rti_connext_dds-6.1.2docker run -it -v $PWD:/home -w /home osrf/ros:humble-desktop in rmw_connext_ws
source ./rti_connext_dds-6.1.2/resource/scripts/rtisetenv_x64Linux4gcc7.3.0.bash
colcon build
source install/setup.bash
export RMW_IMPLEMENTATION=rmw_connextddsmicro
export RMW_CONNEXT_INITIAL_PEERS="_shmem://, 127.0.0.1"
ros2 run examples_rclcpp_minimal_service service_main & ros2 run examples_rclcpp_minimal_client client_main
This will result in this error:
Workarounds
The issues stems (at least partially) from the fact that RMW_Connext_Client::is_service_available uses
which are both only implemented as stubs in connext micro: both will usually return DDS_RETCODE_UNSUPPORTED.
Inspired by https://github.com/ros2/rmw_connext/blob/5557440c0a16dd272812587f17801975a7fa7632/rmw_connext_cpp/src/rmw_service_server_is_available.cpp#L93 I could come up with cwecht@969171a .
With that fix there is no error anymore but the service is found.
Please note that I also head to adjust the RMW_CONNEXT_LIMIT_DEFAULT_MAX to 256 (32 and 64 didn't work).
The text was updated successfully, but these errors were encountered: