Re: How to resolve JMS Dependency ?

Manish Satwani Wed, 09 Aug 2006 22:58:35 -0700

attaching modified geronimo-web.xml and openejb-jar.xml in which i have added admin-object-link

Thanks
Manish

On 8/10/06, Manish Satwani < [EMAIL PROTECTED]> wrote:

Hi All,

I am stillg getting this erro during deployment.

Unable to resolve resource reference 'jms/AcevaPublisherQueue' (Could not auto-map to resource. Try adding a resource-ref mapping to your Geronimo deployment plan.)
org.apache.geronimo.common.DeploymentException: Unable to resolve resource reference 'jms/AcevaPublisherQueue' (Could not auto-map to resource. Try adding a resource-ref mapping to your Geronimo deployment plan.) at org.apache.geronimo.naming.deployment.ENCConfigBuilder.addResourceRefs(ENCConfigBuilder.java:210)

I have added admin-object-link as suggested by Aaron.....

I am attching my web.xml also...and whole RA plan...

please do let me know if you need any other configuration file....for reference...

please help me ...

Thanks
Manish
On 8/8/06, Aaron Mulder < [EMAIL PROTECTED] > wrote:
OK, let's back up a bit.

In order to reference JMS resources from a web app:

* For a connection factory, use a resource-ref (I think you did this)
* For a topic or queue in J2EE 1.4 / Servlet 2.4, use a
messsage-destination-ref
* For a topic or queue in J2EE < 1.4 / Servlet < 2.4, use a resource-env-ref

So your queue reference was not correct in the snippets you posted.
For a walkthrough of the correct syntax, see
http://chariotsolutions.com/geronimo/geronimo-1.1/web-plan.html#web-plan-jms
(section 11.3.5.5 has a discussion with examples of both styles).
Your EJB JAR used EJB 2.0, which suggests that you're using J2EE 1.3,
but you might be using Servlet 2.4 anyway, which would make the
difference.

If you want more specific help, you'll need to post your web.xml files.

Thanks,
     Aaron

On 8/8/06, Manish Satwani < [EMAIL PROTECTED]> wrote:
> Hi ,
>
> I am new in geronimo .... can you please tell me where exactly should i
> change....
> I am attaching all configuration files here....
>
> I have 2 war in my ear thats why i attached 2 geronimo-web.xml
>
>
> please help me
>
> Thanks
> Manish
>
>
> On 8/8/06, Krishnakumar B < [EMAIL PROTECTED]> wrote:
> > For referring to Queues u should use
> >
> > <nam:resource-env-ref>
> >     <nam:ref-name></nam:ref-name>
> >     <admin-object-link></admin-object-link>
> > </nam:resource-env-ref>
> >
> > or Message Destination Reference
> >
> > I think both would work
> >
> >
> http://www.chariotsolutions.com/geronimo/geronimo-1.1/web-plan.html#web-plan-refs
> > ( You can refer to resource-env-ref for J2EE Connector Administered
> > Objects )
> >
> > Resource Environment Ref can be used to reference JMS Destinations.
> >
> > Regards
> > Krishnakumar
> >
> > On 8/8/06, Manish Satwani < [EMAIL PROTECTED]> wrote:
> > > Hi All,
> > >
> > > I am facing problem while deploying my ear on geronimo 1.1
> > >
> > > It is complaining regarding jms/AcevaPublisherQueue (my application need
> > > this)
> > >
> > > I have added this queue from console.
> > >
> > we have acm.war file which also access (resource-ref) this queue
> > > and i have acevaEJB.jar which also have (resource-ref) to this queue
> > >
> > > i also added resource-link entries in geronimo-web.xml and
> openEJB-jar.xml
> > >
> > > this is in openEjb-jar.xml
> > > <session>
> > >             <ejb-name>CollectionService</ejb-name>
> > >
> <jndi-name>ejb/CollectionService</jndi-name>
> > >             <naming:resource-ref>
> > >
> > >
> <naming:ref-name>jms/AcevaPublisherConnectionFactory</naming:ref-name>
> > >
> > >
> <naming:resource-link>jms/AcevaPublisherConnectionFactory</naming:resource-link>
> > >             </naming:resource-ref>
> > >              <naming:resource-ref>
> > >
> > >
> <naming:ref-name>jms/AcevaPublisherQueue</naming:ref-name>
> > >
> > >
> <naming:resource-link>jms/AcevaPublisherQueue</naming:resource-link>
> > >             </naming:resource-ref>
> > >         </session>
> > >
> > >
> > > this is in geronimo-web.xml
> > >
> > > <naming:resource-ref>
> > >
> > >
> <naming:ref-name>jms/AcevaPublisherQueue</naming:ref-name>
> > >
> > >
> <naming:resource-link>jms/AcevaPublisherQueue</naming:resource-link>
> > >     </naming:resource-ref>
> > >
> > >
> > >
> > > any enviroment - > depency entry needed?
> > >
> > > if yes
> > >
> > > <sys:dependency>
> > >                     <sys:groupId>?????</sys:groupId>
> (what
> > > should i write here)
> > >
> > > <sys:artifactId>???</sys:artifactId>(what should i
> write
> > > here)
> > >                 </sys:dependency>
> > >
> > >
> > > --
> > > Manish Satwani
> > > Senior Software Engineer
> > > Aceva Technologies | Unlock Your Working Capital
> > > A-1501, Signature Towers - I,
> > > South City, Gurgaon,
> > > Haryana – 122001
> > > Call at:
> > > +91-124-2805091/92 Ext. 35
> > > +91-99113-16998
> > > Visit: http://www.aceva.com
> >
>
>
>
> --
>
> Manish Satwani
> Senior Software Engineer
> Aceva Technologies | Unlock Your Working Capital
> A-1501, Signature Towers - I,
> South City, Gurgaon,
> Haryana – 122001
> Call at:
> +91-124-2805091/92 Ext. 35
> +91-99113-16998
> Visit: http://www.aceva.com
>

--

Manish Satwani
Senior Software Engineer
Aceva Technologies | Unlock Your Working Capital
A-1501, Signature Towers - I,
South City, Gurgaon,
Haryana – 122001
Call at:
+91-124-2805091/92 Ext. 35
+91-99113-16998
Visit: http://www.aceva.com

--
Manish Satwani
Senior Software Engineer
Aceva Technologies | Unlock Your Working Capital
A-1501, Signature Towers - I,
South City, Gurgaon,
Haryana – 122001
Call at:
+91-124-2805091/92 Ext. 35
+91-99113-16998
Visit: http://www.aceva.com

<?xml version="1.0" encoding="UTF-8"?>

<openejb-jar
  xmlns="http://www.openejb.org/xml/ns/openejb-jar-2.1";
  xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.1";
  xmlns:security="http://geronimo.apache.org/xml/ns/security-1.1";
  xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.1";
  xmlns:pkgen="http://www.openejb.org/xml/ns/pkgen-2.0";>
    <sys:environment>
        <sys:dependencies>
                <sys:dependency>
                    <sys:groupId>console.dbpool</sys:groupId>
                    <sys:artifactId>AcevaDB</sys:artifactId>
                </sys:dependency>
                <sys:dependency>
                    <sys:groupId>console.jms</sys:groupId>
                    <sys:artifactId>Aceva</sys:artifactId>
                </sys:dependency>
                <sys:dependency>
                    <sys:groupId>geronimo</sys:groupId>
                    <sys:artifactId>activemq</sys:artifactId>
                </sys:dependency>
            </sys:dependencies>
    </sys:environment>
    <enterprise-beans>
        <session>
            <ejb-name>SystemConfiguration</ejb-name>
            <jndi-name>ejb/SystemConfiguration</jndi-name>
            <naming:resource-ref>
                <naming:ref-name>jdbc/AcevaDB</naming:ref-name>
                <naming:resource-link>AcevaDB</naming:resource-link>
            </naming:resource-ref>
        </session>
        <session>
            <ejb-name>SourceEventStorage</ejb-name>
            <jndi-name>ejb/SourceEventStorage</jndi-name>
            <naming:resource-ref>
                <naming:ref-name>jdbc/AcevaDB</naming:ref-name>
                <naming:resource-link>AcevaDB</naming:resource-link>
            </naming:resource-ref>
        </session>
        <session>
            <ejb-name>RequestHandler</ejb-name>
            <jndi-name>ejb/RequestHandler</jndi-name>
            <naming:resource-ref>
                <naming:ref-name>jdbc/AcevaDB</naming:ref-name>
                <naming:resource-link>AcevaDB</naming:resource-link>
            </naming:resource-ref>
        </session>
        <session>
            <ejb-name>GroupService</ejb-name>
            <jndi-name>ejb/GroupService</jndi-name>
            <naming:resource-ref>
                <naming:ref-name>jdbc/AcevaDB</naming:ref-name>
                <naming:resource-link>AcevaDB</naming:resource-link>
            </naming:resource-ref>
        </session>
        <session>
            <ejb-name>UserService</ejb-name>
            <jndi-name>ejb/UserService</jndi-name>
            <naming:resource-ref>
                <naming:ref-name>jdbc/AcevaDB</naming:ref-name>
                <naming:resource-link>AcevaDB</naming:resource-link>
            </naming:resource-ref>
        </session>
         <session>
            <ejb-name>SecurityService</ejb-name>
            <jndi-name>ejb/SecurityService</jndi-name>
        </session>
        <session>
            <ejb-name>UserSetUpService</ejb-name>
            <jndi-name>ejb/UserSetUpService</jndi-name>
        </session>
        <session>
            <ejb-name>FilterService</ejb-name>
            <jndi-name>ejb/FilterService</jndi-name>
        </session>
        <session>
            <ejb-name>CollectorService</ejb-name>
            <jndi-name>ejb/CollectorService</jndi-name>
        </session>
        <session>
            <ejb-name>CollectionService</ejb-name>
            <jndi-name>ejb/CollectionService</jndi-name>
            <naming:resource-ref>
                <naming:ref-name>jms/AcevaPublisherConnectionFactory</naming:ref-name>
                <naming:resource-link>jms/AcevaPublisherConnectionFactory</naming:resource-link>
            </naming:resource-ref>
             <naming:resource-env-ref>
                <naming:ref-name>jms/AcevaPublisherQueue</naming:ref-name>
                <naming:admin-object-link>jms/AcevaPublisherQueue</naming:admin-object-link>
            </naming:resource-env-ref>
        </session>
        <session>
            <ejb-name>DisputeService</ejb-name>
            <jndi-name>ejb/DisputeService</jndi-name>
        </session>
        <session>
            <ejb-name>TemplateService</ejb-name>
            <jndi-name>ejb/TemplateService</jndi-name>
        </session>
        <session>
            <ejb-name>DistributorEJB</ejb-name>
            <jndi-name>ejb/DistributorEJB</jndi-name>
        </session>
        <session>
            <ejb-name>RequestHandlerService</ejb-name>
            <jndi-name>ejb/RequestHandlerService</jndi-name>
            <naming:ejb-local-ref>
                <naming:ref-name>ejb/InferenceEngineLocal</naming:ref-name>
                <naming:ejb-link>InferenceEngine</naming:ejb-link>
            </naming:ejb-local-ref>
        </session>
        <session>
            <ejb-name>DataMaintenanceService</ejb-name>
            <jndi-name>ejb/DataMaintenanceService</jndi-name>
        </session>
        <session>
            <ejb-name>ApplicationMaintenanceService</ejb-name>
            <jndi-name>ejb/ApplicationMaintenanceService</jndi-name>
        </session>
        <session>
            <ejb-name>RuleRepository</ejb-name>
            <jndi-name>ejb/RuleRepository</jndi-name>
            <naming:resource-ref>
                <naming:ref-name>jdbc/AcevaDB</naming:ref-name>
                <naming:resource-link>AcevaDB</naming:resource-link>
            </naming:resource-ref>
        </session>
        <session>
            <ejb-name>InferenceEngine</ejb-name>
            <jndi-name>ejb/InferenceEngine</jndi-name>
            <naming:resource-ref>
                <naming:ref-name>jdbc/AcevaDB</naming:ref-name>
                <naming:resource-link>AcevaDB</naming:resource-link>
            </naming:resource-ref>
        </session>
         <session>
            <ejb-name>RuleEvaluation</ejb-name>
            <jndi-name>ejb/RuleEvaluation</jndi-name>
            <naming:resource-ref>
                <naming:ref-name>jdbc/AcevaDB</naming:ref-name>
                <naming:resource-link>AcevaDB</naming:resource-link>
            </naming:resource-ref>
        </session>
        <session>
            <ejb-name>DocumentVersioningQueue</ejb-name>
            <jndi-name>ejb/DocumentVersioningQueue</jndi-name>
            <naming:resource-ref>
                <naming:ref-name>jdbc/AcevaDB</naming:ref-name>
                <naming:resource-link>AcevaDB</naming:resource-link>
            </naming:resource-ref>
        </session>
        <session>
            <ejb-name>DocumentVersioning</ejb-name>
            <jndi-name>ejb/DocumentVersioning</jndi-name>
            <naming:resource-ref>
                <naming:ref-name>jdbc/AcevaDB</naming:ref-name>
                <naming:resource-link>AcevaDB</naming:resource-link>
            </naming:resource-ref>
        </session>
        <session>
            <ejb-name>WorkItemService</ejb-name>
            <jndi-name>ejb/WorkItemService</jndi-name>
        </session>
        <session>
            <ejb-name>ExceptionService</ejb-name>
            <jndi-name>ejb/ExceptionService</jndi-name>
        </session>
        <session>
            <ejb-name>ConfigPageService</ejb-name>
            <jndi-name>ejb/ConfigPageService</jndi-name>
        </session>
        <session>
            <ejb-name>ConfigFilterService</ejb-name>
            <jndi-name>ejb/ConfigFilterService</jndi-name>
        </session>
        <session>
            <ejb-name>ApplicationResourceService</ejb-name>
            <jndi-name>ejb/ApplicationResourceService</jndi-name>
        </session>
        <message-driven>
            <ejb-name>AcevaJms</ejb-name>
            <naming:resource-adapter>
                <naming:resource-link>ActiveMQ RA</naming:resource-link>
            </naming:resource-adapter>
            <naming:ejb-local-ref>
                <naming:ref-name>ejb/InferenceEngineLocal</naming:ref-name>
                <naming:ejb-link>InferenceEngine</naming:ejb-link>
            </naming:ejb-local-ref>
            <naming:resource-ref>
                <naming:ref-name>jms/AcevaJmsCF</naming:ref-name>
                <naming:resource-link>jms/AcevaJmsCF</naming:resource-link>
            </naming:resource-ref>
            <naming:resource-env-ref>
                <naming:ref-name>jms/AcevaJmsTopicOut</naming:ref-name>
                <naming:admin-object-link>jms/AcevaJmsTopicOut</naming:admin-object-link>
            </naming:resource-env-ref>
        </message-driven>
        <message-driven>
            <ejb-name>ClearinghouseMessageBean</ejb-name>
            <naming:resource-adapter>
                <naming:resource-link>ActiveMQ RA</naming:resource-link>
            </naming:resource-adapter>
            <naming:resource-ref>
                <naming:ref-name>jms/AcevaPublisherConnectionFactory</naming:ref-name>
                <naming:resource-link>jms/AcevaPublisherConnectionFactory</naming:resource-link>
            </naming:resource-ref>
        </message-driven>
        <message-driven>
            <ejb-name>AcevaJmsJobDelegate</ejb-name>
            <naming:resource-adapter>
                <naming:resource-link>ActiveMQ RA</naming:resource-link>
            </naming:resource-adapter>
            <naming:ejb-ref>
                <naming:ref-name>ejb/RuleRepository</naming:ref-name>
                <naming:ejb-link>ejb/RuleRepository</naming:ejb-link>
            </naming:ejb-ref>
            <naming:ejb-local-ref>
                <naming:ref-name>ejb/InferenceEngineLocal</naming:ref-name>
                <naming:ejb-link>InferenceEngine</naming:ejb-link>
            </naming:ejb-local-ref>
            <naming:resource-ref>
                <naming:ref-name>jms/SchedulerCF</naming:ref-name>
                <naming:resource-link>jms/SchedulerCF</naming:resource-link>
            </naming:resource-ref>
            <naming:resource-ref>
                <naming:ref-name>jms/AcevaPublisherConnectionFactory</naming:ref-name>
                <naming:resource-link>jms/AcevaPublisherConnectionFactory</naming:resource-link>
            </naming:resource-ref>
            <naming:resource-env-ref>
                <naming:ref-name>jms/AcevaPublisherQueue</naming:ref-name>
                <naming:admin-object-link>jms/AcevaPublisherQueue</naming:admin-object-link>
            </naming:resource-env-ref>


        </message-driven>
    </enterprise-beans>
</openejb-jar>

<?xml version="1.0" encoding="UTF-8"?>
<web-app
  xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1";
  xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.1";
  xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.1";
  xmlns:security="http://geronimo.apache.org/xml/ns/security-1.1";>
    <sys:environment>
            <sys:moduleId>
                <sys:artifactId>acm</sys:artifactId>
            </sys:moduleId>
            <sys:dependencies>
                <sys:dependency>
                    <sys:groupId>console.dbpool</sys:groupId>
                    <sys:artifactId>AcevaDB</sys:artifactId>
                </sys:dependency>
                <sys:dependency>
                    <sys:groupId>console.jms</sys:groupId>
                    <sys:artifactId>Aceva</sys:artifactId>
                </sys:dependency>
                <sys:dependency>
                    <sys:groupId>geronimo</sys:groupId>
                    <sys:artifactId>activemq</sys:artifactId>
                </sys:dependency>
            </sys:dependencies>
    </sys:environment>
    <context-root>/acm</context-root>
    <!-- security settings, if any, go here -->
    <naming:ejb-ref>
        <naming:ref-name>ejb/SystemConfiguration</naming:ref-name>
        <naming:ejb-link>SystemConfiguration</naming:ejb-link>
    </naming:ejb-ref>
    <naming:ejb-ref>
        <naming:ref-name>ejb/RequestHandler</naming:ref-name>
        <naming:ejb-link>RequestHandler</naming:ejb-link>
    </naming:ejb-ref>
    <naming:ejb-ref>
        <naming:ref-name>ejb/CollectionServiceHomeRemote</naming:ref-name>
        <naming:ejb-link>CollectionService</naming:ejb-link>
      </naming:ejb-ref>
    <naming:ejb-ref>
        <naming:ref-name>ejb/DisputeServiceHomeRemote</naming:ref-name>
        <naming:ejb-link>DisputeService</naming:ejb-link>
     </naming:ejb-ref>
    <naming:ejb-ref>
        <naming:ref-name>ejb/TemplateServiceHomeRemote</naming:ref-name>
         <naming:ejb-link>TemplateService</naming:ejb-link>
    </naming:ejb-ref>
    <naming:ejb-ref>
        <naming:ref-name>ejb/CollectionServiceHomeLocal</naming:ref-name>
         <naming:ejb-link>CollectionService</naming:ejb-link>
    </naming:ejb-ref>
    <naming:ejb-ref>
        <naming:ref-name>ejb/DisputeServiceHomeLocal</naming:ref-name>
         <naming:ejb-link>DisputeService</naming:ejb-link>
    </naming:ejb-ref>
    <naming:resource-ref>
        <naming:ref-name>jdbc/AcevaDB</naming:ref-name>
        <naming:resource-link>AcevaDB</naming:resource-link>
    </naming:resource-ref>
    <naming:resource-ref>
        <naming:ref-name>jms/AcevaPublisherConnectionFactory</naming:ref-name>
        <naming:resource-link>jms/AcevaPublisherConnectionFactory</naming:resource-link>
    </naming:resource-ref>
    <naming:resource-env-ref>
        <naming:ref-name>jms/AcevaPublisherQueue</naming:ref-name>
       <naming:admin-object-link>jms/AcevaPublisherQueue</naming:admin-object-link>
    </naming:resource-env-ref>
    <security-realm-name>
        geronimo-properties-realm
    </security-realm-name>
</web-app>

<?xml version="1.0" encoding="UTF-8"?>
<web-app
    xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1";
    xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.1";
    xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.1";
    xmlns:security="http://geronimo.apache.org/xml/ns/security-1.1";>
    <sys:environment>
            <sys:moduleId>
                <sys:artifactId>aceva</sys:artifactId>
            </sys:moduleId>
            <sys:dependencies>
                <sys:dependency>
                    <sys:groupId>console.dbpool</sys:groupId>
                    <sys:artifactId>AcevaDB</sys:artifactId>
                </sys:dependency>
                <sys:dependency>
                    <sys:groupId>console.jms</sys:groupId>
                    <sys:artifactId>Aceva</sys:artifactId>
                </sys:dependency>
                <sys:dependency>
                    <sys:groupId>geronimo</sys:groupId>
                    <sys:artifactId>activemq</sys:artifactId>
                </sys:dependency>
            </sys:dependencies>
    </sys:environment>
    <context-root>/aceva</context-root>
    <naming:ejb-ref>
        <naming:ref-name>ejb/SystemConfiguration</naming:ref-name>
         <naming:ejb-link>SystemConfiguration</naming:ejb-link>
    </naming:ejb-ref>
    <naming:ejb-ref>
        <naming:ref-name>ejb/RequestHandler</naming:ref-name>
      <naming:ejb-link>RequestHandler</naming:ejb-link>
    </naming:ejb-ref>
    <naming:resource-ref>
        <naming:ref-name>jdbc/AcevaDB</naming:ref-name>
       <naming:resource-link>AcevaDB</naming:resource-link>
    </naming:resource-ref>
    <naming:resource-ref>
        <naming:ref-name>jms/AcevaPublisherConnectionFactory</naming:ref-name>
        <naming:resource-link>jms/AcevaPublisherConnectionFactory</naming:resource-link>
    </naming:resource-ref>
    <naming:resource-env-ref>
        <naming:ref-name>jms/AcevaPublisherQueue</naming:ref-name>
        <naming:admin-object-link>jms/AcevaPublisherQueue</naming:admin-object-link>
    </naming:resource-env-ref>
    <security-realm-name>geronimo-properties-realm</security-realm-name>
</web-app>

Re: How to resolve JMS Dependency ?

Reply via email to