Archiva

Error while deploying an artifact to archiva

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 1.0.1
  • Fix Version/s: 1.1
  • Component/s: None
  • Labels:
    None
  • Environment:
  • Number of attachments :
    0

Description

Our integration server (bamboo) more and more often fails to upload artifacts on archiva.
On the integration server side we receive an error like :

[INFO] Error deploying artifact: Failed to transfer file: http://host/​archiva/​repository/snapshots/​groupId/artifactId/0.18.0-SNAPSHOT/​artifactId-0.18.0-20080328.093110-37-tests.jar. Return code is: 500 Internal Server Error

On the archiva side we have this error :

2008/03/28 10:31:30 | Mar 28, 2008 10:31:30 AM org.mortbay.jetty.servlet.ServletHandler handle
INFO   | jvm 1    | 2008/03/28 10:31:30 | WARNING: /archiva/repository/generali-snapshots/fr/generali/gael/commun/gael-common-domain/0.18.0-SNAPSHOT/gael-common-domain-0.18.0-20080328.093110-37-tests.jar:
INFO   | jvm 1    | 2008/03/28 10:31:30 | org.codehaus.plexus.redback.users.UserManagerException: Unable to update the 'org.codehaus.plexus.redback.users.jdo.JdoUser' object in the jdo database.
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.codehaus.plexus.redback.users.jdo.JdoUserManager.updateObject(JdoUserManager.java:458)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.codehaus.plexus.redback.users.jdo.JdoUserManager.updateUser(JdoUserManager.java:366)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.codehaus.plexus.redback.users.cached.CachedUserManager.updateUser(CachedUserManager.java:207)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.codehaus.plexus.redback.users.configurable.ConfigurableUserManager.updateUser(ConfigurableUserManager.java:161)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.codehaus.plexus.redback.authentication.users.UserManagerAuthenticator.authenticate(UserManagerAuthenticator.java:111)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.codehaus.plexus.redback.authentication.DefaultAuthenticationManager.authenticate(DefaultAuthenticationManager.java:74)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.codehaus.plexus.redback.system.DefaultSecuritySystem.authenticate(DefaultSecuritySystem.java:98)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.codehaus.plexus.redback.xwork.filter.authentication.HttpAuthenticator.authenticate(HttpAuthenticator.java:67)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.codehaus.plexus.redback.xwork.filter.authentication.basic.HttpBasicAuthentication.getAuthenticationResult(HttpBasicAuthentication.java:83)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.apache.maven.archiva.web.repository.RepositoryServlet.isAuthenticated(RepositoryServlet.java:186)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:107)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.apache.maven.archiva.web.repository.RepositoryServlet.service(RepositoryServlet.java:155)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.http.HttpServer.service(HttpServer.java:909)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
INFO   | jvm 1    | 2008/03/28 10:31:30 | Caused by: org.codehaus.plexus.jdo.PlexusStoreException: Unable to update object due to unexpected null value.
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.codehaus.plexus.jdo.PlexusJdoUtils.updateObject(PlexusJdoUtils.java:154)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       at org.codehaus.plexus.redback.users.jdo.JdoUserManager.updateObject(JdoUserManager.java:454)
INFO   | jvm 1    | 2008/03/28 10:31:30 |       ... 32 more
INFO   | jvm 1    | 2008/03/28 10:31:30 | Caused by: java.lang.NullPointerException

I can't test to reproduce it with 1.0.2-SNAPSHOT because it occurs only on production with the integration server.

Issue Links

This issue depends upon:
REDBACK-151 Redback attempts to set the failed login attempts to zero even if the number of failed attempts is zero Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Kamen Petroff added a comment -

We have the same problem, I think it occurs if multiple deployes are run simultaneously.

Show
Kamen Petroff added a comment - We have the same problem, I think it occurs if multiple deployes are run simultaneously.
Hide
Permalink
Benoit Decherf added a comment -

Archiva 1.0.2 return the same error.
I have no error logs in server side.

Show
Benoit Decherf added a comment - Archiva 1.0.2 return the same error. I have no error logs in server side.
Hide
Permalink
Brett Porter added a comment -

if this is a concurrency issue, let's review after the webdav changes in 1.1

Show
Brett Porter added a comment - if this is a concurrency issue, let's review after the webdav changes in 1.1
Hide
Permalink
Benoit Decherf added a comment -

We were using the same archiva server for 6 continuum instances.

I create a different user / continuum instance and this solves this problem. So you probably have a concurrency issue independent of webdav.

60 people can upload snapshots to archiva, so this only can be a temporary workaround (I won't create 60 different users in archiva).

Show
Benoit Decherf added a comment - We were using the same archiva server for 6 continuum instances. I create a different user / continuum instance and this solves this problem. So you probably have a concurrency issue independent of webdav. 60 people can upload snapshots to archiva, so this only can be a temporary workaround (I won't create 60 different users in archiva).
Hide
Permalink
Benoit Decherf added a comment -

This still occurs with different users. Don't give attention to my last comment.

Show
Benoit Decherf added a comment - This still occurs with different users. Don't give attention to my last comment.
Hide
Permalink
Wendy Smoak added a comment -

Edited summary to avoid confusion with the web upload form vs. deploying artifacts the usual way.

Show
Wendy Smoak added a comment - Edited summary to avoid confusion with the web upload form vs. deploying artifacts the usual way.
Hide
Permalink
James William Dumay added a comment -

Redback always updates the successful login count even if there were no previous unsuccessful logins.

The fix in REDBACK-151 will only update the count if there has been previous unsuccessful logins which should reduce the chance of this happening again.

Ideally, Redback should be audited for concurrency problems.

Show
James William Dumay added a comment - Redback always updates the successful login count even if there were no previous unsuccessful logins. The fix in REDBACK-151 will only update the count if there has been previous unsuccessful logins which should reduce the chance of this happening again. Ideally, Redback should be audited for concurrency problems.
Hide
Permalink
James William Dumay added a comment -

Should be fixed once Deng applies REDBACK-151 and we release a new redback for 1.1.

Show
James William Dumay added a comment - Should be fixed once Deng applies REDBACK-151 and we release a new redback for 1.1.

People

Vote (8)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.