You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aman Nanner (JIRA)" <ji...@apache.org> on 2007/06/15 20:32:26 UTC
[jira] Created: (GERONIMO-3248) Extraneous WARN messages during
deployment of resource-env-refs in EJB jar
Extraneous WARN messages during deployment of resource-env-refs in EJB jar
--------------------------------------------------------------------------
Key: GERONIMO-3248
URL: https://issues.apache.org/jira/browse/GERONIMO-3248
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 2.0-M6
Environment: Windows XP SP2
Reporter: Aman Nanner
Priority: Minor
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/JabberQueue, 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.
[jira] Updated: (GERONIMO-3248) Extraneous WARN messages during
deployment of resource-env-refs in EJB jar
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vamsavardhana Reddy updated GERONIMO-3248:
------------------------------------------
Fix Version/s: 2.1
2.0.x
2.0.2
Assignee: Vamsavardhana Reddy
> Extraneous WARN messages during deployment of resource-env-refs in EJB jar
> --------------------------------------------------------------------------
>
> Key: GERONIMO-3248
> URL: https://issues.apache.org/jira/browse/GERONIMO-3248
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0-M6
> Environment: Windows XP SP2
> Reporter: Aman Nanner
> Assignee: Vamsavardhana Reddy
> Priority: Minor
> Fix For: 2.0.2, 2.0.x, 2.1
>
> Attachments: GERONIMO-3248-new.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.
[jira] Updated: (GERONIMO-3248) Extraneous WARN messages during
deployment of resource-env-refs in EJB jar
Posted by "Aman Nanner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aman Nanner updated GERONIMO-3248:
----------------------------------
Description:
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.
was:
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/JabberQueue, 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.
> Extraneous WARN messages during deployment of resource-env-refs in EJB jar
> --------------------------------------------------------------------------
>
> Key: GERONIMO-3248
> URL: https://issues.apache.org/jira/browse/GERONIMO-3248
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0-M6
> Environment: Windows XP SP2
> Reporter: Aman Nanner
> Priority: Minor
>
> 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.
[jira] Updated: (GERONIMO-3248) Extraneous WARN messages during
deployment of resource-env-refs in EJB jar
Posted by "Manu T George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manu T George updated GERONIMO-3248:
------------------------------------
Attachment: GERONIMO-3248-new.patch
Attached a patch to prevent unnecessary WARN messages.
> Extraneous WARN messages during deployment of resource-env-refs in EJB jar
> --------------------------------------------------------------------------
>
> Key: GERONIMO-3248
> URL: https://issues.apache.org/jira/browse/GERONIMO-3248
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0-M6
> Environment: Windows XP SP2
> Reporter: Aman Nanner
> Priority: Minor
> Attachments: GERONIMO-3248-new.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.
[jira] Updated: (GERONIMO-3248) Extraneous WARN messages during
deployment of resource-env-refs in EJB jar
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated GERONIMO-3248:
-----------------------------------
Fix Version/s: (was: 2.0.x)
updated Fixed For field
> Extraneous WARN messages during deployment of resource-env-refs in EJB jar
> --------------------------------------------------------------------------
>
> Key: GERONIMO-3248
> URL: https://issues.apache.org/jira/browse/GERONIMO-3248
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0-M6
> Environment: Windows XP SP2
> Reporter: Aman Nanner
> Assignee: Vamsavardhana Reddy
> Priority: Minor
> Fix For: 2.0.2, 2.1
>
> Attachments: GERONIMO-3248-new.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.
[jira] Commented: (GERONIMO-3248) Extraneous WARN messages during
deployment of resource-env-refs in EJB jar
Posted by "Aman Nanner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524875 ]
Aman Nanner commented on GERONIMO-3248:
---------------------------------------
The patch seems to have fixed the problem.
> Extraneous WARN messages during deployment of resource-env-refs in EJB jar
> --------------------------------------------------------------------------
>
> Key: GERONIMO-3248
> URL: https://issues.apache.org/jira/browse/GERONIMO-3248
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0-M6
> Environment: Windows XP SP2
> Reporter: Aman Nanner
> Priority: Minor
> Attachments: GERONIMO-3248-new.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.
[jira] Closed: (GERONIMO-3248) Extraneous WARN messages during
deployment of resource-env-refs in EJB jar
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vamsavardhana Reddy closed GERONIMO-3248.
-----------------------------------------
Resolution: Fixed
Completed: At revision: 572902
> Extraneous WARN messages during deployment of resource-env-refs in EJB jar
> --------------------------------------------------------------------------
>
> Key: GERONIMO-3248
> URL: https://issues.apache.org/jira/browse/GERONIMO-3248
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0-M6
> Environment: Windows XP SP2
> Reporter: Aman Nanner
> Assignee: Vamsavardhana Reddy
> Priority: Minor
> Fix For: 2.0.2, 2.0.x, 2.1
>
> Attachments: GERONIMO-3248-new.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.