8:22 p.m.
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: Deployment, EJB, JCA
Affects Versions: 7.1.0.Alpha1, 7.0.2.Final
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: Thomas Diesler
Priority: Critical
If an application is packaged with MDBs and RAs (resource adapters) such that the order of
deployment of these modules needs to be deterministic, the application fails to load. In
other words, there is no way to define the order in which MDBs and RAs must be loaded in
an application. This is a strict requirement by JEE 6, and without this support, JBoss 7
cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB.
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:22 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
Abhi S updated AS7-2505:
------------------------
Attachment: jee-app.ear
Please just drop this application in your deployment directory to reproduce the issue.
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: Deployment, EJB, JCA
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: Thomas Diesler
Priority: Critical
Labels: deployment, ear, mdb, ra
Attachments: jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB.
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:28 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
Abhi S updated AS7-2505:
------------------------
Description:
If an application is packaged with MDBs and RAs (resource adapters) such that the order of
deployment of these modules needs to be deterministic, the application fails to load. In
other words, there is no way to define the order in which MDBs and RAs must be loaded in
an application. This is a strict requirement by JEE 6, and without this support, JBoss 7
cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
was:
If an application is packaged with MDBs and RAs (resource adapters) such that the order of
deployment of these modules needs to be deterministic, the application fails to load. In
other words, there is no way to define the order in which MDBs and RAs must be loaded in
an application. This is a strict requirement by JEE 6, and without this support, JBoss 7
cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB.
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: Deployment, EJB, JCA
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: Thomas Diesler
Priority: Critical
Labels: deployment, ear, mdb, ra
Attachments: jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:30 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
Abhi S updated AS7-2505:
------------------------
Steps to Reproduce:
*Steps to reproduce:*
* Drop in the EAR attached, and the application will fail to load with an error:
{code}java.lang.IllegalStateException: Cannot find any resource adapter service for
resource adapter connector{code}
*Verify the fix:*
If the application loads without any error, one can access http://host:port/web, which
should display "Web Module Loaded!", guaranteeing that the MDB and the RA were
loaded in the expected order (i.e., first the RA and then the MDB).
*Details on the attached application*
* EAR contains 1 web module, 1 resource adapter (RA), and 1 MDB that depends on the RA to
be loaded first.
* application.xml defines the order in which these modules must be loaded. I have added
comments and toggles to enable the aforementioned different ways to specify the deployment
order.
* I have attached all the source code, including that of RA, MDB and web app. The code is
very simple and straight-ward to understand; however, please let me know if you need more
info.
was:
*Steps to reproduce:*
* Drop in the EAR attached, and the application will fail to load with an error:
{code}java.lang.IllegalStateException: Cannot find any resource adapter service for
resource adapter connector{code}
*Verify the fix:*
If the application load without any error, one can access http://host:port/web, which
should display "Web Module Loaded!", guaranteeing that MDB and RA were loaded in
the expected order (i.e., first the RA and then the MDB).
*Details on the attached application*
* EAR contains 1 web module, 1 resource adapter (RA), and 1 MDB that depends on the RA to
be loaded first.
* application.xml defines the order in which these modules must be loaded. I have added
comments and toggles to enable the aforementioned different ways to specify the deployment
order.
* I have attached all the source code, including that of RA, MDB and web app. The code is
very simple and straight-ward to understand; however, please let me know if you need more
info.
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: Deployment, EJB, JCA
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: Thomas Diesler
Priority: Critical
Labels: deployment, ear, mdb, ra
Attachments: jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:28 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
Abhi S updated AS7-2505:
------------------------
Attachment: jee-app.ear
To reproduce the issue, please use this EAR instead. Thanks.
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: Deployment, EJB, JCA
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: Thomas Diesler
Priority: Critical
Labels: deployment, ear, mdb, ra
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-2505:
------------------------------
Assignee: (was: Thomas Diesler)
Fix Version/s: 7.1.0.CR1
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: Deployment, EJB, JCA
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:36 a.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
jaikiran pai reassigned AS7-2505:
---------------------------------
Assignee: jaikiran pai
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: Deployment, EJB, JCA
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: jaikiran pai
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:36 a.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
SBS JIRA Integration updated AS7-2505:
--------------------------------------
Forum Reference: http://community.jboss.org/message/635180#635180
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: Deployment, EJB, JCA
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: jaikiran pai
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:20 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
jaikiran pai resolved AS7-2505.
-------------------------------
Resolution: Done
Fixed and merged upstream https://github.com/jbossas/jboss-as/pull/777
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: EJB, JCA, JSR88
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: jaikiran pai
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:30 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
Abhi S commented on AS7-2505:
-----------------------------
I am trying to verify this issue, but I am still not able to deploy the EAR I attached. I
get the following exception:
{code}
21:13:19,515 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed
to start service
jboss.deployment.subunit."jee-app.ear"."mdb.jar".comp
onent.message-driven-bean.CREATE: org.jboss.msc.service.StartException in service
jboss.deployment.subunit."jee-app.ear"."mdb.jar".component.message-driven-bean
.CREATE: Failed to start service
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_27]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_27]
Caused by: java.lang.IllegalStateException: JBAS014521: No message listener of type
com.sample.jee.MessageListener found in resource adapter hornetq-ra
at
org.jboss.as.ejb3.component.EJBUtilities.createActivationSpecs(EJBUtilities.java:96)
at
org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.createComponent(MessageDrivenComponentCreateService.java:67)
at
org.jboss.as.ee.component.BasicComponentCreateService.start(BasicComponentCreateService.java:84)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
... 3 more
{code}
NOTE: If you look at my MDB source, I have a @ResourceAdapter annotation, but not sure why
is it trying to connect to hornetq-ra. My MDB code:
{code:java}
@ResourceAdapter("connector.rar")
@Depends("jboss.jca:name='connector.rar',service=RARDeployment")
public class AMessageDrivenBean implements MessageListener {
{code}
Then I added jboss-ejb3.xml in the mdb.jar (please see the attached EAR) as below based on
the example -
https://github.com/jbossas/jboss-as/blob/master/testsuite/integration/bas...:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<jboss xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:jee="http://java.sun.com/xml/ns/javaee"
xmlns:mdb="urn:resource-adapter-binding"
xmlns:security="urn:security">
<jee:assembly-descriptor>
<mdb:resource-adapter-binding>
<!--<jee:ejb-name>ConfiguredResourceAdapterNameMDB</jee:ejb-name>-->
<mdb:resource-adapter-name>connector.rar</mdb:resource-adapter-name>
</mdb:resource-adapter-binding>
</jee:assembly-descriptor>
</jboss>
{code}
BUT now I get another exception:
{code}
21:26:09,214 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001: Failed
to start service jboss.deployment.subunit."jee-app.ear"."mdb.jar".PAR
SE: org.jboss.msc.service.StartException in service
jboss.deployment.subunit."jee-app.ear"."mdb.jar".PARSE: Failed to
process phase PARSE of subdeployment "mdb.
jar" of deployment "jee-app.ear"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
[jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_27]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_27]
Caused by: java.lang.ClassCastException:
org.jboss.metadata.ejb.spec.MessageDrivenBean31MetaData cannot be cast to
org.jboss.metadata.ejb.jboss.ejb3.JBossGeneri
cBeanMetaData
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.merge(MessageDrivenBeanMetaData.java:353)
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:85)
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:36)
at
org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.merge(EnterpriseBeansMetaData.java:73)
at
org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.createMerged(EnterpriseBeansMetaData.java:52)
at org.jboss.metadata.ejb.spec.EjbJarMetaData.merge(EjbJarMetaData.java:177)
at
org.jboss.metadata.ejb.spec.EjbJarMetaData.createMerged(EjbJarMetaData.java:668)
at
org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:124)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
[jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
... 5 more
{code}
What am I missing?
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: EJB, JCA, JSR88
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: jaikiran pai
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:32 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
Abhi S edited comment on AS7-2505 at 12/28/11 4:30 PM:
-------------------------------------------------------
I am trying to verify this issue, but I am still not able to deploy the EAR I attached. I
get the following exception:
{code}
21:13:19,515 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed
to start service
jboss.deployment.subunit."jee-app.ear"."mdb.jar".comp
onent.message-driven-bean.CREATE: org.jboss.msc.service.StartException in service
jboss.deployment.subunit."jee-app.ear"."mdb.jar".component.message-driven-bean
.CREATE: Failed to start service
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_27]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_27]
Caused by: java.lang.IllegalStateException: JBAS014521: No message listener of type
com.sample.jee.MessageListener found in resource adapter hornetq-ra
at
org.jboss.as.ejb3.component.EJBUtilities.createActivationSpecs(EJBUtilities.java:96)
at
org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.createComponent(MessageDrivenComponentCreateService.java:67)
at
org.jboss.as.ee.component.BasicComponentCreateService.start(BasicComponentCreateService.java:84)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
... 3 more
{code}
NOTE: If you look at my MDB source, I have a @ResourceAdapter annotation, but not sure why
is it trying to connect to hornetq-ra. My MDB code:
{code:java}
@ResourceAdapter("connector.rar")
@Depends("jboss.jca:name='connector.rar',service=RARDeployment")
public class AMessageDrivenBean implements MessageListener {
{code}
Then I added jboss-ejb3.xml in the mdb.jar (please see the attached EAR) as below based on
the example -
https://github.com/jbossas/jboss-as/blob/master/testsuite/integration/bas...
:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<jboss xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:jee="http://java.sun.com/xml/ns/javaee"
xmlns:mdb="urn:resource-adapter-binding"
xmlns:security="urn:security">
<jee:assembly-descriptor>
<mdb:resource-adapter-binding>
<!--<jee:ejb-name>ConfiguredResourceAdapterNameMDB</jee:ejb-name>-->
<mdb:resource-adapter-name>connector.rar</mdb:resource-adapter-name>
</mdb:resource-adapter-binding>
</jee:assembly-descriptor>
</jboss>
{code}
BUT now I get another exception:
{code}
21:26:09,214 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001: Failed
to start service jboss.deployment.subunit."jee-app.ear"."mdb.jar".PAR
SE: org.jboss.msc.service.StartException in service
jboss.deployment.subunit."jee-app.ear"."mdb.jar".PARSE: Failed to
process phase PARSE of subdeployment "mdb.
jar" of deployment "jee-app.ear"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
[jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_27]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_27]
Caused by: java.lang.ClassCastException:
org.jboss.metadata.ejb.spec.MessageDrivenBean31MetaData cannot be cast to
org.jboss.metadata.ejb.jboss.ejb3.JBossGeneri
cBeanMetaData
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.merge(MessageDrivenBeanMetaData.java:353)
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:85)
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:36)
at
org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.merge(EnterpriseBeansMetaData.java:73)
at
org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.createMerged(EnterpriseBeansMetaData.java:52)
at org.jboss.metadata.ejb.spec.EjbJarMetaData.merge(EjbJarMetaData.java:177)
at
org.jboss.metadata.ejb.spec.EjbJarMetaData.createMerged(EjbJarMetaData.java:668)
at
org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:124)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
[jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
... 5 more
{code}
What am I missing?
was (Author: abhis):
I am trying to verify this issue, but I am still not able to deploy the EAR I
attached. I get the following exception:
{code}
21:13:19,515 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed
to start service
jboss.deployment.subunit."jee-app.ear"."mdb.jar".comp
onent.message-driven-bean.CREATE: org.jboss.msc.service.StartException in service
jboss.deployment.subunit."jee-app.ear"."mdb.jar".component.message-driven-bean
.CREATE: Failed to start service
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_27]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_27]
Caused by: java.lang.IllegalStateException: JBAS014521: No message listener of type
com.sample.jee.MessageListener found in resource adapter hornetq-ra
at
org.jboss.as.ejb3.component.EJBUtilities.createActivationSpecs(EJBUtilities.java:96)
at
org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.createComponent(MessageDrivenComponentCreateService.java:67)
at
org.jboss.as.ee.component.BasicComponentCreateService.start(BasicComponentCreateService.java:84)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
... 3 more
{code}
NOTE: If you look at my MDB source, I have a @ResourceAdapter annotation, but not sure why
is it trying to connect to hornetq-ra. My MDB code:
{code:java}
@ResourceAdapter("connector.rar")
@Depends("jboss.jca:name='connector.rar',service=RARDeployment")
public class AMessageDrivenBean implements MessageListener {
{code}
Then I added jboss-ejb3.xml in the mdb.jar (please see the attached EAR) as below based on
the example -
https://github.com/jbossas/jboss-as/blob/master/testsuite/integration/bas...:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<jboss xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:jee="http://java.sun.com/xml/ns/javaee"
xmlns:mdb="urn:resource-adapter-binding"
xmlns:security="urn:security">
<jee:assembly-descriptor>
<mdb:resource-adapter-binding>
<!--<jee:ejb-name>ConfiguredResourceAdapterNameMDB</jee:ejb-name>-->
<mdb:resource-adapter-name>connector.rar</mdb:resource-adapter-name>
</mdb:resource-adapter-binding>
</jee:assembly-descriptor>
</jboss>
{code}
BUT now I get another exception:
{code}
21:26:09,214 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001: Failed
to start service jboss.deployment.subunit."jee-app.ear"."mdb.jar".PAR
SE: org.jboss.msc.service.StartException in service
jboss.deployment.subunit."jee-app.ear"."mdb.jar".PARSE: Failed to
process phase PARSE of subdeployment "mdb.
jar" of deployment "jee-app.ear"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
[jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_27]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_27]
Caused by: java.lang.ClassCastException:
org.jboss.metadata.ejb.spec.MessageDrivenBean31MetaData cannot be cast to
org.jboss.metadata.ejb.jboss.ejb3.JBossGeneri
cBeanMetaData
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.merge(MessageDrivenBeanMetaData.java:353)
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:85)
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:36)
at
org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.merge(EnterpriseBeansMetaData.java:73)
at
org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.createMerged(EnterpriseBeansMetaData.java:52)
at org.jboss.metadata.ejb.spec.EjbJarMetaData.merge(EjbJarMetaData.java:177)
at
org.jboss.metadata.ejb.spec.EjbJarMetaData.createMerged(EjbJarMetaData.java:668)
at
org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:124)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
[jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
... 5 more
{code}
What am I missing?
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: EJB, JCA, JSR88
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: jaikiran pai
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:57 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
Abhi S edited comment on AS7-2505 at 12/28/11 5:55 PM:
-------------------------------------------------------
I am trying to verify this issue in 7.1 CR1 version, but I am still not able to deploy the
EAR I attached. I get the following exception:
{code}
21:13:19,515 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed
to start service
jboss.deployment.subunit."jee-app.ear"."mdb.jar".comp
onent.message-driven-bean.CREATE: org.jboss.msc.service.StartException in service
jboss.deployment.subunit."jee-app.ear"."mdb.jar".component.message-driven-bean
.CREATE: Failed to start service
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_27]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_27]
Caused by: java.lang.IllegalStateException: JBAS014521: No message listener of type
com.sample.jee.MessageListener found in resource adapter hornetq-ra
at
org.jboss.as.ejb3.component.EJBUtilities.createActivationSpecs(EJBUtilities.java:96)
at
org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.createComponent(MessageDrivenComponentCreateService.java:67)
at
org.jboss.as.ee.component.BasicComponentCreateService.start(BasicComponentCreateService.java:84)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
... 3 more
{code}
NOTE: If you look at my MDB source, I have a @ResourceAdapter annotation, but not sure why
is it trying to connect to hornetq-ra. My MDB code:
{code:java}
@ResourceAdapter("connector.rar")
@Depends("jboss.jca:name='connector.rar',service=RARDeployment")
public class AMessageDrivenBean implements MessageListener {
{code}
Then I added jboss-ejb3.xml in the mdb.jar (please see the attached EAR) as below based on
the example -
https://github.com/jbossas/jboss-as/blob/master/testsuite/integration/bas...
:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<jboss xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:jee="http://java.sun.com/xml/ns/javaee"
xmlns:mdb="urn:resource-adapter-binding"
xmlns:security="urn:security">
<jee:assembly-descriptor>
<mdb:resource-adapter-binding>
<!--<jee:ejb-name>ConfiguredResourceAdapterNameMDB</jee:ejb-name>-->
<mdb:resource-adapter-name>connector.rar</mdb:resource-adapter-name>
</mdb:resource-adapter-binding>
</jee:assembly-descriptor>
</jboss>
{code}
BUT now I get another exception:
{code}
21:26:09,214 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001: Failed
to start service jboss.deployment.subunit."jee-app.ear"."mdb.jar".PAR
SE: org.jboss.msc.service.StartException in service
jboss.deployment.subunit."jee-app.ear"."mdb.jar".PARSE: Failed to
process phase PARSE of subdeployment "mdb.
jar" of deployment "jee-app.ear"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
[jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_27]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_27]
Caused by: java.lang.ClassCastException:
org.jboss.metadata.ejb.spec.MessageDrivenBean31MetaData cannot be cast to
org.jboss.metadata.ejb.jboss.ejb3.JBossGeneri
cBeanMetaData
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.merge(MessageDrivenBeanMetaData.java:353)
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:85)
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:36)
at
org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.merge(EnterpriseBeansMetaData.java:73)
at
org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.createMerged(EnterpriseBeansMetaData.java:52)
at org.jboss.metadata.ejb.spec.EjbJarMetaData.merge(EjbJarMetaData.java:177)
at
org.jboss.metadata.ejb.spec.EjbJarMetaData.createMerged(EjbJarMetaData.java:668)
at
org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:124)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
[jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
... 5 more
{code}
What am I missing?
was (Author: abhis):
I am trying to verify this issue, but I am still not able to deploy the EAR I
attached. I get the following exception:
{code}
21:13:19,515 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed
to start service
jboss.deployment.subunit."jee-app.ear"."mdb.jar".comp
onent.message-driven-bean.CREATE: org.jboss.msc.service.StartException in service
jboss.deployment.subunit."jee-app.ear"."mdb.jar".component.message-driven-bean
.CREATE: Failed to start service
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_27]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_27]
Caused by: java.lang.IllegalStateException: JBAS014521: No message listener of type
com.sample.jee.MessageListener found in resource adapter hornetq-ra
at
org.jboss.as.ejb3.component.EJBUtilities.createActivationSpecs(EJBUtilities.java:96)
at
org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.createComponent(MessageDrivenComponentCreateService.java:67)
at
org.jboss.as.ee.component.BasicComponentCreateService.start(BasicComponentCreateService.java:84)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
... 3 more
{code}
NOTE: If you look at my MDB source, I have a @ResourceAdapter annotation, but not sure why
is it trying to connect to hornetq-ra. My MDB code:
{code:java}
@ResourceAdapter("connector.rar")
@Depends("jboss.jca:name='connector.rar',service=RARDeployment")
public class AMessageDrivenBean implements MessageListener {
{code}
Then I added jboss-ejb3.xml in the mdb.jar (please see the attached EAR) as below based on
the example -
https://github.com/jbossas/jboss-as/blob/master/testsuite/integration/bas...
:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<jboss xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:jee="http://java.sun.com/xml/ns/javaee"
xmlns:mdb="urn:resource-adapter-binding"
xmlns:security="urn:security">
<jee:assembly-descriptor>
<mdb:resource-adapter-binding>
<!--<jee:ejb-name>ConfiguredResourceAdapterNameMDB</jee:ejb-name>-->
<mdb:resource-adapter-name>connector.rar</mdb:resource-adapter-name>
</mdb:resource-adapter-binding>
</jee:assembly-descriptor>
</jboss>
{code}
BUT now I get another exception:
{code}
21:26:09,214 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001: Failed
to start service jboss.deployment.subunit."jee-app.ear"."mdb.jar".PAR
SE: org.jboss.msc.service.StartException in service
jboss.deployment.subunit."jee-app.ear"."mdb.jar".PARSE: Failed to
process phase PARSE of subdeployment "mdb.
jar" of deployment "jee-app.ear"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
[jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_27]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_27]
Caused by: java.lang.ClassCastException:
org.jboss.metadata.ejb.spec.MessageDrivenBean31MetaData cannot be cast to
org.jboss.metadata.ejb.jboss.ejb3.JBossGeneri
cBeanMetaData
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.merge(MessageDrivenBeanMetaData.java:353)
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:85)
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:36)
at
org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.merge(EnterpriseBeansMetaData.java:73)
at
org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.createMerged(EnterpriseBeansMetaData.java:52)
at org.jboss.metadata.ejb.spec.EjbJarMetaData.merge(EjbJarMetaData.java:177)
at
org.jboss.metadata.ejb.spec.EjbJarMetaData.createMerged(EjbJarMetaData.java:668)
at
org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:124)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
[jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
... 5 more
{code}
What am I missing?
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: EJB, JCA, JSR88
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: jaikiran pai
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:59 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
Abhi S reopened AS7-2505:
-------------------------
The @ResourceAdapter annotation doesn't work anymore, and the resource adapter is
defaulted to "hornetq-ra". Please suggest an alternative if that's
disabled. Please try to reproduce the issue with the original EAR attached.
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: EJB, JCA, JSR88
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: jaikiran pai
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:12 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
Abhi S edited comment on AS7-2505 at 12/29/11 3:10 PM:
-------------------------------------------------------
The @ResourceAdapter annotation doesn't work anymore (this used to work in
7.1.0-Alpha1), and the resource adapter is defaulted to "hornetq-ra". Please
suggest an alternative if that's disabled. Please try to reproduce the issue with the
original EAR attached.
was (Author: abhis):
The @ResourceAdapter annotation doesn't work anymore, and the resource adapter is
defaulted to "hornetq-ra". Please suggest an alternative if that's
disabled. Please try to reproduce the issue with the original EAR attached.
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: EJB, JCA, JSR88
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: jaikiran pai
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:28 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
Abhi S edited comment on AS7-2505 at 12/29/11 4:27 PM:
-------------------------------------------------------
The @ResourceAdapter annotation doesn't work anymore (this used to work in
7.1.0-Alpha1), and the resource adapter is defaulted to "hornetq-ra". Please
suggest an alternative if that's disabled. Please try to reproduce the issue with the
original EAR attached.
Also, using jboss-ejb3.xml as I described above throws ClassCastException as mentioned
above. I debugged the code and I think there is bug in the code, but I can't tell
what should be the right behavior. Please respond when you get chance.
was (Author: abhis):
The @ResourceAdapter annotation doesn't work anymore (this used to work in
7.1.0-Alpha1), and the resource adapter is defaulted to "hornetq-ra". Please
suggest an alternative if that's disabled. Please try to reproduce the issue with the
original EAR attached.
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: EJB, JCA, JSR88
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: jaikiran pai
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:32 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
Abhi S edited comment on AS7-2505 at 12/29/11 4:30 PM:
-------------------------------------------------------
The @ResourceAdapter annotation doesn't work anymore (this used to work in
7.1.0-Alpha1), and the resource adapter is defaulted to "hornetq-ra". Please
suggest an alternative if that's disabled. Please try to reproduce the issue with the
original EAR attached.
Also, using jboss-ejb3.xml as I described above throws ClassCastException as mentioned
above. I debugged the code and I think there is a bug in the code while doing the casting
as above, but I can't tell what should be the expected behavior.
Bottom-line question: How can I deploy a custom RA and an MDB connecting to the RA, both
packaged within the same EAR? I don't see any documentation and workaround to make
custom RA work -- neither the jboss-ejb3.xml, nor the @ResourceAdapter annotation work.
Please respond when you get chance.
was (Author: abhis):
The @ResourceAdapter annotation doesn't work anymore (this used to work in
7.1.0-Alpha1), and the resource adapter is defaulted to "hornetq-ra". Please
suggest an alternative if that's disabled. Please try to reproduce the issue with the
original EAR attached.
Also, using jboss-ejb3.xml as I described above throws ClassCastException as mentioned
above. I debugged the code and I think there is bug in the code, but I can't tell
what should be the right behavior. Please respond when you get chance.
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: EJB, JCA, JSR88
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: jaikiran pai
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:54 a.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
jaikiran pai resolved AS7-2505.
-------------------------------
Resolution: Done
Please do not reopen resolved issues which have been marked as fixed for a specific
version. We have testcases for @ResourceAdapter in our AS7 testsuite and it's highly
unlikely that it isn't working. Please start a new forum thread with the exact details
about which JBoss AS7 version you are using and what you are running into. I had tried
that attached .ear when I fixed this issue and it was working fine. I'll give it a try
again sometime later this week.
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: EJB, JCA, JSR88
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: jaikiran pai
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:03 a.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-2505:
-----------------------------------
The reason why your deployment is failing is because you are deploying 2 different MDBs
(and not one). The ejb-jar.xml has a MDB named:
{code}
<ejb-name>message-driven-bean</ejb-name>
{code}
which I think you meant to be used as an override for the annotated MDB:
{code}
@ResourceAdapter("connector.rar")
@Depends("jboss.jca:name='connector.rar',service=RARDeployment")
public class AMessageDrivenBean implements MessageListener {
{code}
However, the names of these MDBs don't match. Hence the deployment descriptor MDB is
considered as a separate MDB and since it doesn't have a custom resource adapter, it
uses the default hornetq-ra resource adapter. You'll have to fix the deployment. One
way to do it is change the ejb-jar.xml to:
{code}
<ejb-name>AMessageDrivenBean</ejb-name>
{code}
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: EJB, JCA, JSR88
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: jaikiran pai
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:45 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
Peter Rönnqvist commented on AS7-2505:
--------------------------------------
I must agree with Abhi.
The message bean in his sample is NOT annotated with @MessageDriven. Therefore there
should be no name conflict as described in jakiran's comment from 29/12. I myself am
interested in this issue since I have encountered exactly the same problem on AS 7.1.0
CR1B.
/Regards
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: EJB, JCA, JSR88
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: jaikiran pai
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:24 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-2505:
-----------------------------------
You are right, the AMessageDrivenBean isn't annotated with an @MessageDriven. This
looks like a different bug (related to annotation/deployment descriptor merging). Can you
please create a new JIRA for that and paste it here? I'll add some comments to that
new JIRA.
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: EJB, JCA, JSR88
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: jaikiran pai
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:21 p.m.
[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
Peter Rönnqvist commented on AS7-2505:
--------------------------------------
I have added a Jira: https://issues.jboss.org/browse/AS7-3202
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL: https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: EJB, JCA, JSR88
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: jaikiran pai
Priority: Critical
Labels: deployment, ear, mdb, ra
Fix For: 7.1.0.CR1
Attachments: jee-app.ear, jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4556
days inactive
4619
days old
20 comments
11 participants
participants (11)
-
Abhi S (Commented) (JIRA) -
Abhi S (Created) (JIRA)
-
Abhi S (Issue Comment Edited) (JIRA)
-
Abhi S (Reopened) (JIRA)
-
Abhi S (Updated) (JIRA)
-
jaikiran pai (Assigned) (JIRA)
-
jaikiran pai (Commented) (JIRA)
-
jaikiran pai (Resolved) (JIRA)
-
Jason Greene (Updated) (JIRA)
-
Peter Rönnqvist (Commented) (JIRA)
-
SBS JIRA Integration (Updated) (JIRA)