[jira] [Commented] (KARAF-1674) Abnormal Timeout with multiple maven repositories in pax-url

["Grzegorz Grzybek (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KARAF-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769833#comment-15769833 ] 

Grzegorz Grzybek commented on KARAF-1674:
-----------------------------------------

KARAF-4795 adds support for new timeout related options from pax-url 2.5.x. Here's {{etc/org.ops4j.pax.url.mvn.cfg}}:
{noformat}
#
# socket and connection configuration (pax-url-aether 2.5.0)
#
# default value for connection and read timeouts, when socket.readTimeout and socket.connectionTimeout
# are not specified
org.ops4j.pax.url.mvn.timeout = 5000
# timeout in ms when establishing http connection during artifact resolution
org.ops4j.pax.url.mvn.socket.connectionTimeout = 5000
# timeout in ms when reading data after connecting to remote repository
org.ops4j.pax.url.mvn.socket.readTimeout = 30000
# SO_KEEPALIVE option for sockets, defaults to false
org.ops4j.pax.url.mvn.socket.keepAlive = false
# SO_LINGER option for sockets, defaults to -1
org.ops4j.pax.url.mvn.socket.linger = -1
# SO_REUSEADDR option for sockets, defaults to false
org.ops4j.pax.url.mvn.socket.reuseAddress = false
# TCP_NODELAY option for sockets, defaults to true
org.ops4j.pax.url.mvn.socket.tcpNoDelay = true
# Configure buffer size for HTTP connections (output and input buffers), defaults to 8192 bytes
org.ops4j.pax.url.mvn.connection.bufferSize = 8192
# Number of connection retries after failure is detected in http client. httpclient uses default value "3"
org.ops4j.pax.url.mvn.connection.retryCount = 3
{noformat}


> Abnormal Timeout with multiple maven repositories in pax-url
> ------------------------------------------------------------
>
>                 Key: KARAF-1674
>                 URL: https://issues.apache.org/jira/browse/KARAF-1674
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 2.2.8
>         Environment: karaf 2.2.8 with equinox running on debian with java 1.7.0_03
>            Reporter: Sammy Ramareddy
>            Assignee: Grzegorz Grzybek
>             Fix For: 4.1.0, 4.0.8
>
>
> I'm having a strange issue where karaf needs a lot of time (around 5-10minutes) to generate for the first time the "features" tab in the webconsole or give some feedback to a "features:list" command in the ssh console.
> I currently have the following urls configured in $KARAF_HOME/etc/org.ops4j.pax.url.mvn.cfg:
> org.ops4j.pax.url.mvn.repositories= \
>     http://192.168.2.224:8080/artifactory/repo@snapshots, \
>     http://i0019231.subdomain.domain.tld:8080/artifactory/repo@snapshots
> The second url is actually pointing to the same artifactory repository as the first one, just running with another IP (within our VPN subnet).
> Once in production, karaf will run outside our network and will need to reach our artifactory server through a VPN connection, hence the need for two urls.
> The problem is the following: when the VPN connection is *not* running, and thus "i0019231.subdomain.domain.tld" is not reachable (its IP is 172.21.x.x), karaf needs 5-10 minutes to be able to start the features-plugin.
> When this is happening, the following entry is in the Karaf log:
> "failed to open bundleresource://78.fwk10937487/"
> where bundle 78 is org.apache.karaf.webconsole.features
> This issue happens only when the VPN client is not running and thus the second repository is not reachable. When the second url is reachable, then everything runs fine.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)