1. Sebastian Sebastian
  2. scm-manager
  3. Issues

Issues

Issue #118 duplicate

NPE with svn LOCK url

Anonymous created an issue

Hi, i am not able to lock SVN files due to a NPE exception happening somewhere in SCM-Manager. The output from curl: {{{

!plaintext

  • About to connect() to *** port 80 (#0)
  • Trying 127.0.0.1... connected
  • Connected to *** (127.0.0.1) port 80 (#0)
  • Server auth using Basic with user '***'

    LOCK /scm/svn/c14003/model/trunk/Class%20Model.xml HTTP/1.1 Authorization: Basic ** User-Agent: curl/7.21.0 (x86_64-pc-linux-gnu) libcurl/7.21.0 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18 Host: Accept: /

    < HTTP/1.1 500 java.lang.NullPointerException at org.tmatesoft.svn.core.internal.server.dav.handlers.DAVLockHandler.execute(DAVLockHandler.java:101) at org.tmatesoft.svn.core.internal.server.dav.DAVServlet.service(DAVServlet.java:133) at sonia.scm.web.SvnDAVServlet.service(SvnDAVServlet.java:122) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:263) at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:178) at com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91) at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:62) at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168) at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58) at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168) at com.google.inject.servlet.FilterChainInvocation.doFilter < Set-Cookie: JSESSIONID=;Path=/scm < Set-Cookie: crowd.token_key=; Path=/; HttpOnly < Connection: close < Server: Jetty(7.6.1.v20120215) <

  • Closing connection #0 }}}

Unfortunately this is a blocker for me as I am using SVN to store Enterprise Architect models which requires locking before being able to modify anything.

Any ideas / workarounds ?

Thanks in advance Dimo

Comments (2)

  1. Log in to comment