[ 
https://issues.apache.org/jira/browse/FELIX-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Felix Meschberger closed FELIX-738.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: webconsole-1.2.2

Replaced the "Update" button by a new "Refresh" button on the bundles page. 
This should prevent the display delay and adds new functionality to forcibly 
refresh, that is re-wire, a single bundle.

> First access to "Bundles" web console tab takes a long time if the server has 
> no internet access 
> -------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-738
>                 URL: https://issues.apache.org/jira/browse/FELIX-738
>             Project: Felix
>          Issue Type: Bug
>          Components: Web Console
>    Affects Versions: webconsole-1.2.0
>         Environment: Linux box without internet access (firewalled intranet)
>            Reporter: Mike Pfaff
>            Assignee: Felix Meschberger
>            Priority: Minor
>             Fix For: webconsole-1.2.2
>
>
> Log entries:
> [...]
> RepositoryAdminImpl: Exception creating repository - 
> java.net.ConnectException: Operation timed out
> RepositoryAdminImpl: Ignoring repository 
> http://oscar-osgi.sourceforge.net/obr2/repository.xml
> [...]
> I know that the repo URL is outdated, but even with the new URL 
> http://felix.apache.org/obr/releases.xml we would have the same problem, as 
> the box has no internet access.
> Possible solutions and ideas:
> - Make it possible to disable the lookup and/or the entire "bundle 
> repository"  bundle by some config value.
> - Set the timeout to a lower value (maybe 5 or 10 seconds)
> - Is it really necessary for the "bundle repository" bundle to access the 
> repo URL when you go to the "Bundle" web console tab? (It makes sense for the 
> "OSGi Repository" web console tab).
> - Stopping/Uninstalling the "bundle repository" bundle poses some kind of 
> chicken/egg problem, as one would have to use the "Bundle" web console tab - 
> which is where the problem occurs - for that.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to