Questions for Confluence license has expired.

Please purchase a new license to continue using Questions for Confluence.

Unexpected Error

 
1
0
-1

Hi,


We have received the following unexpected error and was wondering if anything can be seen from the stack trace.


Impact:

Sync for ticket 1878153 is blocked

Local ticket:


1878153

Connection:


CS_to_2ndlines

Error Type:


Unexpected error

Error Creation Time:


Sep 13, 2021 22:30:06

Error Detail Message:


Unexpected error occurred while communicating with destination side. Error when posting sync request from sync event `5037` to `https://jcloudnode-egba-maux-kali-esox.exalate.cloud`. Received a response `Not Found(404)`: `404 page not found ` Generate an exalate support.zip file and contact support.

Error Stack Trace

com.exalate.api.exception.bug.rest.RestTransportBugException: Unexpected error occurred while communicating with destination side. Error when posting sync request from sync event `5037` to `https://jcloudnode-egba-maux-kali-esox.exalate.cloud`. Received a response `Not Found(404)`: `404 page not found ` Generate an exalate support.zip file and contact support. at com.exalate.error.services.BugExceptionCategoryService.generateRestExalateTransportBugException(BugExceptionCategoryService.scala:265) at com.exalate.error.services.ExalateRestErrorResponseCategoryService.$anonfun$categorizeNetworkAndRestResponseException$4(ExalateRestErrorResponseCategoryService.scala:36) at scala.Option.getOrElse(Option.scala:189) at com.exalate.error.services.ExalateRestErrorResponseCategoryService.categorizeNetworkAndRestResponseException(ExalateRestErrorResponseCategoryService.scala:36) at com.exalate.replication.services.transport.v1.rest.SyncRequestClient$$anonfun$postSyncRequest$3.applyOrElse(SyncRequestClient.scala:54) at com.exalate.replication.services.transport.v1.rest.SyncRequestClient$$anonfun$postSyncRequest$3.applyOrElse(SyncRequestClient.scala:50) at scala.concurrent.Future.$anonfun$recoverWith$1(Future.scala:417) at scala.concurrent.impl.Promise.$anonfun$transformWith$1(Promise.scala:41) at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:64) at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:56) at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:93) at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23) at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:85) at akka.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:93) at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:48) at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:48) at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290) at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020) at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656) at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594) at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183) Caused by: com.exalate.domain.exception.rest.ExalateRestResponseException: Received a response `Not Found(404)`: `404 page not found ` at com.exalate.replication.services.transport.ResponseHandler.handleUnsuccessfulResponse(ResponseHandler.scala:81) at com.exalate.replication.services.transport.ResponseHandler.handleExalateResponse(ResponseHandler.scala:52) at com.exalate.replication.services.transport.ResponseHandler.handleResponses(ResponseHandler.scala:27) at com.exalate.replication.services.transport.v1.rest.SyncRequestClient.$anonfun$postSyncRequest$2(SyncRequestClient.scala:48) at scala.concurrent.Future.$anonfun$flatMap$1(Future.scala:307) ... 14 more

Appreciate any help or insight you may have.


Thanks,

    CommentAdd your comment...

    2 answers

    1.  
      1
      0
      -1

      Hey Chris,

      Can you send your technical issue to support@exalate.com?


      This will create a ticket in our JIRA Helpdesk allowing for further tracking by our support engineers.

        CommentAdd your comment...
      1.  
        1
        0
        -1

        Hi Jose,


        I have now sent the query to support@exalate.com.


        Thanks,


          CommentAdd your comment...