Hi,
as the error occurs now frequently - I added the artifactory.log for the error.
The error is obious (Too many open files) - so is there a way to avoid this ?
I now switched of the "Nexus Indexer Support" - does this affect the system
somehow ? And could this solve the problem ?
2011-05-10 01:59:37,723 [art-exec-21755] [INFO ] (o.a.s.a.ArchiveIndexer:96) -
The content of the archive: 'RemoteCorba-0.3-SNAPSHOT-tests.jar' was indexed
successfully.
2011-05-10 01:59:39,337 [jackrabbit-pool-1] [WARN ]
(o.a.j.c.q.l.LazyTextExtractorField:180) - Failed to extract text from a binary
property
org.apache.jackrabbit.core.data.DataStoreException: Error opening input stream
of
/u01/open-dev/opt/artifactory/data/filestore/9c/12/c0/9c12c0e3c726e239ac312e73a4f4df4e9acb4719
at
org.artifactory.jcr.jackrabbit.ArtifactoryDbDataRecord.getStream(ArtifactoryDbDataRecord.java:139)
[artifactory-core-2.2.5.jar:na]
at
org.apache.jackrabbit.core.value.BLOBInDataStore.getStream(BLOBInDataStore.java:101)
[jackrabbit-core-jfrog-2.1.0a.jar:2.1.0a]
at
org.apache.jackrabbit.core.value.InternalValue.getStream(InternalValue.java:686)
[jackrabbit-core-jfrog-2.1.0a.jar:2.1.0a]
at
org.apache.jackrabbit.core.query.lucene.LazyTextExtractorField$ParsingTask.run(LazyTextExtractorField.java:172)
[jackrabbit-core-jfrog-2.1.0a.jar:2.1.0a]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
[na:1.6.0_24]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
[na:1.6.0_24]
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
[na:1.6.0_24]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
[na:1.6.0_24]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
[na:1.6.0_24]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[na:1.6.0_24]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[na:1.6.0_24]
at
org.apache.jackrabbit.core.RepositoryImpl$ThreadWrapper.run(RepositoryImpl.java:276)
[jackrabbit-core-jfrog-2.1.0a.jar:2.1.0a]
at java.lang.Thread.run(Thread.java:662) [na:1.6.0_24]
Caused by: java.io.FileNotFoundException:
/u01/open-dev/opt/artifactory/data/filestore/9c/12/c0/9c12c0e3c726e239ac312e73a4f4df4e9acb4719
(Too many open files)
at java.io.FileInputStream.open(Native Method) [na:1.6.0_24]
at java.io.FileInputStream.<init>(FileInputStream.java:106)
[na:1.6.0_24]
at
org.artifactory.jcr.jackrabbit.ArtifactoryDbDataRecord$DataRecordFileStream.<init>(ArtifactoryDbDataRecord.java:187)
[artifactory-core-2.2.5.jar:na]
at
org.artifactory.jcr.jackrabbit.ArtifactoryDbDataRecord.getStream(ArtifactoryDbDataRecord.java:136)
[artifactory-core-2.2.5.jar:na]
... 12 common frames omitted
2011-05-10 02:13:02,555 [art-exec-21751] [INFO ]
(o.a.a.s.GarbageCollectorInfo:82) - Artifactory Jackrabbit's datastore garbage
collector report:
Total execution: 4068043ms
Data Store Query: 2056023ms
Binary Properties Query: 85801ms
Total Scanning: 3701008ms
Deletion execution: 367035ms
Initial element count: 50295
Bereaved nodes: 0
Elements cleaned: 3953
Initial size: 1,67 GB
Total size cleaned: 119,46 MB
Current total size: 1,55 GB
Thanks
-----Original Message-----
From: Noam Y. Tenne <[email protected]>
To: artifactory-users <[email protected]>
Sent: Tue, May 3, 2011 1:45 pm
Subject: Re: [Artifactory-users] Return code 500
Hi,
The indexing messages you see are actually from our own archive indexer, not
the Nexus indexer task.
If you're running Artifactory on a JVM of version 6+, you can configure
Artifactory to log a thread dump when a lock timeout occurs; this should help
us investigate this issue.
To switch on the thread dump, edit
${ARTIFACTORY_HOME}/etc/artifactory.system.properties by setting the property
"artifactory.locks.debugTimeouts" to true and restart Artifactory.
Please send us the log after the timeout occurs again.
HTH,
Noam
On Tue, May 3, 2011 at 8:35 AM, <[email protected]> wrote:
Hi,
arbitrarily our builds faile because of a Return code is: 500
if I look at the artifactory log I see at that time (failure happend at 04:03)
2011-05-03 03:55:56,877 [art-exec-19001] [INFO ] (o.a.s.a.ArchiveIndexer:96) -
The content of the archive: 'artifact-0.3-SNAPSHOT.jar' was indexed
successfully.
2011-05-03 03:56:13,779 [art-exec-19002] [INFO ] (o.a.s.a.ArchiveIndexer:96) -
The content of the archive: 'artifact-0.3-SNAPSHOT-publish.jar' was indexed
successfully.
2011-05-03 04:03:06,151 [pool-1-thread-16] [ERROR] (o.a.w.s.RepoFilter :139) -
Sending HTTP error code 500: WRITE lock on LockEntryId
repo:foo/bar/publish/artifact/0.3-SNAPSHOT/artifact-0.3-SNAPSHOT-publish.jar
not acquired in 120 seconds. Lock info:
java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock@2090127e[Locked by
thread art-exec-19002].
Can someone say more in detail what failed here ?
Apparently something with the indexer is the problem... On the Services ->
Indexer tab we have the indexer enabled with 24h Interval. Shall we configure
this differently ?
Thanks
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
