[
https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi...
]
Adriano Teixeira de Souza commented on WFLY-14284:
--------------------------------------------------
[~ochaloup] I'd like to fix de documentation but in fact I don't know how is
the right way to configure Wildfly without messages about deprecations.
At this time I just had changed the protocol and use the already documented workaround for
authentication. On our instances we are still getting this messages.
The Developer Guide has only one referece to remote+http protocol and the remaining use
always http-remoting. Have I provide a pull request change all of them without discern the
context or you want to say only about the chapter that refer to remote outbound
connection?
What would be the right way to use remote outbound without username, security-realm and
protocol attributes?
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)