[JBoss JIRA] Created: (EMBJOPR-21) "CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} ... RHQDS" warning logged during AS5 startup
5:04 p.m.
"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
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
8:47 p.m.
New subject: [JBoss JIRA] Commented: (EMBJOPR-21) "CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} ... RHQDS" warning logged during AS5 startup
[
https://jira.jboss.org/jira/browse/EMBJOPR-21?page=com.atlassian.jira.plu...
]
Charles Crouch commented on EMBJOPR-21:
---------------------------------------
Just to clarify we don't want rhq-core-domain-1.2.0-SNAPSHOT.jar deployed as an EJB
jar, just a regular old bunch of POJOs, as it was in JBAS4.x
"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
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
9:14 p.m.
New subject: [JBoss JIRA] Updated: (EMBJOPR-21) "CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} ... RHQDS" warning logged during AS5 startup
[
https://jira.jboss.org/jira/browse/EMBJOPR-21?page=com.atlassian.jira.plu...
]
Ales Justin updated EMBJOPR-21:
-------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185815#...
"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
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
9:28 p.m.
New subject: [JBoss JIRA] Commented: (EMBJOPR-21) "CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} ... RHQDS" warning logged during AS5 startup
[
https://jira.jboss.org/jira/browse/EMBJOPR-21?page=com.atlassian.jira.plu...
]
Andrew Lee Rubinger commented on EMBJOPR-21:
--------------------------------------------
Looks like the Structural Deployers are working just fine in AS5 ;)
EJB3 Persistence Specification 6.2: Persistence Unit Packaging:
"A persistence unit is defined by a persistence.xml file. The jar file or directory
whose META-INF
directory contains the persistence.xml file is termed the root of the persistence unit. In
Java EE,
the root of a persistence unit may be one of the following:
* the WEB-INF/classes directory of a WAR file[40]
[40] The root of the persistence unit is the WEB-INF/classes directory; the
persistence.xml file is therefore contained in the
WEB-INF/classes/META-INF directory."
...so either remove the persistence.xml or provide the DataSource.
"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
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
9:34 p.m.
New subject: [JBoss JIRA] Commented: (EMBJOPR-21) "CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} ... RHQDS" warning logged during AS5 startup
[
https://jira.jboss.org/jira/browse/EMBJOPR-21?page=com.atlassian.jira.plu...
]
Andrew Lee Rubinger commented on EMBJOPR-21:
--------------------------------------------
Oh, also valid in:
"a jar file in the WEB-INF/lib directory of a WAR file"
...also EJB3 Persistence Spec 6.2
"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
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
2:56 p.m.
New subject: [JBoss JIRA] Resolved: (EMBJOPR-21) "CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} ... RHQDS" warning logged during AS5 startup
[
https://jira.jboss.org/jira/browse/EMBJOPR-21?page=com.atlassian.jira.plu...
]
Ian Springer resolved EMBJOPR-21.
---------------------------------
Resolution: Done
Assignee: Ian Springer
Added an antrun execution to core/pom.xml that excises ejb-jar.xml and persistence.xml
from the domain jar - r30.
"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: Ian Springer
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
9:04 p.m.
New subject: [JBoss JIRA] Reopened: (EMBJOPR-21) "CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} ... RHQDS" warning logged during AS5 startup
[
https://jira.jboss.org/jira/browse/EMBJOPR-21?page=com.atlassian.jira.plu...
]
Charles Crouch reopened EMBJOPR-21:
-----------------------------------
I don't really like the idea of futzing with the core domain jar. This means in future
embedded is going to have one version of rhq-core-domain-1.2.0.jar and jopr is going to
have a different version of rhq-core-domain-1.2.0.jar. Just doesn't seem right.
I think we should investigate the option Ales mentioned on the associated forum thread.
I'm continuing the discussion with him there.
"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: Ian Springer
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
9:39 p.m.
New subject: [JBoss JIRA] Updated: (EMBJOPR-21) "CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} ... RHQDS" warning logged during AS5 startup
[
https://jira.jboss.org/jira/browse/EMBJOPR-21?page=com.atlassian.jira.plu...
]
Ian Springer updated EMBJOPR-21:
--------------------------------
Assignee: Charles Crouch (was: Ian Springer)
Ok, I don't see any problem with it, but feel free to look into alternatives.
"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
11:27 p.m.
New subject: [JBoss JIRA] Commented: (EMBJOPR-21) "CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} ... RHQDS" warning logged during AS5 startup
[
https://jira.jboss.org/jira/browse/EMBJOPR-21?page=com.atlassian.jira.plu...
]
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
6:51 p.m.
New subject: [JBoss JIRA] Commented: (EMBJOPR-21) "CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} ... RHQDS" warning logged during AS5 startup
[
https://jira.jboss.org/jira/browse/EMBJOPR-21?page=com.atlassian.jira.plu...
]
Charles Crouch commented on EMBJOPR-21:
---------------------------------------
If core-domain was published with a no-ejb version then I would be ok with depending on
that but I don't like the idea of repackaging .jar's. Having this as part of the
build procedure will make porting to other build systems harder (e.g. when we need to get
into brew) versus having a standalone file (jboss-structure.xml) which will get included
using the default mvn mechanism.
"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
6:53 p.m.
New subject: [JBoss JIRA] Resolved: (EMBJOPR-21) "CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} ... RHQDS" warning logged during AS5 startup
[
https://jira.jboss.org/jira/browse/EMBJOPR-21?page=com.atlassian.jira.plu...
]
Charles Crouch resolved EMBJOPR-21.
-----------------------------------
Resolution: Done
r39 and r40 backout the jar repackaging from the core pom.xml and include
jboss-structure.xml in the jbas5 deployment.
"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
5898
days inactive
5909
days old
embjopr-issues@lists.jboss.org
10 comments
4 participants
participants (4)
-
Ales Justin (JIRA) -
Andrew Lee Rubinger (JIRA)
-
Charles Crouch (JIRA)
-
Ian Springer (JIRA)