[kepler-dev] proxy problems
ben leinfelder
leinfelder at nceas.ucsb.edu
Wed Nov 26 14:25:37 PST 2008
Peter,
You can bypass the registry query that occurs during Kepler startup by
modifying the $KEPLER/lib/config.xml file like so:
<!--set to 'true' to auto-refresh datasources (registry entries)
when Kepler first starts -->
<!--the delay attribute is the number of seconds to wait before
executing the update thread -->
<autoDataSourcesUpdate delay="0">false</autoDataSourcesUpdate>
I'm a bit confused as to why your "workaround" worked because I
believe those repositoryBundle.properties are not referenced during
start up.
-ben
On Nov 26, 2008, at 1:52 PM, Peter Reutemann wrote:
> Hi everybody
>
> I got a question for the Kepler gurus: is it possible to have a Kepler
> instance running that does *not* attempt to access the internet at
> all? E.g., turning off accessing EcoGrid services?
>
> The reason I'm asking is that it took me ages figuring out why my
> laptop (on a wireless network with proxy authentication for internet
> access) couldn't start up Kepler. Kepler was always hanging after some
> initial I/O, still displaying the splash screen. Only after adding the
> "-verbose" flag to the Java call in the kepler.sh script, did I find
> out, that it may be related to timeout issues due to attempted
> internet access (Java was loading web related classes, e.g.,
> sun.net.util.IPAddressUtils and sun.net.www.http.HttpClient just
> before Kepler stopped). And when I plugged my laptop into the wired
> network, it worked!
> Then the hunt for proxy parameters started, but I couldn't figure out
> where to set "Kepler-global" proxy settings and resorted to finding a
> way for turning off the Kepler-functionality attempting to access the
> internet. The only solution that worked for me was modifying the
> "repositoryBundle.properties" file in the
> "$KEPLER/configs/ptolemy/configs/kepler" directory, using "localhost"
> as the server address for the following properties:
> keplerRepository.registrypath
> keplerRepository.registryauth
>
> My Kepler build is not really the newest (if I'm not mistaken: trunk,
> rev 8022), so this issue might have been resolved already.
>
> Any input is appreciated!
>
> Cheers, Peter
> --
> Peter Reutemann, Dept. of Computer Science, University of Waikato, NZ
> http://www.cs.waikato.ac.nz/~fracpete/ Ph. +64 (7) 858-5174
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>
More information about the Kepler-dev
mailing list