|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thanks for the last comment. Interesting that this happened simultaneously on two different installations, one of which has NEVER had a JDK installed previously. We only noticed the problem because we wanted to build a Java application for the first time.
I checked the access log but I am unsure what to look for. We have Apache access logs showing every call to the Jenkins URL from outside the box, but of course if it's internally calling itself on port 8080 then this will be invisible. Besides, I have just noticed that the log doesn't go back far enough - I'll have to see the archived ones. Will update this comment if I find anything significant.