Hi
I'm not sure about any know issue.
BTW with 2.2 we upgraded Maven Indexer version which change locking
mechanism.
Maybe worth to try it.

Cheers
Olivier

On 29 January 2016 at 11:32, Charlie Kim <charl...@yahoo-inc.com.invalid>
wrote:

>
>
> "localhost-startStop-2" daemon prio=10 tid=0x000000000becb800 nid=0x7cf6
> waiting on condition [0x00007f47ad5d1000]
>    java.lang.Thread.State: WAITING (parking)
>         at sun.misc.Unsafe.park(Native Method)
>         - parking to wait for  <0x00000005914d55d8> (a
> java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
>         at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:867)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197)
>         at
> java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:945)
>         at
> org.apache.maven.index.context.DefaultIndexingContext.lockExclusively(DefaultIndexingContext.java:198)
>         at
> org.apache.maven.index.context.DefaultIndexingContext.close(DefaultIndexingContext.java:759)
>         at
> org.apache.maven.index.DefaultNexusIndexer.removeIndexingContext(DefaultNexusIndexer.java:222)
>
>
>
> pool-1-thread-1" prio=10 tid=0x000000000358e800 nid=0x5bbd waiting on
> condition [0x00007f47accc9000]
>    java.lang.Thread.State: WAITING (parking)
>         at sun.misc.Unsafe.park(Native Method)
>         - parking to wait for  <0x00000005914d55d8> (a
> java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
>         at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:867)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197)
>         at
> java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:945)
>         at
> org.apache.maven.index.context.DefaultIndexingContext.lockExclusively(DefaultIndexingContext.java:198)
>         at
> org.apache.maven.index.context.DefaultIndexingContext.close(DefaultIndexingContext.java:759)
>         at
> org.apache.maven.index.context.DefaultIndexingContext.doCommit(DefaultIndexingContext.java:677)
>         at
> org.apache.maven.index.context.DefaultIndexingContext.commit(DefaultIndexingContext.java:626)
>         at
> org.apache.maven.index.DefaultNexusIndexer.addArtifactToIndex(DefaultNexusIndexer.java:373)
>
>
> Hi there, it seems that Archiva was trying to close indexes on shutdown
> but failed. See
> https://archiva.apache.org/ref/1.4-M4/xref/org/apache/archiva/admin/repository/managed/DefaultManagedRepositoryAdmin.html#138I
> see 2 threads tries to lock.  One tries to add another tries to delete.Is
> there known issue about this?Thanks.We are running 1.4-M2




-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Reply via email to