geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "toby cabot (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMO-3806) CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB jar
Date Mon, 04 Feb 2008 21:41:08 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

toby cabot updated GERONIMO-3806:
---------------------------------

    Attachment: bug3806-patch.txt

Here's a patch that quiets the messages in my case (and adds a couple of debug messages that
I found helpful).  With this patch applied and log4j screwed down to DEBUG I get:

16:36:46,764 DEBUG [ResourceRefBuilder] trying to resolve JobCF, type reva.job.ra.ConnectionFactory,
resourceRef null
16:36:46,766 DEBUG [ResourceRefBuilder] initial 0 unresolved 0 refmap 0
16:36:47,004 DEBUG [ResourceRefBuilder] trying to resolve JobCF, type reva.job.ra.ConnectionFactory,
resourceRef null
16:36:47,005 DEBUG [ResourceRefBuilder] initial 0 unresolved 0 refmap 0

... and no warnings.

Someone who understands the operation of the buildNaming() method better than I do should
inspect the code but I believe (from inspection) that it shouldn't break the case that GERONIMO-3248
solved.


> 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
>
>         Attachments: bug3806-patch.txt
>
>
> 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.


Mime
View raw message