[jboss-jira] [JBoss JIRA] (WFLY-10101) [Artemis 2.x upgrade] Unexptected crash of server in SOAK test

[Clebert Suconic (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560226#comment-13560226 ] 

Clebert Suconic edited comment on WFLY-10101 at 4/12/18 9:36 AM:
-----------------------------------------------------------------

[~mnovak] There's a feature in 2.x for deadlock detection. (Critical Analyzer)

There's a mode that would halt the VM in case of a deadlock. What is the configuration used?

Perhaps you could set it to Log instead of Hatl.. and maybe the logged output is being ignored for some reason? It's worth to check it.



I bet a beer this is the Critical Analyzer.. (If I lose it I will pay it next time we meet ;) )


was (Author: clebert.suconic):
[~mnovak] There's a feature in 2.x for deadlock detection. (Critical Analyzer)

There's a mode that would halt the VM in case of a deadlock. What is the configuration used...

Perhaps you could set it to Log instead of Hatl.. and maybe the logged output is being ignored for some reason? It's worth to check it.

> [Artemis 2.x upgrade] Unexptected crash of server in SOAK test
> --------------------------------------------------------------
>
>                 Key: WFLY-10101
>                 URL: https://issues.jboss.org/browse/WFLY-10101
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>            Reporter: Miroslav Novak
>            Assignee: Martyn Taylor
>            Priority: Blocker
>              Labels: feature-branch-blocker
>
> After ~13 hours there is unexpected crash of one server in SOAK test. There is no error/warning in the logs. 
> Test Scenario:
> * Start 2 servers 
> * Client sends messages to input queue. Messages then go through:
> * One server to another through MDB reading and sending them from remote container through resource adapter
> * Messages are forwarded from one server to another over JMS bridge and back over Core bridge
> * Messages have JMSReplyTo defined with a temporary queue, that is filled with responses for the client
> * Messages are read from the destination with stateless EJB and sent back to clients
> * Client reads the messages after the pass through all the soak modules.
> Pass Criteria: In the last step receiver consumes all messages sent by producer.
> Actual Result:
> After ~13 hours 1st server suddenly crashes. There is no error/warning in server logs.
> Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_with_prefix (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d)



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