You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Conrad Pilloud <co...@ngc.com> on 2008/09/10 01:11:38 UTC
RMI Component looks up wrong name
Hi,
I'm using Camel 1.4.0 It appears the RMI component is not pulling the
right name from the URI I defined in my routebuilder.
In a separate application (the one I'm trying to connect and send data to),
I've bound a remote object in the RMI Registry as: "GDRService". (I even
wrote a little app to list the RMI registry entries and it does indeed show
up as "GDRService").
However, my camel route: .to("rmi://localhost:1099/GDRService");
produces this result...
java.rmi.NotBoundException: /GDRService
at sun.rmi.registry.RegistryImpl.lookup(RegistryImpl.java:106)
at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
....
I think this is the problem...
According to the code for
http://svn.apache.org/viewvc/activemq/camel/trunk/components/camel-rmi/src/main/java/org/apache/camel/component/rmi/RmiEndpoint.java?view=markup
RMIEndPoint
public String getName() {
String path = uri.getPath();
if (path == null) {
path = uri.getSchemeSpecificPart();
}
return path;
}
I believe uri.getPath() is returning "/GDRService" and not "GDRService" and
thus, Camel can't find the actual service.
Am I doing something wrong? Or is this a camel-rmi bug?
Cheers
Conrad
--
View this message in context: http://www.nabble.com/RMI-Component-looks-up-wrong-name-tp19403188s22882p19403188.html
Sent from the Camel - Users mailing list archive at Nabble.com.
RE: RMI Component looks up wrong name
Posted by Conrad Pilloud <co...@ngc.com>.
Done. Please see https://issues.apache.org/activemq/browse/CAMEL-890
CAMEL-890
Cheers
Conrad
Claus Ibsen wrote:
>
> Hi
>
> Looks like a bug. Could you report it in JIRA
> http://activemq.apache.org/camel/support.html
>
>
>
>
> Med venlig hilsen
>
> Claus Ibsen
> ......................................
> Silverbullet
> Skovsgårdsvænget 21
> 8362 Hørning
> Tlf. +45 2962 7576
> Web: www.silverbullet.dk
>
--
View this message in context: http://www.nabble.com/RMI-Component-looks-up-wrong-name-tp19403188s22882p19415049.html
Sent from the Camel - Users mailing list archive at Nabble.com.
RE: RMI Component looks up wrong name
Posted by Claus Ibsen <ci...@silverbullet.dk>.
Hi
Looks like a bug. Could you report it in JIRA
http://activemq.apache.org/camel/support.html
Med venlig hilsen
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-----Original Message-----
From: Conrad Pilloud [mailto:conrad.pilloud@ngc.com]
Sent: 10. september 2008 01:12
To: camel-user@activemq.apache.org
Subject: RMI Component looks up wrong name
Hi,
I'm using Camel 1.4.0 It appears the RMI component is not pulling the
right name from the URI I defined in my routebuilder.
In a separate application (the one I'm trying to connect and send data to),
I've bound a remote object in the RMI Registry as: "GDRService". (I even
wrote a little app to list the RMI registry entries and it does indeed show
up as "GDRService").
However, my camel route: .to("rmi://localhost:1099/GDRService");
produces this result...
java.rmi.NotBoundException: /GDRService
at sun.rmi.registry.RegistryImpl.lookup(RegistryImpl.java:106)
at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
....
I think this is the problem...
According to the code for
http://svn.apache.org/viewvc/activemq/camel/trunk/components/camel-rmi/src/main/java/org/apache/camel/component/rmi/RmiEndpoint.java?view=markup
RMIEndPoint
public String getName() {
String path = uri.getPath();
if (path == null) {
path = uri.getSchemeSpecificPart();
}
return path;
}
I believe uri.getPath() is returning "/GDRService" and not "GDRService" and
thus, Camel can't find the actual service.
Am I doing something wrong? Or is this a camel-rmi bug?
Cheers
Conrad
--
View this message in context: http://www.nabble.com/RMI-Component-looks-up-wrong-name-tp19403188s22882p19403188.html
Sent from the Camel - Users mailing list archive at Nabble.com.