1 2 Previous Next 15 Replies Latest reply: Aug 17, 2012 11:25 AM by sun certified RSS

SPECjEnterprise2010 new missing/unsatisfied dependencies.

gatla srinivasareddy Newbie

Dear all,

 

I am a very beginner in the JBoss world. During the deployment of SpecJenterprise2010 on JBoss 7.1.1 I'm having the following problem:

 

 

11:07:18,720 INFO  [org.jboss.as.server] (HttpManagementService-threads - 4) JBAS015870: Deploy of deployment "specj.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.\"org.spec.jent.ejb.mfg.session.MessageSenderSession\".buyerQueuejboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.jms.BuyerQueueMissing[jboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.\"org.spec.jent.ejb.mfg.session.MessageSenderSession\".buyerQueuejboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.jms.BuyerQueue]","jboss.naming.context.java.comp.specj.\"specj.jar\".BuyerMDB.env.\"org.spec.jent.ejb.supplier.mdb.BuyerMDB\".queueConnFactoryjboss.naming.context.java.comp.specj.\"specj.jar\".BuyerMDB.env.jms.PurchaseQueueConnectionFactoryMissing[jboss.naming.context.java.comp.specj.\"specj.jar\".BuyerMDB.env.\"org.spec.jent.ejb.supplier.mdb.BuyerMDB\".queueConnFactoryjboss.naming.context.java.comp.specj.\"specj.jar\".BuyerMDB.env.jms.PurchaseQueueConnectionFactory]","jboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.\"org.spec.jent.ejb.mfg.session.MessageSenderSession\".buyerQueueConnFactoryjboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.jms.BuyerQueueConnectionFactoryMissing[jboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.\"org.spec.jent.ejb.mfg.session.MessageSenderSession\".buyerQueueConnFactoryjboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.jms.BuyerQueueConnectionFactory]","jboss.naming.context.java.comp.specj.\"specj.jar\".LoaderSession.env.\"org.spec.jent.loader.session.LoaderSession\".queueConnFactoryjboss.naming.context.java.comp.specj.\"specj.jar\".LoaderSession.env.jms.LoaderQueueConnectionFactoryMissing[jboss.naming.context.java.comp.specj.\"specj.jar\".LoaderSession.env.\"org.spec.jent.loader.session.LoaderSession\".queueConnFactoryjboss.naming.context.java.comp.specj.\"specj.jar\".LoaderSession.env.jms.LoaderQueueConnectionFactory]","jboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.\"org.spec.jent.ejb.mfg.session.MessageSenderSession\".fulfillOrderQueueConnFactoryjboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.jms.FulfillOrderQueueConnectionFactoryMissing[jboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.\"org.spec.jent.ejb.mfg.session.MessageSenderSession\".fulfillOrderQueueConnFactoryjboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.jms.FulfillOrderQueueConnectionFactory]","jboss.naming.context.java.comp.specj.\"specj.jar\".LargeOrderSenderSession.env.\"org.spec.jent.ejb.orders.session.LargeOrderSenderSession\".queueConnFactoryjboss.naming.context.java.comp.specj.\"specj.jar\".LargeOrderSenderSession.env.jms.LargeOrderQueueConnectionFactoryMissing[jboss.naming.context.java.comp.specj.\"specj.jar\".LargeOrderSenderSession.env.\"org.spec.jent.ejb.orders.session.LargeOrderSenderSession\".queueConnFactoryjboss.naming.context.java.comp.specj.\"specj.jar\".LargeOrderSenderSession.env.jms.LargeOrderQueueConnectionFactory]","jboss.naming.context.java.comp.specj.\"specj.jar\".LargeOrderSenderSession.env.\"org.spec.jent.ejb.orders.session.LargeOrderSenderSession\".queuejboss.naming.context.java.comp.specj.\"specj.jar\".LargeOrderSenderSession.env.jms.LargeOrderQueueMissing[jboss.naming.context.java.comp.specj.\"specj.jar\".LargeOrderSenderSession.env.\"org.spec.jent.ejb.orders.session.LargeOrderSenderSession\".queuejboss.naming.context.java.comp.specj.\"specj.jar\".LargeOrderSenderSession.env.jms.LargeOrderQueue]","jboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.\"org.spec.jent.ejb.mfg.session.MessageSenderSession\".fulfillQueuejboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.jms.FulfillOrderQueueMissing[jboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.\"org.spec.jent.ejb.mfg.session.MessageSenderSession\".fulfillQueuejboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.jms.FulfillOrderQueue]","jboss.naming.context.java.comp.specj.\"specj.jar\".SupplierSession.env.\"org.spec.jent.ejb.supplier.session.SupplierSession\".queuejboss.naming.context.java.comp.specj.\"specj.jar\".SupplierSession.env.jms.ReceiveQueueMissing[jboss.naming.context.java.comp.specj.\"specj.jar\".SupplierSession.env.\"org.spec.jent.ejb.supplier.session.SupplierSession\".queuejboss.naming.context.java.comp.specj.\"specj.jar\".SupplierSession.env.jms.ReceiveQueue]","jboss.naming.context.java.comp.specj.\"specj.jar\".SupplierSession.env.\"org.spec.jent.ejb.supplier.session.SupplierSession\".queueConnFactoryjboss.naming.context.java.comp.specj.\"specj.jar\".SupplierSession.env.jms.ReceiveQueueConnectionFactoryMissing[jboss.naming.context.java.comp.specj.\"specj.jar\".SupplierSession.env.\"org.spec.jent.ejb.supplier.session.SupplierSession\".queueConnFactoryjboss.naming.context.java.comp.specj.\"specj.jar\".SupplierSession.env.jms.ReceiveQueueConnectionFactory]","jboss.naming.context.java.comp.specj.\"specj.jar\".BuyerMDB.env.\"org.spec.jent.ejb.supplier.mdb.BuyerMDB\".purchaseOrderQueuejboss.naming.context.java.comp.specj.\"specj.jar\".BuyerMDB.env.jms.PurchaseOrderQueueMissing[jboss.naming.context.java.comp.specj.\"specj.jar\".BuyerMDB.env.\"org.spec.jent.ejb.supplier.mdb.BuyerMDB\".purchaseOrderQueuejboss.naming.context.java.comp.specj.\"specj.jar\".BuyerMDB.env.jms.PurchaseOrderQueue]","jboss.naming.context.java.comp.specj.\"specj.jar\".LoaderSession.env.\"org.spec.jent.loader.session.LoaderSession\".loadQueuejboss.naming.context.java.comp.specj.\"specj.jar\".LoaderSession.env.jms.LoaderQueueMissing[jboss.naming.context.java.comp.specj.\"specj.jar\".LoaderSession.env.\"org.spec.jent.loader.session.LoaderSession\".loadQueuejboss.naming.context.java.comp.specj.\"specj.jar\".LoaderSession.env.jms.LoaderQueue]"]}

11:07:18,741 INFO  [org.jboss.as.webservices] (MSC service thread 1-15) JBAS015540: Stopping service jboss.ws.endpoint."specj.ear"."specj.jar".WorkOrderSession

11:07:18,754 INFO  [org.apache.catalina.core.StandardContext] (MSC service thread 1-15) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jbossws] has not been started

11:07:18,758 INFO  [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-15) remove: jboss.ws:context=specj,endpoint=WorkOrderSession

11:07:18,760 INFO  [org.jboss.as.jpa] (MSC service thread 1-8) JBAS011403: Stopping Persistence Unit Service 'specj.ear/specj.jar#Mfg'

11:07:18,761 INFO  [org.jboss.as.jpa] (MSC service thread 1-7) JBAS011403: Stopping Persistence Unit Service 'specj.ear/specj.jar#Order'

11:07:18,761 INFO  [org.jboss.as.jpa] (MSC service thread 1-6) JBAS011403: Stopping Persistence Unit Service 'specj.ear/specj.jar#Loader'

11:07:18,763 INFO  [org.jboss.as.jpa] (MSC service thread 1-7) JBAS011403: Stopping Persistence Unit Service 'specj.ear/specj.jar#Supplier'

11:07:18,809 INFO  [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015540: Stopping service jboss.ws.endpoint."specj.ear"."supplier.war"."org.spec.jent.supplier.web.BuyerService"

11:07:18,811 INFO  [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-4) remove: jboss.ws:context=supplier,endpoint=org.spec.jent.supplier.web.BuyerService

11:07:18,838 INFO  [org.jboss.as.webservices] (MSC service thread 1-9) JBAS015540: Stopping service jboss.ws.port-component-link

11:07:18,871 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015877: Stopped deployment specj.jar in 151ms

11:07:18,874 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment supplier.war in 154ms

11:07:18,878 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-12) JBAS015877: Stopped deployment specj.war in 157ms

11:07:18,882 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015877: Stopped deployment specj.ear in 164ms

11:07:18,886 INFO  [org.jboss.as.controller] (HttpManagementService-threads - 4) JBAS014774: Service status report

JBAS014775:    New missing/unsatisfied dependencies:

      service jboss.naming.context.java.comp.specj."specj.jar".BuyerMDB.env.jms.PurchaseOrderQueue (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".BuyerMDB.env."org.spec.jent.ejb.supplier.mdb.BuyerMDB".purchaseOrderQueue]

      service jboss.naming.context.java.comp.specj."specj.jar".BuyerMDB.env.jms.PurchaseQueueConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".BuyerMDB.env."org.spec.jent.ejb.supplier.mdb.BuyerMDB".queueConnFactory]

      service jboss.naming.context.java.comp.specj."specj.jar".LargeOrderSenderSession.env.jms.LargeOrderQueue (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".LargeOrderSenderSession.env."org.spec.jent.ejb.orders.session.LargeOrderSenderSession".queue]

      service jboss.naming.context.java.comp.specj."specj.jar".LargeOrderSenderSession.env.jms.LargeOrderQueueConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".LargeOrderSenderSession.env."org.spec.jent.ejb.orders.session.LargeOrderSenderSession".queueConnFactory]

      service jboss.naming.context.java.comp.specj."specj.jar".LoaderSession.env.jms.LoaderQueue (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".LoaderSession.env."org.spec.jent.loader.session.LoaderSession".loadQueue]

      service jboss.naming.context.java.comp.specj."specj.jar".LoaderSession.env.jms.LoaderQueueConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".LoaderSession.env."org.spec.jent.loader.session.LoaderSession".queueConnFactory]

      service jboss.naming.context.java.comp.specj."specj.jar".MessageSenderSession.env.jms.BuyerQueue (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".MessageSenderSession.env."org.spec.jent.ejb.mfg.session.MessageSenderSession".buyerQueue]

      service jboss.naming.context.java.comp.specj."specj.jar".MessageSenderSession.env.jms.BuyerQueueConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".MessageSenderSession.env."org.spec.jent.ejb.mfg.session.MessageSenderSession".buyerQueueConnFactory]

      service jboss.naming.context.java.comp.specj."specj.jar".MessageSenderSession.env.jms.FulfillOrderQueue (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".MessageSenderSession.env."org.spec.jent.ejb.mfg.session.MessageSenderSession".fulfillQueue]

      service jboss.naming.context.java.comp.specj."specj.jar".MessageSenderSession.env.jms.FulfillOrderQueueConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".MessageSenderSession.env."org.spec.jent.ejb.mfg.session.MessageSenderSession".fulfillOrderQueueConnFactory]

      service jboss.naming.context.java.comp.specj."specj.jar".SupplierSession.env.jms.ReceiveQueue (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".SupplierSession.env."org.spec.jent.ejb.supplier.session.SupplierSession".queue]

      service jboss.naming.context.java.comp.specj."specj.jar".SupplierSession.env.jms.ReceiveQueueConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".SupplierSession.env."org.spec.jent.ejb.supplier.session.SupplierSession".queueConnFactory]

 

1. I tried to add the missing dependencies by hand in the jboss.xml file and ejb-jar.xml file on the new built.xml file but it does not work, also I noticed that in the META-INF folder the copied one are old and the build.xml file is referring to some "order-orm.xml" and "hbm.xml" that I don't have, and I don't know what they should contain.

 

2. I changed the standalone-full in order to have the new jndi naming style java:jboss/env/jdbc/NameOfDS

 

Can anyone help? I would really appriciate!

 

Thanks,

Gatla

  • 1. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
    Jeremy Whiting Apprentice

    Hi Gatla,

      You will need to update the ejb-jar.xml file to define the properties so the JNDI resources can be found.

     

    Add entries for each MDB and SLSB. Your changes to the standalone-full.xml with the new JNDI names is a good start. You will need the new JNDI entries to complete the deployment descriptor file. The changes in the deployment descriptor will look similar to the following.

     

    MDB

      <message-driven>

       <ejb-name>LoaderMDB</ejb-name>

       <activation-config>

         <activation-config-property>

           <activation-config-property-name>destination</activation-config-property-name>

           <activation-config-property-value>java:jboss/jms/LoaderQueue</activation-config-property-value>

         </activation-config-property>

       </activation-config>

       <resource-ref>

         <res-ref-name>jdbc/SPECjOrderLoaderDS</res-ref-name>

         <jndi-name>java:/jdbc/SPECjLoaderDS</jndi-name>

       </resource-ref>

       <resource-ref>

         <res-ref-name>jdbc/SPECjMfgLoaderDS</res-ref-name>

         <jndi-name>java:/jdbc/SPECjLoaderDS</jndi-name>

       </resource-ref>

       <resource-ref>

         <res-ref-name>jdbc/SPECjSupplierLoaderDS</res-ref-name>

         <jndi-name>java:/jdbc/SPECjLoaderDS</jndi-name>

       </resource-ref>

      

    </message-driven>

     

     

    SLSB

     

    <session>

       <ejb-name>OrderAuditSession</ejb-name>

       <resource-ref>

          <res-ref-name>jdbc/SPECjOrderDS</res-ref-name>

          <jndi-name>java:/jdbc/SPECjOrderDS</jndi-name>

       </resource-ref>

    </session>

     

    Can you confirm that resolves the resource lookup issue you are having ?

     

    Regards,

    Jeremy

  • 2. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
    gatla srinivasareddy Newbie

    Dear Jeremy,

     

    Thanks for your help.

     

    My problem is that when I modify the ejb-jar.xml file in the SPECjEnterprise2010_v1.03/src/resources/ejb folder and after I run the command:

    ant install; ant specj.ear; ant emulator.ear; ant prepare-jboss-lib-jar

    the file included in the ear/jar file is not the modified one, but the old one.

     

    If I modify the SPECjEnterprise2010_v1.03/appservers/jboss/build.xml file to force the usage of ejb-jar.xml the naming problem is in any case not solved.

     

    Where is it talking the file from? Even if I remove all the ejb-jar.xml  file it keeps creating it. Is it taking the reference from some java code? If yes, which one?

     

    Thanks,

    Gatla

  • 3. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
    Jeremy Whiting Apprentice

    Hi Gatla,

      Yes you have come across the same problem I have found. I recommend you take an additional step before running the Ant tasks. Doing this beforehand is necessary to have the artifact generated again with the modified deployment descriptor.

     

    $ rm target/jar/specj.*

     

    Then continue as you would normally to create the artifacts.

     

    Regards,

    Jeremy

  • 4. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
    gatla srinivasareddy Newbie

    Hi Jeremy,

               Thank you very much for your prompt reply, Every time i am going run the ant tasks i removed the entire target folder(and also tried to remove only specj.* files), but still i am unable to find the upadted version of deployment descriptor file?

    are there any steps to follow additionally apart form above?

    Thanks

    Gatla.

  • 5. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
    Jeremy Whiting Apprentice

    Hi Gatla,

    Updating of the file is not handled by the Ant targets. You need to modify this file by hand. It is then bundled in the specj.jar.

     

    src/resources/ejb/META-INF/ejb-jar.xml

     

    Regards,

    Jeremy

  • 6. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
    gatla srinivasareddy Newbie

    Dear Jeremy

    I did not do any progress.

    Here is (a part of) my jboss-ejb3.xml file (in SPECj2010 was called jboss.xml but I read on the forum that JBossAS7 doesn't use that name anymore)

     

    <?xml version="1.0"?> 

       <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"

                      xmlns="http://java.sun.com/xml/ns/javaee"

                      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

                      xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd

                         http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"

                      version="3.1"

                      impl-version="2.0">

            <!-- other lines-->

    <message-driven>

       <ejb-name>FulfillOrderMDB</ejb-name>

       <activation-config>

         <activation-config-property>

           <activation-config-property-name>destination</activation-config-property-name>

           <activation-config-property-value>jms/FulfillOrderQueue</activation-config-property-value>

         </activation-config-property>

       </activation-config>

    </message-driven>

     

    <message-driven>

       <ejb-name>BuyerMDB</ejb-name>

       <activation-config>

         <activation-config-property>

           <activation-config-property-name>destination</activation-config-property-name>

           <activation-config-property-value>jms/BuyerQueue</activation-config-property-value>

         </activation-config-property>

    <activation-config-property>

           <activation-config-property-name>purchaseOrderQueue</activation-config-property-name>

           <activation-config-property-value>jms/PurchaseOrderQueue</activation-config-property-value>

         </activation-config-property>

    <activation-config-property>

           <activation-config-property-name>queueConnFactory</activation-config-property-name>

           <activation-config-property-value>jms/BuyerQueueConnectionFactory</activation-config-property-value>

         </activation-config-property>

       </activation-config>

    </message-driven>

     

     

     

    Here is an extract of my ejb-jar.xml file:

     

    <message-driven>

       <ejb-name>BuyerMDB</ejb-name>

       <ejb-class>org.spec.jent.ejb.supplier.mdb.BuyerMDB</ejb-class>

       <activation-config>

    <!--<activation-config-property>

           <activation-config-property-name>destination</activation-config-property-name>

           <activation-config-property-value>java:jboss/env/jms/BuyerQueue</activation-config-property-value>

         </activation-config-property>-->

        <activation-config-property>

           <activation-config-property-name>purchaseOrderQueue</activation-config-property-name>

           <activation-config-property-value>java:jboss/jms/PurchaseOrderQueue</activation-config-property-value>

         </activation-config-property>

        <activation-config-property>

           <activation-config-property-name>queueConnFactory</activation-config-property-name>

           <activation-config-property-value>java:jboss/jms/BuyerQueueConnectionFactory</activation-config-property-value>

         </activation-config-property>

       </activation-config>

       <resource-ref>

         <res-ref-name>jdbc/SPECjOrderLoaderDS</res-ref-name>

         <jndi-name>java:/jdbc/SPECjLoaderDS</jndi-name>

       </resource-ref>

       <resource-ref>

         <res-ref-name>jdbc/SPECjMfgLoaderDS</res-ref-name>

         <jndi-name>java:/jdbc/SPECjLoaderDS</jndi-name>

       </resource-ref>

       <resource-ref>

         <res-ref-name>jdbc/SPECjSupplierLoaderDS</res-ref-name>

         <jndi-name>java:/jdbc/SPECjLoaderDS</jndi-name>

       </resource-ref>

    </message-driven>

       <session>

           <ejb-name>LargeOrderSenderSession</ejb-name>

           <resource-ref>

              <res-ref-name>queue</res-ref-name>

              <jndi-name>jms/LargeOrderQueue</jndi-name>

           </resource-ref>

        </session>

    </enterprise-beans>

     

    Can you tell me what I am doing wrong?

    Thank you very much,

    Gatla

  • 7. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
    Jeremy Whiting Apprentice

    Hi Galta,

    Have you changed your application deployment descriptor ? I have found the deployment of the specj.war application and the specj.jar WorkOrderSession web service clash.

    Try changing the context root of the specj.war to "specj-web".

     

    <module>

       <web>

          <web-uri>specj.war</web-uri>

          <context-root>specj-web</context-root>

       </web>

    </module>

     

    Does that solve the dependency problem ?

     

    Regards,

    Jeremy

  • 8. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
    gatla srinivasareddy Newbie

    Hi Jeremy,

     

    I did change it, it was:

    <module>

              <web>

                  <web-uri>specj.war</web-uri>

                  <context-root>specj-specj</context-root>

              </web>

          </module>

     

    I also tryied to change it how you say, but nothing changes. Can you have a look at my files (last post) and tell me if I'm doing something wrong?

     

    Thanks,

    Gatla

  • 9. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
    Jeremy Whiting Apprentice

    Hi Gatla,

    You need to change ejb-jar.xml. Your extract provided shows you have not looked at each MDB and matched the necessary JMS connection factories/queues or datasources.

     

    For example, your version of BuyerMDB has

     

    • PurchaseOrderQueue
    • BuyerQueueConnectionFactory
    • SPECjLoaderDS
    • SPECjLoaderDS
    • SPECjLoaderDS
    • and the destination for BuyerQueue is commented out.

     

    Instead you should have for BuyerMDB

     

    1. An uncommented destination activation property for BuyerQueue.
    2. PurchaseQueueConnectionFactory
    3. PurchaseOrderQueue

     

    You need to repeat this process of looking at the source code and configure each MDB and SLSB.

     

    Regards,

    Jeremy

  • 10. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
    gatla srinivasareddy Newbie

    Dear Jeremy,

    going step by step here I am. This is my still unsolved problem:

     

    JBAS014775:    New missing/unsatisfied dependencies:

          service jboss.naming.context.java.comp.specj."specj.jar".BuyerMDB.env.jms.PurchaseQueueConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".BuyerMDB.env."org.spec.jent.ejb.supplier.mdb.BuyerMDB".queueConnFactory]

          service jboss.naming.context.java.comp.specj."specj.jar".LargeOrderSenderSession.env.jms.LargeOrderQueueConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".LargeOrderSenderSession.env."org.spec.jent.ejb.orders.session.LargeOrderSenderSession".queueConnFactory]

          service jboss.naming.context.java.comp.specj."specj.jar".LoaderSession.env.jms.LoaderQueueConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".LoaderSession.env."org.spec.jent.loader.session.LoaderSession".queueConnFactory]

          service jboss.naming.context.java.comp.specj."specj.jar".MessageSenderSession.env.jms.BuyerQueueConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".MessageSenderSession.env."org.spec.jent.ejb.mfg.session.MessageSenderSession".buyerQueueConnFactory]

          service jboss.naming.context.java.comp.specj."specj.jar".MessageSenderSession.env.jms.FulfillOrderQueueConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".MessageSenderSession.env."org.spec.jent.ejb.mfg.session.MessageSenderSession".fulfillOrderQueueConnFactory]

          service jboss.naming.context.java.comp.specj."specj.jar".SupplierSession.env.jms.ReceiveQueueConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".SupplierSession.env."org.spec.jent.ejb.supplier.session.SupplierSession".queueConnFactory]

          service jboss.naming.context.java.jms.PurchaseQueueConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.specj."specj.jar".BuyerMDB.env.queueConnFactory]

     

    So as you see just connectionfactory ones. Can you give me an hint? How can I add the connection factory in my jboss-ejb3.xml file?

     

    Thanks,

    Gatla

  • 11. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
    Jeremy Whiting Apprentice

    Hi Gatla,

    Try defining the connection factories like this. Don't forget using the jndi-name defined in your standalone.xml.

     

    <session>

       <ejb-name>LoaderSession</ejb-name>

       <resource-ref>

         <res-ref-name>jms/LoaderQueueConnectionFactory</res-ref-name>

         <jndi-name>java:jboss/jms/JmsXA</jndi-name>

       </resource-ref>

       <message-destination-ref>

         <message-destination-ref-name>jms/LoaderQueue</message-destination-ref-name>

         <jndi-name>java:jboss/jms/LoaderQueue</jndi-name>

       </message-destination-ref>

    </session>

     

    Regards,

    Jeremy

  • 12. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
    gatla srinivasareddy Newbie

    Dear Jeremy,

     

    thank you very much for you answers, they were really useful!

    I finally managed to solve the missing/unsatisfied dependencies error.

     

    Thanks again,

    Gatla

  • 13. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
    sun certified Newbie

    hello,

     

    please, can anybody here share with me how and/or from where i can download the ear files for "SPECjEnterprise2010"?

     

    thanks in advance for sharing whatever you can.

     

    many thanks,

    sun-certified

1 2 Previous Next