Bug #2080

spread connect error

Added by Q. Li over 9 years ago. Updated over 9 years ago.

Status:ClosedStart date:11/09/2014
Priority:NormalDue date:
Assignee:Q. Li% Done:

0%

Category:Spread Connector
Target version:rsb-0.11

Description

I am using RSB for two computer(kuka-vision and kuka-arm) communication.
The communication can be constructed, but after a short time running, programe running in kuka-vision complain the following error.
in both computer I am using rsb.conf
[transport.spread]
enabled = 1
host = kuka-arm

SP_error: (-1) Illegal spread was provided
1415524406281 rsb.transport.spread.spreadconnection [FATAL]: Error connecting to '4803@kuka-arm': connection to spread daemon at 4803@kuka-arm failed, check port and hostname
terminate called after throwing an instance of 'rsb::CommException'
what(): Error connecting to '4803@kuka-arm': connection to spread daemon at 4803@kuka-arm failed, check port and hostname
Aborted

History

#1 Updated by J. Moringen over 9 years ago

  • Category set to Spread Connector
  • Status changed from New to Feedback
  • Assignee changed from J. Moringen to Q. Li
  • Target version set to rsb-0.11

Thanks for the report. Unfortunately, it does not contain enough information to diagnose the problem. Please provide a more detailed description according to the guidelines in the manual.

I can still say that something seems wrong:

SP_error: (-1) Illegal spread was provided
1415524406281 rsb.transport.spread.spreadconnection [FATAL]: Error connecting to '4803@kuka-arm': connection to spread daemon at 4803@kuka-arm failed, check port and hostname
terminate called after throwing an instance of 'rsb::CommException'
what(): Error connecting to '4803@kuka-arm': connection to spread daemon at 4803@kuka-arm failed, check port and hostname
Aborted

This should only happen when initially connecting to the Spread daemon. Does your program create and destroy RSB informers and/or listeners while it runs?

#2 Updated by Q. Li over 9 years ago

Thanks, Jan.
I find the problem. I am creating/destroy the informer during its running. My problem is solved.

#3 Updated by J. Moringen over 9 years ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF