January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14284) WildFly doesn't stop while waiting for PeriodicRecovery

by Adriano Teixeira de Souza (Jira)

[ 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)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14284) WildFly doesn't stop while waiting for PeriodicRecovery

by Adriano Teixeira de Souza (Jira)

[ https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi... ] Adriano Teixeira de Souza commented on WFLY-14284: -------------------------------------------------- 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)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1265) UI Automations - Fix Graph Failures

by Praneeth Bajjuri (Jira)

[ https://issues.redhat.com/browse/SWSQE-1265?page=com.atlassian.jira.plugi... ] Praneeth Bajjuri resolved SWSQE-1265. ------------------------------------- Labels: automation (was: ) Resolution: Done > UI Automations - Fix Graph Failures > ----------------------------------- > > Key: SWSQE-1265 > URL: https://issues.redhat.com/browse/SWSQE-1265 > Project: Kiali QE > Issue Type: QE Task > Reporter: Praneeth Bajjuri > Priority: Major > Labels: automation > > Updating the enums values for Graph Page. > Multi-Cluster changes > https://github.com/Kiali-QE/kiali-qe-python/pull/377 -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1265) UI Automations - Fix Graph Failures

by Praneeth Bajjuri (Jira)

[ https://issues.redhat.com/browse/SWSQE-1265?page=com.atlassian.jira.plugi... ] Praneeth Bajjuri updated SWSQE-1265: ------------------------------------ Labels: (was: automation) > UI Automations - Fix Graph Failures > ----------------------------------- > > Key: SWSQE-1265 > URL: https://issues.redhat.com/browse/SWSQE-1265 > Project: Kiali QE > Issue Type: QE Task > Reporter: Praneeth Bajjuri > Priority: Major > > Updating the enums values for Graph Page. > Multi-Cluster changes > https://github.com/Kiali-QE/kiali-qe-python/pull/377 -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1265) UI Automations - Fix Graph Failures

by Praneeth Bajjuri (Jira)

[ https://issues.redhat.com/browse/SWSQE-1265?page=com.atlassian.jira.plugi... ] Praneeth Bajjuri updated SWSQE-1265: ------------------------------------ Labels: automation (was: ) > UI Automations - Fix Graph Failures > ----------------------------------- > > Key: SWSQE-1265 > URL: https://issues.redhat.com/browse/SWSQE-1265 > Project: Kiali QE > Issue Type: QE Task > Reporter: Praneeth Bajjuri > Priority: Major > Labels: automation > > Updating the enums values for Graph Page. > Multi-Cluster changes > https://github.com/Kiali-QE/kiali-qe-python/pull/377 -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1265) UI Automations - Fix Graph Failures

by Praneeth Bajjuri (Jira)

[ https://issues.redhat.com/browse/SWSQE-1265?page=com.atlassian.jira.plugi... ] Praneeth Bajjuri reopened SWSQE-1265: ------------------------------------- > UI Automations - Fix Graph Failures > ----------------------------------- > > Key: SWSQE-1265 > URL: https://issues.redhat.com/browse/SWSQE-1265 > Project: Kiali QE > Issue Type: QE Task > Reporter: Praneeth Bajjuri > Priority: Major > > Updating the enums values for Graph Page. > Multi-Cluster changes > https://github.com/Kiali-QE/kiali-qe-python/pull/377 -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1265) UI Automations - Fix Graph Failures

by Praneeth Bajjuri (Jira)

[ https://issues.redhat.com/browse/SWSQE-1265?page=com.atlassian.jira.plugi... ] Praneeth Bajjuri resolved SWSQE-1265. ------------------------------------- Resolution: Done > UI Automations - Fix Graph Failures > ----------------------------------- > > Key: SWSQE-1265 > URL: https://issues.redhat.com/browse/SWSQE-1265 > Project: Kiali QE > Issue Type: QE Task > Reporter: Praneeth Bajjuri > Priority: Major > > Updating the enums values for Graph Page. > Multi-Cluster changes > https://github.com/Kiali-QE/kiali-qe-python/pull/377 -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1265) UI Automations - Fix Graph Failures

by Praneeth Bajjuri (Jira)

Praneeth Bajjuri created SWSQE-1265: --------------------------------------- Summary: UI Automations - Fix Graph Failures Key: SWSQE-1265 URL: https://issues.redhat.com/browse/SWSQE-1265 Project: Kiali QE Issue Type: QE Task Reporter: Praneeth Bajjuri Updating the enums values for Graph Page. Multi-Cluster changes https://github.com/Kiali-QE/kiali-qe-python/pull/377 -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-9577) Upgrade procrun to latest version

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-9577?page=com.atlassian.jira.plugin... ] James Perkins reassigned WFLY-9577: ----------------------------------- Assignee: (was: Tomaž Cerar) > Upgrade procrun to latest version > --------------------------------- > > Key: WFLY-9577 > URL: https://issues.redhat.com/browse/WFLY-9577 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 10.1.0.Final, 11.0.0.Final, 15.0.0.Final > Environment: Windows 10, Windows Server 2012 R2 > Reporter: Markus Stier > Priority: Major > > I've installed Wildflay as a Windows Service using the provided scripts in <Root>\docs\contrib\scripts\service. When stopping the windows service with > {code} > net stop <servicename> > {code} > the service terminates with an application error 1000. > {code} > Name der fehlerhaften Anwendung: wildfly-service.exe, Version: 1.0.15.0, Zeitstempel: 0x51543b9d > Name des fehlerhaften Moduls: ntdll.dll, Version: 6.3.9600.18821, Zeitstempel: 0x59ba86db > Ausnahmecode: 0xc0000005 > Fehleroffset: 0x00000000000356a0 > ID des fehlerhaften Prozesses: 0x608 > Startzeit der fehlerhaften Anwendung: 0x01d3637dd37fa9c8 > Pfad der fehlerhaften Anwendung: ....\wildfly-service.exe > Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll > Berichtskennung: ee6df2e2-d0eb-11e7-80e2-00505698739a > {code} > This is a known bug in the Apache Commons Daemon Service Runner version which is used in the wildfly distribution. See https://issues.apache.org/jira/browse/DAEMON-336 > The bug is fixed in version 1.1.x. Please update the Daemon Service to this version. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5967) Move implementation details to PMMLRuntimeFactoryInternal

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5967?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-5967. ------------------------------------ > Move implementation details to PMMLRuntimeFactoryInternal > --------------------------------------------------------- > > Key: DROOLS-5967 > URL: https://issues.redhat.com/browse/DROOLS-5967 > Project: Drools > Issue Type: Feature Request > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Minor > Labels: TrustyAI > > Move implementation details from PMMLRuntimeFactoryImpl to PMMLRuntimeFactoryInternal. Extend test coverage PMMLRuntimeFactoryInternal -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2021