October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4733) Server stops after switching from 'local' DC to 'remote' DC

by Joerg Baesner (Jira)

Joerg Baesner created WFCORE-4733: ------------------------------------- Summary: Server stops after switching from 'local' DC to 'remote' DC Key: WFCORE-4733 URL: https://issues.jboss.org/browse/WFCORE-4733 Project: WildFly Core Issue Type: Bug Components: Management Affects Versions: 10.0.0.Final Environment: 2 servers started as DC on two different machines Reporter: Joerg Baesner Assignee: Jeff Mesnil Install WildFly on two different machines, add an 'admin' user and start the {{host-master.xml}} configurations on each node, like: machineA: (10.10.10.1) {noformat} $JBOSS_HOME/bin/add-user.sh -u admin -p admin $JBOSS_HOME/bin/domain.sh --host-config.xml -Djboss.bind.address.management=10.10.10.1 {noformat} machineB: 10.10.10.2 {noformat} $JBOSS_HOME/bin/add-user.sh -u admin -p admin $JBOSS_HOME/bin/domain.sh --host-config.xml -Djboss.bind.address.management=10.10.10.2 {noformat} And then applying a simplified script like below to machineB: {code} batch /host=master:write-attribute(name=name, value=slave) /host=master/core-service=discovery-options/static-discovery=primary:add(host=10.10.10.1, port=9990, protocol=remote+http) /host=master:write-remote-domain-controller(username=admin, security-realm="ManagementRealm") /host=master/core-service=management/security-realm=ManagementRealm/server-identity=secret:add(value="YWRtaW4=") run-batch /host=master:reload {code} Executing this scripts results in a server log output like below and stopping of the 'DomainController': {noformat} [Host Controller] INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1) [Host Controller] WARN [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /home/jbaesner/cases/02477162/jboss-eap-7.2/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost [Host Controller] WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0001: Could not connect to remote domain controller remote+http://10.0.0.1:9990: 2-$-WFLYDC0015: There is already a registered host named 'master' [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnection$HostControllerConnectRequest.handleRequest(RemoteDomainConnection.java:390) [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:321) [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleRequest(AbstractMessageHandler.java:286) [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:234) [Host Controller] at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:85) [Host Controller] at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) [Host Controller] at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991) [Host Controller] at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [Host Controller] at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [Host Controller] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [Host Controller] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) [Host Controller] at java.lang.Thread.run(Thread.java:748) [Host Controller] [Host Controller] WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0147: No domain controller discovery options remain. [Host Controller] ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0002: Could not connect to master. Error was: java.lang.IllegalStateException: WFLYHC0120: Tried all domain controller discovery option(s) but unable to connect [Host Controller] FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0178: Aborting with exit code 99 [Host Controller] INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: JBoss EAP 7.2.4.GA (WildFly Core 6.0.16.Final-redhat-00002) stopped in 77ms {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4696) [DMN Designer] BC DOs as DMN DTs - Show a warning message into the import dialog

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-4696: --------------------------------------- Summary: [DMN Designer] BC DOs as DMN DTs - Show a warning message into the import dialog Key: DROOLS-4696 URL: https://issues.jboss.org/browse/DROOLS-4696 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Gomes Assignee: Daniel José dos Santos Attachments: warning.png Show a warning message into the import dialog when any Data Object name matches with some Data Type name: -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4695) [DMN Designer] BC DOs as DMN DTs - Show a success message after the import operation

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-4695: --------------------------------------- Summary: [DMN Designer] BC DOs as DMN DTs - Show a success message after the import operation Key: DROOLS-4695 URL: https://issues.jboss.org/browse/DROOLS-4695 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Gomes Assignee: Daniel José dos Santos Attachments: success.png Show the following success message after the import operation: !success.png|width=600! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2391) BindException on Windows

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2391?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2391: -------------------------------- OK, the testsuite passed. I commited and merged this patch to master. [~thmarx] Please try it out and let me know if this fixes the Windows bind issue! Cheers, > BindException on Windows > ------------------------ > > Key: JGRP-2391 > URL: https://issues.jboss.org/browse/JGRP-2391 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.1.0, 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, 4.1.6 > Environment: Openjdk 13 > Microsoft Windows 10 > Reporter: Thorsten Marx > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.7 > > Attachments: jgroups.patch > > > After updating to jgroups 4.1.6 i get the following BindException > {code} > java.net.BindException: Cannot assign requested address: Cannot bind > at java.base/java.net.TwoStacksPlainDatagramSocketImpl.bind0(Native Method) > at java.base/java.net.TwoStacksPlainDatagramSocketImpl.bind0(TwoStacksPlainDatagramSocketImpl.java:114) > at java.base/java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:117) > at java.base/java.net.TwoStacksPlainDatagramSocketImpl.bind(TwoStacksPlainDatagramSocketImpl.java:98) > at java.base/java.net.DatagramSocket.bind(DatagramSocket.java:395) > at java.base/java.net.MulticastSocket.<init>(MulticastSocket.java:176) > at org.jgroups.util.DefaultSocketFactory.createMulticastSocket(DefaultSocketFactory.java:92) > at org.jgroups.stack.DiagnosticsHandler.startUDP(DiagnosticsHandler.java:180) > at org.jgroups.stack.DiagnosticsHandler.start(DiagnosticsHandler.java:122) > at org.jgroups.protocols.TP.startDiagnostics(TP.java:1031) > at org.jgroups.protocols.TP.start(TP.java:938) > at org.jgroups.protocols.UDP.start(UDP.java:295) > at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:888) > at org.jgroups.JChannel.startStack(JChannel.java:980) > at org.jgroups.JChannel._preConnect(JChannel.java:844) > at org.jgroups.JChannel.connect(JChannel.java:349) > at org.jgroups.JChannel.connect(JChannel.java:343) > at com.thorstenmarx.webtools.cluster.JGroupsTest.simple(JGroupsTest.java:43) > {code} > It seems to be caused by https://stackoverflow.com/questions/14086740/how-to-create-a-new-multicas... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2391) BindException on Windows

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2391?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2391. ---------------------------- Resolution: Done > BindException on Windows > ------------------------ > > Key: JGRP-2391 > URL: https://issues.jboss.org/browse/JGRP-2391 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.1.0, 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, 4.1.6 > Environment: Openjdk 13 > Microsoft Windows 10 > Reporter: Thorsten Marx > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.7 > > Attachments: jgroups.patch > > > After updating to jgroups 4.1.6 i get the following BindException > {code} > java.net.BindException: Cannot assign requested address: Cannot bind > at java.base/java.net.TwoStacksPlainDatagramSocketImpl.bind0(Native Method) > at java.base/java.net.TwoStacksPlainDatagramSocketImpl.bind0(TwoStacksPlainDatagramSocketImpl.java:114) > at java.base/java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:117) > at java.base/java.net.TwoStacksPlainDatagramSocketImpl.bind(TwoStacksPlainDatagramSocketImpl.java:98) > at java.base/java.net.DatagramSocket.bind(DatagramSocket.java:395) > at java.base/java.net.MulticastSocket.<init>(MulticastSocket.java:176) > at org.jgroups.util.DefaultSocketFactory.createMulticastSocket(DefaultSocketFactory.java:92) > at org.jgroups.stack.DiagnosticsHandler.startUDP(DiagnosticsHandler.java:180) > at org.jgroups.stack.DiagnosticsHandler.start(DiagnosticsHandler.java:122) > at org.jgroups.protocols.TP.startDiagnostics(TP.java:1031) > at org.jgroups.protocols.TP.start(TP.java:938) > at org.jgroups.protocols.UDP.start(UDP.java:295) > at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:888) > at org.jgroups.JChannel.startStack(JChannel.java:980) > at org.jgroups.JChannel._preConnect(JChannel.java:844) > at org.jgroups.JChannel.connect(JChannel.java:349) > at org.jgroups.JChannel.connect(JChannel.java:343) > at com.thorstenmarx.webtools.cluster.JGroupsTest.simple(JGroupsTest.java:43) > {code} > It seems to be caused by https://stackoverflow.com/questions/14086740/how-to-create-a-new-multicas... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-4694: --------------------------------------- Summary: [DMN Designer] BC DOs as DMN DTs - Create import action into the UI Key: DROOLS-4694 URL: https://issues.jboss.org/browse/DROOLS-4694 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Gomes Assignee: Daniel José dos Santos Consume the service provided by DROOLS-4680 and create Data Types in the UI. ⚠️ Notice: - Respect the nesting logic - Use the data types manager for creating type (just like the "Add" button) - The new data types must be added in the end of the list - If a Data Type with the same name already exists, remove it, and add the new one. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4687) k8s won't kill a pod who expose not available flag after n-attempts to read a snapshot

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4687?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4687: --------------------------------------- Sprint: 2019 Week 44-46 (from Okt 28) > k8s won't kill a pod who expose not available flag after n-attempts to read a snapshot > -------------------------------------------------------------------------------------- > > Key: DROOLS-4687 > URL: https://issues.jboss.org/browse/DROOLS-4687 > Project: Drools > Issue Type: Bug > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > Labels: HADrools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4623) Using a negated constraint in a not pattern doesn't work with executable model

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-4623?page=com.atlassian.jira.plugi... ] Luca Molteni updated DROOLS-4623: --------------------------------- Story Points: 5 > Using a negated constraint in a not pattern doesn't work with executable model > ------------------------------------------------------------------------------- > > Key: DROOLS-4623 > URL: https://issues.jboss.org/browse/DROOLS-4623 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Mario Fusco > Assignee: Luca Molteni > Priority: Major > Labels: good-first-issue > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4480) [DMN Designer] Business Central Data Objects as DMN Data Types (7.6)

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4480?page=com.atlassian.jira.plugi... ] Guilherme Gomes reassigned DROOLS-4480: --------------------------------------- Assignee: Daniel José dos Santos (was: Guilherme Gomes) > [DMN Designer] Business Central Data Objects as DMN Data Types (7.6) > -------------------------------------------------------------------- > > Key: DROOLS-4480 > URL: https://issues.jboss.org/browse/DROOLS-4480 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > This is an umbrella for all JIRAs (target to 7.6) related to Business Central Data Objects as DMN Data Types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4549) [DMN Designer] Data Types - Update release notes

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4549?page=com.atlassian.jira.plugi... ] Guilherme Gomes reassigned DROOLS-4549: --------------------------------------- Assignee: Daniel José dos Santos (was: Guilherme Gomes) > [DMN Designer] Data Types - Update release notes > ------------------------------------------------ > > Key: DROOLS-4549 > URL: https://issues.jboss.org/browse/DROOLS-4549 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > Update release notes with changes related to the epic. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019