[
https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi...
]
Adriano Teixeira de Souza commented on WFLY-14284:
--------------------------------------------------
Hi [~ochaloup]
I have some questions to take some decisions about our production environment:
1 - According to what you say, probably this kind of errors won't occur anymore. Can I
think in this way?
2 - Will it be safe to delete data / ejb-txn-recovery and data / tx-object-store if this
problems occurs again?
3 - Is it safe to put a load balance like haproxy between wildfly remote outbound
communication and the target server?
4 - On our tests we notice wildfly 18.0.1 has shown a fewer errors cases than wildfly
20.0.1. I wonder if could be just randomly situation or the version 18.0.1 is more stable
than 20.0.1? We ar in doubt on wich to use definitely on our production environment. Could
you give us some advice about it?
WildFly doesn't stop while waiting for PeriodicRecovery
-------------------------------------------------------
Key: WFLY-14284
URL:
https://issues.redhat.com/browse/WFLY-14284
Project: WildFly
Issue Type: Bug
Components: EJB, Transactions
Affects Versions: 18.0.1.Final, 20.0.1.Final
Reporter: Adriano Teixeira de Souza
Assignee: Michael Musgrove
Priority: Major
Attachments: ejb-configs.sh, jboss-ejb-client.xml, server(transaction).log,
thread-dump-stop-1.txt
I'm testing wildfly 20.0.1 (and 21.0.2 was tested too) for replace our old version of
Wildfly 10.
it happens that frequently we have seen that the stop function of server does not work
and we need to kill the process by manual operation on the OS.
It sounds like a dead look.
I attatch the thread dump on this.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)