[JBoss JIRA] (WFLY-11045) Jaeger remote sampler fails to deserialize response
by Pavol Loffay (JIRA)
[ https://issues.jboss.org/browse/WFLY-11045?page=com.atlassian.jira.plugin... ]
Pavol Loffay commented on WFLY-11045:
-------------------------------------
[~brian.stansberry] [~juraci.costa] is working on the patch as part of TRACING-248
> Jaeger remote sampler fails to deserialize response
> ---------------------------------------------------
>
> Key: WFLY-11045
> URL: https://issues.jboss.org/browse/WFLY-11045
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing
> Affects Versions: 14.0.0.Final
> Reporter: Pavol Loffay
>
> JAEGER_REPORTER_LOG_SPANS=true JAEGER_SAMPLER_TYPE=remote $WILDFLY_HOME/bin/standalone.sh 1:39
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/ploffay/projects/javaee-traced-store/wildfly-14.0.1.Final
> JAVA: java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 13:39:30,432 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.6.Final
> 13:39:30,861 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.3.Final
> 13:39:30,868 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final
> 13:39:30,992 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) starting
> 13:39:31,697 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.6.0.Final
> 13:39:32,155 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' 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.
> 13:39:32,188 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 26) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' 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.
> 13:39:32,221 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 34) WFLYDR0001: Content added at location /home/ploffay/projects/javaee-traced-store/wildfly-14.0.1.Final/standalone/data/content/91/04caab3329ba82bafd92755e900187a74e536c/content
> 13:39:32,259 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
> 13:39:32,278 INFO [org.xnio] (MSC service thread 1-4) XNIO version 3.6.5.Final
> 13:39:32,290 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.6.5.Final
> 13:39:32,371 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 41) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
> 13:39:32,396 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) WFLYCLINF0001: Activating Infinispan subsystem.
> 13:39:32,400 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 49) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
> 13:39:32,402 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.8.Final
> 13:39:32,435 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
> 13:39:32,444 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 50) WFLYRS0016: RESTEasy version 3.6.1.Final
> 13:39:32,478 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.11.Final)
> 13:39:32,493 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 55) WFLYJSF0007: Activated the following JSF Implementations: [main]
> 13:39:32,494 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
> 13:39:32,495 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2
> 13:39:32,506 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 57) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
> 13:39:32,508 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 59) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
> 13:39:32,531 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 60) WFLYNAM0001: Activating Naming Subsystem
> 13:39:32,545 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 58) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
> 13:39:32,559 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 68) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
> 13:39:32,575 INFO [org.jboss.as.security] (ServerService Thread Pool -- 66) WFLYSEC0002: Activating Security Subsystem
> 13:39:32,581 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 70) WFLYWS0002: Activating WebServices Extension
> 13:39:32,589 INFO [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Starting Naming Service
> 13:39:32,592 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
> 13:39:32,617 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=5.0.3.Final
> 13:39:32,662 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 2.0.13.Final starting
> 13:39:32,670 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 128 (per class), which is derived from thread worker pool sizing.
> 13:39:32,673 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 32 (per class), which is derived from the number of CPUs on this host.
> 13:39:32,901 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 69) WFLYUT0014: Creating file handler for path '/home/ploffay/projects/javaee-traced-store/wildfly-14.0.1.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
> 13:39:32,915 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
> 13:39:32,918 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
> 13:39:32,985 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
> 13:39:33,103 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0493: EJB subsystem suspension complete
> 13:39:33,176 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
> 13:39:33,224 INFO [org.jboss.as.patching] (MSC service thread 1-1) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
> 13:39:33,252 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore /home/ploffay/projects/javaee-traced-store/wildfly-14.0.1.Final/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> 13:39:33,258 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) WFLYDS0013: Started FileSystemDeploymentService for directory /home/ploffay/projects/javaee-traced-store/wildfly-14.0.1.Final/standalone/deployments
> 13:39:33,274 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "javaee-traced-store-1.0-SNAPSHOT.war" (runtime-name: "javaee-traced-store-1.0-SNAPSHOT.war")
> 13:39:33,337 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
> 13:39:33,417 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.2.3.Final (Apache CXF 3.2.5.jbossorg-1)
> 13:39:33,807 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment javaee-traced-store-1.0-SNAPSHOT.war
> 13:39:33,921 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 6.0.13.Final
> 13:39:34,075 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'OrderEndpoint' in deployment unit 'deployment "javaee-traced-store-1.0-SNAPSHOT.war"' are as follows:
> java:global/javaee-traced-store-1.0-SNAPSHOT/OrderEndpoint!io.jaegertracing.examples.wildfly.OrderEndpoint
> java:app/javaee-traced-store-1.0-SNAPSHOT/OrderEndpoint!io.jaegertracing.examples.wildfly.OrderEndpoint
> java:module/OrderEndpoint!io.jaegertracing.examples.wildfly.OrderEndpoint
> ejb:javaee-traced-store-1.0-SNAPSHOT/OrderEndpoint!io.jaegertracing.examples.wildfly.OrderEndpoint
> java:global/javaee-traced-store-1.0-SNAPSHOT/OrderEndpoint
> java:app/javaee-traced-store-1.0-SNAPSHOT/OrderEndpoint
> java:module/OrderEndpoint
> 13:39:34,248 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 3.0.5 (Final)
> 13:39:34,439 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Estrella Galicia' 9.3.1.Final
> 13:39:34,634 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 72) WFLYCLINF0002: Started client-mappings cache from ejb container
> 13:39:35,007 WARN [io.jaegertracing.internal.senders.SenderResolver] (ServerService Thread Pool -- 72) No suitable sender found. Using NoopSender, meaning that data will not be sent anywhere!
> 13:39:35,061 ERROR [stderr] (Timer-2) Exception in thread "Timer-2" java.lang.RuntimeException: Unable to invoke no-args constructor for class io.jaegertracing.internal.samplers.http.SamplingStrategyResponse. Registering an InstanceCreator with Gson for this type may fix this problem.
> 13:39:35,062 ERROR [stderr] (Timer-2) at com.google.gson.internal.ConstructorConstructor$14.construct(ConstructorConstructor.java:226)
> 13:39:35,062 ERROR [stderr] (Timer-2) at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:210)
> 13:39:35,062 ERROR [stderr] (Timer-2) at com.google.gson.Gson.fromJson(Gson.java:888)
> 13:39:35,062 ERROR [stderr] (Timer-2) at com.google.gson.Gson.fromJson(Gson.java:853)
> 13:39:35,062 ERROR [stderr] (Timer-2) at com.google.gson.Gson.fromJson(Gson.java:802)
> 13:39:35,062 ERROR [stderr] (Timer-2) at com.google.gson.Gson.fromJson(Gson.java:774)
> 13:39:35,062 ERROR [stderr] (Timer-2) at io.jaegertracing.internal.samplers.HttpSamplingManager.parseJson(HttpSamplingManager.java:49)
> 13:39:35,062 ERROR [stderr] (Timer-2) at io.jaegertracing.internal.samplers.HttpSamplingManager.getSamplingStrategy(HttpSamplingManager.java:68)
> 13:39:35,063 ERROR [stderr] (Timer-2) at io.jaegertracing.internal.samplers.RemoteControlledSampler.updateSampler(RemoteControlledSampler.java:88)
> 13:39:35,063 ERROR [stderr] (Timer-2) at io.jaegertracing.internal.samplers.RemoteControlledSampler$1.run(RemoteControlledSampler.java:70)
> 13:39:35,063 ERROR [stderr] (Timer-2) at java.util.TimerThread.mainLoop(Timer.java:555)
> 13:39:35,063 ERROR [stderr] (Timer-2) at java.util.TimerThread.run(Timer.java:505)
> 13:39:35,063 ERROR [stderr] (Timer-2) Caused by: java.lang.UnsupportedOperationException: Cannot allocate class io.jaegertracing.internal.samplers.http.SamplingStrategyResponse
> 13:39:35,063 ERROR [stderr] (Timer-2) at com.google.gson.internal.UnsafeAllocator$4.newInstance(UnsafeAllocator.java:104)
> 13:39:35,064 ERROR [stderr] (Timer-2) at com.google.gson.internal.ConstructorConstructor$14.construct(ConstructorConstructor.java:223)
> 13:39:35,064 ERROR [stderr] (Timer-2) ... 11 more
> 13:39:35,210 INFO [io.jaegertracing.Configuration] (ServerService Thread Pool -- 72) Initialized tracer=JaegerTracer(version=Java-0.30.6, serviceName=javaee-traced-store-1.0-SNAPSHOT.war, reporter=CompositeReporter(reporters=[RemoteReporter(sender=NoopSender(), closeEnqueueTimeout=1000), LoggingReporter(logger=org.slf4j.impl.Slf4jLogger(io.jaegertracing.internal.reporters.LoggingReporter))]), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=dhcp-144-223.gva.redhat.com, jaeger.version=Java-0.30.6, ip=10.33.144.223}, zipkinSharedRpcSpan=false, expandExceptionLogs=false)
> 13:39:35,557 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 72) RESTEASY002225: Deploying javax.ws.rs.core.Application: class io.jaegertracing.examples.wildfly.TracedStoreApplication
> 13:39:35,589 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0021: Registered web context: '/javaee-traced-store-1.0-SNAPSHOT' for server 'default-server'
> 13:39:35,605 INFO [org.jboss.as.server] (ServerService Thread Pool -- 42) WFLYSRV0010: Deployed "javaee-traced-store-1.0-SNAPSHOT.war" (runtime-name : "javaee-traced-store-1.0-SNAPSHOT.war")
> 13:39:35,683 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> 13:39:35,685 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 13:39:35,686 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 13:39:35,686 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) started in 5525ms - Started 445 of 628 services (326 services are lazy, passive or on-demand)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-10985) UnsupportedOperationException thrown during start if CredentialReference is used in messaging-activemq subsystem
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-10985?page=com.atlassian.jira.plugin... ]
Kabir Khan resolved WFLY-10985.
-------------------------------
Fix Version/s: 14.0.1.Final
Resolution: Done
> UnsupportedOperationException thrown during start if CredentialReference is used in messaging-activemq subsystem
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10985
> URL: https://issues.jboss.org/browse/WFLY-10985
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Reporter: Miroslav Novak
> Assignee: ehsavoie Hugonnet
> Priority: Critical
> Fix For: 14.0.1.Final
>
> Attachments: bridge-cs001.jceks, standalone-full-ha.xml
>
>
> If messaging subsystem is referencing elytron's credential store like in:
> {code}
> <bridge name="myBridge" queue-name="jms.queue.InQueue" forwarding-address="jms.queue.OutQueue" ha="true" reconnect-attempts="-1" use-duplicate-detection="true" user="johnOut" static-connectors="bridge-connector">
> <credential-reference store="bridge-cs001" alias="john_out_alias_wrong"/>
> </bridge>
> {code}
> then during start server throws exception:
> {code}
> 12:49:04,367 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 66) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default")
> ]): java.lang.UnsupportedOperationException
> at org.jboss.msc.service.ServiceBuilderImpl.addDependency(ServiceBuilderImpl.java:409)
> at org.jboss.msc.service.DelegatingServiceBuilder.addDependency(DelegatingServiceBuilder.java:147)
> at org.jboss.as.controller.security.CredentialReference.getCredentialSourceSupplier(CredentialReference.java:323)
> at org.wildfly.extension.messaging.activemq.ServerAdd.addBridgeCredentialStoreReference(ServerAdd.java:732)
> at org.wildfly.extension.messaging.activemq.ServerAdd.access$200(ServerAdd.java:175)
> at org.wildfly.extension.messaging.activemq.ServerAdd$2.execute(ServerAdd.java:439)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {code}
> Attaching standalone-full-ha.xml with which is possible to reproduce the issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-10736) Server in cluster hangs during start after previous kill
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-10736?page=com.atlassian.jira.plugin... ]
Kabir Khan resolved WFLY-10736.
-------------------------------
Resolution: Done
> Server in cluster hangs during start after previous kill
> --------------------------------------------------------
>
> Key: WFLY-10736
> URL: https://issues.jboss.org/browse/WFLY-10736
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Miroslav Novak
> Assignee: Paul Ferraro
> Priority: Blocker
> Labels: blocker-WF14
> Fix For: 15.0.0.Alpha1
>
> Attachments: Lodh2TestCase.testRemoteJcaInboundOnly-traces.zip, Lodh2TestCase.testRemoteJcaInboundOnly.zip, Lodh2TestCase.testRemoteJcaInboundOnly2.zip, clusterKilTest.zip, logs-traces.zip, logs-traces2.zip, logs-traces3.zip, logs-traces4.zip, logs-with-workaround.zip, node-1-thread-dump-before-kill-shutdown-sequence.txt, server-with-mdb.log, standalone-full-ha-1.xml, standalone-full-ha-2.xml
>
>
> There is regression in JGroups or Infinispan in one of our tests for fault tolerance of JMS bridges. However work on JMS bridge appears to be unrelated. Issue was hit in WF weekly run.
> Test Scenario:
> * There are two servers. InQueue is deployed on Node 1,
> * OutQueue is deployed on Node 2. Both servers are started.
> * Large byte messages are sent to InQueue deployed on Node 1. Bridge between servers/queues transfers messages from node 1 to node 2.
> * Node 1 is killed and started again.
> * All messages are received from OutQueue deployed on Node 2.
> Result:
> Node 1 does not start after kill and hangs. There is following exception logged in node 2:
> {code}
> :26:17,894 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN100000: Node node-1 joined the cluster
> 09:26:18,520 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN000094: Received new cluster view for channel ejb: [node-2|7] (2) [node-2, node-1]
> 09:26:18,521 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN100001: Node node-1 left the cluster
> 09:26:18,521 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN000094: Received new cluster view for channel ejb: [node-2|7] (2) [node-2, node-1]
> 09:26:18,522 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN100001: Node node-1 left the cluster
> 09:26:18,522 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN000094: Received new cluster view for channel ejb: [node-2|7] (2) [node-2, node-1]
> 09:26:18,522 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN100001: Node node-1 left the cluster
> 09:26:18,522 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN000094: Received new cluster view for channel ejb: [node-2|7] (2) [node-2, node-1]
> 09:26:18,523 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN100001: Node node-1 left the cluster
> 09:26:18,868 INFO [org.infinispan.CLUSTER] (remote-thread--p5-t2) ISPN000310: Starting cluster-wide rebalance for cache default, topology CacheTopology{id=17, phase=READ_OLD_WRITE_ALL, rebalanceId=6, currentCH=ReplicatedConsistentHash{ns = 256, owners = (2)[node-2: 122, node-1: 134]}, pendingCH=ReplicatedConsistentHash{ns = 256, owners = (3)[node-2: 84, node-1: 90, node-1: 82]}, unionCH=null, actualMembers=[node-2, node-1, node-1], persistentUUIDs=[12443bfb-e88a-46f3-919e-9213bf38ce19, 2873237f-d881-463f-8a5a-940bf1d764e5, a05ea8af-a83b-42a9-b937-dc2da1cae6d1]}
> 09:26:18,869 INFO [org.infinispan.CLUSTER] (remote-thread--p5-t2) [Context=default][Scope=node-2]ISPN100002: Started rebalance with topology id 17
> 09:26:18,870 INFO [org.infinispan.CLUSTER] (transport-thread--p14-t5) [Context=default][Scope=node-2]ISPN100003: Node node-2 finished rebalance phase with topology id 17
> 09:26:18,981 INFO [org.infinispan.CLUSTER] (remote-thread--p5-t2) [Context=default][Scope=node-1]ISPN100003: Node node-1 finished rebalance phase with topology id 17
> 09:27:18,530 WARN [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p15-t4) ISPN000197: Error updating cluster member list: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1
> at org.infinispan.remoting.transport.impl.MultiTargetRequest.onTimeout(MultiTargetRequest.java:167)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:87)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:22)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131]
> Suppressed: java.util.concurrent.ExecutionException: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1
> at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) [rt.jar:1.8.0_131]
> at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915) [rt.jar:1.8.0_131]
> at org.infinispan.util.concurrent.CompletableFutures.await(CompletableFutures.java:82)
> at org.infinispan.remoting.transport.Transport.invokeRemotely(Transport.java:71)
> at org.infinispan.topology.ClusterTopologyManagerImpl.confirmMembersAvailable(ClusterTopologyManagerImpl.java:540)
> at org.infinispan.topology.ClusterTopologyManagerImpl.updateCacheMembers(ClusterTopologyManagerImpl.java:523)
> at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:334)
> at org.infinispan.topology.ClusterTopologyManagerImpl.access$500(ClusterTopologyManagerImpl.java:85)
> at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener.lambda$handleViewChange$0(ClusterTopologyManagerImpl.java:745)
> at org.infinispan.executors.LimitedExecutor.runTasks(LimitedExecutor.java:144)
> at org.infinispan.executors.LimitedExecutor.access$100(LimitedExecutor.java:33)
> at org.infinispan.executors.LimitedExecutor$Runner.run(LimitedExecutor.java:174)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131]
> at org.wildfly.clustering.service.concurrent.ClassLoaderThreadFactory.lambda$newThread$0(ClassLoaderThreadFactory.java:47)
> ... 1 more
> Caused by: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1
> at org.infinispan.remoting.transport.impl.MultiTargetRequest.onTimeout(MultiTargetRequest.java:167)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:87)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:22)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131]
> ... 1 more
> [CIRCULAR REFERENCE:java.util.concurrent.ExecutionException: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1]
> 09:27:18,530 WARN [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p16-t4) ISPN000197: Error updating cluster member list: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1
> at org.infinispan.remoting.transport.impl.MultiTargetRequest.onTimeout(MultiTargetRequest.java:167)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:87)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:22)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131]
> Suppressed: java.util.concurrent.ExecutionException: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1
> at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) [rt.jar:1.8.0_131]
> at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915) [rt.jar:1.8.0_131]
> at org.infinispan.util.concurrent.CompletableFutures.await(CompletableFutures.java:82)
> at org.infinispan.remoting.transport.Transport.invokeRemotely(Transport.java:71)
> at org.infinispan.topology.ClusterTopologyManagerImpl.confirmMembersAvailable(ClusterTopologyManagerImpl.java:540)
> at org.infinispan.topology.ClusterTopologyManagerImpl.updateCacheMembers(ClusterTopologyManagerImpl.java:523)
> at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:334)
> at org.infinispan.topology.ClusterTopologyManagerImpl.access$500(ClusterTopologyManagerImpl.java:85)
> at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener.lambda$handleViewChange$0(ClusterTopologyManagerImpl.java:745)
> at org.infinispan.executors.LimitedExecutor.runTasks(LimitedExecutor.java:144)
> at org.infinispan.executors.LimitedExecutor.access$100(LimitedExecutor.java:33)
> at org.infinispan.executors.LimitedExecutor$Runner.run(LimitedExecutor.java:174)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131]
> at org.wildfly.clustering.service.concurrent.ClassLoaderThreadFactory.lambda$newThread$0(ClassLoaderThreadFactory.java:47)
> ... 1 more
> Caused by: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1
> at org.infinispan.remoting.transport.impl.MultiTargetRequest.onTimeout(MultiTargetRequest.java:167)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:87)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:22)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131]
> ... 1 more
> [CIRCULAR REFERENCE:java.util.concurrent.ExecutionException: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1]
> {code}
> There is default JGroups udp stack configured which is used by Infinispan. Both of the servers (jgroups udp) are bound to 127.0.0.1. Node 2 has port offset 1000.
> Attaching thread dump from node 1 when it hangs during start.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (ELY-1675) Merge roles from entry and entry attributes
by Martin Choma (JIRA)
Martin Choma created ELY-1675:
---------------------------------
Summary: Merge roles from entry and entry attributes
Key: ELY-1675
URL: https://issues.jboss.org/browse/ELY-1675
Project: WildFly Elytron
Issue Type: Bug
Components: Realms
Affects Versions: 1.7.0.CR1
Reporter: Martin Choma
Priority: Critical
Double check Elytron ldap realm is capable doing this:
Having ldap entries like this
{code}
dn: cn=jduke,ou=Roles,ou=example2,${dnSuffix}
objectClass: top
objectClass: organizationalRole
description: cn=Echo,ou=Roles,ou=example2,${dnSuffix}
description: cn=TheDuke,ou=Roles,ou=example2,${dnSuffix}
cn: jduke
{code}
User will have roles jduke, Echo and TheDuke.
This was possible with Picketbox with this configuration
{code}
EapSetupTask roleAttributesConfiguration =
new LdapExtSecurityDomainBuilder(SECURITY_DOMAIN_NAME_PREFIX + DEP2)
.prepareDefaultForLdapServer(ldapServer)
.baseCtxDN("ou=People,ou=example2," + ldapServer.getDNSuffix())
.rolesCtxDN("ou=Roles,ou=example2," + ldapServer.getDNSuffix())
.referral("ignore")
.roleFilter("(|(objectClass=referral)(cn={0}))")
.roleAttributeID("description")
.roleAttributeIsDN("true")
.roleNameAttributeID("cn")
.roleRecursion("0")
.configure();
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JGRP-2295) Add local Operation System DNS resolver implementation
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/JGRP-2295?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec commented on JGRP-2295:
-------------------------------------------
//cc [~ryanemerson][~galderz] for visibility.
> Add local Operation System DNS resolver implementation
> ------------------------------------------------------
>
> Key: JGRP-2295
> URL: https://issues.jboss.org/browse/JGRP-2295
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Sebastian Łaskawiec
> Assignee: Sebastian Łaskawiec
>
> The {{DefaultDNSResolver}} queries the DNS server and extracts values it returned. There's however another approach - query the local OS DNS resolver. This approach has some advantages because it takes both {{/etc/hosts}} as well as {{/etc/resolv.conf}} files under consideration. We should provide an {{OSDNSResolver}} implementation that would do it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2650) date comparison using LocatDateTime
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2650?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-2650:
--------------------------------
Sprint: 2018 Week 36-38
> date comparison using LocatDateTime
> -----------------------------------
>
> Key: DROOLS-2650
> URL: https://issues.jboss.org/browse/DROOLS-2650
> Project: Drools
> Issue Type: Feature Request
> Components: core engine
> Affects Versions: 7.7.0.Final
> Environment: Windows 7, Java 8
> Reporter: Sachin Subhedar
> Assignee: Mario Fusco
>
> While upgrading Drools from version 6.5 to 7.7.0, there is a compile issue in rules that use Date Compare.
> e.g. the following rule works fine in 6.5, but errors out in 7.7.0:
> when
> $inventory : AllocatedInventory(expireDateTime != null && (expireDateTime > Custom.todayPlus(0) && <= Custom.todayPlus(2)) )
> …
> then
> modify(...) {
> ...
> }
> retract($inventory);
> end
> =======================
> Custom function returns Java LocalDateTime (java.util.Date and JodaTime use is deprecated)
> The reason it breaks is due to check in function https://github.com/kiegroup/drools/blob/master/drools-compiler/src/main/j...
> Previous version does not have that check. Now, it seems the compiler check compares date value to java.util.Date
> Request a feature to allow LocalDateTime date compare
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-3006) Move test cases affected by equality mode to a specific test class
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-3006:
-----------------------------------
Summary: Move test cases affected by equality mode to a specific test class
Key: DROOLS-3006
URL: https://issues.jboss.org/browse/DROOLS-3006
Project: Drools
Issue Type: Task
Reporter: Mario Fusco
Assignee: Tibor Zimányi
At the moment drools-test-coverage waste lots of time for parametric tests. In particular running same tests for equality and identity it's useless in 99% of cases, so I suggest to create a specific class for equality tests and move there only the tests that make a difference in equality mode
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months