[GERONIMO-3806] CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB jar

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.2, 2.1, 2.1.1, 2.2
• Fix Version/s: 2.0.3, 2.1.1, 2.2
• Component/s: deployment
• Security Level: public (Regular issues)

Environment

Windows XP SP2

• Patch Info: Patch Available
• Regression: Regression
• Assignee: Manu T George
• Reporter: Tobias Schlitt
• Created: 04/Feb/08 21:11
• Updated: 23/Jul/08 20:31
• Resolved: 22/Mar/08 06:33

Description

During deployment of one of my EJB jar files in my EAR, I get the following WARN messages:

14:29:37,425 WARN  [AdminObjectRefBuilder] Failed to build reference to Admin object reference [jms/UnsequencedDestination, jms/MailQueue, jms/InboundEventQueue, jms/OutboundQueue, jms/SystemQueue, jms/ActionQueue, jms/SequencedDestination, jms/InboundIntegrationQueue, jms/OutboundEventQueue] defined in plan file, reason - corresponding entry in deployment descriptor missing.
14:29:37,440 WARN  [ResourceRefBuilder] Failed to build reference to resource reference [jms/ConnectionFactory, jms/QueueConnectionFactory, mail/MailSession, jms/TopicConnectionFactory] defined in plan file, reason - corresponding entry in deployment descriptor missing.

This occurs at the point in the following point in the stack:

AdminObjectRefBuilder.buildNaming(XmlObject, XmlObject, Module, Map) line: 160

The "specDD" that is passed in is a XML fragment for a specific session bean. However, the "plan" that is passed in contains all the resource-ref and resource-env-ref elements in the openejb-jar.xml plan. Therefore, the "refMap" variable does not get completely emptied out, since the specific session bean will only contain a subset of the resource-env-refs that are defined in the plan.

Issue Links

• is a clone of: GERONIMO-3248 Extraneous WARN messages during deployment of resource-env-refs in EJB jar