Discussions  >  CollabNet TeamForge  >  Re: Error during Subversion Edge integration

Back to topic list

Re: Error during Subversion Edge integration

Author markphip
Full name Mark Phippard
Date 2012-04-30 07:52:37 PDT
Message On Apr 29, 2012, at 2:17 PM, Joe Schmoe wrote: > I am running TeamForge on Windows Server 2008 R2 > > When I go to "Integrations" and press "Discover Subversion Edge Servers" applet runs and discovers server at http://10.0.0.12:3343/csvn > > When I select this server in the list Subversion Edge login dialog appears. After I login I am presented with CollabNet TeamForge integration interface (Introduction tab). When I press "Continue" button this error comes up: > ==== > Grails Runtime Exception > Error Details > Error 500: Executing action [ctfInfo] of controller [com.collabnet.svnedge.console.ui.SetupTeamForgeController] caused exception: No such property: errors for class: com.collabnet.svnedge.teamforge.CtfConversionBean > Servlet: grails > URI: /csvn/grails/setupTeamForge/ctfInfo.dispatch > Exception Message: No such property: errors for class: com.collabnet.svnedge.teamforge.CtfConversionBean > Caused by: No such property: errors for class: com.collabnet.svnedge.teamforge.CtfConversionBean > Class: SetupTeamForgeController > At Line: [82] > Code Snippet: > ==== > Stack trace > > groovy.lang.MissingPropertyException: No such property: errors for class: com.collabnet.svnedge.teamforge.CtfConversionBean > at com.collabnet.svnedge.console.ui.SetupTeamForgeController$_closure2.doCall(SetupTeamForgeController.groovy:82) > at com.collabnet.svnedge.console.ui.SetupTeamForgeController$_closure2.doCall(SetupTeamForgeController.groovy) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:530) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1219) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1190) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1190) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1190) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:424) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119) > at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:494) > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:229) > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:931) > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:361) > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186) > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:867) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117) > at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:346) > at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:115) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1190) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1190) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1190) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1190) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1190) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1190) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:424) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119) > at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:457) > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:229) > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:931) > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:361) > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186) > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:867) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117) > at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:245) > at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113) > at org.eclipse.jetty.server.Server.handle(Server.java:337) > at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:581) > at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1020) > at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:775) > at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:228) > at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:417) > at org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:474) > at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:437) > at java.lang.Thread.run(Unknown Source) > =========== This stack trace is identical to the bug described in https://ctf.open.collab.net/sf/go/artf6000 This found in SVN Edge 1.3.3 which I believe is the version included with TeamForge on Windows. So I suspect you just ran into that bug. I am guessing you either got this bug before you upgraded, or the upgrade itself did not work properly as this bug should not exist with SVN Edge 3.0. FWIW, when running TeamForge on Windows you should not upgrade SVN Edge and instead use the version included with TeamForge. Future TeamForge upgrades will include newer SVN Edge versions with the upgrade. The issue is that TeamForge on Windows uses some of the pieces provided by SVN Edge, such as its Apache server and Python runtime. So it is important to not upgrade to a newer version that changes those components as it is possible those updates could cause problems. This is not an issue when SVN Edge and TeamForge are running on different physical servers. Mark

« Previous message in topic | 6 of 10 | Next message in topic »

Messages

Show all messages in topic

Subject
Author
Full name
Date posted
+
Error during Subversion Edge integration joeschmoe007 Joe Schmoe 2012-04-29 11:17:26 PDT
     RE: Error during Subversion Edge integration joeschmoe007 Joe Schmoe 2012-04-29 11:18:22 PDT
     RE: Error during Subversion Edge integration markphip Mark Phippard 2012-04-29 13:56:44 PDT
         RE: Error during Subversion Edge integration joeschmoe007 Joe Schmoe 2012-04-29 19:11:56 PDT
             Re: Error during Subversion Edge integration markphip Mark Phippard 2012-04-30 05:34:09 PDT
     Re: Error during Subversion Edge integration markphip Mark Phippard 2012-04-30 07:52:37 PDT
         RE: Re: Error during Subversion Edge integration joeschmoe007 Joe Schmoe 2012-04-30 08:09:05 PDT
             Re: Error during Subversion Edge integration markphip Mark Phippard 2012-04-30 08:33:57 PDT
     RE: Error during Subversion Edge integration robertpattinson Robert Pattinson 2012-05-03 03:40:09 PDT
         RE: Error during Subversion Edge integration robertpattinson Robert Pattinson 2012-05-03 03:40:59 PDT
Messages per page: