i have war has being working fine under eap 6.4.x (x 8, under 6 , 4 , on down 6.4.0).
the war has simple jms client features adding message queue on remote machine. target qbroker activemq 5.8.0.
i use 5.8.0 rar set adapter/connector remote broker , normal jms client stuff push message q. fine this.
beginning "port" 6.4.x 7.0.1; , hung on amq 5.8.0 rar stuff. starters -- not going use of amq artemis stuff part of eap 7 (yet). want war working under 7.0 few changes possible -- leaving rar in place important.
under 6.4.x, use standalone profile , deploy rar via cli kinda this:
./jboss-cli.sh --connect -c "deploy --name=${amq_deploy_name} --runtime-name=${amq_rar_fname} ${_tmpdir}/${amq_rar_fname}" i use cli set resource adapter, connection def/factory , admin-object queue.
following same process eap 7.0.1, if use standalone profile
java.lang.noclassdeffounderror: javax/jms/jmsexception issues while trying enable war uses rar. ok when used standalone-full sorts of variations of sort of error:
2016-07-18 15:48:10,867 error [org.jboss.as.controller.management-operation] (controller boot thread) wflyctl0013: operation ("add") failed - address: ([ ("subsystem" => "messaging-activemq"), ("server" => "default") ]) - failure description: { "wflyctl0180: services missing/unavailable dependencies" => ["jboss.messaging-activemq.default missing [jboss.http-upgrade-registry.default]"], "wflyctl0288: 1 or more services unable start due 1 or more indirect dependencies not being available." => { "services unable start:" => ["jboss.messaging-activemq.default.jms.manager"], "services may cause:" => [ "jboss.http-upgrade-registry.default", "jboss.naming.context.java.jmsxa" ] } } the above messages suggest wrong messaging-activemq stuff (or built in artemis stuff).
in both cases, set ejb default resource adapter rar created above.
so missing on set up?
some particulars environment:
war doesn't have jboss/wildfly specific dds in it.
i not have amq rar deployed static module (nor want to) -- jar have deployed - other jar (for db drivers) or wars, ejb jars, etc.
cat version.txt red hat jboss enterprise application platform - version 7.0.1.ga
java -version java version "1.8.0_92" java(tm) se runtime environment (build 1.8.0_92-b14) java hotspot(tm) 64-bit server vm (build 25.92-b14, mixed mode)
uname -a linux wellandf3 4.6.4-301.fc24.x86_64 #1 smp tue jul 12 11:50:00 utc 2016 x86_64 x86_64 x86_64 gnu/linux
is noclassdeffounderror caused classnotfoundexception? if thats case try add javax.jms.api global module.
Comments
Post a Comment