[
https://issues.jboss.org/browse/WFLY-3211?page=com.atlassian.jira.plugin....
]
Wolfgang Knauf commented on WFLY-3211:
--------------------------------------
The same problem happens on WildFly 10.0.0CR4.
Attached is my sample app which was be base for the initial issue (see also
https://developer.jboss.org/message/863696). The zip file contains an EAR file and a
modified "appclient.xml" for WF10 which defines the jms related stuff.
To reproduce:
-deploy "Message.ear" to WF 10
-copy client config to %WILDFLY_HOME%\appclient\configuration"
-start client: %WILDFLY_HOME%\bin\appclient.bat c:\Path\To\Message.ear#MessageClient.jar
Error message:
2015-11-07 20:17:24,220 ERROR [org.jboss.as.controller.management-operation] (Thread-40)
WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment"
=> "Message.ear")]) - failure description: {"WFLYCTL0180: Services with
missing/unavailable dependencies" =>
["jboss.naming.context.java.module.Message.MessageClient.env.jms.MBQueueRef is
missing [jboss.naming.context.java.app.Message.jms.queue.MessageBeanQueue]"]}
2015-11-07 20:17:24,223 ERROR [org.jboss.as.server] (Thread-40) WFLYSRV0021: Deploy of
deployment "Message.ear" was rolled back with the following failure message:
{"WFLYCTL0180: Services with missing/unavailable dependencies" =>
["jboss.naming.context.java.module.Message.MessageClient.env.jms.MBQueueRef is
missing [jboss.naming.context.java.app.Message.jms.queue.MessageBeanQueue]"]}
java:app resources can not be shared between ejb and appclient
modules
----------------------------------------------------------------------
Key: WFLY-3211
URL:
https://issues.jboss.org/browse/WFLY-3211
Project: WildFly
Issue Type: Bug
Components: Naming
Affects Versions: 8.0.0.Final
Reporter: Jeff Mesnil
Assignee: Eduardo Martins
Attachments: Sample_WildFly10.zip
use case:
1 ear composed of:
1 appclient module that defines 2 JMS queues (one in java:app, the other in
java:global)
1 ejb modules with 2 MDBs (one listening to the java:app queue and the other to the
java:global queue)
When the ear is deployed:
1. the ejb module is deployed, the MDBs are created and wait for the creations of their
respective queues (defined in the appclient module)
2. the appclient module is deployed, its 2 queues are deployed
3. the appclient main is run
When the appclient uses the java:global queue, it looks it up, sends the message and the
corresponding MDB receives it fine.
When the appclient uses the java:app queue, it looks it up, sends the message but the
corresponding MDB never receives it
=> the MDB was never deployed because it did not see the java:app queue deployed from
the appclient module.
Note that if I move the destination definitions to the ejb module, the MDBs are correctly
activated but the appclient module is no longer deployed with errors:
{noformat}
[APPCLIENT-out] {"JBAS014771: Services with missing/unavailable dependencies"
=> [
[APPCLIENT-out]
"jboss.naming.context.java.module.simple-jms-appclient-test.appclient.env.jms.queueInGlobal
is missing [jboss.naming.context.java.global.jms.queu
e.queue1]",
[APPCLIENT-out]
"jboss.naming.context.java.module.simple-jms-appclient-test.appclient.env.jms.queueInApp
is missing [jboss.naming.context.java.app.simple-jms-app
client-test.jms.queue.queue2]"
[APPCLIENT-out] ]}
{noformat}
Steps to reproduce:
1. fetch git branch
https://github.com/jmesnil/wildfly/tree/jms_appclient
2. build WildFly
3. run ./integration-tests.sh -Dts.basic
-Dtest=org.jboss.as.test.integration.ee.appclient.jms.basic.SimpleJMSApplicationClientTestCase
-DnoWebProfile
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)