[JBoss JIRA] (WFLY-3573) Adding incorrect JGroups protocol should provide better error description than CNFE
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3573?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-3573:
---------------------------------
Fix Version/s: (was: 10.0.0.Final)
> Adding incorrect JGroups protocol should provide better error description than CNFE
> -----------------------------------------------------------------------------------
>
> Key: WFLY-3573
> URL: https://issues.jboss.org/browse/WFLY-3573
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: JBoss AS7 7.2.0.Final, 8.1.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Labels: ux
>
> As reported by the community user:
> {noformat}
> [standalone@localhost:9990 / #] list-batch
> #1 /subsystem=jgroups/stack=test:add()
> #2 /subsystem=jgroups/stack=test/transport=TRANSPORT:add(type="udp",socket-binding=jgroups-udp)
> #3 /subsystem=jgroups/stack=test:add-protocol(type=FD_SOCK,socket-binding=jgroups-udp-fd)
> [standalone@localhost:9990 / #] run-batch
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0158: Operation handler failed: java.lang.ClassNotFoundException: org.jgroups.protocols.udp from [Module \"org.jboss.as.clustering.jgroups:main\" from local module loader @4d9f6ce5 (finder: local module finder @1da65633 (roots: /home/rhusar/as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules,/home/rhusar/as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))]"}}
> [standalone@localhost:9990 / #]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-3573) Adding incorrect JGroups protocol should provide better error description than CNFE
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3573?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-3573:
---------------------------------
Issue Type: Enhancement (was: Feature Request)
> Adding incorrect JGroups protocol should provide better error description than CNFE
> -----------------------------------------------------------------------------------
>
> Key: WFLY-3573
> URL: https://issues.jboss.org/browse/WFLY-3573
> Project: WildFly
> Issue Type: Enhancement
> Components: Clustering
> Affects Versions: JBoss AS7 7.2.0.Final, 8.1.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Labels: ux
>
> As reported by the community user:
> {noformat}
> [standalone@localhost:9990 / #] list-batch
> #1 /subsystem=jgroups/stack=test:add()
> #2 /subsystem=jgroups/stack=test/transport=TRANSPORT:add(type="udp",socket-binding=jgroups-udp)
> #3 /subsystem=jgroups/stack=test:add-protocol(type=FD_SOCK,socket-binding=jgroups-udp-fd)
> [standalone@localhost:9990 / #] run-batch
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0158: Operation handler failed: java.lang.ClassNotFoundException: org.jgroups.protocols.udp from [Module \"org.jboss.as.clustering.jgroups:main\" from local module loader @4d9f6ce5 (finder: local module finder @1da65633 (roots: /home/rhusar/as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules,/home/rhusar/as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))]"}}
> [standalone@localhost:9990 / #]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1226) undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1226?page=com.atlassian.jira.plugi... ]
Tomaz Cerar commented on WFCORE-1226:
-------------------------------------
you marked that this is issue in WFCORE 2.0.4, aka currently latest, but description about reproducing is on EAP 6.4.4 which is much older code.
Can you confirm that problem exists in both versions?
> undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler
> -------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1226
> URL: https://issues.jboss.org/browse/WFCORE-1226
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.4.Final
> Reporter: Chao Wang
> Assignee: Chao Wang
> Attachments: WFCORE-1226-wildflytest.patch, WFCORE-1226.patch
>
>
> {noformat}
> 1. Start EAP 6.4.4 in domain mode and deploy application using following CLI command:
> ~~
> [domain@localhost:9999 /] deploy /Applications/WebApp-1.war --server-groups=main-server-group --name=WebApp-1.war --runtime-name=WebApp-1.war
> ~~~
> 2. Deploy next version of application in "disabled" state with same "runtime-name"
> ~~~
> [domain@localhost:9999 /] deploy /Applications/WebApp-2.war --disabled --name=WebApp-2.war --runtime-name=WebApp-1.war
> ~~~
> 3. Now use replace-deployment command to access latest version of application:
> ~~~
> [domain@localhost:9999 /] /server-group=main-server-group:replace-deployment(name=WebApp-2.war,to-replace=WebApp-1.war)
> ~~~
> its working fine,laest version of application is accessable.
> 4. Now try to undeploy old version of application
> ~~~
> /server-group=main-server-group/deployment=WebApp-1.war:undeploy()
> ~~~
> After undploying older version, we are not able to access(404) latest version of application(WebApp-2.war) as well.To access it we have to redeploy it.
> Same steps are working fine in Standalone mode.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1268) undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1268:
----------------------------------------
Summary: undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler
Key: WFCORE-1268
URL: https://issues.jboss.org/browse/WFCORE-1268
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 2.0.4.Final
Reporter: Chao Wang
Assignee: Chao Wang
{noformat}
1. Start EAP 6.4.4 in domain mode and deploy application using following CLI command:
~~
[domain@localhost:9999 /] deploy /Applications/WebApp-1.war --server-groups=main-server-group --name=WebApp-1.war --runtime-name=WebApp-1.war
~~~
2. Deploy next version of application in "disabled" state with same "runtime-name"
~~~
[domain@localhost:9999 /] deploy /Applications/WebApp-2.war --disabled --name=WebApp-2.war --runtime-name=WebApp-1.war
~~~
3. Now use replace-deployment command to access latest version of application:
~~~
[domain@localhost:9999 /] /server-group=main-server-group:replace-deployment(name=WebApp-2.war,to-replace=WebApp-1.war)
~~~
its working fine,laest version of application is accessable.
4. Now try to undeploy old version of application
~~~
/server-group=main-server-group/deployment=WebApp-1.war:undeploy()
~~~
After undploying older version, we are not able to access(404) latest version of application(WebApp-2.war) as well.To access it we have to redeploy it.
Same steps are working fine in Standalone mode.
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-5928) Intermittent NPE registering a slave HC in mixed-domain test suite
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-5928?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-5928:
----------------------------------------
BTW, the alternate code paths for creating a different OperationTransformerRegistry go through GlobalTransformerRegistry.create OperationTransformerRegistry.SubRegistry.create.
> Intermittent NPE registering a slave HC in mixed-domain test suite
> ------------------------------------------------------------------
>
> Key: WFLY-5928
> URL: https://issues.jboss.org/browse/WFLY-5928
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, Test Suite
> Affects Versions: 10.0.0.CR4
> Reporter: Brian Stansberry
> Assignee: Kabir Khan
>
> I've occasionally seen test failures in the mixed domain tests when a testsuite cannot start because the slave HC can't register due to an NPE on the master:
> For example:
> http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=82653&tab=buil...
> Critical log details:
> {code}[0m16:16:15,252 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1
> [0m[0m16:16:15,363 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
> [0m[Host Controller] [0m16:16:15,871 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1[0m
> [Host Controller] [0m[0m16:16:16,015 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1[0m
> [Host Controller] [0m[0m16:16:16,068 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting[0m
> [Host Controller] [0m[0m16:16:16,625 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.10.GA-redhat-1[0m
> [Host Controller] [0m[0m16:16:16,629 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.10.GA-redhat-1[0m
> [Host Controller] [0m[0m16:16:16,657 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version (unknown)[0m
> [Host Controller] [0m[0m16:16:16,705 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on [::1]:19999[0m
> INFO [org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil] ServerIdentity{name=server-one, host=slave, server-group=other-server-group} status is starting
> [Host Controller] [0m[31m16:16:17,913 ERROR [org.jboss.as.controller.management-operation] (Host Controller Service Threads - 50) WFLYCTL0013: Operation ("read-master-domain-model") failed - address: ([]): java.lang.NullPointerException[0m
> [Host Controller] [31m at org.jboss.as.controller.registry.OperationTransformerRegistry$1.getResourceTransformer(OperationTransformerRegistry.java:83)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.resolveTransformer(ResourceTransformationContextImpl.java:235)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChild(ResourceTransformationContextImpl.java:285)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChildren(ResourceTransformationContextImpl.java:254)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformer$1.transformResource(ResourceTransformer.java:53)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.description.TransformingDescription$3.invokeNext(TransformingDescription.java:161)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.description.AttributeTransformationRule.transformResource(AttributeTransformationRule.java:103)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.description.TransformingDescription.transformResource(TransformingDescription.java:167)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChild(ResourceTransformationContextImpl.java:289)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChildren(ResourceTransformationContextImpl.java:254)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformer$1.transformResource(ResourceTransformer.java:53)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.TransformersImpl.transformRootResource(TransformersImpl.java:115)[0m
> [Host Controller] [31m at org.jboss.as.domain.controller.operations.ReadMasterDomainModelUtil.readMasterDomainResourcesForInitialConnect(ReadMasterDomainModelUtil.java:88)[0m
> [Host Controller] [31m at org.jboss.as.domain.controller.operations.ReadDomainModelHandler.execute(ReadDomainModelHandler.java:51)[0m
> [Host Controller] [31m at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)[0m
> [Host Controller] [31m at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)[0m
> [Host Controller] [31m at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)[0m
> [Host Controller] [31m at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1343)[0m
> [Host Controller] [31m at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:395)[0m
> [Host Controller] [31m at org.jboss.as.controller.AbstractControllerService.internalExecute(AbstractControllerService.java:408)[0m
> [Host Controller] [31m at org.jboss.as.host.controller.DomainModelControllerService.access$900(DomainModelControllerService.java:175)[0m
> [Host Controller] [31m at org.jboss.as.host.controller.DomainModelControllerService$InternalExecutor.execute(DomainModelControllerService.java:1229)[0m
> [Host Controller] [31m at org.jboss.as.host.controller.mgmt.HostControllerRegistrationHandler$RegistrationContext.processRegistration(HostControllerRegistrationHandler.java:424)[0m
> [Host Controller] [31m at org.jboss.as.host.controller.mgmt.HostControllerRegistrationHandler$RegistrationContext.access$400(HostControllerRegistrationHandler.java:334)[0m
> [Host Controller] [31m at org.jboss.as.host.controller.mgmt.HostControllerRegistrationHandler$InitiateRegistrationHandler$1.execute(HostControllerRegistrationHandler.java:230)[0m
> [Host Controller] [31m at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)[0m
> [Host Controller] [31m at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:465)[0m
> [Host Controller] [31m at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[0m
> [Host Controller] [31m at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[0m
> [Host Controller] [31m at java.lang.Thread.run(Thread.java:745)[0m
> [Host Controller] [31m at org.jboss.threads.JBossThread.run(JBossThread.java:320)[0m
> [Host Controller] [31m[0m
> [Host Controller] [0m[33m16:16:17,935 WARN [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010900: Could not connect to remote domain controller at remote://[::1]:9999 -- 1-$-WFLYCTL0158: Operation handler failed: java.lang.NullPointerException[0m
> [Host Controller] [33m[0m[33m16:16:17,936 WARN [org.jboss.as.host.controller] (Controller Boot Thread) JBAS016581: No domain controller discovery options remain.[0m
> [Host Controller] [33m[0m[31m16:16:17,939 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: JBAS016519: Tried all domain controller discovery option(s) but unable to connect[0m
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-5928) Intermittent NPE registering a slave HC in mixed-domain test suite
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-5928?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-5928:
--------------------------------------
Assignee: Kabir Khan (was: Brian Stansberry)
Per our conversation, assigning to you in case you see something.
https://github.com/wildfly/wildfly-core/pull/1339 avoids the NPE, but I don't get why this failure is intermittent.
GlobalTransformerRegistry.registerTransformer will pass a 'null' into the getOrCreate method that creates a OperationTransformerRegistry, so having this var be 'null' is possible via a normal code path. Why this doesn't regularly fail is a mystery though. Perhaps a different OperationTransformerRegistry instance with the same address/version is created via a different code path in some cases, and there is some timing effect involved. The transformer registration is all single threaded AFAIK though.
> Intermittent NPE registering a slave HC in mixed-domain test suite
> ------------------------------------------------------------------
>
> Key: WFLY-5928
> URL: https://issues.jboss.org/browse/WFLY-5928
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, Test Suite
> Affects Versions: 10.0.0.CR4
> Reporter: Brian Stansberry
> Assignee: Kabir Khan
>
> I've occasionally seen test failures in the mixed domain tests when a testsuite cannot start because the slave HC can't register due to an NPE on the master:
> For example:
> http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=82653&tab=buil...
> Critical log details:
> {code}[0m16:16:15,252 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1
> [0m[0m16:16:15,363 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
> [0m[Host Controller] [0m16:16:15,871 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1[0m
> [Host Controller] [0m[0m16:16:16,015 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1[0m
> [Host Controller] [0m[0m16:16:16,068 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting[0m
> [Host Controller] [0m[0m16:16:16,625 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.10.GA-redhat-1[0m
> [Host Controller] [0m[0m16:16:16,629 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.10.GA-redhat-1[0m
> [Host Controller] [0m[0m16:16:16,657 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version (unknown)[0m
> [Host Controller] [0m[0m16:16:16,705 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on [::1]:19999[0m
> INFO [org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil] ServerIdentity{name=server-one, host=slave, server-group=other-server-group} status is starting
> [Host Controller] [0m[31m16:16:17,913 ERROR [org.jboss.as.controller.management-operation] (Host Controller Service Threads - 50) WFLYCTL0013: Operation ("read-master-domain-model") failed - address: ([]): java.lang.NullPointerException[0m
> [Host Controller] [31m at org.jboss.as.controller.registry.OperationTransformerRegistry$1.getResourceTransformer(OperationTransformerRegistry.java:83)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.resolveTransformer(ResourceTransformationContextImpl.java:235)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChild(ResourceTransformationContextImpl.java:285)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChildren(ResourceTransformationContextImpl.java:254)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformer$1.transformResource(ResourceTransformer.java:53)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.description.TransformingDescription$3.invokeNext(TransformingDescription.java:161)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.description.AttributeTransformationRule.transformResource(AttributeTransformationRule.java:103)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.description.TransformingDescription.transformResource(TransformingDescription.java:167)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChild(ResourceTransformationContextImpl.java:289)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChildren(ResourceTransformationContextImpl.java:254)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformer$1.transformResource(ResourceTransformer.java:53)[0m
> [Host Controller] [31m at org.jboss.as.controller.transform.TransformersImpl.transformRootResource(TransformersImpl.java:115)[0m
> [Host Controller] [31m at org.jboss.as.domain.controller.operations.ReadMasterDomainModelUtil.readMasterDomainResourcesForInitialConnect(ReadMasterDomainModelUtil.java:88)[0m
> [Host Controller] [31m at org.jboss.as.domain.controller.operations.ReadDomainModelHandler.execute(ReadDomainModelHandler.java:51)[0m
> [Host Controller] [31m at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)[0m
> [Host Controller] [31m at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)[0m
> [Host Controller] [31m at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)[0m
> [Host Controller] [31m at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1343)[0m
> [Host Controller] [31m at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:395)[0m
> [Host Controller] [31m at org.jboss.as.controller.AbstractControllerService.internalExecute(AbstractControllerService.java:408)[0m
> [Host Controller] [31m at org.jboss.as.host.controller.DomainModelControllerService.access$900(DomainModelControllerService.java:175)[0m
> [Host Controller] [31m at org.jboss.as.host.controller.DomainModelControllerService$InternalExecutor.execute(DomainModelControllerService.java:1229)[0m
> [Host Controller] [31m at org.jboss.as.host.controller.mgmt.HostControllerRegistrationHandler$RegistrationContext.processRegistration(HostControllerRegistrationHandler.java:424)[0m
> [Host Controller] [31m at org.jboss.as.host.controller.mgmt.HostControllerRegistrationHandler$RegistrationContext.access$400(HostControllerRegistrationHandler.java:334)[0m
> [Host Controller] [31m at org.jboss.as.host.controller.mgmt.HostControllerRegistrationHandler$InitiateRegistrationHandler$1.execute(HostControllerRegistrationHandler.java:230)[0m
> [Host Controller] [31m at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)[0m
> [Host Controller] [31m at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:465)[0m
> [Host Controller] [31m at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[0m
> [Host Controller] [31m at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[0m
> [Host Controller] [31m at java.lang.Thread.run(Thread.java:745)[0m
> [Host Controller] [31m at org.jboss.threads.JBossThread.run(JBossThread.java:320)[0m
> [Host Controller] [31m[0m
> [Host Controller] [0m[33m16:16:17,935 WARN [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010900: Could not connect to remote domain controller at remote://[::1]:9999 -- 1-$-WFLYCTL0158: Operation handler failed: java.lang.NullPointerException[0m
> [Host Controller] [33m[0m[33m16:16:17,936 WARN [org.jboss.as.host.controller] (Controller Boot Thread) JBAS016581: No domain controller discovery options remain.[0m
> [Host Controller] [33m[0m[31m16:16:17,939 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: JBAS016519: Tried all domain controller discovery option(s) but unable to connect[0m
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JGRP-2000) Output of ProtocolStack.printProtocolSpecAsXML() cannot be used as a protocol stack without manual modifications
by Jim Thomas (JIRA)
[ https://issues.jboss.org/browse/JGRP-2000?page=com.atlassian.jira.plugin.... ]
Jim Thomas commented on JGRP-2000:
----------------------------------
I ended up switching to using property variables so I could use the same hand-built file on all members, so no big deal if you don't get to it any time soon (or at all). I probably should have figured that out a long time ago instead of going to programmatic in the first place.
I think you can use props.getClass().getName() instead of props.getName() and then strip off a leading "org.jgroups.protocols." if present to keep it looking clean. It will also add clarity if the user is using custom protocols. The other thing I noticed is that it wrote this under GMS:
membership_change_policy="org.jgroups.protocols.pbcast.GMS$DefaultMembershipPolicy@47c89ac"
which might cause an error as well but I never got that far.
> Output of ProtocolStack.printProtocolSpecAsXML() cannot be used as a protocol stack without manual modifications
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JGRP-2000
> URL: https://issues.jboss.org/browse/JGRP-2000
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.4
> Reporter: Jim Thomas
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.6.7
>
>
> The output of printProtocolSpecAsXML does not contain the pbcast package prefix for NACKACK2, GMS, STATE, etc. so the load fails due to class load failure.
> Suggest either add org.jgroups.protocols.pbcast to the protocol loading search or write protocol names with full classpath when printing the spec.
> Might it also make sense to skip writing out deprecated parameters?
> Reason: I'm generating my protocol stack programmatically because some of the parameter values are determined at run time. In order to facilitate some experimentation with timeouts/retries/etc. I decided to temporarily use an xml file which I first generate by writing out the stack to an xml file which we can tweak the settings for subsequent runs. Since every member has a unique protocol stack keeping the edits to a minimum is helpful. (Maybe using property variables would be a better approach for me?)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months