[ 
https://issues.apache.org/jira/browse/FELIX-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634767#action_12634767
 ] 

Felix Meschberger commented on FELIX-738:
-----------------------------------------

> we would have the same problem, as the box has no internet access.

If the box is behind a firewill, the firewall admin should actually have set up 
the firewall to send back an error in case of trying to connect to the 
internet. So a timeout should not happen.

> Make it possible to disable the lookup and/or the entire "bundle repository" 
> bundle by some config value. 

We could define a framework property and or a Config Admin property, which 
would disable the OBR lookup for the bundle list. Of course, I would think to 
enable OBR by default ;-)

> Is it really necessary for the "bundle repository" bundle to access....

The bundle list page provides the "Update" buttons. These are enabled if the 
OBR might have a more recent version of the respective bundle. To be able to 
check the OBR, the URL must of course be accessed. If you can go by without OBR 
updates from within the bundles list, then OBR access may be switched off (see 
above).


So I propose to define a property -- say 
org.apache.felix.webconsole.bundle.obr.disable -- which is false by default (if 
missing or wrong value). It is checked as a framework propery and as a 
ConfigurationAdmin configuration property, where the ConfigurationAdmin setting 
overruels the framework property.

WDYT ?

> 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
>         Environment: Linux box without internet access (firewalled intranet)
>            Reporter: Mike Pfaff
>            Priority: Minor
>
> 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