[
https://issues.apache.org/jira/browse/GERONIMO-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
toby cabot updated GERONIMO-3806:
---------------------------------
Attachment: GERONIMO-3806-2.0.2.patch
Hi Manu, thanks for giving this your attention.
I tried your patch and it had the same problem as the old code, i.e. it
displayed the spurious warnings. The problem appears to be that a resource ref
might be resolved after you've added its name to unresolvedRefs.
I modified your patch so it applies to 2.0.2 (which is what I'm using) and
added a line to take the name out of unresolvedRefs if we find it later. That
works for my application. I also added back the debug line that I found useful
in looking for the problem.
Thanks!
Toby
> 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)
> Components: deployment
> Affects Versions: 2.0.2, 2.1, 2.1.1, 2.2
> Environment: Windows XP SP2
> Reporter: toby cabot
> Assignee: toby cabot
> Priority: Minor
> Fix For: 2.1.1, 2.2
>
> Attachments: GERONIMO-3806-2.0.2.patch, GERONIMO-3806_r638814.patch
>
>
> 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.
