Closed GoogleCodeExporter closed 9 years ago
Gitblit pushes messages into a queue and tries to send them to your SMTP server
asynchronously from the triggering Gitblit event. If the SMTP comms fail, the
message remains in the queue until the SMTP comms succeed. This is designed to
prevent loss of important mail messages in the event of temporary downtime or
mail server overload.
The real fix to this issue is ensuring that the mail server connection is
properly configured. I'm not sure what I can do to improve this. Perhaps a
test utility? Do you have a recommendation?
Original comment by James.Mo...@gmail.com
on 10 Oct 2014 at 12:49
At last the E-Mail settings do not seem to be an issue. I completely deativated
the mail system (by removing the settings). Still the process starts to hang
after 1-2 Days with 100% CPU.
Apart from failed logins the log does not mention any errors.
Any suggestion on how I can get a hold of this error?
Original comment by gabi.dev...@gmail.com
on 17 Oct 2014 at 2:55
1. You could hookup VisualVM and inspect the running instance
2. If you are on *nix, you can "kill -QUIT process_id" to get a thread dump
which can be analyzed by VisualVM
Have you tried disabling Lucene?
Original comment by James.Mo...@gmail.com
on 17 Oct 2014 at 3:06
Strangely sine I installed VisualVM, the server seems to run fine... (maybe
scared I don't know...) I'll monitor the issue, but I think you can close this
one.
Thanks anyway.
Original comment by gabi.dev...@gmail.com
on 21 Oct 2014 at 9:50
Ok, post back here if you collect more data.
Original comment by James.Mo...@gmail.com
on 21 Oct 2014 at 2:05
Original issue reported on code.google.com by
gabi.dev...@gmail.com
on 8 Oct 2014 at 8:12