[GLASSFISH-19272] deploy MDB failed Created: 01/Nov/12  Updated: 17/Dec/12  Resolved: 17/Dec/12

Status: Resolved
Project: glassfish
Component/s: jms
Affects Version/s: 4.0_b60
Fix Version/s: 4.0_b68_EE7MS3

Type: Bug Priority: Major
Reporter: Simon Meng Assignee: Simon Meng
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File MDBApp.ear     Java Source File MessageBean.java     Text File server.log    
Tags: ee7platspec, jms-2-implementation

 Description   

Use case 1
An application contains a session bean and a MDB. The MDB uses the "@MessageDriven(mappedName=" annotation to specify the JNDI name of the destination. This destination resource is defined using a @JMSDestinationDefinition annotation in the session bean. When the application is deployed, deployment of the MDB fails because the resource does not exist.

Use case 2
An application contains a MDB only. The MDB uses the "@MessageDriven(mappedName=" annotation to specify the JNDI name of the destination. This destination resource is defined using a @JMSDestinationDefinition annotation in the MDB.
When the application is deployed, deployment of the MDB fails because the resource does not exist.

Following exception occured when deploy the MDB, detailed exception stack can see the attached server.log
com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: JMS resource not created : java:global/jms/myInboundQueue

Can the resources defined in an application be deployed before MDB deployment?

Attachment list:
MDBApp.ear the reproducer application,
MessageBean.java MDB source code
server.log GF server log



 Comments   
Comment by Hong Zhang [ 05/Nov/12 ]

As this is a JMS specific issue (per Jagadish' comments from the email discussions), ressign to Simon to drive the fix for this issue. The deployment team will work with the JMS team to provide any necessary APIs from the deployment side.

Comment by Simon Meng [ 17/Dec/12 ]

Fixed at revision 57591.

Generated at Fri Dec 09 09:58:40 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.