This relates to http://issues.jfrog.org/jira/browse/RTFACT-1855, which has
been addressed and resolved in 2.1 (soon to be released).
The error that you see means your datastore will not be cleaned up from
deleted artifacts. This affects the storage size used, but should not affect
the normal operation of Artifactory.
Another, preferable option is to use an external database like MySQL.
Yoav
On Tue, Sep 29, 2009 at 2:46 PM, Jeroen De Vries <
[email protected]> wrote:
> Hello,
>
>
>
>
>
> I reinstalled our artifactory on WebSphere, and I now use the Filesystem
> datastore file provided with the standalone artifactory (because WebSphere
> won’t cooperate nicely with the standard Derby DB, and MySQL is not an
> option anymore due to persistent problems with it). Now, we have a few
> errors in the error log, which I am still looking at. The one that most
> worries me is this one:
>
> 2009-09-29 14:34:44,542 [pool-1-thread-17] [ERROR]
> (o.a.j.JcrServiceImpl:785) - Jackrabbit's datastore garbage collector
> execution failed.
>
> java.lang.ClassCastException: org.apache.jackrabbit.core.data.FileDataStore
> incompatible with org.artifactory.jcr.jackrabbit.ArtifactoryDbDataStoreImpl
>
> at
> org.artifactory.jcr.jackrabbit.ArtifactoryGarbageCollector.<init>(ArtifactoryGarbageCollector.java:107)
> [artifactory-core-2.0.8.jar:na]
>
> at
> org.apache.jackrabbit.core.GarbageCollectorFactory.createDataStoreGarbageCollector(GarbageCollectorFactory.java:68)
> [artifactory-core-2.0.8.jar:na]
>
> at
> org.artifactory.jcr.JcrServiceImpl.garbageCollect(JcrServiceImpl.java:767)
> [artifactory-core-2.0.8.jar:na]
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [na:1.5.0]
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
> [na:1.5.0]
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [na:1.5.0]
>
> at java.lang.reflect.Method.invoke(Method.java:618) [na:1.5.0]
>
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
> [spring-aop-2.5.5.jar:2.5.5]
>
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
> [spring-aop-2.5.5.jar:2.5.5]
>
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
> [spring-aop-2.5.5.jar:2.5.5]
>
> at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
> [spring-tx-2.5.5.jar:2.5.5]
>
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
> [spring-aop-2.5.5.jar:2.5.5]
>
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> [spring-aop-2.5.5.jar:2.5.5]
>
> at $Proxy21.garbageCollect(Unknown Source) [na:na]
>
> at
> org.artifactory.jcr.schedule.JcrGarbageCollector.onExecute(JcrGarbageCollector.java:37)
> [artifactory-core-2.0.8.jar:na]
>
> at
> org.artifactory.jcr.schedule.JcrGarbageCollector.onExecute(JcrGarbageCollector.java:30)
> [artifactory-core-2.0.8.jar:na]
>
> at
> org.artifactory.schedule.quartz.QuartzCommand.execute(QuartzCommand.java:42)
> [artifactory-core-2.0.8.jar:na]
>
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
> [quartz-1.6.3.jar:1.6.3]
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> [na:1.5.0]
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> [na:1.5.0
>
>
>
> I guess this is just a config issue? Any ideas?
>
>
>
>
>
> Regards,
>
> Jeroen
>
>
>
> [image: BTR Services] *We assist Banks on their Transformation Road* *Jeroen
> De Vries*
> *Junior Java Developer* Groene Hofstraat 31
> 2850 Boom
> Belgium
> [email protected] tel: +32 3 450 89 80
> fax: +32 3 450 89 89
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> - DISCLAIMER -
> This message contains confidential information and is intended only for
> [email protected]. If you are not
> [email protected], you should not disseminate,
> distribute or copy this e-mail. Please notify
> [email protected] immediately by e-mail if you have received
> this e-mail by mistake and delete this e-mail from your system. E-mail
> transmission cannot be guaranteed to be secure or error-free as information
> could be intercepted, corrupted, lost, destroyed, arrive late or incomplete,
> or contain viruses. Jeroen De Vries therefore does not accept liability for
> any errors or omissions in the contents of this message, which arise as a
> result of e-mail transmission. If verification is required please request a
> hard-copy version.
> ------------------------------
>
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
