[JBoss JIRA] (WFLY-6690) Read-resource(include-runtime=true) fais on jms-bridge in domain mode
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-6690?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil resolved WFLY-6690.
-------------------------------
Fix Version/s: 11.0.0.Alpha1
Resolution: Done
Underlying fix in wildfly-core has been integrated in WildFly 11.0.0.Alpha1
> Read-resource(include-runtime=true) fais on jms-bridge in domain mode
> ---------------------------------------------------------------------
>
> Key: WFLY-6690
> URL: https://issues.jboss.org/browse/WFLY-6690
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 11.0.0.Alpha1
>
>
> /profile=full/subsystem=messaging-activemq/jms-bridge=bridge-mane-3:read-resource(include-runtime=true)
> {
> "outcome" => "failed",
> "rolled-back" => true
> }
> The server log
> [Host Controller] 15:30:49,150 ERROR
> [org.jboss.as.controller.management-operation]
> (management-handler-thread - 9) WFLYCTL0013: Operation
> ("read-attribute") failed - address: ([
> [Host Controller] ("profile" => "full"),
> [Host Controller] ("subsystem" => "messaging-activemq"),
> [Host Controller] ("jms-bridge" => "bridge-mane-3")
> [Host Controller] ]) - failure description: "WFLYCTL0216: Management resource '[
> [Host Controller] (\"profile\" => \"full\"),
> [Host Controller] (\"subsystem\" => \"messaging-activemq\"),
> [Host Controller] (\"jms-bridge\" => \"bridge-mane-3\")
> [Host Controller] ]' not found"
> Remove the include-runtime=true, it works.
> The issue lies with the "paused" and "started" runtime attributes whose read handler throws an exception if the bridge is not available in the runtime (that is the case in the profile).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (DROOLS-1723) Rule compiler does not fail for misspelled sliding window predicates
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1723?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-1723:
--------------------------------
Sprint: 2017 Week 34-35
> Rule compiler does not fail for misspelled sliding window predicates
> --------------------------------------------------------------------
>
> Key: DROOLS-1723
> URL: https://issues.jboss.org/browse/DROOLS-1723
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.3.0.Final
> Environment: DRL files
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> Rule engine compiles the following DRL with no exception, despite the erroneous expression *window:len*.
> From behavior, it seems that the last part of the condition is simply disregarded.
> {code}
> rule "Risky Event"
> no-loop
> when
> $plcEvent: PLCEvent( input2 > 10.0 ) over window:len(3)
> then
> insert(new RiskyEvent($plcEvent));
>
> end
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (DROOLS-1723) Rule compiler does not fail for misspelled sliding window predicates
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1723?page=com.atlassian.jira.plugi... ]
Mario Fusco moved RHBRMS-2904 to DROOLS-1723:
---------------------------------------------
Project: Drools (was: JBoss BRMS Platform)
Key: DROOLS-1723 (was: RHBRMS-2904)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Docs QE Status: NEW
Component/s: core engine
(was: BRE)
Affects Version/s: (was: 6.4.4.GA)
QE Status: NEW
> Rule compiler does not fail for misspelled sliding window predicates
> --------------------------------------------------------------------
>
> Key: DROOLS-1723
> URL: https://issues.jboss.org/browse/DROOLS-1723
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Environment: DRL files
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> Rule engine compiles the following DRL with no exception, despite the erroneous expression *window:len*.
> From behavior, it seems that the last part of the condition is simply disregarded.
> {code}
> rule "Risky Event"
> no-loop
> when
> $plcEvent: PLCEvent( input2 > 10.0 ) over window:len(3)
> then
> insert(new RiskyEvent($plcEvent));
>
> end
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (DROOLS-1723) Rule compiler does not fail for misspelled sliding window predicates
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1723?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-1723:
--------------------------------
Affects Version/s: 7.3.0.Final
> Rule compiler does not fail for misspelled sliding window predicates
> --------------------------------------------------------------------
>
> Key: DROOLS-1723
> URL: https://issues.jboss.org/browse/DROOLS-1723
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.3.0.Final
> Environment: DRL files
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> Rule engine compiles the following DRL with no exception, despite the erroneous expression *window:len*.
> From behavior, it seems that the last part of the condition is simply disregarded.
> {code}
> rule "Risky Event"
> no-loop
> when
> $plcEvent: PLCEvent( input2 > 10.0 ) over window:len(3)
> then
> insert(new RiskyEvent($plcEvent));
>
> end
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9302) JCA Classes expect new wildfly/elytron metadata class types when processing metadata
by Flavia Rainone (JIRA)
Flavia Rainone created WFLY-9302:
------------------------------------
Summary: JCA Classes expect new wildfly/elytron metadata class types when processing metadata
Key: WFLY-9302
URL: https://issues.jboss.org/browse/WFLY-9302
Project: WildFly
Issue Type: Bug
Components: JCA
Reporter: Flavia Rainone
Assignee: Flavia Rainone
Priority: Critical
Fix For: 11.0.0.Final
The classes that process metadata inside JBoss AS are always enforcing and expecting the new metadata classes.
As a result, if, say, an old version of the ironjacamar.xml file is processed, the IronJacamar metadata types will be returned instead of the new ones, added to Wildfly, and those class cast/and assertions will fail.
This will result in stack traces as the one below:
{code}
Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/store/work/tc-work/a31d203e70e89f90/testsuite/integration/basic/target/jbossas/standalone/tmp/vfs/temp/tempbab5c471e16347e3/content-8f35152e79af20d3/contents/ at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2064) at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterDeploymentService$WildFLyRaDeployer.doDeploy(ResourceAdapterDeploymentService.java:226) at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterDeploymentService.start(ResourceAdapterDeploymentService.java:124) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.AssertionError at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$AbstractWildFlyRaDeployer.getSubjectFactory(AbstractResourceAdapterDeploymentService.java:624) at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1610) ... 7 more{code}
A thorough check has to be made to reverse those casts and replace them by checks only when Elytron data is needed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JGRP-2034) SASLTest-functional and SASL_SimpleAuthorizingCallbackTest-functional fails on IBM jdk 1.8
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2034?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2034:
--------------------------------
OK, great! I moved this back to 3.6.14 and will wait until FRI with the release (closed all the other issues).
> SASLTest-functional and SASL_SimpleAuthorizingCallbackTest-functional fails on IBM jdk 1.8
> ------------------------------------------------------------------------------------------
>
> Key: JGRP-2034
> URL: https://issues.jboss.org/browse/JGRP-2034
> Project: JGroups
> Issue Type: Bug
> Reporter: Ivan Straka
> Assignee: Tristan Tarrant
> Fix For: 3.6.14
>
>
> We see these two tests failing on IBM jdk 1.8
> org.jgroups.protocols.SASLTest-functional
> org.jgroups.protocols.SASL_SimpleAuthorizingCallbackTest-functional
> This issue may be related to https://issues.jboss.org/browse/JGRP-1993 somehow.
> There is standard output of tests.
> {code}
> ------------- testSASLDigestMD5 -----------
> -------------------------------------------------------------------
> GMS: address=A, cluster=SaslTest
> -------------------------------------------------------------------
> 521823 [TRACE] GMS: A: no members discovered after 3000 ms: creating cluster as first member
> 521823 [DEBUG] GMS: A: installing view [A|0] (1) [A]
> 521823 [DEBUG] GMS: A: created cluster (first member). My view is [A|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl
> -------------------------------------------------------------------
> GMS: address=B, cluster=SaslTest
> -------------------------------------------------------------------
> 521825 [TRACE] GMS: B: discovery took 0 ms, members: 1 rsps (1 coords) [done]
> 521826 [DEBUG] GMS: B: sending JOIN(B) to A
> 521826 [TRACE] SASL: B: received CHALLENGE from A
> 521827 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 524826 [WARN] GMS: B: JOIN(B) sent to A timed out (after 3000 ms), on try 1
> 524827 [TRACE] GMS: B: discovery took 1 ms, members: 1 rsps (1 coords) [done]
> 524827 [DEBUG] GMS: B: sending JOIN(B) to A
> 524828 [TRACE] SASL: B: received CHALLENGE from A
> 524828 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 526826 [WARN] SASL: failed to validate SaslHeader from B, header: payload=[B@ad737f58
> ------------- testSASLDigestMD5Failure -----------
> -------------------------------------------------------------------
> GMS: address=A, cluster=SaslTest
> -------------------------------------------------------------------
> 529863 [TRACE] GMS: A: no members discovered after 3000 ms: creating cluster as first member
> 529864 [DEBUG] GMS: A: installing view [A|0] (1) [A]
> 529864 [DEBUG] GMS: A: created cluster (first member). My view is [A|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl
> -------------------------------------------------------------------
> GMS: address=B, cluster=SaslTest
> -------------------------------------------------------------------
> 529866 [TRACE] GMS: B: discovery took 1 ms, members: 1 rsps (1 coords) [done]
> 529866 [DEBUG] GMS: B: sending JOIN(B) to A
> 529867 [TRACE] SASL: B: received CHALLENGE from A
> 529867 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 532867 [WARN] GMS: B: JOIN(B) sent to A timed out (after 3000 ms), on try 1
> 532867 [TRACE] GMS: B: discovery took 0 ms, members: 1 rsps (1 coords) [done]
> 532867 [DEBUG] GMS: B: sending JOIN(B) to A
> 532868 [TRACE] SASL: B: received CHALLENGE from A
> 532869 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 534867 [WARN] SASL: failed to validate SaslHeader from B, header: payload=[B@6f6c2511
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JGRP-2103) GroupRequest times out when the only recipient leaves too soon
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2103?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-2103.
----------------------------
Resolution: Done
A view change will complete the future (done==true) if responses from all view members have been received.
> GroupRequest times out when the only recipient leaves too soon
> --------------------------------------------------------------
>
> Key: JGRP-2103
> URL: https://issues.jboss.org/browse/JGRP-2103
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.10
> Reporter: Dan Berindei
> Assignee: Bela Ban
> Fix For: 3.6.14
>
>
> There is a concurrency issue when a user calls {{messageDispatcher.cast(dests, msg, options, block_for_results, null)}} and adds a listener later with {{req.setListener(listener)}}.
> If the node installs a new view between {{cast()}} and {{setListener()}} that removes all the {{dests}} nodes, the listener is never called. This test fails:
> {code}
> public void testCastToMissingNode() throws Exception {
> d1.setRequestHandler(new MyHandler(new byte[10]));
> b = createChannel(a);
> b.setName("B");
> final CountDownLatch targetLatch = new CountDownLatch(1);
> d2 = new MessageDispatcher(b, null, null, new RequestHandler() {
> @Override
> public Object handle(Message msg) throws Exception {
> targetLatch.await();
> return null;
> }
> });
> b.connect("MessageDispatcherUnitTest");
> Assert.assertEquals(2, b.getView().size());
> final CountDownLatch futureLatch = new CountDownLatch(1);
> FutureListener listener = new FutureListener() {
> @Override
> public void futureDone(Future future) {
> futureLatch.countDown();
> }
> };
> List<Address> dests = Collections.singletonList(b.getAddress());
> byte[] buf = new byte[1];
> Message msg = new Message();
> msg.setBuffer(buf);
> NotifyingFuture<RspList<Object>> future = d1.castMessageWithFuture(dests, msg, RequestOptions.SYNC(), null);
> b.disconnect();
> Thread.sleep(100);
> future.setListener(listener);
> assertTrue(futureLatch.await(10, TimeUnit.SECONDS));
> targetLatch.countDown();
> }
> {code}
> If I change the {{d1.castMessageWithFuture(dests, msg, RequestOptions.SYNC(), null)}} with {{d1.castMessageWithFuture(dests, msg, RequestOptions.SYNC(), listener)}} and comment out the {{future.setListener(listener)}} line, the test passes.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JGRP-2034) SASLTest-functional and SASL_SimpleAuthorizingCallbackTest-functional fails on IBM jdk 1.8
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2034?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2034:
---------------------------
Fix Version/s: 3.6.14
(was: 3.6.15)
> SASLTest-functional and SASL_SimpleAuthorizingCallbackTest-functional fails on IBM jdk 1.8
> ------------------------------------------------------------------------------------------
>
> Key: JGRP-2034
> URL: https://issues.jboss.org/browse/JGRP-2034
> Project: JGroups
> Issue Type: Bug
> Reporter: Ivan Straka
> Assignee: Tristan Tarrant
> Fix For: 3.6.14
>
>
> We see these two tests failing on IBM jdk 1.8
> org.jgroups.protocols.SASLTest-functional
> org.jgroups.protocols.SASL_SimpleAuthorizingCallbackTest-functional
> This issue may be related to https://issues.jboss.org/browse/JGRP-1993 somehow.
> There is standard output of tests.
> {code}
> ------------- testSASLDigestMD5 -----------
> -------------------------------------------------------------------
> GMS: address=A, cluster=SaslTest
> -------------------------------------------------------------------
> 521823 [TRACE] GMS: A: no members discovered after 3000 ms: creating cluster as first member
> 521823 [DEBUG] GMS: A: installing view [A|0] (1) [A]
> 521823 [DEBUG] GMS: A: created cluster (first member). My view is [A|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl
> -------------------------------------------------------------------
> GMS: address=B, cluster=SaslTest
> -------------------------------------------------------------------
> 521825 [TRACE] GMS: B: discovery took 0 ms, members: 1 rsps (1 coords) [done]
> 521826 [DEBUG] GMS: B: sending JOIN(B) to A
> 521826 [TRACE] SASL: B: received CHALLENGE from A
> 521827 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 524826 [WARN] GMS: B: JOIN(B) sent to A timed out (after 3000 ms), on try 1
> 524827 [TRACE] GMS: B: discovery took 1 ms, members: 1 rsps (1 coords) [done]
> 524827 [DEBUG] GMS: B: sending JOIN(B) to A
> 524828 [TRACE] SASL: B: received CHALLENGE from A
> 524828 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 526826 [WARN] SASL: failed to validate SaslHeader from B, header: payload=[B@ad737f58
> ------------- testSASLDigestMD5Failure -----------
> -------------------------------------------------------------------
> GMS: address=A, cluster=SaslTest
> -------------------------------------------------------------------
> 529863 [TRACE] GMS: A: no members discovered after 3000 ms: creating cluster as first member
> 529864 [DEBUG] GMS: A: installing view [A|0] (1) [A]
> 529864 [DEBUG] GMS: A: created cluster (first member). My view is [A|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl
> -------------------------------------------------------------------
> GMS: address=B, cluster=SaslTest
> -------------------------------------------------------------------
> 529866 [TRACE] GMS: B: discovery took 1 ms, members: 1 rsps (1 coords) [done]
> 529866 [DEBUG] GMS: B: sending JOIN(B) to A
> 529867 [TRACE] SASL: B: received CHALLENGE from A
> 529867 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 532867 [WARN] GMS: B: JOIN(B) sent to A timed out (after 3000 ms), on try 1
> 532867 [TRACE] GMS: B: discovery took 0 ms, members: 1 rsps (1 coords) [done]
> 532867 [DEBUG] GMS: B: sending JOIN(B) to A
> 532868 [TRACE] SASL: B: received CHALLENGE from A
> 532869 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 534867 [WARN] SASL: failed to validate SaslHeader from B, header: payload=[B@6f6c2511
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JGRP-2034) SASLTest-functional and SASL_SimpleAuthorizingCallbackTest-functional fails on IBM jdk 1.8
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/JGRP-2034?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant commented on JGRP-2034:
---------------------------------------
I have a fix for this. Will issue a pr on Friday
> SASLTest-functional and SASL_SimpleAuthorizingCallbackTest-functional fails on IBM jdk 1.8
> ------------------------------------------------------------------------------------------
>
> Key: JGRP-2034
> URL: https://issues.jboss.org/browse/JGRP-2034
> Project: JGroups
> Issue Type: Bug
> Reporter: Ivan Straka
> Assignee: Tristan Tarrant
> Fix For: 3.6.15
>
>
> We see these two tests failing on IBM jdk 1.8
> org.jgroups.protocols.SASLTest-functional
> org.jgroups.protocols.SASL_SimpleAuthorizingCallbackTest-functional
> This issue may be related to https://issues.jboss.org/browse/JGRP-1993 somehow.
> There is standard output of tests.
> {code}
> ------------- testSASLDigestMD5 -----------
> -------------------------------------------------------------------
> GMS: address=A, cluster=SaslTest
> -------------------------------------------------------------------
> 521823 [TRACE] GMS: A: no members discovered after 3000 ms: creating cluster as first member
> 521823 [DEBUG] GMS: A: installing view [A|0] (1) [A]
> 521823 [DEBUG] GMS: A: created cluster (first member). My view is [A|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl
> -------------------------------------------------------------------
> GMS: address=B, cluster=SaslTest
> -------------------------------------------------------------------
> 521825 [TRACE] GMS: B: discovery took 0 ms, members: 1 rsps (1 coords) [done]
> 521826 [DEBUG] GMS: B: sending JOIN(B) to A
> 521826 [TRACE] SASL: B: received CHALLENGE from A
> 521827 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 524826 [WARN] GMS: B: JOIN(B) sent to A timed out (after 3000 ms), on try 1
> 524827 [TRACE] GMS: B: discovery took 1 ms, members: 1 rsps (1 coords) [done]
> 524827 [DEBUG] GMS: B: sending JOIN(B) to A
> 524828 [TRACE] SASL: B: received CHALLENGE from A
> 524828 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 526826 [WARN] SASL: failed to validate SaslHeader from B, header: payload=[B@ad737f58
> ------------- testSASLDigestMD5Failure -----------
> -------------------------------------------------------------------
> GMS: address=A, cluster=SaslTest
> -------------------------------------------------------------------
> 529863 [TRACE] GMS: A: no members discovered after 3000 ms: creating cluster as first member
> 529864 [DEBUG] GMS: A: installing view [A|0] (1) [A]
> 529864 [DEBUG] GMS: A: created cluster (first member). My view is [A|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl
> -------------------------------------------------------------------
> GMS: address=B, cluster=SaslTest
> -------------------------------------------------------------------
> 529866 [TRACE] GMS: B: discovery took 1 ms, members: 1 rsps (1 coords) [done]
> 529866 [DEBUG] GMS: B: sending JOIN(B) to A
> 529867 [TRACE] SASL: B: received CHALLENGE from A
> 529867 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 532867 [WARN] GMS: B: JOIN(B) sent to A timed out (after 3000 ms), on try 1
> 532867 [TRACE] GMS: B: discovery took 0 ms, members: 1 rsps (1 coords) [done]
> 532867 [DEBUG] GMS: B: sending JOIN(B) to A
> 532868 [TRACE] SASL: B: received CHALLENGE from A
> 532869 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 534867 [WARN] SASL: failed to validate SaslHeader from B, header: payload=[B@6f6c2511
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3210) Wildfly module isolation not working consistently
by Nuno Godinho de Matos (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3210?page=com.atlassian.jira.plugi... ]
Nuno Godinho de Matos commented on WFCORE-3210:
-----------------------------------------------
Uau!
That is really powerful.
I will try to get the configuration I have on the log4jwildfly.properties file into the subsystem configuration and see how the experience of puting the appenders there goes.
I will not work on this this week due to other priority tasks, but I will try to as soon as possible to take a look at this approach.
Many thanks for all the help.
Kindest regards.
> Wildfly module isolation not working consistently
> -------------------------------------------------
>
> Key: WFCORE-3210
> URL: https://issues.jboss.org/browse/WFCORE-3210
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging, Modules
> Affects Versions: 2.2.0.Final
> Reporter: Nuno Godinho de Matos
>
> There is an underministic bug on the module layer of wildfly, whereby the boot logic of the application server is not ensured to give the appropriate module isolation - which can lead to unexpected boot classpath problems.
> An example of this phenomena is given on the wildfly forum thread:
> https://developer.jboss.org/thread/275839
> In this example, we have the logging subsystem setup to use a custome handler.
> The custom handler wishes to have acces to the JUL extension classes on the org.jboss.logmanger module, but wishes to do have no relationship with the org.apache.log4j packages associated to the wildfly org.jboss.log4j module.
> What we see in this example is that an application gets from wildfly mixed behavior.
> Most of the time, during boot, the processes works without problem, where the custom handler runs isolated from the undersired log4j libraries within wildfly.
> But other times the application boot procedure will not go smoothly with the custom handler having processes routing JUL LogRecords events into the bundled log4j because the application server has loaded some of the classes that exist the org.jboss.log4j module.
> And as we know when the same class is loaded by different class loaders, then that class that orinates from class loader A cannot be assigned to the corresponding class of class loader B, even if the classes are exactly the same.
> This is not an isolated issue.
> There are also open issues on the wildfly forum reporting on startup problems on the logging subsystme where sometimes the LogManager class had not yet been loaded, and sometimes this issue goes away.
> This is an indication of some deep issue engrained into the module loading, where the module isolation behavior is not ensured to work all the time and that the boot procedure is not deterministically reliable.
> It should not be that the application server some time starts successfully and others not.
> Booting wildfly should always result in the same outcode.
> Problems of this nature with class loading problems should either always happen if the configuration is not done properly or never happen if the configuration is proper.
> In the case of thread:
> https://developer.jboss.org/thread/275839
> Our belief is that the configuration is doing all it possible can to request the necessary module isolation from base packages and the outcome where log4j class load problems take place should never be allowed to happen.
> Many thanks.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months