[
https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi...
]
Adriano Teixeira de Souza edited comment on WFLY-14284 at 1/26/21 12:01 PM:
----------------------------------------------------------------------------
Hi [~ochaloup]
I would like to thank you for sharing some precious knowledge about this kind of complex
Wildfly stack behaviour.
And I'd propose some kind of correction on the oficial documentation about Remote
Outbout Connection because all of them is bring a wrong way to use de protocol with
"http-remoting" (according you advise me to change)
[
https://docs.wildfly.org/18/Developer_Guide.html#create-a-remote-outbound...]
and
[
https://docs.wildfly.org/22/Developer_Guide.html#create-a-remote-outbound...]
I would say still that it is showing the configuration using a deprecated way and causes
the log like this:
{code:java}
12:12:34,839 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread
Pool -- 28) WFLYCTL0028: Attribute 'username' in the resource at address
'/subsystem=remoting/remote-outbound-connection=remote-workflow-connection' is
deprecated, and may be removed in a future version. See the attribute description in the
output of the read-resource-description operation to learn more about the deprecation.
12:12:34,899 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread
Pool -- 28) WFLYCTL0028: Attribute 'security-realm' in the resource at address
'/subsystem=remoting/remote-outbound-connection=remote-workflow-connection' is
deprecated, and may be removed in a future version. See the attribute description in the
output of the read-resource-description operation to learn more about the deprecation.
12:12:34,899 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread
Pool -- 28) WFLYCTL0028: Attribute 'protocol' in the resource at address
'/subsystem=remoting/remote-outbound-connection=remote-workflow-connection' is
deprecated, and may be removed in a future version. See the attribute description in the
output of the read-resource-description operation to learn more about the deprecation.
{code}
I wonder if is not the time to refresh this extensive documentation of wildfly. Sometimes
look like the product is going so far of it documentation.
was (Author: JIRAUSER147207):
Hi [~ochaloup]
I would like to thank you for sharing some precious knowledge about this kind of complex
Wildfly stack behaviour.
And I'd propose some kind of correction on the oficial documentation about Remote
Outbout Connection because all of them is bring a wrong way to use de protocol with
"http-remoting"
[
https://docs.wildfly.org/18/Developer_Guide.html#create-a-remote-outbound...]
and
[
https://docs.wildfly.org/22/Developer_Guide.html#create-a-remote-outbound...]
I would say still that it is showing the configuration using a deprecated way and causes
the log like this:
{code:java}
12:12:34,839 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread
Pool -- 28) WFLYCTL0028: Attribute 'username' in the resource at address
'/subsystem=remoting/remote-outbound-connection=remote-workflow-connection' is
deprecated, and may be removed in a future version. See the attribute description in the
output of the read-resource-description operation to learn more about the deprecation.
12:12:34,899 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread
Pool -- 28) WFLYCTL0028: Attribute 'security-realm' in the resource at address
'/subsystem=remoting/remote-outbound-connection=remote-workflow-connection' is
deprecated, and may be removed in a future version. See the attribute description in the
output of the read-resource-description operation to learn more about the deprecation.
12:12:34,899 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread
Pool -- 28) WFLYCTL0028: Attribute 'protocol' in the resource at address
'/subsystem=remoting/remote-outbound-connection=remote-workflow-connection' is
deprecated, and may be removed in a future version. See the attribute description in the
output of the read-resource-description operation to learn more about the deprecation.
{code}
I wonder if is not the time to refresh this extensive documentation of wildfly. Sometimes
look like the product is going so far of it documentation.
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)