January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4801) RemoteConnectionHandler and ConnectionImpl objects leak when org.jboss.as.cli is used

by Vinoth Kumar Natarajan (Jira)

[ https://issues.redhat.com/browse/WFCORE-4801?page=com.atlassian.jira.plug... ] Vinoth Kumar Natarajan updated WFCORE-4801: ------------------------------------------- Affects Version/s: 9.0.1.Final > RemoteConnectionHandler and ConnectionImpl objects leak when org.jboss.as.cli is used > ------------------------------------------------------------------------------------- > > Key: WFCORE-4801 > URL: https://issues.redhat.com/browse/WFCORE-4801 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 9.0.1.Final > Reporter: Vinoth Kumar Natarajan > Priority: Major > > Heap dump analysis of services deployed in Wildfly standalone deployment show a large number of stale objects of class org.jboss.remoting3.ConnectionImpl and org.jboss.remoting3.remote.RemoteConnectionHandler. These objects are not getting garbage collected and eventually cause JVM to go out of memory. > Analysis of the heap dump indicate that, > * All org.jboss.remoting3.ConnectionImpl objects lingering around are CLOSED as the state and associated with JBOSS management endpoint. > * All org.jboss.remoting3.remote.RemoteConnectionHandler objects lingering around are associated with Remote Endpoint Name "cli-client". which is the endpoint name used by org.jboss.as.cli. > Above observations seem to indicate that JBOSS CLI commands that are executed periodically in this deployment, to monitor status of deployments, is causing these stale objects. > To confirm this observation, we have executed jboss-cli.sh a couple of times on our deployment and could see that each execution of this script is leaving nehind one instance of each of these classes. > *Wildfly version details:* > bash-4.4# ./jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] connect > [standalone@localhost:9990 /] version > JBoss Admin Command-line Interface > JBOSS_HOME: /ericsson/3pp/wildfly > Release: 9.0.1.Final > Product: WildFly Full 17.0.0.Final > JAVA_HOME: /usr/ > java.version: 1.8.0_222 > java.vm.vendor: IcedTea > java.vm.version: 25.222-b10 > os.name: Linux > os.version: 4.12.14-197.15-default -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13000) Put an end to problems with Jackson caused by jaxrs subsystem

by Dominik Derwiński (Jira)

[ https://issues.redhat.com/browse/WFLY-13000?page=com.atlassian.jira.plugi... ] Dominik Derwiński updated WFLY-13000: ------------------------------------- Description: There is a serious problem with using bundled (inside ear) Jackson JSON library in version different than the one included inside WildFly. There are dozens of threads of people trying to solve this issue by manually upgrading modules in WildFly, excluding certain Jackson modules pulled by jaxrs and including them again in custom modules without exporting classes, to (finally) excluding the whole jaxrs subsystem, and using different implementation of JAXRS. Without doing so one can end with the following: {noformat} java.lang.NoSuchMethodError: 'com.fasterxml.jackson.core.TSFBuilder com.fasterxml.jackson.core.JsonFactory.builder()' {noformat} or {noformat} java.lang.IllegalAccessError: class com.fasterxml.jackson.core.JsonFactoryBuilder tried to access private field com.fasterxml.jackson.core.JsonFactory.DEFAULT_ROOT_VALUE_SEPARATOR (com.fasterxml.jackson.core.JsonFactoryBuilder is in unnamed module of loader 'deployment.xyz-ear-1.ear' @b6d0dc5; com.fasterxml.jackson.core.JsonFactory is in unnamed module of loader 'com.fasterxml.jackson.core.jackson-core(a)2.9.10' @68fc71cf) {noformat} Could this be fixed somehow by not exporting Jackson classes from jaxrs/resteasy/jackson2-provider modules? Why do they even get priority before classes from ear classloader? Found these on the net while trying to solve my issue: http://alloutfornoloss.com/exclude-jackson-module-wildfly/ https://stackoverflow.com/questions/37616096/wildfly-10-how-to-use-a-newe... https://stackoverflow.com/questions/38173460/dependency-conflict-loading-... https://stackoverflow.com/questions/47838240/jboss-resteasy-custom-jackso... https://stackoverflow.com/questions/56780117/unknown-conflict-causing-jav... https://stackoverflow.com/questions/20683843/jackson-annotations-ignored-... https://dzone.com/articles/jboss-modules-suck-it%E2%80%99s https://forum.camunda.org/t/camunda-json-marshalling-and-jsonignore/271/18 was: There is a serious problem with using bundled (inside ear) Jackson JSON library in version different than the one included inside WildFly. There are dozens of threads of people trying to solve this issue by manually upgrading modules in WildFly, excluding certain Jackson modules pulled by jaxrs and including them again in custom modules without exporting classes, to (finally) excluding the whole jaxrs subsystem, and using different implementation of JAXRS. Without doing so one can end with the following: {noformat} java.lang.NoSuchMethodError: 'com.fasterxml.jackson.core.TSFBuilder com.fasterxml.jackson.core.JsonFactory.builder()' {noformat} or {noformat} java.lang.IllegalAccessError: class com.fasterxml.jackson.core.JsonFactoryBuilder tried to access private field com.fasterxml.jackson.core.JsonFactory.DEFAULT_ROOT_VALUE_SEPARATOR (com.fasterxml.jackson.core.JsonFactoryBuilder is in unnamed module of loader 'deployment.xyz-ear-1.ear' @b6d0dc5; com.fasterxml.jackson.core.JsonFactory is in unnamed module of loader 'com.fasterxml.jackson.core.jackson-core(a)2.9.10' @68fc71cf) {noformat} Could this be fixed somehow by not exporting Jackson classes from jaxrs/resteasy/jackson2-provider modules? Why do they even get priority before classes from ear classloader? > Put an end to problems with Jackson caused by jaxrs subsystem > ------------------------------------------------------------- > > Key: WFLY-13000 > URL: https://issues.redhat.com/browse/WFLY-13000 > Project: WildFly > Issue Type: Feature Request > Components: REST > Affects Versions: 18.0.1.Final > Reporter: Dominik Derwiński > Assignee: Alessio Soldano > Priority: Major > > There is a serious problem with using bundled (inside ear) Jackson JSON library in version different than the one included inside WildFly. There are dozens of threads of people trying to solve this issue by manually upgrading modules in WildFly, excluding certain Jackson modules pulled by jaxrs and including them again in custom modules without exporting classes, to (finally) excluding the whole jaxrs subsystem, and using different implementation of JAXRS. Without doing so one can end with the following: > {noformat} > java.lang.NoSuchMethodError: 'com.fasterxml.jackson.core.TSFBuilder com.fasterxml.jackson.core.JsonFactory.builder()' > {noformat} > or > {noformat} > java.lang.IllegalAccessError: class com.fasterxml.jackson.core.JsonFactoryBuilder tried to access private field com.fasterxml.jackson.core.JsonFactory.DEFAULT_ROOT_VALUE_SEPARATOR (com.fasterxml.jackson.core.JsonFactoryBuilder is in unnamed module of loader 'deployment.xyz-ear-1.ear' @b6d0dc5; com.fasterxml.jackson.core.JsonFactory is in unnamed module of loader 'com.fasterxml.jackson.core.jackson-core(a)2.9.10' @68fc71cf) > {noformat} > Could this be fixed somehow by not exporting Jackson classes from jaxrs/resteasy/jackson2-provider modules? Why do they even get priority before classes from ear classloader? > Found these on the net while trying to solve my issue: > http://alloutfornoloss.com/exclude-jackson-module-wildfly/ > https://stackoverflow.com/questions/37616096/wildfly-10-how-to-use-a-newe... > https://stackoverflow.com/questions/38173460/dependency-conflict-loading-... > https://stackoverflow.com/questions/47838240/jboss-resteasy-custom-jackso... > https://stackoverflow.com/questions/56780117/unknown-conflict-causing-jav... > https://stackoverflow.com/questions/20683843/jackson-annotations-ignored-... > https://dzone.com/articles/jboss-modules-suck-it%E2%80%99s > https://forum.camunda.org/t/camunda-json-marshalling-and-jsonignore/271/18 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13000) Put an end to problems with Jackson caused by jaxrs subsystem

by Dominik Derwiński (Jira)

Dominik Derwiński created WFLY-13000: ---------------------------------------- Summary: Put an end to problems with Jackson caused by jaxrs subsystem Key: WFLY-13000 URL: https://issues.redhat.com/browse/WFLY-13000 Project: WildFly Issue Type: Feature Request Components: REST Affects Versions: 18.0.1.Final Reporter: Dominik Derwiński Assignee: Alessio Soldano There is a serious problem with using bundled (inside ear) Jackson JSON library in version different than the one included inside WildFly. There are dozens of threads of people trying to solve this issue by manually upgrading modules in WildFly, excluding certain Jackson modules pulled by jaxrs and including them again in custom modules without exporting classes, to (finally) excluding the whole jaxrs subsystem, and using different implementation of JAXRS. Without doing so one can end with the following: {noformat} java.lang.NoSuchMethodError: 'com.fasterxml.jackson.core.TSFBuilder com.fasterxml.jackson.core.JsonFactory.builder()' {noformat} or {noformat} java.lang.IllegalAccessError: class com.fasterxml.jackson.core.JsonFactoryBuilder tried to access private field com.fasterxml.jackson.core.JsonFactory.DEFAULT_ROOT_VALUE_SEPARATOR (com.fasterxml.jackson.core.JsonFactoryBuilder is in unnamed module of loader 'deployment.xyz-ear-1.ear' @b6d0dc5; com.fasterxml.jackson.core.JsonFactory is in unnamed module of loader 'com.fasterxml.jackson.core.jackson-core(a)2.9.10' @68fc71cf) {noformat} Could this be fixed somehow by not exporting Jackson classes from jaxrs/resteasy/jackson2-provider modules? Why do they even get priority before classes from ear classloader? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4764) Availability of web console during the startup of the Domain Controller

by Yeray Borges (Jira)

[ https://issues.redhat.com/browse/WFCORE-4764?page=com.atlassian.jira.plug... ] Yeray Borges commented on WFCORE-4764: -------------------------------------- Thanks [~harald.pehl] np, indeed, I was going to ask you to wait a bit more before start your review. I'm still working on a wildfly-core oriented solution for HAL-1653, I have something already but not 100% satisfied yet with the solution. Keep in mind that HAL-1653 could be related when if you are testing WFCORE-4764, so please, wait a bit more to have both solutions as PR before checking on your side HAL. > Availability of web console during the startup of the Domain Controller > ----------------------------------------------------------------------- > > Key: WFCORE-4764 > URL: https://issues.redhat.com/browse/WFCORE-4764 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Affects Versions: 11.0.0.Beta3 > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Minor > > The customer asking why the web console is only available after all servers are registered in the Domain. > If the customer starts a domain controller using the host.xml file for example and enables all servers to auto-start="true" the web console is not available until all servers are registered and the browser prompts to add a new interface. > In the log file, the HTTP management interface is enable in the end of the events: > ~~~ > [Host Controller] 18:41:29,247 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) starting > [Host Controller] 18:41:30,208 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:30,210 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:30,284 INFO [org.wildfly.security] (Controller Boot Thread) ELY00001: WildFly Elytron version 1.1.7.Final-redhat-1 > [Host Controller] 18:41:30,342 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.5.4.Final-redhat-1 > [Host Controller] 18:41:30,356 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1) > [Host Controller] 18:41:30,383 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.5.4.Final-redhat-1 > [Host Controller] 18:41:30,478 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.5.Final-redhat-1 > [Host Controller] 18:41:30,603 INFO [org.jboss.as.patching] (MSC service thread 1-8) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none > [Host Controller] 18:41:30,647 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore /opt/jboss-eap-7.1/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost > [Host Controller] 18:41:30,705 INFO [org.jboss.as.remoting] (MSC service thread 1-8) WFLYRMT0001: Listening on 127.0.0.1:9999 > [Host Controller] 18:41:32,922 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=default/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:32,990 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:33,046 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:33,112 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full-ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:33,612 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-one > 18:41:33,665 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-one' > [Host Controller] 18:41:35,496 INFO [org.jboss.as.host.controller] (management task-1) WFLYHC0021: Server [Server:server-one] connected using connection [Channel ID 348b688d (inbound) of Remoting connection 0f97728d to localhost/127.0.0.1:53171 of endpoint "master:MANAGEMENT" <46167ef2>] > [Host Controller] 18:41:35,562 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-two > [Host Controller] 18:41:35,582 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server server-one > 18:41:35,606 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-two' > [Host Controller] 18:41:38,901 INFO [org.jboss.as.host.controller] (management task-5) WFLYHC0021: Server [Server:server-two] connected using connection [Channel ID 114e3864 (inbound) of Remoting connection 30f65708 to localhost/127.0.0.1:42083 of endpoint "master:MANAGEMENT" <46167ef2>] > [Host Controller] 18:41:38,969 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0062: Http management interface listening on http://127.0.0.1:9990/management and https://127.0.0.1:-1/management > [Host Controller] 18:41:38,969 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0053: Admin console listening on http://127.0.0.1:9990 and https://127.0.0.1:-1 > [Host Controller] 18:41:38,970 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) (Host Controller) started in 10487ms - Started 77 of 79 services (23 services are lazy, passive or on-demand) > ~~~ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4764) Availability of web console during the startup of the Domain Controller

by Harald Pehl (Jira)

[ https://issues.redhat.com/browse/WFCORE-4764?page=com.atlassian.jira.plug... ] Harald Pehl commented on WFCORE-4764: ------------------------------------- Hi [~yersan] sorry for the delay, I'll try to test your PR this week and give feedback asap. > Availability of web console during the startup of the Domain Controller > ----------------------------------------------------------------------- > > Key: WFCORE-4764 > URL: https://issues.redhat.com/browse/WFCORE-4764 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Affects Versions: 11.0.0.Beta3 > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Minor > > The customer asking why the web console is only available after all servers are registered in the Domain. > If the customer starts a domain controller using the host.xml file for example and enables all servers to auto-start="true" the web console is not available until all servers are registered and the browser prompts to add a new interface. > In the log file, the HTTP management interface is enable in the end of the events: > ~~~ > [Host Controller] 18:41:29,247 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) starting > [Host Controller] 18:41:30,208 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:30,210 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:30,284 INFO [org.wildfly.security] (Controller Boot Thread) ELY00001: WildFly Elytron version 1.1.7.Final-redhat-1 > [Host Controller] 18:41:30,342 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.5.4.Final-redhat-1 > [Host Controller] 18:41:30,356 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1) > [Host Controller] 18:41:30,383 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.5.4.Final-redhat-1 > [Host Controller] 18:41:30,478 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.5.Final-redhat-1 > [Host Controller] 18:41:30,603 INFO [org.jboss.as.patching] (MSC service thread 1-8) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none > [Host Controller] 18:41:30,647 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore /opt/jboss-eap-7.1/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost > [Host Controller] 18:41:30,705 INFO [org.jboss.as.remoting] (MSC service thread 1-8) WFLYRMT0001: Listening on 127.0.0.1:9999 > [Host Controller] 18:41:32,922 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=default/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:32,990 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:33,046 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:33,112 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full-ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:33,612 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-one > 18:41:33,665 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-one' > [Host Controller] 18:41:35,496 INFO [org.jboss.as.host.controller] (management task-1) WFLYHC0021: Server [Server:server-one] connected using connection [Channel ID 348b688d (inbound) of Remoting connection 0f97728d to localhost/127.0.0.1:53171 of endpoint "master:MANAGEMENT" <46167ef2>] > [Host Controller] 18:41:35,562 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-two > [Host Controller] 18:41:35,582 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server server-one > 18:41:35,606 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-two' > [Host Controller] 18:41:38,901 INFO [org.jboss.as.host.controller] (management task-5) WFLYHC0021: Server [Server:server-two] connected using connection [Channel ID 114e3864 (inbound) of Remoting connection 30f65708 to localhost/127.0.0.1:42083 of endpoint "master:MANAGEMENT" <46167ef2>] > [Host Controller] 18:41:38,969 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0062: Http management interface listening on http://127.0.0.1:9990/management and https://127.0.0.1:-1/management > [Host Controller] 18:41:38,969 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0053: Admin console listening on http://127.0.0.1:9990 and https://127.0.0.1:-1 > [Host Controller] 18:41:38,970 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) (Host Controller) started in 10487ms - Started 77 of 79 services (23 services are lazy, passive or on-demand) > ~~~ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Miroslav Novak (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFWIP-287: -------------------------------------- @Stefano Maestri @Jeff Mesnil hi guys, this should be addressed by separate RFE as discussed above with [~rhusar], wdyt? > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Critical > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Miroslav Novak (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Miroslav Novak edited comment on WFWIP-287 at 1/21/20 6:10 AM: --------------------------------------------------------------- [~maeste] [~jmesnil]hi guys, this should be addressed by separate RFE as discussed above with [~rhusar], wdyt? was (Author: mnovak): @Stefano Maestri @Jeff Mesnil hi guys, this should be addressed by separate RFE as discussed above with [~rhusar], wdyt? > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Critical > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Miroslav Novak (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Miroslav Novak reopened WFWIP-287: ---------------------------------- > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Critical > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Miroslav Novak (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Miroslav Novak closed WFWIP-287. -------------------------------- Resolution: Rejected > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Critical > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1053) Automate Weight < 100 https://github.com/kiali/kiali/pull/2108

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1053?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan reassigned SWSQE-1053: ------------------------------------- Assignee: Hayk Hovsepyan > Automate Weight < 100 https://github.com/kiali/kiali/pull/2108 > -------------------------------------------------------------- > > Key: SWSQE-1053 > URL: https://issues.redhat.com/browse/SWSQE-1053 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2020