RE: How to remove an artifact

[Engebakken Geir <ge...@edb.com>]

Not able to help, sorry. I did exactly as proposed and like you said you did and that worked (fortunately) for us. I think there is a patch in the latest Archiva beta release to remove artifacts, so maybe that is a way to go,  although this is not a released version as far as I remember, just a milestone release, so we have opted to wait until an official release.



Geir

-----Original Message-----
From: oby1 [mailto:oren@clearspring.com] 
Sent: 29. desember 2008 20:03
To: users@archiva.apache.org
Subject: RE: How to remove an artifact


After removing the archiva database and .index directories, archiva failed to start with the following exception in archiva.log:

[main] ERROR JPOX.RDBMS.Schema  - Failed initialising databas e. Please check that your database JDBC driver is accessible, and the database URL an d username/password are correct. Exception : Cannot create PoolableConnectionFactory (Failed to start database 'db/users', see the next exception for details.)
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFacto ry (Failed to start database 'db/users', see the next exception for
details.)
        at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSour
ce.java:1225)
        at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.
java:880)
        at org.jpox.util.FailoverUtils.getConnection(FailoverUtils.java:51)
        at org.jpox.store.rdbms.RDBMSManager.<init>(RDBMSManager.java:244)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
        at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAcc
essorImpl.java:39)
        at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstr
uctorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at org.jpox.util.ClassUtils.newInstance(ClassUtils.java:73)
        at
org.jpox.store.StoreManagerFactory.getStoreManager(StoreManagerFactory.jav
a:73)
...
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: SQL Exception: Failed to start database 'db/users', see the next exception  for details.
        at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown
Source)
        at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown
Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
Source)
        at
org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown
Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(Unknown
Source)
        at org.apache.derby.jdbc.Driver30.getNewEmbedConnection(Unknown
Source)
        at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) ... 70 more

Strangely enough, it had trouble opening the user db even though I only removed the archiva db.  Replacing the archiva db didn't help (I made a backup before removing) - archiva still wouldn't start with the same error about the user db.  I had to remove both the archiva and user db's to get archiva to start up again.  Having to recreate all the user accounts each time I want to remove something from the repository is something of an inconvenience.

Any help would be much appreciated,

    -- Oren



drhelmer wrote:
> 
> I had the same issue, and was also a bit afraid of what I was doing, 
> but jumped into it and followed the instructions to remove the archiva 
> database and .index file for the repos, and it worked ok, so just go 
> ahead!
> 
> 
> 
> Geir
> 
> -----Original Message-----
> From: Wendy Smoak [mailto:wsmoak@gmail.com]
> Sent: 26. november 2008 19:04
> To: users@archiva.apache.org
> Subject: Re: How to remove an artifact
> 
> Are you concerned about people building their projects?  You're not 
> touching the repository content, just the index and database, which 
> will be re-created.
> 
> If the scheduled scanning isn't doing the job, then this is the 
> easiest way to work around the problem.
> 
> --
> Wendy
> 
> On Wed, Nov 26, 2008 at 10:13 AM, solo1970 
> <so...@ericsson.com> wrote:
>>
>> Seems quite drastic....
>>
>> I have lots of people depending on the repository and somehow don't 
>> feel very secure doing that....
>>
>> No other solution???
> 
> 

--
View this message in context: http://www.nabble.com/How-to-remove-an-artifact-tp15005386p21207601.html
Sent from the archiva-users mailing list archive at Nabble.com.