3 Replies Latest reply on Feb 23, 2012 12:13 AM by janakiraman.e

Jboss 6.1.0-Final DEPLOYMENTS MISSING DEPENDENCIES ERROR

janakiraman.e Feb 21, 2012 11:17 PM

Hi,

I have doing the migration of jboss from 4 to jboss 6.1.0 final version and hence i got the below deployment error .

Kindly suggest for the mentioned error

Deployment "jboss-switchboard:appName=power,module=power" is missing the following dependencies:

Dependency "java:/queue/autoReleaseQueue" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'java:/queue/autoReleaseQueue'**")

Dependency "java:/queue/postProcessQueue" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'java:/queue/postProcessQueue'**")

Dependency "java:/mail/Power" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'java:/mail/Power' **")

Deployment "jboss.web.deployment:war=/power" is missing the following dependencies:

Dependency "jboss-switchboard:appName=power,module=power" (should be in state "Installed", but is actually in state "Create")

DEPLOYMENTS IN ERROR:
Deployment "java:/queue/autoReleaseQueue" is in error due to the following rea
son(s): ** NOT FOUND Depends on 'java:/queue/autoReleaseQueue' **
Deployment "java:/mail/Power" is in error due to the following reason(s): ** N
OT FOUND Depends on 'java:/mail/Power' **
Deployment "java:/queue/postProcessQueue" is in error due to the following rea
son(s): ** NOT FOUND Depends on 'java:/queue/postProcessQueue' **

at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(Dep

well my jboss-web.xml

<?xml version="1.0" encoding="UTF-8"?>
<jboss-web>
<context-root>power</context-root>
<security-domain>java:/jaas/PowerRealm</security-domain>
<resource-ref>
<res-ref-name>jdbc/Cylab</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<jndi-name>java:/jdbc/Cylab</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>mail/Power</res-ref-name>
<res-type>javax.mail.Session</res-type>
<jndi-name>java:/mail/Power</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>queue/autoReleaseQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<jndi-name>java:/queue/autoReleaseQueue</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>queue/postProcessQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<jndi-name>java:/queue/postProcessQueue</jndi-name>
</resource-ref>
<ejb-ref>
<ejb-ref-name>ejb/ReportRenderEJB</ejb-ref-name>
<jndi-name>ReportRenderEJB</jndi-name>
</ejb-ref>
</jboss-web>

web.xml

<resource-ref>
    <description>Resource reference to a factory for javax.mail.Session
      instances that may be used for sending electronic mail
      messages, preconfigured to connect to the appropriate
      SMTP server.</description>
    <res-ref-name>mail/Power</res-ref-name>
    <res-type>javax.mail.Session</res-type>
    <res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
<res-ref-name>queue/autoReleaseQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
<res-ref-name>queue/postProcessQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<res-auth>Container</res-auth>
</resource-ref>

Please advice for the above mentioned request..

Once i commented the following lines in the xml files the application deployed without error.

Thanks & Regards,

Janakiraman E

1. Re: Jboss 6.1.0-Final DEPLOYMENTS MISSING DEPENDENCIES ERROR

jaikiran Feb 22, 2012 1:35 AM (in response to janakiraman.e)

How are you deploying those queues referenced by those JNDI names?
Actions
2. Re: Jboss 6.1.0-Final DEPLOYMENTS MISSING DEPENDENCIES ERROR

janakiraman.e Feb 22, 2012 2:14 AM (in response to jaikiran)

Thanks for your reply.

The process of Autorelease and postprocess are working in the backend of the application.

Well the queues are deployed inside the conf folder as autorelease,postprocess folder with the reference of ejb-jar.xml and jboss.xml

autorelease/jboss.xml

<?xml version="1.0"?>
<jboss>
          <enterprise-beans>
                    <message-driven>
                              <ejb-name>AutoReleaseMDB</ejb-name>
                              <destination-jndi-name>queue/autoReleaseQueue</destination-jndi-name>
                              <resource-ref>
                                        <res-ref-name>jms/QCF</res-ref-name>
                                        <jndi-name>ConnectionFactory</jndi-name>
                              </resource-ref>
                              <resource-ref>
                                        <res-ref-name>jdbc/Cylab</res-ref-name>
                                        <jndi-name>java:/jdbc/Cylab</jndi-name>
                              </resource-ref>
                              <ejb-ref>
                                        <ejb-ref-name>ejb/ReportRenderEJB</ejb-ref-name>
                                        <jndi-name>ReportRenderEJB</jndi-name>
                              </ejb-ref>
                    </message-driven>
          </enterprise-beans>
</jboss>

autorelease/ejb-jar.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
          <enterprise-beans>
                    <message-driven>
                              <ejb-name>AutoReleaseMDB</ejb-name>
                              <destination-jndi-name>queue/autoReleaseQueue</destination-jndi-name>
                              <ejb-class>com.questdiagnostics.power.autorelease.ejb.AutoReleaseMDB</ejb-class>
                              <transaction-type>Bean</transaction-type>
                              <message-driven-destination>
                                        <destination-type>javax.jms.Queue</destination-type>
                              </message-driven-destination>
                              <resource-ref>
                                        <res-ref-name>jms/QCF</res-ref-name>
                                        <res-type>javax.jms.QueueConnectionFactory</res-type>
                                        <res-auth>Container</res-auth>
                              </resource-ref>
                              <resource-ref>
                                        <res-ref-name>jdbc/Cylab</res-ref-name>
                                        <res-type>javax.sql.DataSource</res-type>
                                        <res-auth>Container</res-auth>
                              </resource-ref>
                              <env-entry>
                                        <env-entry-name>ejb/Site</env-entry-name>
                                        <env-entry-value>com.questdiagnostics.power.site.dao.SiteDAOOracle</env-entry-value>
                                        <env-entry-type>java.lang.String</env-entry-type>
                              </env-entry>
                              <env-entry>
                                        <env-entry-name>ejb/FileManager</env-entry-name>
                                        <env-entry-value>com.questdiagnostics.power.filemanager.dao.FileManagerDAOOracle</env-entry-value>
                                        <env-entry-type>java.lang.String</env-entry-type>
                              </env-entry>
                                    <env-entry>
                                      <env-entry-name>ejb/RecordManager</env-entry-name>
                                      <env-entry-value>com.questdiagnostics.power.recordmanager.dao.RecordManagerDAOOracle</env-entry-value>
                                      <env-entry-type>java.lang.String</env-entry-type>
                                    </env-entry>
                              <env-entry>
                                        <env-entry-name>ejb/AccessionManager</env-entry-name>
                                        <env-entry-value>com.questdiagnostics.power.accessionmanager.dao.AccessionManagerDAOOracle</env-entry-value>
                                        <env-entry-type>java.lang.String</env-entry-type>
                              </env-entry>
                                    <env-entry>
                                      <env-entry-name>ejb/ReportManager</env-entry-name>
                                      <env-entry-value>com.questdiagnostics.power.reportmanager.dao.ReportManagerDAOOracle</env-entry-value>
                                      <env-entry-type>java.lang.String</env-entry-type>
                                    </env-entry>
                              <env-entry>
                                        <env-entry-name>ejb/Demographics</env-entry-name>
                                        <env-entry-value>com.questdiagnostics.power.demographics.dao.ClientDemographicsDAOOracle</env-entry-value>
                                        <env-entry-type>java.lang.String</env-entry-type>
                              </env-entry>
                              <env-entry>
                                        <env-entry-name>ejb/AutoRelease</env-entry-name>
                                        <env-entry-value>com.questdiagnostics.power.autorelease.dao.AutoReleaseDAOOracle</env-entry-value>
                                        <env-entry-type>java.lang.String</env-entry-type>
                              </env-entry>
                              <ejb-ref>
                                        <ejb-ref-name>ejb/ReportRenderEJB</ejb-ref-name>
                                        <ejb-ref-type>Session</ejb-ref-type>
                                        <home>com.questdiagnostics.power.render.ejb.ReportRenderHome</home>
                                        <remote>com.questdiagnostics.power.render.ejb.ReportRender</remote>
                              </ejb-ref>
                    </message-driven>
          </enterprise-beans>
</ejb-jar>

Similarly for the postprocess queue..

Regards,
Janakiraman E
Actions
3. Re: Jboss 6.1.0-Final DEPLOYMENTS MISSING DEPENDENCIES ERROR

janakiraman.e Feb 23, 2012 12:13 AM (in response to jaikiran)

Thnaks for your reply..

The process of Autorelease and postprocess are working in the backend of the application.

Well the queues are deployed inside the conf folder as autorelease,postprocess folder with the reference of ejb-jar.xml and jboss.xml

autorelease/jboss.xml

<?xml version="1.0"?>
<jboss>
<enterprise-beans>
<message-driven>
<ejb-name>AutoReleaseMDB</ejb-name>
<destination-jndi-name>queue/autoReleaseQueue</destination-jndi-name>
<resource-ref>
<res-ref-name>jms/QCF</res-ref-name>
<jndi-name>ConnectionFactory</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>jdbc/Cylab</res-ref-name>
<jndi-name>java:/jdbc/Cylab</jndi-name>
</resource-ref>
<ejb-ref>
<ejb-ref-name>ejb/ReportRenderEJB</ejb-ref-name>
<jndi-name>ReportRenderEJB</jndi-name>
</ejb-ref>
</message-driven>
</enterprise-beans>
</jboss>

autorelease/ejb-jar.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<message-driven>
<ejb-name>AutoReleaseMDB</ejb-name>
<destination-jndi-name>queue/autoReleaseQueue</destination-jndi-name>
<ejb-class>com.questdiagnostics.power.autorelease.ejb.AutoReleaseMDB</ejb-class>
<transaction-type>Bean</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
<resource-ref>
<res-ref-name>jms/QCF</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
<res-ref-name>jdbc/Cylab</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<env-entry>
<env-entry-name>ejb/Site</env-entry-name>
<env-entry-value>com.questdiagnostics.power.site.dao.SiteDAOOracle</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
<env-entry>
<env-entry-name>ejb/FileManager</env-entry-name>
<env-entry-value>com.questdiagnostics.power.filemanager.dao.FileManagerDAOOracle</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
<env-entry>
<env-entry-name>ejb/RecordManager</env-entry-name>
<env-entry-value>com.questdiagnostics.power.recordmanager.dao.RecordManagerDAOOracle</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
<env-entry>
<env-entry-name>ejb/AccessionManager</env-entry-name>
<env-entry-value>com.questdiagnostics.power.accessionmanager.dao.AccessionManagerDAOOracle</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
<env-entry>
<env-entry-name>ejb/ReportManager</env-entry-name>
<env-entry-value>com.questdiagnostics.power.reportmanager.dao.ReportManagerDAOOracle</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
<env-entry>
<env-entry-name>ejb/Demographics</env-entry-name>
<env-entry-value>com.questdiagnostics.power.demographics.dao.ClientDemographicsDAOOracle</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
<env-entry>
<env-entry-name>ejb/AutoRelease</env-entry-name>
<env-entry-value>com.questdiagnostics.power.autorelease.dao.AutoReleaseDAOOracle</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
<ejb-ref>
<ejb-ref-name>ejb/ReportRenderEJB</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.questdiagnostics.power.render.ejb.ReportRenderHome</home>
<remote>com.questdiagnostics.power.render.ejb.ReportRender</remote>
</ejb-ref>
</message-driven>
</enterprise-beans>
</ejb-jar>

Similarly for the postprocess queue..

Regards,
Janakiraman E
Actions

Go to original post