java.lang.RuntimeException

This exception has no message.

Solutions on the web701

  • via Coderanch by Saagar Kappa, 7 months ago
    This exception has no message.
  • This exception has no message.
  • via Coderanch by beata jane, 7 months ago
    This exception has no message.
  • Stack trace

    • java.lang.RuntimeException at com.rsa.replication.ApplyThread$1.doWork(ApplyThread.java:66) at com.rsa.replication.AutoFileCloser.<init>(AutoFileCloser.java:28) at com.rsa.replication.ApplyThread$1.<init>(ApplyThread.java:55) at com.rsa.replication.ApplyThread.applyChangesFromFileToDatabase(ApplyThread.java:71) at com.rsa.replication.ApplyThread.applyInsideTransaction(ApplyThread.java:50) at com.rsa.replication.ApplyThread.apply(ApplyThread.java:36) at com.rsa.replication.ApplyP2R.workIfNeccessary(ApplyP2R.java:69) at com.rsa.replication.ReplicationRunnable.work(ReplicationRunnable.java:73) at com.rsa.replication.util.ServiceCallable.work(ServiceCallable.java:110) at com.rsa.replication.util.ServiceCallable.runMainLoopUnsafe(ServiceCallable.java:99) at com.rsa.replication.util.ServiceCallable.runMainLoop(ServiceCallable.java:80) at com.rsa.replication.util.ServiceCallable.call(ServiceCallable.java:42) at com.rsa.replication.util.ServiceCallable.call(ServiceCallable.java:1) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:139) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.IOException at java.util.zip.GZIPInputStream.readHeader(GZIPInputStream.java:141) at java.util.zip.GZIPInputStream.<init>(GZIPInputStream.java:56) at java.util.zip.GZIPInputStream.<init>(GZIPInputStream.java:65) at com.rsa.replication.ApplyThread$1.doWork(ApplyThread.java:60)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    6 times, 5 months ago
    7 times, 1 year ago
    Unknown user
    Once, 1 year ago