ReportServer Forum

mkrause

Member

Registered: 2018-07-01

Scheduler jobs that are not editable after 4.2 upgrade

Long story short, we have some scheduler jobs from a pre-4.2 upgrade (3.7) that are no longer accessible, despite the report IDs being there still.

Is there a way to force delete them?  When I open them, this error pops up and I don't get the normal edit dialogue that allows deletion of the job...

java.lang.NullPointerException<br>    at net.datenwerke.rs.ftp.service.ftp.hooker.ScheduleConfigAsSftpFileHooker.adaptScheduleDefinition(ScheduleConfigAsSftpFileHooker.java:70)<br>    at net.datenwerke.rs.scheduler.server.scheduler.SchedulerRpcServiceImpl.lambda$5(SchedulerRpcServiceImpl.java:465)<br>    at net.datenwerke.rs.utils.exception.shared.LambdaExceptionUtil.lambda$0(LambdaExceptionUtil.java:56)<br>    at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)<br>    at net.datenwerke.rs.scheduler.server.scheduler.SchedulerRpcServiceImpl.loadScheduleInformation(SchedulerRpcServiceImpl.java:464)<br>    at net.datenwerke.rs.scheduler.server.scheduler.SchedulerRpcServiceImpl.loadFullScheduleInformation(SchedulerRpcServiceImpl.java:418)<br>    at com.google.inject.persist.jpa.JpaLocalTxnInterceptor.invoke(JpaLocalTxnInterceptor.java:64)<br>    at net.datenwerke.security.service.security.aop.SecurityCheckInterceptor.invoke(SecurityCheckInterceptor.java:112)<br>    at net.datenwerke.gf.service.gwtstacktrace.CatchStacktraceInterceptor.invoke(CatchStacktraceInterceptor.java:38)<br>    at jdk.internal.reflect.GeneratedMethodAccessor102.invoke(Unknown Source)<br>    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)<br>    at java.base/java.lang.reflect.Method.invoke(Method.java:566)<br>    at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:587)<br>    at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:333)<br>    at net.datenwerke.security.service.security.aop.SecurityCheckInterceptor.invoke(SecurityCheckInterceptor.java:112)<br>    at net.datenwerke.gf.service.gwtstacktrace.CatchStacktraceInterceptor.invoke(CatchStacktraceInterceptor.java:38)<br>    at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:303)<br>    at net.datenwerke.security.service.security.aop.SecurityCheckInterceptor.invoke(SecurityCheckInterceptor.java:112)<br>    at net.datenwerke.gf.service.gwtstacktrace.CatchStacktraceInterceptor.invoke(CatchStacktraceInterceptor.java:38)<br>    at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:373)<br>    at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)<br>    at javax.servlet.http.HttpServlet.service(HttpServlet.java:681)<br>    at javax.servlet.http.HttpServlet.service(HttpServlet.java:764)<br>    at net.datenwerke.security.service.security.aop.SecurityCheckInterceptor.invoke(SecurityCheckInterceptor.java:112)<br>    at net.datenwerke.gf.service.gwtstacktrace.CatchStacktraceInterceptor.invoke(CatchStacktraceInterceptor.java:38)<br>    at com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:290)<br>    at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:280)<br>    at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:184)<br>    at com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:89)<br>    at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)<br>    at com.google.inject.persist.PersistFilter.doFilter(PersistFilter.java:94)<br>    at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)<br>    at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:121)<br>    at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:133)<br>    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)<br>    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)<br>    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:197)<br>    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)<br>    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541)<br>    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135)<br>    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)<br>    at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:687)<br>    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78)<br>    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:360)<br>    at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:399)<br>    at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)<br>    at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)<br>    at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1789)<br>    at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)<br>    at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)<br>    at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)<br>    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)<br>    at java.base/java.lang.Thread.run(Thread.java:834)<br>

eduardo

Administrator

Registered: 2016-11-01

Website

Re: Scheduler jobs that are not editable after 4.2 upgrade

Hi mkrause,

which 4.2. version exactly are you using?

Regards,
Eduardo

eduardo

Administrator

Registered: 2016-11-01

Website

Re: Scheduler jobs that are not editable after 4.2 upgrade

Hi mkrause,

we identified the issue and are currently working on a patch-version. We raised ticket RS-6025 for this purpose.

Regards,
Eduardo

eduardo

Administrator

Registered: 2016-11-01

Website

Re: Scheduler jobs that are not editable after 4.2 upgrade

Hi mkrause,

we fixed the bug in the 4.2.0-6072 patch release. Pls take a look here: https://forum.reportserver.net/viewtopi … 9820#p9820

Regards,
Eduardo

mkrause

Member

Registered: 2018-07-01

Re: Scheduler jobs that are not editable after 4.2 upgrade

will test.
One other problem... Have some sftp scheduler jobs to a sftp sink that uses simple password authentication.  These are the failure messages I get -- it is intermittent. It works fine for a while, then I start getting this -- only way to get it working is to build a new scheduler item.  And the tomcat user does have a known hosts file with the same host in it... so sftp sessions work fine using a sudo -u tomcat  user on the same machine.  not sure what's up.

net.datenwerke.scheduler.service.scheduler.exceptions.ActionExecutionException: report could not be sent to SFTP
    at net.datenwerke.rs.ftp.service.ftp.action.ScheduleAsSftpFileAction.sendViaSFTPDatasink(ScheduleAsSftpFileAction.java:155)
    at net.datenwerke.rs.ftp.service.ftp.action.ScheduleAsSftpFileAction.execute(ScheduleAsSftpFileAction.java:93)
    at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.executeAction(SchedulerTask.java:630)
    at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.executeActions(SchedulerTask.java:513)
    at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.safeCall(SchedulerTask.java:207)
    at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:99)
    at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:1)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.IllegalArgumentException: known_hosts file does not exist
    at net.datenwerke.rs.ftp.service.ftp.FtpSenderServiceImpl.configureSftp(FtpSenderServiceImpl.java:143)
    at net.datenwerke.rs.ftp.service.ftp.FtpSenderServiceImpl.sendToFtpServer(FtpSenderServiceImpl.java:93)
    at net.datenwerke.rs.ftp.service.ftp.SftpServiceImpl.doExportIntoDatasink(SftpServiceImpl.java:47)
    at net.datenwerke.rs.core.service.datasinkmanager.DatasinkServiceImpl.exportIntoDatasink(DatasinkServiceImpl.java:94)
    at net.datenwerke.rs.ftp.service.ftp.action.ScheduleAsSftpFileAction.sendViaSFTPDatasink(ScheduleAsSftpFileAction.java:140)
    ... 10 more

mkrause

Member

Registered: 2018-07-01

Re: Scheduler jobs that are not editable after 4.2 upgrade

Trying to switch to FTP.  The new datasink tests OK, but then I put it into the same scheduler item and this happens.

net.datenwerke.scheduler.service.scheduler.exceptions.ActionExecutionException: report could not be sent to FTP
    at net.datenwerke.rs.ftp.service.ftp.action.ScheduleAsFtpFileAction.sendViaFTPDatasink(ScheduleAsFtpFileAction.java:146)
    at net.datenwerke.rs.ftp.service.ftp.action.ScheduleAsFtpFileAction.execute(ScheduleAsFtpFileAction.java:91)
    at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.executeAction(SchedulerTask.java:630)
    at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.executeActions(SchedulerTask.java:513)
    at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.safeCall(SchedulerTask.java:207)
    at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:99)
    at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:1)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: net.datenwerke.rs.core.service.datasinkmanager.exceptions.DatasinkExportException: An error occurred during datasink export
    at net.datenwerke.rs.ftp.service.ftp.FtpServiceImpl.doExportIntoDatasink(FtpServiceImpl.java:49)
    at net.datenwerke.rs.core.service.datasinkmanager.DatasinkServiceImpl.exportIntoDatasink(DatasinkServiceImpl.java:94)
    at net.datenwerke.rs.ftp.service.ftp.action.ScheduleAsFtpFileAction.sendViaFTPDatasink(ScheduleAsFtpFileAction.java:130)
    ... 10 more
Caused by: org.apache.commons.vfs2.FileSystemException: Could not connect to FTP server on "localhost".
    at org.apache.commons.vfs2.provider.ftp.FtpClientFactory$ConnectionFactory.createConnection(FtpClientFactory.java:232)
    at org.apache.commons.vfs2.provider.ftp.FtpClientFactory.createConnection(FtpClientFactory.java:272)
    at org.apache.commons.vfs2.provider.ftp.FTPClientWrapper.createClient(FTPClientWrapper.java:106)
    at org.apache.commons.vfs2.provider.ftp.FTPClientWrapper.createClient(FTPClientWrapper.java:98)
    at org.apache.commons.vfs2.provider.ftp.FTPClientWrapper.getFtpClient(FTPClientWrapper.java:147)
    at org.apache.commons.vfs2.provider.ftp.FTPClientWrapper.&lt;init&gt;(FTPClientWrapper.java:53)
    at org.apache.commons.vfs2.provider.ftp.FtpFileProvider.doCreateFileSystem(FtpFileProvider.java:70)
    at org.apache.commons.vfs2.provider.AbstractOriginatingFileProvider.getFileSystem(AbstractOriginatingFileProvider.java:92)
    at org.apache.commons.vfs2.provider.AbstractOriginatingFileProvider.findFile(AbstractOriginatingFileProvider.java:71)
    at org.apache.commons.vfs2.provider.AbstractOriginatingFileProvider.findFile(AbstractOriginatingFileProvider.java:55)
    at org.apache.commons.vfs2.impl.DefaultFileSystemManager.resolveFile(DefaultFileSystemManager.java:788)
    at org.apache.commons.vfs2.impl.DefaultFileSystemManager.resolveFile(DefaultFileSystemManager.java:835)
    at net.datenwerke.rs.ftp.service.ftp.FtpSenderServiceImpl.sendToFtpServer(FtpSenderServiceImpl.java:103)
    at net.datenwerke.rs.ftp.service.ftp.FtpServiceImpl.doExportIntoDatasink(FtpServiceImpl.java:47)
    ... 12 more
Caused by: java.net.ConnectException: Connection refused (Connection refused)
    at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:412)
    at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:255)
    at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:237)
    at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    at java.base/java.net.Socket.connect(Socket.java:609)
    at org.apache.commons.net.SocketClient._connect(SocketClient.java:253)
    at org.apache.commons.net.SocketClient.connect(SocketClient.java:212)
    at org.apache.commons.vfs2.provider.ftp.FtpClientFactory$ConnectionFactory.createConnection(FtpClientFactory.java:165)
    ... 25 more

mkrause

Member

Registered: 2018-07-01

Re: Scheduler jobs that are not editable after 4.2 upgrade

Now it's altogether failing to do SFTP too.. here is the error:

        ... 52 common frames omitted
Caused by: org.apache.commons.vfs2.FileSystemException: Could not connect to SFTP server at "localhost".
        at org.apache.commons.vfs2.provider.sftp.SftpClientFactory.createConnection(SftpClientFactory.java:228)
        at org.apache.commons.vfs2.provider.sftp.SftpFileProvider.createSession(SftpFileProvider.java:65)
        ... 60 common frames omitted
Caused by: com.jcraft.jsch.JSchException: reject HostKey: localhost
        at com.jcraft.jsch.Session.checkHost(Session.java:789)
        at com.jcraft.jsch.Session.connect(Session.java:345)
        at com.jcraft.jsch.Session.connect(Session.java:183)
        at org.apache.commons.vfs2.provider.sftp.SftpClientFactory.createConnection(SftpClientFactory.java:226)
        ... 61 common frames omitted

I made sure the correct lines were in the known_hosts file and the the /etc/security/misc.cf had the reference to the correct filesystem location of known_hosts...
No luck.

eduardo

Administrator

Registered: 2016-11-01

Website

Re: Scheduler jobs that are not editable after 4.2 upgrade

For completeness: discussions on this here: https://forum.reportserver.net/viewtopic.php?id=3161