Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Multi-Protocol: wrong URL generated by RemoteObjectHelper, when enabling an active object for PAMR protocol with a custom name #1274

Open
activeeon-bot opened this issue Aug 18, 2014 · 1 comment
Open

Multi-Protocol: wrong URL generated by RemoteObjectHelper, when enabling an active object for PAMR protocol with a custom name #1274

activeeon-bot opened this issue Aug 18, 2014 · 1 comment
Labels
severity:trivial type:bug

Comments

@activeeon-bot
Copy link

Original issue created by Lorenzo Cantelmi on 18, Aug 2014 at 15:10 PM - PALIGHT-65

According with the attached files, when I try to enable a ServerObject for PAMR protocol, the URL for reaching it is wrong (see log file):

it is pamr://node/myActiveServerObject, instead of pamr://1/myActiveServerObject

Basically, RemoteObjectHelper generates an URL taking the hostname (a String), instead of AgentID, so could not be parsed as Long object.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
severity:trivial type:bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@activeeon-bot