October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2296) DNS_PING is dropping port values with SRV based service discovery

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2296?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2296: -------------------------------- [~ethompson] Can you resolve this issue? > DNS_PING is dropping port values with SRV based service discovery > ----------------------------------------------------------------- > > Key: JGRP-2296 > URL: https://issues.jboss.org/browse/JGRP-2296 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.11 > Environment: JGroups version 4.0.11.Final > Used in Keycloak 4.4.0 > Deployed as Jboss based Docker container from jboss/keycloak into AWS ECS > Reporter: Eric Thompson > Assignee: Bela Ban > Priority: Blocker > Fix For: 4.0.16 > > > Using DNS_PING in Jgroups 4.0.11 and SRV records the port from the SRV record is being dropped (set to zero) and the default is used instead (7600). > I am using this Jgroups config: > {code} > <subsystem xmlns="urn:jboss:domain:jgroups:6.0"> > <channels default="ee"> > <channel name="ee" stack="tcp" cluster="ejb"/> > </channels> > <stacks> > <stack name="tcp"> > <transport type="TCP" socket-binding="jgroups-tcp"> > <property name="external_addr">${env.EXTERNAL_ADDR}</property> > </transport> > <protocol type="dns.DNS_PING"> > <property name="dns_query"> > jgroups.${env.DNS_NAME}.svc.cluster.local > </property> > <property name="dns_record_type"> > SRV > </property> > </protocol> > <protocol type="MERGE3"/> > <protocol type="FD_SOCK"/> > <protocol type="FD_ALL"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="MFC"/> > <protocol type="FRAG3"/> > </stack> > </stacks> > </subsystem> > {code} > I have these service discovery DNS entries > {code} > $ dig jgroups.dev.auth.example.com.svc.cluster.local SRV > ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.68.rc1.58.amzn1 <<>> jgroups.dev.auth.example.com.svc.cluster.local SRV > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16690 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0 > ;; QUESTION SECTION: > ;jgroups.dev.auth.example.com.svc.cluster.local. IN SRV > ;; ANSWER SECTION: > jgroups.dev.auth.example.com.svc.cluster.local. 10 IN SRV 1 1 32921 9ec82e3f-3a0e-4e30-b785-17879c63cd7d.jgroups.dev.auth.example.com.svc.cluster.local. > jgroups.dev.auth.example.com.svc.cluster.local. 10 IN SRV 1 1 32923 60b5a820-9678-4bd2-84c6-00061a52bde0.jgroups.dev.auth.example.com.svc.cluster.local. > jgroups.dev.auth.example.com.svc.cluster.local. 10 IN SRV 1 1 32915 9d9d78d0-8919-4b91-9df8-2e4e65afedae.jgroups.dev.auth.example.com.svc.cluster.local. > jgroups.dev.auth.example.com.svc.cluster.local. 10 IN SRV 1 1 32917 161f3d66-f1e3-46f4-a44f-ebda925a25c6.jgroups.dev.auth.example.com.svc.cluster.local. > ;; Query time: 2 msec > ;; SERVER: 10.42.3.2#53(10.42.3.2) > ;; WHEN: Fri Sep 21 01:45:44 2018 > ;; MSG SIZE rcvd: 481 > {code} > But I get this in the logs when running Keycloak in standalone cluster: > {code} > 17:45:10,121 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-3,null,null) Performing initial discovery > 17:45:10,154 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-3,null,null) Entries collected from DNS: [10.42.3.56:0, 10.42.3.56:0, 10.42.3.44:0, 10.42.3.44:0] > 17:45:10,155 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-3,null,null) Discovered IP Address with port 0 (10.42.3.56:0). Replacing with default Transport port: 7600 > 17:45:10,159 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-3,null,null) Discovered IP Address with port 0 (10.42.3.56:0). Replacing with default Transport port: 7600 > 17:45:10,159 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-3,null,null) Discovered IP Address with port 0 (10.42.3.44:0). Replacing with default Transport port: 7600 > 17:45:10,159 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-3,null,null) Discovered IP Address with port 0 (10.42.3.44:0). Replacing with default Transport port: 7600 > 17:45:10,159 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-3,null,null) Performing discovery of the following hosts [10.42.3.56:7600, 10.42.3.44:7600, e200a617bf7a] > 17:45:10,159 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-3,null,null) e200a617bf7a: sending discovery request to 10.42.3.56:7600 > 17:45:10,160 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-3,null,null) e200a617bf7a: sending discovery request to 10.42.3.44:7600 > 17:45:10,160 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-10,ejb,e200a617bf7a) Received discovery from: e200a617bf7a, IP: 10.42.3.44:7600 > 17:45:10,161 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-3,null,null) e200a617bf7a: sending discovery request to e200a617bf7a > 17:45:10,162 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-11,ejb,e200a617bf7a) Received discovery from: e200a617bf7a, IP: 10.42.3.44:7600 > {code} > As you can see it is resolving the DNS addresses, but discarding the ports. > To be clear, in this example 32923 ids the port (eg: > 1 1 32923 60b5a820-9678-4bd2-84c6-00061a52bde0.jgroups.dev.auth.example.com.svc.cluster.local). > These are dynamic ports mapped to port 7600 in order to put more Keycloak containers on each instance. > {code} > $ docker ps > CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES > f67e39f8f403 datadog/agent:latest-jmx "/init" 8 hours ago Up 8 hours (healthy) 8125/udp, 8126/tcp ecs-auth-service-dev-26-datadog-agent-a2b7f783ddd0ba9cf601 > bbb12f0c43a5 233747045000.dkr.ecr.us-east-2.amazonaws.com/ops/keycloak:latest "/opt/jboss/tools/do…" 8 hours ago Up 8 hours 0.0.0.0:32923->7600/tcp, 0.0.0.0:32922->8080/tcp ecs-auth-service-dev-26-keycloak-f4bd8f8dca9fd4cd4f00 > 932cad7c4fb9 datadog/agent:latest-jmx "/init" 8 hours ago Up 8 hours (healthy) 8125/udp, 8126/tcp ecs-auth-service-dev-26-datadog-agent-baa38a98ccaddea6f501 > e200a617bf7a 233747045000.dkr.ecr.us-east-2.amazonaws.com/ops/keycloak:latest "/opt/jboss/tools/do…" 8 hours ago Up 8 hours 0.0.0.0:32921->7600/tcp, 0.0.0.0:32920->8080/tcp ecs-auth-service-dev-26-keycloak-e6f398e6cc8db5b5f101 > 73bc0b863c73 amazon/amazon-ecs-agent:latest "/agent" 2 days ago Up 2 days ecs-agent > {code} > This seems like it might be where ports are getting lost: > https://github.com/belaban/JGroups/blob/07060c3ba6e52ad4aad3ac799c2bc95ff... > I don't see the port number being extracted from the SRV entry and appended to the IP returned from resolveAEntries. > Let me know if I am missing any details. This is a major blocker for development. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2839) Document how to run Drools with a flat classpath by merging kie.conf files

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-2839?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2839: -------------------------------- Issue Type: Task (was: Bug) > Document how to run Drools with a flat classpath by merging kie.conf files > -------------------------------------------------------------------------- > > Key: DROOLS-2839 > URL: https://issues.jboss.org/browse/DROOLS-2839 > Project: Drools > Issue Type: Task > Components: docs > Affects Versions: 7.9.0.Final > Reporter: Duncan Doyle > Assignee: Mario Fusco > Priority: Major > > When running Drools in a Fat JAR, for example created by the Maven Shade Plugin, the various "kie.conf" files of the Drools JARs (e.g. drools-core, drools-compiler) need to be merged, otherwise , the Fat JAR will contain only 1 kie.conf from a single dependency, resulting into errors. > This is for example required when running Drools in a Vert.x application. > You can merge resources in the Maven Shade Plugin using transformers, like this: > {code} > <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"> > <resource>META-INF/kie.conf</resource> > </transformer> > {code} > For example, in my Vert.x app this is the full config of the Maven Shade Plugin: > {code} > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-shade-plugin</artifactId> > <version>3.1.0</version> > <executions> > <execution> > <phase>package</phase> > <goals> > <goal>shade</goal> > </goals> > <configuration> > <transformers> > <transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer"> > <manifestEntries> > <Main-Class>io.vertx.core.Launcher</Main-Class> > <Main-Verticle>${main.verticle}</Main-Verticle> > </manifestEntries> > </transformer> > <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"> > <resource>META-INF/services/io.vertx.core.spi.VerticleFactory</resource> > </transformer> > <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"> > <resource>META-INF/kie.conf</resource> > </transformer> > </transformers> > <artifactSet> > </artifactSet> > <outputFile>${project.build.directory}/${project.artifactId}-${project.version}-fat.jar</outputFile> > </configuration> > </execution> > </executions> > </plugin> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2839) Document how to run Drools with a flat classpath by merging kie.conf files

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-2839?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2839: -------------------------------- Sprint: 2018 Week 42-44 > Document how to run Drools with a flat classpath by merging kie.conf files > -------------------------------------------------------------------------- > > Key: DROOLS-2839 > URL: https://issues.jboss.org/browse/DROOLS-2839 > Project: Drools > Issue Type: Bug > Components: docs > Affects Versions: 7.9.0.Final > Reporter: Duncan Doyle > Assignee: Mario Fusco > Priority: Major > > When running Drools in a Fat JAR, for example created by the Maven Shade Plugin, the various "kie.conf" files of the Drools JARs (e.g. drools-core, drools-compiler) need to be merged, otherwise , the Fat JAR will contain only 1 kie.conf from a single dependency, resulting into errors. > This is for example required when running Drools in a Vert.x application. > You can merge resources in the Maven Shade Plugin using transformers, like this: > {code} > <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"> > <resource>META-INF/kie.conf</resource> > </transformer> > {code} > For example, in my Vert.x app this is the full config of the Maven Shade Plugin: > {code} > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-shade-plugin</artifactId> > <version>3.1.0</version> > <executions> > <execution> > <phase>package</phase> > <goals> > <goal>shade</goal> > </goals> > <configuration> > <transformers> > <transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer"> > <manifestEntries> > <Main-Class>io.vertx.core.Launcher</Main-Class> > <Main-Verticle>${main.verticle}</Main-Verticle> > </manifestEntries> > </transformer> > <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"> > <resource>META-INF/services/io.vertx.core.spi.VerticleFactory</resource> > </transformer> > <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"> > <resource>META-INF/kie.conf</resource> > </transformer> > </transformers> > <artifactSet> > </artifactSet> > <outputFile>${project.build.directory}/${project.artifactId}-${project.version}-fat.jar</outputFile> > </configuration> > </execution> > </executions> > </plugin> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3093) Necessary configuration information is missing when running rules engine in active mode

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3093?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-3093: -------------------------------- Sprint: 2018 Week 39-41 > Necessary configuration information is missing when running rules engine in active mode > --------------------------------------------------------------------------------------- > > Key: DROOLS-3093 > URL: https://issues.jboss.org/browse/DROOLS-3093 > Project: Drools > Issue Type: Enhancement > Components: docs > Affects Versions: 6.5.0.Final, 7.12.0.Final > Reporter: Lyle Wang > Assignee: Mario Fusco > Priority: Major > > When following this doc page to run rules engine in active mode > https://docs.jboss.org/drools/release/6.5.0.Final/drools-docs/html/ch07.h... > If application code opens another thread and do ksession.insert(fact) then it's possible to have threading issues. > https://access.redhat.com/solutions/3645752 > Requesting to add suggestion to highlight "ThreadSafeTrackableTimeJobFactoryManager" should be used in multithreading environment, code example: > ------------------------------------------------------------- > KieSessionConfiguration kconf = KnowledgeBaseFactory.newKnowledgeSessionConfiguration(); > ((org.drools.core.SessionConfiguration)kconf).setTimerJobFactoryType( TimerJobFactoryType.THREAD_SAFE_TRACKABLE ); > KieSession ksession = kContainer.newKieSession("ksession-name", kconf); > ------------------------------------------------------------- > Following code change has been made to update the default implementation to use ThreadSafeTrackableTimeJobFactoryManager : > https://github.com/kiegroup/drools/commit/92623e2435401db4f80eaf5e3e804c1... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11158) [EAT] : Method resolution needed for WFLY-10561

by Panagiotis Sotiropoulos (Jira)

[ https://issues.jboss.org/browse/WFLY-11158?page=com.atlassian.jira.plugin... ] Panagiotis Sotiropoulos updated WFLY-11158: ------------------------------------------- Summary: [EAT] : Method resolution needed for WFLY-10561 (was: [EAT] : Method resolution needed for JBEAP-14874) > [EAT] : Method resolution needed for WFLY-10561 > ----------------------------------------------- > > Key: WFLY-11158 > URL: https://issues.jboss.org/browse/WFLY-11158 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Priority: Major > > Method resolution as part of the implementation of the 4th AT Structure. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11158) [EAT] : Method resolution needed for JBEAP-14874

by Panagiotis Sotiropoulos (Jira)

[ https://issues.jboss.org/browse/WFLY-11158?page=com.atlassian.jira.plugin... ] Panagiotis Sotiropoulos moved JBEAP-15646 to WFLY-11158: -------------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11158 (was: JBEAP-15646) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) > [EAT] : Method resolution needed for JBEAP-14874 > ------------------------------------------------ > > Key: WFLY-11158 > URL: https://issues.jboss.org/browse/WFLY-11158 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Priority: Major > > Method resolution as part of the implementation of the 4th AT Structure. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3108) Allow KieScanner to work with a plain file system

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3108?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-3108: ------------------------------------- poker: 5 > Allow KieScanner to work with a plain file system > ------------------------------------------------- > > Key: DROOLS-3108 > URL: https://issues.jboss.org/browse/DROOLS-3108 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > > Many users need incremental compilation but doesn't want an instance of maven installed in production. For this reason it is required to allow the KieScanner to also work on a plain file system. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3107) Provide optional lazy segment memories creation

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3107?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-3107: ------------------------------------- poker: 8 > Provide optional lazy segment memories creation > ----------------------------------------------- > > Key: DROOLS-3107 > URL: https://issues.jboss.org/browse/DROOLS-3107 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > > The execution of the very first ksession created from a kbase is (much) slower than the subsequent ones, because of lazy segment memories creation. It is requested to provide an option to eagerly create them at kbase creation time. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11112) WildFly intermittently fails to add pooled-connection-factory but it still got registered after

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-11112?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet reassigned WFLY-11112: ---------------------------------------- Assignee: ehsavoie Hugonnet (was: Jeff Mesnil) > WildFly intermittently fails to add pooled-connection-factory but it still got registered after > ----------------------------------------------------------------------------------------------- > > Key: WFLY-11112 > URL: https://issues.jboss.org/browse/WFLY-11112 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 15.0.0.Alpha1 > Reporter: Ivan Straka > Assignee: ehsavoie Hugonnet > Priority: Blocker > Attachments: server.log, standalone-full.xml > > > We see following error in log of WildFly (master): > {code} > 2018-10-03 22:28:02,503 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("server" => "default"), > ("pooled-connection-factory" => "activemq-ra") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.JmsXA-bkp"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.JmsXA-bkp]"] > } > {code} > Factory is defined: > {code:java} > <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA-bkp java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/> > {code} > However factory is registered after and deployment is able to use it. Error is logged intermittently. > Log file and xml configuration file are enclosed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11112) WildFly intermittently fails to add pooled-connection-factory but it still got registered after

by Ivan Straka (Jira)

[ https://issues.jboss.org/browse/WFLY-11112?page=com.atlassian.jira.plugin... ] Ivan Straka commented on WFLY-11112: ------------------------------------ [~ehugonnet] I have not hit the issue with the fix. Without the commit the issue is seen. > WildFly intermittently fails to add pooled-connection-factory but it still got registered after > ----------------------------------------------------------------------------------------------- > > Key: WFLY-11112 > URL: https://issues.jboss.org/browse/WFLY-11112 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 15.0.0.Alpha1 > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Blocker > Attachments: server.log, standalone-full.xml > > > We see following error in log of WildFly (master): > {code} > 2018-10-03 22:28:02,503 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("server" => "default"), > ("pooled-connection-factory" => "activemq-ra") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.JmsXA-bkp"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.JmsXA-bkp]"] > } > {code} > Factory is defined: > {code:java} > <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA-bkp java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/> > {code} > However factory is registered after and deployment is able to use it. Error is logged intermittently. > Log file and xml configuration file are enclosed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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 October 2018