Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] [m2e-users] updated http transport, please test 
You sure you use the same settings.xml file both in Jenkins and when
running the build on command line?

That test goes to a real remote repository, iirc, so I wonder if you end
up using different repository url and/or proxy configuration when
running on command line vs Jenkins. Sadly, neither m2e nor okhttp
connector have relevant log, so maybe adding debug log message is the
first step to troubleshoot.

--
Regards,
Igor

On 2014-05-02, 7:16, Fred Bricon wrote:

I have Jenkins server running on a MacMini and no matter what,
m2e-core-tests time out every time.
Here's what a threaddump gives me :
"main" prio=5 tid=0x00007faef380a000 nid=0x507 runnable [0x00007fff56d30000]
    java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:152)
at java.net.SocketInputStream.read(SocketInputStream.java:122)
at com.squareup.okhttp.internal.okio.Okio$2.read(Okio.java:113)
at
com.squareup.okhttp.internal.okio.RealBufferedSource.read(RealBufferedSource.java:48)
at
com.squareup.okhttp.internal.http.HttpConnection$FixedLengthSource.read(HttpConnection.java:417)
at
com.squareup.okhttp.internal.okio.RealBufferedSource$1.read(RealBufferedSource.java:168)
at java.io.InputStream.read(InputStream.java:101)
at
org.eclipse.m2e.core.internal.index.nexus.AetherClientResourceFetcher.retrieve(AetherClientResourceFetcher.java:87)
at
org.apache.maven.index.updater.AbstractResourceFetcher.retrieve(AbstractResourceFetcher.java:35)
at
org.apache.maven.index.updater.DefaultIndexUpdater$LocalCacheIndexAdaptor.setIndexFile(DefaultIndexUpdater.java:700)
at
org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:829)
at
org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:135)
at
org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.updateRemoteIndex(NexusIndexManager.java:1127)
at
org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.updateIndex(NexusIndexManager.java:1087)
- locked <0x00000007f0cf4f00> (a java.lang.Object)
at
org.eclipse.m2e.core.internal.index.nexus.NexusIndex.updateIndex(NexusIndex.java:145)
at
org.eclipse.m2e.tests.internal.index.NexusIndexManagerSearchTest.updateRepo(NexusIndexManagerSearchTest.java:81)
at
org.eclipse.m2e.tests.internal.index.NexusIndexManagerSearchTest.setUp(NexusIndexManagerSearchTest.java:55)

"Funny" thing is tests run fine when executed from CLI on the same machine


On Thu, May 1, 2014 at 1:54 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>> wrote:

    There was pretty bad bug in m2e http transport used in Luna/1.5 M6 and
    most of the earlier 1.5 builds [1]. I pushed a fix earlier today and new
    m2e build is available from the snapshot repository [2]. I am quite
    certain that http digest auth and ntlm are still not supported, but
    basic auth and ssl are expected to work reliably now. Please test this
    new m2e version in your environment(s) and report any oddities with http
    transport either here or through bugzilla.


    [1] https://bugs.eclipse.org/bugs/__show_bug.cgi?id=430772
    <https://bugs.eclipse.org/bugs/show_bug.cgi?id=430772>
    [2]
    http://repository.takari.io:__8081/nexus/content/sites/m2e.__extras/m2e/1.5.0/N/LATEST/
    <http://repository.takari.io:8081/nexus/content/sites/m2e.extras/m2e/1.5.0/N/LATEST/>

    --
    Regards,
    Igor
    _________________________________________________
    m2e-users mailing list
    m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
    https://dev.eclipse.org/__mailman/listinfo/m2e-users
    <https://dev.eclipse.org/mailman/listinfo/m2e-users>




--
"Have you tried turning it off and on again" - The IT Crowd


_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev

Back to the top