[infinispan-issues] [JBoss JIRA] (ISPN-8893) Stack trace of a primary request of Infinispan is lost, damaging supportability severely

[Tristan Tarrant (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-8893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tristan Tarrant updated ISPN-8893:
----------------------------------
    Fix Version/s: 8.2.10.Final
                       (was: 8.2.9.Final)


> Stack trace of a primary request of Infinispan is lost, damaging supportability severely
> ----------------------------------------------------------------------------------------
>
>                 Key: ISPN-8893
>                 URL: https://issues.jboss.org/browse/ISPN-8893
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core
>            Reporter: Yeray Borges
>            Assignee: Yeray Borges
>              Labels: top-50-list
>             Fix For: 9.2.1.Final, 8.2.10.Final
>
>
> A request is handled by XNIO's "default task-NNN" thread. If the request executes a clustering cache operation, like session replication, it waits for the backup operation on another server. And if the other server failed on the backup operation, the primary server unwraps the exception to print only the remote exception. The original context of thread "default task-NNN" is lost and a user can't even identify what the primary operation was.
> This affects supportability too much. It seems only JDG 7.1 is free from this issue (it has {{AsyncInterceptorChain}}). All other releases like EAP 7.1, RHSSO which is based on EAP 7.0 has this issue.
> See the "Forum Reference" link of a mail thread for the detail.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)