Unfortunately, there isn't an easy way (we probably should provide a way to
disable this). Basically, in your situation you could try either of the
following:
a) build felix yourself and rip out this code:
try
{
(new URL("http://felix.extensions:9/";)).openConnection();
}
catch (Throwable t)
{
// This doesn't matter much - we only need the above to
init the url subsystem
}
in src/main/java/org/apache/felix/framework/ExtensionManager.java
b) provide your own name service provider that can handle the name for you
(which probably is to much work but possible iirc - ping me again if you
need more info on this).
regards,
Karl
On Thu, Jan 30, 2014 at 2:50 PM, Daniel McGreal <[email protected]> wrote:
> Hi there,
>
> Some bug in my deployment environment causes web requests for
> non-resolveable DNS requests to take a prohibitively long time to time-out.
> For some reason, Felix makes a bunch of these requests at startup asking
> for felix.extensions, a request which is obviously doomed to fail.
>
> Does anyone know how these requests can be prevented? I do not have any
> control over the deployment environment to fix the timeout of DNS requests.
>
> Best, Dan.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
Karl Pauls
[email protected]
http://twitter.com/karlpauls
http://www.linkedin.com/in/karlpauls
https://profiles.google.com/karlpauls
