Bugzilla – Bug 4560
Changing default ports with ManagedJobFactoryClientHelper
Last modified: 2006-10-04 17:35:34
You need to
before you can comment on or make changes to this bug.
ServiceHost.getDefaultPort(). The first call works fine. However, if a callback
container is started, ServiceHost.setDefaults() gets called, which sets a new
default port. The next call to
ManagedJobFactoryClientHelper.getServiceURL(server).getURL() will return the
callback container port.
There's nothing much GRAM can do about this. It seems to me that setting the
defaults dynamically is a bad idea. I'm reassigning this to Jarek since I'm not
sure what to do with it.
First, if the ManagedJobFactoryClientHelper API is only supposed to be used on
the client-side then I think it should not use ServiceHost API. But I will
change the container code not to set the host/port defaults if a container is
started on the client to handle notifications.
Committed fixes (as described before) to trunk and globus_4_0_branch.