3 Replies Latest reply on Jan 23, 2012 7:14 PM by gregcharles

Can't deploy EAR on JBoss AS 7.1 CR1b

gregcharles Jan 20, 2012 2:46 PM

I'm trying to deploy an ear file that contains one war, five EJb jars, and some library jars. I've copied over the ear that deploys and runs without issues. on the jboss-as-web-7.0.2.Final. The deployment starts well.

Here's an (obfuscated) exerpt from the console log:

10:29:02,937 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "myear.ear"

10:29:08,125 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "BeanOneEJB.jar"

10:29:08,125 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "BeanTwoEJB.jar"

10:29:08,125 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "BeanThreeEJB.jar"

10:29:08,125 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "mywar.war"

10:29:08,140 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "BeanFourEJB.jar"

10:29:08,125 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "BeanFiveEJB.jar"

10:29:13,812 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread

1-4) JNDI bindings for session bean named BeanOneBean in deployment unit subdeployment "BeanOneEJB.jar" of deployment

"myear.ear" are as follows:

java:global/myear/BeanOneEJB/BeanOneBean!my.package.one.ejb.BeanOne

java:app/BeanOneEJB/BeanOneBean!my.package.one.ejb.BeanOne

java:module/BeanOneBean!my.package.one.ejb.BeanOne

java:global/myear/BeanOneEJB/BeanOneBean

java:app/BeanOneEJB/BeanOneBean

java:module/BeanOneBean

10:29:13,812 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread

1-1) JNDI bindings for session bean named BeanFiveBean in deployment unit subdeployment "BeanFiveEJB.jar" of deploymen

t "myear.ear" are as follows:

java:global/myear/BeanFiveEJB/BeanFiveBean!my.package.one.ejb.BeanFive

java:app/BeanFiveEJB/BeanFiveBean!my.package.one.ejb.BeanFive

java:module/BeanFiveBean!my.package.one.ejb.BeanFive

java:global/myear/BeanFiveEJB/BeanFiveBean

java:app/BeanFiveEJB/BeanFiveBean

java:module/BeanFiveBean

10:29:13,828 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread

1-4) JNDI bindings for session bean named BeanTwoBean in deployment unit subdeployment "BeanTwoEJB.jar" of deploymen

t "myear.ear" are as follows:

java:global/myear/BeanTwoEJB/BeanTwoBean!my.package.one.ejb.BeanTwo

java:app/BeanTwoEJB/BeanTwoBean!my.package.one.ejb.BeanTwo

java:module/BeanTwoBean!my.package.one.ejb.BeanTwo

java:global/myear/BeanTwoEJB/BeanTwoBean

java:app/BeanTwoEJB/BeanTwoBean

java:module/BeanTwoBean

10:29:13,828 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread

1-3) JNDI bindings for session bean named BeanThreeRetrievalBean in deployment unit subdeployment "BeanThreeEJB.jar" of depl

oyment "myear.ear" are as follows:

java:global/myear/BeanThreeEJB/BeanThreeRetrievalBean!mil.mhs.tc2.rr.ejb.BeanThreeRetrieval

java:app/BeanThreeEJB/BeanThreeRetrievalBean!mil.mhs.tc2.rr.ejb.BeanThreeRetrieval

java:module/BeanThreeRetrievalBean!mil.mhs.tc2.rr.ejb.BeanThreeRetrieval

java:global/myear/BeanThreeEJB/BeanThreeRetrievalBean

java:app/BeanThreeEJB/BeanThreeRetrievalBean

java:module/BeanThreeRetrievalBean

10:29:13,843 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread

1-2) JNDI bindings for session bean named BeanFourBean in deployment unit subdeployment "BeanFourEJB.jar" of deployment "p

oe.ear" are as follows:

java:global/myear/BeanFourEJB/BeanFourBean!my.package.one.ejb.BeanFour

java:app/BeanFourEJB/BeanFourBean!my.package.one.ejb.BeanFour

java:module/BeanFourBean!my.package.one.ejb.BeanFour

java:global/myear/BeanFourEJB/BeanFourBean

java:app/BeanFourEJB/BeanFourBean

java:module/BeanFourBean

10:29:15,765 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Initializing Mojarra 2.1

.5 (SNAPSHOT 20111202) for context '/mywar'

10:29:19,250 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-4) Hibernate Validator 4.2.0.Final

10:29:19,921 INFO [org.ajax4jsf.cache.CacheManager] (MSC service thread 1-4) Selected [org.ajax4jsf.cache.LRUMapCacheFa

ctory] cache factory

10:29:19,937 INFO [org.ajax4jsf.cache.LRUMapCacheFactory] (MSC service thread 1-4) Creating LRUMap cache instance using

parameters: {org.richfaces.CONTROL_SKINNING=enabled, facelets.DEVELOPMENT=false, facelets.LIBRARIES=/WEB-INF/custom.taglib

.xml, org.ajax4jsf.VIEW_HANDLERS=com.sun.facelets.FaceletViewHandler, org.richfaces.SKIN=#{appUserBean.currentSkin}, fac

elets.REFRESH_PERIOD=2, facelets.SKIP_COMMENTS=true, javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER=true, javax.faces.STATE

_SAVING_METHOD=server, javax.faces.DEFAULT_SUFFIX=.xhtml, com.sun.faces.enableRestoreView11Compatibility=false}

10:29:19,937 INFO [org.ajax4jsf.cache.LRUMapCacheFactory] (MSC service thread 1-4) Creating LRUMap cache instance of de

fault capacity

10:29:19,937 INFO [org.ajax4jsf.cache.CacheManager] (MSC service thread 1-4) Selected [org.ajax4jsf.cache.LRUMapCacheFa

ctory] cache factory

10:29:19,937 INFO [org.ajax4jsf.cache.LRUMapCacheFactory] (MSC service thread 1-4) Creating LRUMap cache instance using

parameters: {org.richfaces.CONTROL_SKINNING=enabled, facelets.DEVELOPMENT=false, facelets.LIBRARIES=/WEB-INF/custom.taglib

.xml, org.ajax4jsf.VIEW_HANDLERS=com.sun.facelets.FaceletViewHandler, org.richfaces.SKIN=#{appUserBean.currentSkin}, fac

elets.REFRESH_PERIOD=2, facelets.SKIP_COMMENTS=true, javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER=true, javax.faces.STATE

_SAVING_METHOD=server, javax.faces.DEFAULT_SUFFIX=.xhtml, com.sun.faces.enableRestoreView11Compatibility=false}

10:29:19,937 INFO [org.ajax4jsf.cache.LRUMapCacheFactory] (MSC service thread 1-4) Creating LRUMap cache instance of de

fault capacity

10:29:19,968 INFO [org.jboss.web] (MSC service thread 1-4) registering web context: /mywar

It then fails for no apparent reason. The console log continues:

10:29:20,187 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015856: Undeploy of deployment "myear.ear" wa

s rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.s

ubunit.\"myear.ear\".\"BeanFourEJB.jar\".component.BeanFourBean.CREATEjboss.ejb.remote-transactions-repositoryMissing[jboss.

deployment.subunit.\"myear.ear\".\"BeanFourEJB.jar\".component.BeanFourBean.CREATEjboss.ejb.remote-transactions-repository]"

,"jboss.deployment.subunit.\"myear.ear\".\"BeanTwoEJB.jar\".component.BeanTwoBean.CREATEjboss.ejb.remote-transactions-

repositoryMissing[jboss.deployment.subunit.\"myear.ear\".\"BeanTwoEJB.jar\".component.BeanTwoBean.CREATEjboss.ejb.remo

te-transactions-repository]","jboss.deployment.subunit.\"myear.ear\".\"BeanThreeEJB.jar\".component.BeanThreeRetrievalBean.CRE

ATEjboss.ejb.remote-transactions-repositoryMissing[jboss.deployment.subunit.\"myear.ear\".\"BeanThreeEJB.jar\".component.Res

ultsRetrievalBean.CREATEjboss.ejb.remote-transactions-repository]","jboss.deployment.subunit.\"myear.ear\".\"BeanOneEJB.j

ar\".component.BeanOneBean.CREATEjboss.ejb.remote-transactions-repositoryMissing[jboss.deployment.subunit.\"myear.ear\".\

"BeanOneEJB.jar\".component.BeanOneBean.CREATEjboss.ejb.remote-transactions-repository]","jboss.deployment.subunit.\"p

oe.ear\".\"BeanFiveEJB.jar\".component.BeanFiveBean.CREATEjboss.ejb.remote-transactions-repositoryMissing[jboss.deploy

ment.subunit.\"myear.ear\".\"BeanFiveEJB.jar\".component.BeanFiveBean.CREATEjboss.ejb.remote-transactions-repository]"]}

10:29:20,281 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment BeanFiveEJB.jar in 93ms

10:29:20,281 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment BeanFourEJB.jar in 94ms

10:29:20,281 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment BeanThreeEJB.jar in 94ms

10:29:20,281 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment BeanTwoEJB.jar in 95ms

10:29:20,281 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment BeanOneEJB.jar in 101ms

10:29:20,625 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Stopped deployment mywar.war i

n 444ms

10:29:20,671 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Stopped deployment myear.ear in 494ms

10:29:20,671 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report

JBAS014775: New missing/unsatisfied dependencies:

service jboss.ejb.remote-transactions-repository (missing) dependents: [service jboss.deployment.subunit."myear.ear"

."BeanFourEJB.jar".component.BeanFourBean.CREATE, service jboss.deployment.subunit."myear.ear"."BeanThreeEJB.jar".component.Re

sultsRetrievalBean.CREATE, service jboss.deployment.subunit."myear.ear"."BeanFiveEJB.jar".component.BeanFiveBean.CREATE,

service jboss.deployment.subunit."myear.ear"."BeanTwoEJB.jar".component.BeanTwoBean.CREATE, JBAS014799: ... and 2 mor

e ]

10:29:20,671 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite oper

ation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unav

ailable dependencies" => ["jboss.deployment.subunit.\"myear.ear\".\"BeanFourEJB.jar\".component.BeanFourBean.CREATEjboss.ejb

.remote-transactions-repositoryMissing[jboss.deployment.subunit.\"myear.ear\".\"BeanFourEJB.jar\".component.BeanFourBean.CRE

ATEjboss.ejb.remote-transactions-repository]","jboss.deployment.subunit.\"myear.ear\".\"BeanTwoEJB.jar\".component.Order

UtilBean.CREATEjboss.ejb.remote-transactions-repositoryMissing[jboss.deployment.subunit.\"myear.ear\".\"BeanTwoEJB.jar\"

.component.BeanTwoBean.CREATEjboss.ejb.remote-transactions-repository]","jboss.deployment.subunit.\"myear.ear\".\"Result

sEJB.jar\".component.BeanThreeRetrievalBean.CREATEjboss.ejb.remote-transactions-repositoryMissing[jboss.deployment.subunit

.\"myear.ear\".\"BeanThreeEJB.jar\".component.BeanThreeRetrievalBean.CREATEjboss.ejb.remote-transactions-repository]","jboss.d

eployment.subunit.\"myear.ear\".\"BeanOneEJB.jar\".component.BeanOneBean.CREATEjboss.ejb.remote-transactions-repositoryM

issing[jboss.deployment.subunit.\"myear.ear\".\"BeanOneEJB.jar\".component.BeanOneBean.CREATEjboss.ejb.remote-transactio

ns-repository]","jboss.deployment.subunit.\"myear.ear\".\"BeanFiveEJB.jar\".component.BeanFiveBean.CREATEjboss.ejb.remot

e-transactions-repositoryMissing[jboss.deployment.subunit.\"myear.ear\".\"BeanFiveEJB.jar\".component.BeanFiveBean.CREAT

Ejboss.ejb.remote-transactions-repository]"]}}}

It seems to be claiming about missing dependencies for the EJBs that milliseconds before it assured me were deployed just fine. What could be causing this? The only configuration I use is a simple application.xml file. I don't use any special JBoss config files. Should I be?

jboss-7.1cr1b-console-log.txt.zip 2.0 KB

1. Re: Can't deploy EAR on JBoss AS 7.1 CR1b

jaikiran Jan 20, 2012 10:51 PM (in response to gregcharles)

Do you have any changes to your standalone.xml/standalone-full.xml?
1 of 1 people found this helpful
Actions
2. Re: Can't deploy EAR on JBoss AS 7.1 CR1b

ouaser Jan 23, 2012 3:09 PM (in response to gregcharles)

just let us see your EAR- jboss-deployment-structure.xml.
Actions
3. Re: Can't deploy EAR on JBoss AS 7.1 CR1b

gregcharles Jan 23, 2012 7:14 PM (in response to ouaser)

Jaikiran posted me in the right direction. I had made changes to standalone.xml to customize the logging, add a datasource, configure an https connector, and a couple of other minor changes. Stupidly, I just used the ammended standalone.xml on the new JBoss 7.1. What I really needed to do was merge my changes into the new standalone.xml, which changed in some fairly significant ways between the JBoss 7.02 and JBoss 7.1 releases.

It's nice that JBoss configuration is more centralized now, whereas there used to be a whole array of xml and properties files spread across multiple directories. The downside is there are multiple points of change for that one configuration file: JBoss developers, application deployers (like me), and even the JBoss runtime writes changes to it. Merging it was a non-trivial challenge.

@Mustapha -- thanks for your advice. I did get it working through careful merging of the standalone.xml. In any case, I'm not using a jboss-deployment-structure.xml file, so I wouldn't have had anything to show you. Fortunately, convention over configuration seems to be working for me here.
Actions

Go to original post