Thanks, this is informative. On Fri, 2008-12-19 at 15:53 -0500, Brian Marshall wrote: > 2008/12/19 10:22:05 Scmbug WARN> > Process.pm:886:Scmbug::Daemon::Process::process_activity_verify - > 127.0.0.1:6699 Processing an 'activity_verify' for bug id '2' from SCM > user 'marshallb'
> 2008/12/19 10:22:25 Scmbug WARN> > Process.pm:867:Scmbug::Daemon::Process::process_activity_commit - > 127.0.0.1:6701 Processing an 'activity_commit' for bug id '2' from SCM > user 'marshallb' It seems that after the activity_verify it takes the Scmbug glue 20 seconds before it issues the activity_commit. This is unusual. Try raising 'logging' in glue.conf by modifying this line: log4perl.category.Glue = WARN, AppWarn, AppRest into log4perl.category.Glue = DEBUG, AppWarn, AppRest, Logfile Try to commit after this change and you should see a verbose log of the steps Scmbug takes, along with timestamps. This should help pinpoint the problem. > > Also, can you check how long it takes to commit if you disable the glue > > in glue.conf ? > > With enabled=>0 the commit happens in < 2 seconds. This is clearly a Scmbug issue then. http://bugzilla.mkgnu.net/show_bug.cgi?id=1308
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
