[JIRA] (JENKINS-54641) UnsupportedOperation Flooding Jenkins Master

[m@phrk.de (JIRA)]

Stephan Watermeyer updated an issue

Jenkins / JENKINS-54641 UnsupportedOperation Flooding Jenkins Master Change By: Stephan Watermeyer Summary: UnsupportedOperation Flooging Flooding Jenkins Master Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[m@phrk.de (JIRA)]

Stephan Watermeyer updated an issue

Jenkins / JENKINS-54641 UnsupportedOperation Flooding Jenkins Master Change By: Stephan Watermeyer

Since yesterday we've installed the logfilesizechecker-plugin on our Jenkins (2.138.3) and the Jenkins Log is flodded flooded with the following Exception {code} Avoid calling getLogFile on sanmx-tm/feature%-1-payment #1 java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at hudson.plugins.logfilesizechecker.LogfilesizecheckerWrapper$LogSizeTimerTask.doRun(LogfilesizecheckerWrapper.java:108) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} The Exception is written in the log, as the method _getLogFile()_ is deprecated. https://javadoc.jenkins.io/plugin/workflow-job/org/jenkinsci/plugins/workflow/job/WorkflowRun.html#getLogFile-- {code} @Deprecated     @Override public File getLogFile() {         LOGGER.log(Level.WARNING, "Avoid calling getLogFile on " + this, new UnsupportedOperationException());         return LogStorage.of(asFlowExecutionOwner()).getLogFile(this, !isLogUpdated());     } {code} Our filesystem on the master went out of space, as due to our amount of Jobs and the Timersettings in the plugin the code is called very often.

Add Comment

[m@phrk.de (JIRA)]

Stephan Watermeyer updated an issue

Jenkins / JENKINS-54641 UnsupportedOperation Flooding Jenkins Master Change By: Stephan Watermeyer

Since yesterday we've installed the logfilesizechecker-plugin on our Jenkins (2.138.3) and the Jenkins Log is flooded with the following Exception

{code} Avoid calling getLogFile on sanmx-tm/feature%-1-payment #1 java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at hudson.plugins.logfilesizechecker.LogfilesizecheckerWrapper$LogSizeTimerTask.doRun(LogfilesizecheckerWrapper.java:108) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} The Exception is written in the log, as the method _getLogFile()_ is deprecated. https://javadoc.jenkins.io/plugin/workflow-job/org/jenkinsci/plugins/workflow/job/WorkflowRun.html#getLogFile-- {code} @Deprecated     @Override public File getLogFile() {         LOGGER.log(Level.WARNING, "Avoid calling getLogFile on " + this, new UnsupportedOperationException());         return LogStorage.of(asFlowExecutionOwner()).getLogFile(this, !isLogUpdated());     } {code} Our filesystem on the master went out of space, as due to our amount of Jobs and the Timersettings in the plugin the code is called very often.

We've installed the plugin to prevent that builds are flooding the filesystem with logs and now the plugin itself does the flooding. Thats bad humor ;)

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated an issue

Jenkins / JENKINS-54641 UnsupportedOperation Flooding Jenkins Master

Change By: Oleg Nenashev Labels: pipeline-compatibility

Add Comment

[stefan.brausch@1und1.de (JIRA)]

Stefan Brausch updated JENKINS-54641

Fixed version 1.5 should be available in update center soon.

Jenkins / JENKINS-54641 UnsupportedOperation Flooding Jenkins Master

Change By: Stefan Brausch Status: Open Fixed but Unreleased Resolution: Fixed

Add Comment

[stefan.brausch@1und1.de (JIRA)]

Stefan Brausch updated JENKINS-54641

Jenkins / JENKINS-54641 UnsupportedOperation Flooding Jenkins Master

Change By: Stefan Brausch Status: Fixed but Unreleased Resolved

Add Comment

[m@phrk.de (JIRA)]

Stephan Watermeyer commented on JENKINS-54641

Re: UnsupportedOperation Flooding Jenkins Master Thanks Stefan. Will check again with the version and come back to you asap.

Add Comment

[m@phrk.de (JIRA)]

Stephan Watermeyer updated an issue

Jenkins / JENKINS-54641 UnsupportedOperation Flooding Jenkins Master

Change By: Stephan Watermeyer

Since yesterday we've installed the logfilesizechecker-plugin on our Jenkins (2.138.3) and the Jenkins Log is flooded with the following Exception {code} Avoid calling getLogFile on sanmx-tm/feature%-1-payment #1 java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at hudson.plugins.logfilesizechecker.LogfilesizecheckerWrapper$LogSizeTimerTask.doRun(LogfilesizecheckerWrapper.java:108) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} The Exception is written in the log, as the method _getLogFile()_ is deprecated. https://javadoc.jenkins.io/plugin/workflow-job/org/jenkinsci/plugins/workflow/job/WorkflowRun.html#getLogFile--

https://github.com/jenkinsci/workflow-job-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java

{code} @Deprecated     @Override public File getLogFile() {         LOGGER.log(Level.WARNING, "Avoid calling getLogFile on " + this, new UnsupportedOperationException());         return LogStorage.of(asFlowExecutionOwner()).getLogFile(this, !isLogUpdated());     } {code} Our filesystem on the master went out of space, as due to our amount of Jobs and the Timersettings in the plugin the code is called very often. We've installed the plugin to prevent that builds are flooding the filesystem with logs and now the plugin itself does the flooding. Thats bad humor ;)

Add Comment

[m@phrk.de (JIRA)]

Stephan Watermeyer commented on JENKINS-54641

Re: UnsupportedOperation Flooding Jenkins Master

Looks good to me. Thanks.

Add Comment