[
https://issues.apache.org/jira/browse/GERONIMO-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565545#action_12565545
]
toby cabot commented on GERONIMO-3806:
--------------------------------------
The fix for GERONIMO-3248 causes two warnings in the log when a webapp has a
resource-ref in web.xml to a resource adapter in the same .ear:
16:24:19,032 WARN [ResourceRefBuilder] Failed to build reference to resource
reference [] defined in plan file, reason - corresponding entry in deployment
descriptor missing.
16:24:19,311 WARN [ResourceRefBuilder] Failed to build reference to resource
reference [] defined in plan file, reason - corresponding entry in deployment
descriptor missing.
This worked OK prior to r572902.
> CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB
> jar
> ---------------------------------------------------------------------------------
>
> Key: GERONIMO-3806
> URL: https://issues.apache.org/jira/browse/GERONIMO-3806
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0-M6
> Environment: Windows XP SP2
> Reporter: toby cabot
> Assignee: Vamsavardhana Reddy
> Priority: Minor
> Fix For: 2.0.2, 2.1
>
>
> During deployment of one of my EJB jar files in my EAR, I get the following
> WARN messages:
> {code}
> 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.
> {code}
> This occurs at the point in the following point in the stack:
> {code}
> AdminObjectRefBuilder.buildNaming(XmlObject, XmlObject, Module, Map) line: 160
> {code}
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
