[
https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi...
]
Ondrej Chaloupka commented on WFLY-14284:
-----------------------------------------
hi [~adrianots].
I checked the behaviour of the {{http-remoting}} with [~tomekadamski] and he considers it
as an issue. I created a jira for it:
https://issues.redhat.com/browse/WEJBHTTP-53
To your questions
ad 1. yes, agree. With use of {{remote+http}} the container should not be stopped hanging
endlessly.
ad 2. that depends on your application and I would really **not** recommend it as a
generic rule of thumb. The heuristic error means there was some unexpected error in the
transaction processing (ie. 2PC protocol can't proceed in deterministic way). The
reason should be verified first and then you can proceed with the deletion. You may take a
look e.g. on guidance at
https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...
, something about troubleshooting here
https://docs.wildfly.org/19.1/Developer_Guide.html#in-ejbs
ad 3. it depends on configuration but I assume it should be possible. E.g. if the app
works that the connection is opened, be directed to one of the server, is established and
retained until finished then the ejb client recovery will point to that particular server
and recovery will probably not be touching the loadbalancer. From transaction perspective
is important that the server behind the loadbalancer keeps the ip and the transaction
log.
But I'm not able to say how exactly this works in your environment.
ad 4. Here I'm really not sure. In general every next WFLY release should contain
fixes on top of the previous one. It's a generic question which may depend on your
workload. I would suggest to place this type of question at
https://groups.google.com/g/wildfly.
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)