I'm currently working on a Jini service that registers objects in at a lookupservice. I use the JoinManager class, from Jini 2.1, for the management of the registration of those objects. The service is already in use in our "labs" environment, but no when deploying it to our "production" environment problems occur.
The thing is that the object is never registered at the lookupservice. But when I add a DiscoveryListener to the LookupDiscoveryManager I use, I receive an event indicating that a ServiceRegistrar is discovered. And it is "serving" the correct lookup groups. But the joinset of the JoinManager stays empty and the ServiceIDListener I use never receives an event that the object has been registered at the lookup service (=reggie).
The service that is supposed to register the objects in at reggie is physically located at the same machine as reggie. The weird thing is that when I run this code from my developer machine it DOES register the objects. The only thing is that when doing that I use a LookupLocator to discover the lookup service instead of giving the lookup group String array. I have checked though that the lookup service is running correctly with a ‘service browser like’ tool.
If someone has experience with these kind of problems or could give me some pointers were to look to solve this problem, please do!
Previous Topic
