1 Reply Latest reply on Feb 2, 2017 8:34 AM by mnovak

Failing deployment of JMS message consumer in Jboss black up server.

isurumd Jan 27, 2017 5:10 AM

I have setup HA Jboss live and back up server using shared store policy. Each node contains a JMS message consumer. deployment if live sever is successful but deployment of backup server is failing.

Following is the error

2017-01-27 11:15:38,275 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000094: Received new cluster view for channel ejb: [live|1] (2) [live, backup]

2017-01-27 11:15:38,275 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000094: Received new cluster view for channel web: [live|1] (2) [live, backup]

2017-01-27 11:15:38,275 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000094: Received new cluster view for channel server: [live|1] (2) [live, backup]

2017-01-27 11:15:38,275 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000094: Received new cluster view for channel hibernate: [live|1] (2) [live, backup]

2017-01-27 11:15:38,280 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000079: Channel web local address is backup, physical addresses are [127.0.0.1:55400]

2017-01-27 11:15:38,280 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000079: Channel ejb local address is backup, physical addresses are [127.0.0.1:55400]

2017-01-27 11:15:38,280 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000079: Channel hibernate local address is backup, physical addresses are [127.0.0.1:55400]

2017-01-27 11:15:38,280 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000079: Channel server local address is backup, physical addresses are [127.0.0.1:55400]

2017-01-27 11:15:38,383 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-3) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1

2017-01-27 11:15:38,700 INFO [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)

2017-01-27 11:15:39,361 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear")]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [

"jboss.naming.context.java.comp.\"TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT\".TestActiveMq-TestSubscriber.PatientMDB.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",

"jboss.deployment.subunit.\"TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear\".\"TestActiveMq-TestSubscriber.jar\".component.PatientMDB.CREATE is missing [jboss.ra.activemq-ra]"

]}

2017-01-27 11:15:39,414 INFO [org.jboss.as.server] (ServerService Thread Pool -- 40) WFLYSRV0010: Deployed "TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear" (runtime-name : "TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear")

2017-01-27 11:15:39,416 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report

WFLYCTL0184: New missing/unsatisfied dependencies:

service jboss.naming.context.java.jboss.DefaultJMSConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp."TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT".TestActiveMq-TestSubscriber.PatientMDB.DefaultJMSConnectionFactory]

service jboss.ra.activemq-ra (missing) dependents: [service jboss.deployment.subunit."TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear"."TestActiveMq-TestSubscriber.jar".component.PatientMDB.CREATE]

2017-01-27 11:15:39,538 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:10190/management

2017-01-27 11:15:39,538 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:10190

2017-01-27 11:15:39,538 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) started (with errors) in 11436ms - Started 417 of 751 services (10 services failed or missing dependencies, 460 services are lazy, passive or on-demand)

2017-01-27 11:15:39,612 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-5) HV000001: Hibernate Validator 5.2.4.Final-redhat-1

2017-01-27 11:15:39,686 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0208: Stopped subdeployment (runtime-name: TestActiveMq-TestSubscriber.jar) in 121ms

2017-01-27 11:15:39,689 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear (runtime-name: TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear) in 125ms

2017-01-27 11:15:39,788 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0002: Content removed from location C:\Jboss_cluster\jboss-eap-7.0 -slave\standalone\data\content\67\f4b36c68d65996a2c615aa3bf303331d8dbba8\content

2017-01-27 11:15:39,788 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Undeployed "TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear" (runtime-name: "TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear")

2017-01-27 11:15:39,790 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Service status report

WFLYCTL0184: New missing/unsatisfied dependencies:

service jboss.deployment.subunit."TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear"."TestActiveMq-TestSubscriber.jar".component.PatientMDB.CREATE (missing) dependents: [service jboss.deployment.subunit."TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear"."TestActiveMq-TestSubscriber.jar".moduleDeploymentRuntimeInformation, service jboss.deployment.subunit."TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear"."TestActiveMq-TestSubscriber.jar".component.PatientMDB.VIEW."se.Test.platform.hornetq.subscriber.PatientMDB".MESSAGE_ENDPOINT, service jboss.deployment.subunit."TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear"."TestActiveMq-TestSubscriber.jar".component.PatientMDB.START]

service jboss.deployment.subunit."TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear"."TestActiveMq-TestSubscriber.jar".component.PatientMDB.JndiBindingsService (missing) dependents: [service jboss.deployment.subunit."TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear"."TestActiveMq-TestSubscriber.jar".jndiDependencyService]

service jboss.deployment.subunit."TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear"."TestActiveMq-TestSubscriber.jar".component.PatientMDB.START (missing) dependents: [service jboss.deployment.subunit."TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear"."TestActiveMq-TestSubscriber.jar".moduleDeploymentRuntimeInformationStart, service jboss.deployment.subunit."TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear"."TestActiveMq-TestSubscriber.jar".deploymentCompleteService]

service jboss.deployment.subunit."TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear"."TestActiveMq-TestSubscriber.jar".component.PatientMDB.VIEW."se.Test.platform.hornetq.subscriber.PatientMDB".MESSAGE_ENDPOINT (missing) dependents: [service jboss.deployment.subunit."TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear"."TestActiveMq-TestSubscriber.jar".moduleDeploymentRuntimeInformation, service jboss.deployment.subunit."TestActiveMq-TestSubscriber-0.0.1-SNAPSHOT.ear"."TestActiveMq-TestSubscriber.jar".component.PatientMDB.START]

here is the AqtiveMQ subsystem looks like.

<shared-store-slave/>

<bindings-directory path="\\CLLK-cj1-s23\SharedStore\bindings"/>

<journal-directory path="\\CLLK-cj1-s23\SharedStore\journal"/>

<large-messages-directory path="\\CLLK-cj1-s23\SharedStore\largemessages"/>

<paging-directory path="\\CLLK-cj1-s23\SharedStore\paging"/>

<security-setting name="#">

</security-setting>

<address-setting name="#" redistribution-delay="1000" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>

<http-connector name="http-connector" endpoint="http-acceptor" socket-binding="http"/>

<http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http">

</http-connector>

<in-vm-connector name="in-vm" server-id="0"/>

<http-acceptor name="http-acceptor" http-listener="default"/>

<http-acceptor name="http-acceptor-throughput" http-listener="default">

</http-acceptor>

<in-vm-acceptor name="in-vm" server-id="0"/>

<broadcast-group name="bg-group1" connectors="http-connector" jgroups-channel="activemq-cluster"/>

<discovery-group name="dg-group1" jgroups-channel="activemq-cluster"/>

<cluster-connection name="my-cluster" discovery-group="dg-group1" connector-name="http-connector" address="jms"/>

<jms-queue name="ExpiryQueue" entries="java:/jms/queue/ExpiryQueue"/>

<jms-queue name="DLQ" entries="java:/jms/queue/DLQ"/>

<connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>

<connection-factory name="RemoteConnectionFactory" reconnect-attempts="-1" block-on-acknowledge="true" ha="true" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="http-connector"/>

<pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>

</server>

</subsystem>

1. Re: Failing deployment of JMS message consumer in Jboss black up server.

mnovak Feb 2, 2017 8:34 AM (in response to isurumd)

Hi Isuru,

Artemis is using active-passive philosophy for HA. Live is active and server clients and backup just sits in stand-by mode and only thing it does, is that it waits for live to fail. For this reason if you deploy MDB on Widfly server which has configured Artemis as backup, the MDB does not get deployed as it cannot to backup.

I suggest you to use configuration where you will have 2 live-backup pairs where 2 Widlfy servers will contain Artemis backup for each other. It will be like WF1(Live1,Backup2) <-> WF2(Live2,Backup1). Some time ago I placed the configuration in another thread, see my comment - Re: How to make messages in cluster queue replicated in real time

With this config both of the MDBs will be active and get deployed.
1 of 1 people found this helpful
Actions