I can't help you with MyEclipse, but to use the patch you have to apply the
redback patch (to the right version of redback - the one used by your
version of archiva), build it. Then you need to apply the archiva patch and
build archiva. The archiva patch actually includes a small bit of spring
conf
Hello, Brent
Per you suggestion, I applied REDBACK-266 patch onto archiva source code
checked out from svn repository and imported to my eclipse as existing
maven project, and run maven packaging inside MyEclipse, I got following
error
Compilation failure
/home/yqian/Workspaces/MyEclipse
8.6/arch
Hi,
There are multiple tools to do this, but Java 6 comes with jconsole and
there's a third party plugin called topthreads that allows you to see the
thread, class and method that is taking up time. It's not a full profiler,
but it's simple enough to get some decent information about where the iss
Update: we updated Archiva to 1.3.4. last Wednesday same problem.
Yesterday archiva used 100% of CPU since 14:06
14:02 1%
14:04 21%
14:06 100%
Am 16.02.2011 02:24, schrieb Brett Porter:
>
> On 16/02/2011, at 2:14 AM, Benjamin Knoth wrote:
>
>> Sorry only one java process is running.
>> But two
Yesterday archiva used 100% of CPU since 14:06
14:02 1%
14:04 21%
14:06 100%
Am 16.02.2011 02:24, schrieb Brett Porter:
>
> On 16/02/2011, at 2:14 AM, Benjamin Knoth wrote:
>
>> Sorry only one java process is running.
>> But two processes from archiva.
>> If i start archiva dump i get this two