7:38 a.m.
Error when defining dependency between an EAR and its related WAR
-----------------------------------------------------------------
Key: JBAS-7760
URL: https://jira.jboss.org/jira/browse/JBAS-7760
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: System service
Affects Versions: JBossAS-6.0.0.M1
Environment: JBOSS6.0.0M1 Windows XP
Reporter: denis boutin
Assignee: Dimitris Andreadis
Hi,
When JBoss 6.0M1 starts, I've got the following error :
<<
18:06:32,754 INFO [AbstractServer] JBossAS [6.0.0.M1 (build: SVNTag=JBoss_6_0_0_M1
date=200912040958)] Started in 43s:204ms
18:07:56,352 WARN [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "jboss.web.deployment:war=/myapp" is missing the following
dependencies:
Dependency
"jboss.j2ee:module="company-agents-ejb.jar",service=EjbModule" (should
be in state "Create", but is actually in state "** NOT FOUND Depends on
'jboss.j2ee:module="company-agents-ejb.jar",serv
ice=EjbModule' **")
Dependency
"jboss.j2ee:module="company-engine-ejb.jar",service=EjbModule" (should
be in state "Create", but is actually in state "** NOT FOUND Depends on
'jboss.j2ee:module="company-engine-ejb.jar",serv
ice=EjbModule' **")
Dependency
"jboss.j2ee:module="company-data-readwrite-ejb.jar",service=EjbModule"
(should be in state "Create", but is actually in state "** NOT FOUND
Depends on 'jboss.j2ee:module="company-data-readwri
te-ejb.jar",service=EjbModule' **")
DEPLOYMENTS IN ERROR:
Deployment
"jboss.j2ee:module="company-agents-ejb.jar",service=EjbModule" is in
error due to the following reason(s): ** NOT FOUND Depends on
'jboss.j2ee:module="company-agents-ejb.jar",service=EjbModule'
**
Deployment
"jboss.j2ee:module="company-engine-ejb.jar",service=EjbModule" is in
error due to the following reason(s): ** NOT FOUND Depends on
'jboss.j2ee:module="company-engine-ejb.jar",service=EjbModule'
**
Deployment
"jboss.j2ee:module="company-data-readwrite-ejb.jar",service=EjbModule"
is in error due to the following reason(s): ** NOT FOUND Depends on
'jboss.j2ee:module="company-data-readwrite-ejb.jar",se
rvice=EjbModule' **
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1002)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:948)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:870)
at
org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at
org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:378)
>
The EAR is well deployed, however the WAR application seems not to detect that the module
set in the jboss-web.xml of WEB-INF folder in WAR.
Jboss-web.xml
<<
<?xml version="1.0" encoding="utf-8"?>
<jboss-web>
<context-root>/myapp</context-root>
<security-domain>java:jaas/myapp-web</security-domain>
<!-- Make the webapp dependent of the deployment of the engine -->
<depends>jboss.j2ee:module="company-agents-ejb.jar",service=EjbModule</depends>
<depends>jboss.j2ee:module="company-data-readwrite-ejb.jar",service=EjbModule</depends>
<depends>jboss.j2ee:module="company-engine-ejb.jar",service=EjbModule</depends>
</jboss-web>
>
The following modules are well deployed in the JMX console :
- jboss.j2ee:module="company-agents-ejb.jar",service=EjbModule
- jboss.j2ee:module="company-data-readwrite-ejb.jar",service=EjbModule
- jboss.j2ee:module="company-engine-ejb.jar",service=EjbModule
If I query the JMX console with exactly those strings those modules are well found but it
is not the case inside JBoss 6.0M1. Those kind of settings works well under JBoss 4.0.0.
Does something changed inside JBoss 6.0M1 related to those dependencies between WAR &
EAR ?
The idea beyond that is to be sure that the EAR is loaded before the WAR file.
Do you need more elements regarding that case ?
Regards,
Denis.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira