MonicaGB | Posts: 13

Error while confirming document

0 votes

Hello,

I need help with an error message relatef to hornetq that we detected  in one of our prod environments. The related package has 5 documents, 4 documents were successfully signed and the last one signing confirmation failed and produced this error.

I appreciate any information to understand the problem. 

There are not similar error message in previous or next days.

Thanks,

Mónica

2021-06-02 13:07:46,764 INFO  [com.silanis.docengine.DECommandMgr] (default task-47) [168] --> Run DECommand..., mode = MODE_PARALLEL_BLOCKING
2021-06-02 13:07:46,765 INFO  [com.silanis.docengine.client.StubCommandRunner] (default task-47) [168] --> ChainCommand starting, id = 626414e3-e10b-4e01-a0cc-76c53f0d9b11-84d71bce2eac, sequential = false, leadingCmd = "BatchPrepareCommand : defaultDocumentName", CmdNum = 3, try=1.
2021-06-02 13:07:46,766 INFO  [com.silanis.docengine.DECommandMgr] (default task-47) [168] --> DECommand wait for blocking latch, sync mode = "true", uuids =  | 626414e3-e10b-4e01-a0cc-76c53f0d9b11-84d71bce2eac
2021-06-02 13:07:46,915 INFO  [com.silanis.docengine.client.StubCommandRunner] (Axis2 Task) [186b] <-- ChainCommand finished, id = 626414e3-e10b-4e01-a0cc-76c53f0d9b11-84d71bce2eac, in 150 ms, try=1.
2021-06-02 13:07:46,938 WARN  [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]
2021-06-02 13:07:46,939 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session b4dda7ac-c34f-11eb-a93d-0d2d719fa01d
2021-06-02 13:07:46,939 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session b4dda7ad-c34f-11eb-a93d-0d2d719fa01d
2021-06-02 13:07:46,939 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session b4dda7ac-c34f-11eb-a93d-0d2d719fa01d
2021-06-02 13:07:46,939 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session b4dda7ad-c34f-11eb-a93d-0d2d719fa01d
2021-06-02 13:07:46,943 WARN  [com.silanis.docengine.DECommandMgr] (Axis2 Task) [186b] !-- DECommand failed: invoking a command's listener failed, exception = "javax.jms.JMSException: HQ119016: Connection failure detected. Unblocking a blocking call that will never get a response"
2021-06-02 13:07:46,948 ERROR [com.silanis.awsng.rs.impl.v1.ScriptServiceImpl] (default task-47) [168] Failed to execute script "com.silanis.workflow.controller.Dispatcher.groovy" from context "boq".: com.silanis.awsng.process.ProcessRuntimeException: An unhandled exception occurred in CommandExecutor or GroovyExecutor. Error: "javax.jms.JMSException: HQ119016: Connection failure detected. Unblocking a blocking call that will never get a response".
2021-06-02 13:07:46,997 INFO  [com.silanis.notifier.service.NotificationMDBRequestHandler] (Thread-2689 (HornetQ-client-global-threads-1045273963)) [188c] Sending notification completed
2021-06-02 13:07:47,006 INFO  [com.silanis.esl.rest.resource.DocumentResource] (default task-17) END: com.silanis.esl.rest.resource.DocumentResource@3a7c68a3.confirmDocument elapsed (ms): 384
2021-06-02 13:07:47,006 SEVERE [com.silanis.esl.web.exception.mappers.ThrowableMapper] (default task-17) EsepCommand failed and no fallback available.: com.netflix.hystrix.exception.HystrixRuntimeException: EsepCommand failed and no fallback available.


Duo_Liang | Posts: 3776

Reply to: Error while confirming document

0 votes

Hi Mónica,

 

Thanks for your post! Are you leveraging the OneSpan Sign SaaS solution or on-premise installation? Because the log you posted above seems come from internal server. If the latter, could you kindly raise it to our support at [email protected] and our on-premise product specialists will reply back to you in a short time.

 

Duo


MonicaGB | Posts: 13

Reply to: Error while confirming document

0 votes

Hi Duo,

We are using on-premise installation in this case.

Thanks for your answer, I'll send it to support team.

Mónica


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off