0 Replies Latest reply on Nov 26, 2019 4:41 AM by ragans2005

Problem starting cluster node,"WFLYSRV0082: failed to resolve interface messaging"

ragans2005 Nov 26, 2019 4:41 AM

Hi,

I'm relatively new to clustering JBoss and after dealing with some authentication issues, I am able to get the cluster node running but the interface messaging fails. I've tried turning up server logging and I don't seem to get any additional information other than the errors output below, the messaging is working fine on the master node without any errors or problems.

I am running JBOSS EAP 7.1.1 as this is a requirement for the software I support SOE.

It only occurs on the secondary node.

[Server:GraniteCore-server] WFLYRMT0001: Listening on 0.0.0.0:4447

[Server:GraniteCore-server] MSC000001: Failed to start service org.wildfly.network.interface.messaging: org.jboss.msc.service.StartException in service org.wildfly.network.interface.messaging: WFLYSRV0082: failed to resolve interface messaging

[Server:GraniteCore-server] at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:96) [wildfly-server-3.0.12.Final-redhat-1.jar:3.0.12.Final-redhat-1]

[Server:GraniteCore-server] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1]

[Server:GraniteCore-server] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1]

[Server:GraniteCore-server] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_181]

[Server:GraniteCore-server] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_181]

[Server:GraniteCore-server] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_181]

[Server:GraniteCore-server]

[Server:GraniteCore-server] WFLYJCA0098: Bound non-transactional data source: java:/platform/jdbc/bpm_platform_db

[Server:GraniteCore-server] WFLYUT0012: Started server default-server.

[Server:GraniteCore-server] WFLYUT0018: Host default-host starting

[Server:GraniteCore-server] WFLYUT0006: Undertow AJP listener ajp listening on 0.0.0.0:8009

[Server:GraniteCore-server] MODCLUSTER000001: Initializing mod_cluster version 1.3.7.Final-redhat-1

[Server:GraniteCore-server] WFLYUT0006: Undertow HTTP listener http listening on 0.0.0.0:8080

[Server:GraniteCore-server] MODCLUSTER000032: Listening to proxy advertisements on /224.75.1.105:23364

[Server:GraniteCore-server] ARJUNA032010: JBossTS Recovery Service (tag: 3f491) - JBoss Inc.

[Server:GraniteCore-server] ARJUNA032013: Starting transaction recovery manager

[Server:GraniteCore-server] ARJUNA012389: OSB: Error constructing record header reader: com.hp.mwtests.ts.jta.jts.tools.JCAServerTransactionHeaderReader from [Module "org.jboss.jts" from local module loader @3f3afe78 (finder: local module finder @7f63425a (roots: /app/jboss/modules,/app/jboss/modules/system/layers/base/.overlays/layer-base-jboss-eap-7.1.1.CP,/app/jboss/modules/system/layers/base))]

[Server:GraniteCore-server] WFLYIIOP0009: CORBA ORB Service started

[Server:GraniteCore-server] ARJUNA032017: JBossTS Transaction Service (JTA version - tag: 3f491) - JBoss Inc.

[Server:GraniteCore-server] WFLYEJB0493: EJB subsystem suspension complete

[Server:GraniteCore-server] IJ020018: Enabling <validate-on-match> for java:/xng/jdbc/localhost_install

[Server:GraniteCore-server] IJ020018: Enabling <validate-on-match> for java:/platform/jdbc/platform_db

[Server:GraniteCore-server] WFLYJCA0001: Bound data source [java:/xng/jdbc/localhost_install]

[Server:GraniteCore-server] WFLYJCA0001: Bound data source [java:/platform/jdbc/platform_db]

[Server:GraniteCore-server] WFLYPAT0050: JBoss EAP cumulative patch ID is: jboss-eap-7.1.1.CP, one-off patches include: none

[Server:GraniteCore-server] JBWS022052: Starting JBossWS 5.1.10.Final-redhat-1 (Apache CXF 3.1.13.redhat-1)

[Server:GraniteCore-server] JGRP000014: Discovery.timeout has been deprecated: GMS.join_timeout should be used instead

[Server:GraniteCore-server] JGRP000014: Discovery.num_initial_members has been deprecated: will be ignored

[Server:GraniteCore-server] UFC is not needed (and can be removed) as we're running on a TCP transport

[Server:GraniteCore-server] ISPN000078: Starting JGroups channel ee

[Server:GraniteCore-server] ISPN000094: Received new cluster view for channel ee: [slave:GraniteCore-server|0] (1) [slave:GraniteCore-server]

[Server:GraniteCore-server] ISPN000079: Channel ee local address is slave:GraniteCore-server, physical addresses are [127.0.0.1:7600]

[Server:GraniteCore-server] ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.9.Final-redhat-1

[Server:GraniteCore-server] WFLYCLINF0002: Started default-host cache from web container

[Server:GraniteCore-server] WFLYCTL0013: Operation ("add") failed - address: ([("interface" => "messaging")]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.network.interface.messaging" => "WFLYSRV0082: failed to resolve interface messaging"}}

[Server:GraniteCore-server] WFLYCTL0183: Service status report

[Server:GraniteCore-server] WFLYCTL0186: Services which failed to start: service org.wildfly.network.interface.messaging: WFLYSRV0082: failed to resolve interface messaging

[Server:GraniteCore-server]

[Server:GraniteCore-server] WFLYSRV0212: Resuming server

[Server:GraniteCore-server] ARJUNA032035: Resuming transaction recovery manager

[Server:GraniteCore-server] WFLYSRV0026: JBoss EAP 7.1.1.GA (WildFly Core 3.0.12.Final-redhat-1) started (with errors) in 12073ms - Started 442 of 994 services (4 services failed or missing dependencies, 741 services are lazy, passive or on-demand)