[embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-21) "CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} ... RHQDS" warning logged during AS5 startup

[Ian Springer (JIRA)]

    [ https://jira.jboss.org/jira/browse/EMBJOPR-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12436894#action_12436894 ] 

Ian Springer commented on EMBJOPR-21:
-------------------------------------

Another advantage of stripping the JPA/EJB descriptors out of the jar is that it could prevent similar errors in other app servers (e.g. GlassFish, Geronimo) should someone try to get Embedded Jopr running in one of them at some point. We never use the domain classes as EJBs, only as POJOs, so not deploying them in something that is technically an EJB-JAR makes sense no matter what app server EmbJopr is being deployed to.



> "CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} ... RHQDS" warning logged during AS5 startup
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: EMBJOPR-21
>                 URL: https://jira.jboss.org/jira/browse/EMBJOPR-21
>             Project: Embedded Jopr
>          Issue Type: Bug
>          Components: Core Infrastructure
>    Affects Versions: 1.0
>            Reporter: Ian Springer
>            Assignee: Charles Crouch
>             Fix For: 1.1
>
>
> Here's the full log message:
> 11:23:54,071 WARN  [HDScanner] Failed to process changes
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR
>  DETAILS):
> *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
> persistence.unit:unitName=#rhqpu
>  -> jboss.jca:name=RHQDS,service=DataSourceBinding{Create:** NOT FOUND Depends on 'jboss.jca:name=RHQDS,service=DataSourceBinding' **}
> *** CONTEXTS IN ERROR: Name -> Error
> jboss.jca:name=RHQDS,service=DataSourceBinding -> ** NOT FOUND Depends on 'jboss.jca:name=RHQDS,service=DataSourceBinding' **
>         at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:834)
>         at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:661)
>         at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:291)
>         at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>         at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>         at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
>         at java.lang.Thread.run(Thread.java:619)
> I'm pretty sure this warning is the result of AS5 trying to deploy admin-console.war/WEB-INF/lib/rhq-core-domain-1.2.0-SNAPSHOT.jar as an EJB-JAR. This jar contains a META-INF/persistence.xml which defines a "rhqpu" persistence unit that references a "RHQDS" datasource. It also contains a META-INF/ejb-jar.xml. I'm not sure whether it's correct for AS5 to be trying to deploy the jar as an EJB-JAR, being as its in a WEB-INF/lib directory. We don't see a similar warning on AS4, so it presumably does not try to deloy it as an EJB-JAR.
> The warning doesn't seem to break anything. However, it is long and ugly and will alarm users, so we need to figure out a way to get rid of it.

-- 
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