New missing/unsatisfied dependencies in curren migration from JBoss 6.1.0 to JBoss 7.1.0
technokrat Jun 20, 2012 8:13 AMHi, I have problem with deploying application.
jboss-deployment-structure:
<jboss-deployment-structure>
<ear-subdeployments-isolated>false</ear-subdeployments-isolated>
<deployment>
<dependencies>
<!--module name="javax.api" export="true"/-->
<module name="org.apache.log4j" export="true" />
<module name="org.hibernate" slot="3" export="true" />
<module name="defgo_libs" export="true"/>
<module name="deployment.module.hibernate-utils" export="true"/>
<module name="deployment.module.defgo-utils" export="true"/>
</dependencies>
</deployment>
<sub-deployment name="logger.jar"/>
<sub-deployment name="benchmark.jar"/>
<module name="deployment.module.hibernate-utils">
<resources>
<resource-root path="hibernate-utils.jar"/>
</resources>
</module>
<module name="deployment.module.defgo-utils">
<resources>
<resource-root path="defgo-utils.jar"/>
</resources>
</module>
</jboss-deployment-structure>
Benchmark jboss-ejb3.xml:
<?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">
<enterprise-beans>
<session>
<description>Unit data access object</description>
<display-name>Unit Accessor</display-name>
<ejb-name>UnitAccessor</ejb-name>
<ejb-class>net.defgo.benchmark.hierarchy.impl.UnitDAO</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<description>UnitStatistic data access object</description>
<display-name>UnitStatistic Accessor</display-name>
<ejb-name>UnitStatisticAccessor</ejb-name>
<ejb-class>net.defgo.benchmark.hierarchy.impl.UnitStatisticDAO</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<description>Business interface for hierarchy</description>
<display-name>Business Hierarchy</display-name>
<ejb-name>BusinessHierarchy</ejb-name>
<ejb-class>net.defgo.benchmark.hierarchy.impl.BusinessHierarchyBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
</jboss:ejb-jar>
Logger jboss-ejb3.xml:
<?xml version="1.0"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
version="3.0">
<enterprise-beans>
<session>
<description>Logger data access object</description>
<display-name>LogAccessor</display-name>
<ejb-name>LogAccessor</ejb-name>
<ejb-class>net.defgo.logger.impl.LogDAO</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<description>Write diary log</description>
<display-name>DiaryLoggerBean</display-name>
<ejb-name>DiaryLoggerBean</ejb-name>
<ejb-class>net.defgo.logger.impl.DiaryLoggerBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<message-driven>
<description>Write diary log</description>
<display-name>LogWriterBean</display-name>
<ejb-name>LogWriter</ejb-name>
<ejb-class>net.defgo.logger.impl.LogWriter</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>destinationType</activation-config-property-name>
<activation-config-property-value>javax.jms.Queue</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>destination</activation-config-property-name>
<activation-config-property-value>queue/LogQueue</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>subscriptionDurability</activation-config-property-name>
<activation-config-property-value>Durable</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>acknowledgeMode</activation-config-property-name>
<activation-config-property-value>Auto-acknowledge</activation-config-property-value>
</activation-config-property>
</activation-config>
<!--resource-ref>
<res-ref-name>java:/ConnectionFactory</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref-->
</message-driven>
</enterprise-beans>
</ejb-jar>
JBoss writes about missing/unavailable dependents. But I can't find which dependents and how I can fix it.
The part of log is:
"15:47:05,019 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy
of deployment "defgo.ear" was rolled back with failure message {"JBAS014771: Services with m
issing/unavailable dependencies" => ["jboss.naming.context.java.comp.defgo.benchmark.UnitSta
tisticAccessor.ORBjboss.naming.context.java.comp.defgo.benchmark.UnitStatisticAccessorMissin..."
Detailed log see in server.log.
boot.log isn't informative, I set log level to TRACE for finding problem with JAXP, but I didn't find.
-
server.log.zip 162.1 KB
-
boot.log.zip 2.1 KB