November 2008 - embjopr-issues - Jboss List Archives

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

by Ian Springer (JIRA)

"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

15 years, 5 months

4
10
0 / 0

[JBoss JIRA] Created: (EMBJOPR-20) problem with apache https

by davide pasinato (JIRA)

problem with apache https ------------------------- Key: EMBJOPR-20 URL: https://jira.jboss.org/jira/browse/EMBJOPR-20 Project: Embedded Jopr Issue Type: Bug Components: Web App/Integration Affects Versions: 1.0 Environment: apache Reporter: davide pasinato In my opinion this is link to JIRA issue EMBJOPR-15 There is a problem if I try to access embedde-jopr in https (through an apache) Accessing this page to login https://MYWEB/embedded-jopr/login.seam?conversationId=8 After submitting user and password I am redirected to http://MYWEB:443/embedded-jopr/login.seam That is incorrect (WRONG protocol). The URL should be https://MYWEB/embedded-jopr/login.seam Regars Davide -- 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

15 years, 5 months

2
2
0 / 0

[JBoss JIRA] Resolved: (EMBJOPR-15) Incorrectly generate base url for app if listening on port 80

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/EMBJOPR-15?page=com.atlassian.jira.plu... ] Charles Crouch resolved EMBJOPR-15. ----------------------------------- Resolution: Done r38, tested with http connector set to port 80 and everything looked good > Incorrectly generate base url for app if listening on port 80 > ------------------------------------------------------------- > > Key: EMBJOPR-15 > URL: https://jira.jboss.org/jira/browse/EMBJOPR-15 > Project: Embedded Jopr > Issue Type: Bug > Affects Versions: 1.0 > Reporter: Charles Crouch > Assignee: Charles Crouch > Fix For: 1.1 > > > NavigationAction line 104 instead of > url.append(request.getServerPort() == 80 ? null : ":" + request.getServerPort()); > needs to be > url.append(request.getServerPort() == 80 ? "" : ":" + request.getServerPort()); -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (EMBJOPR-29) creating a new datasource results in an error when admin-console.war is deployed to JBoss AS 5 trunk

by Farah Juma (JIRA)

creating a new datasource results in an error when admin-console.war is deployed to JBoss AS 5 trunk ---------------------------------------------------------------------------------------------------- Key: EMBJOPR-29 URL: https://jira.jboss.org/jira/browse/EMBJOPR-29 Project: Embedded Jopr Issue Type: Bug Components: Web App/Integration Environment: JBoss AS 5 trunk r80657, embjopr r34 Reporter: Farah Juma Steps to reproduce: Under "Datasource", go to "Local Transaction", then "Add a new resource", and then select a resource template. An error will occur after clicking "Continue". The error message is shown in the attached console output. -- 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

15 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (EMBJOPR-28) if the call to redeploy() during an EAR/WAR update fails, the EAR/WAR will not be discovered by the subsequent runtime scan, and the Resource will disappear from inventory

by Ian Springer (JIRA)

if the call to redeploy() during an EAR/WAR update fails, the EAR/WAR will not be discovered by the subsequent runtime scan, and the Resource will disappear from inventory --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: EMBJOPR-28 URL: https://jira.jboss.org/jira/browse/EMBJOPR-28 Project: Embedded Jopr Issue Type: Bug Components: Plugin Affects Versions: 1.0 Reporter: Ian Springer I think the most robust thing to do would be: 1) Backup the original war to filename.war.rej first thing using File.rename() 2) Then write the new file and call deploy(). 3) If deploy() fails, rename the rej file back to the original name and then call deploy() once again. This 2nd call to deploy() should always succeed, but if it fails, inform the user that in addition to the update failing, rollback to the original war failed. -- 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

15 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (EMBJOPR-27) when adding a WAR or EAR via the admin console, and the WAR or EAR fails to deploy, the console still reports that the Resource was added successfully

by Ian Springer (JIRA)

when adding a WAR or EAR via the admin console, and the WAR or EAR fails to deploy, the console still reports that the Resource was added successfully ------------------------------------------------------------------------------------------------------------------------------------------------------ Key: EMBJOPR-27 URL: https://jira.jboss.org/jira/browse/EMBJOPR-27 Project: Embedded Jopr Issue Type: Bug Components: Plugin, Web App/Integration Affects Versions: 1.0 Reporter: Ian Springer Assignee: Ian Springer Fix For: 1.1 I think to make this work, we'll have to call MainDeployer.deploy() on the WAR or EAR after copying the file into the deploy dir. If an exception occurs during deployment, we can then catch it and return a FAILURE status for the create request. -- 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

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (EMBJOPR-25) discovery fails with ClassNotFoundExceptions when admin-console.war is deployed to a Jopr Server JBossAS instance

by Ian Springer (JIRA)

discovery fails with ClassNotFoundExceptions when admin-console.war is deployed to a Jopr Server JBossAS instance ----------------------------------------------------------------------------------------------------------------- Key: EMBJOPR-25 URL: https://jira.jboss.org/jira/browse/EMBJOPR-25 Project: Embedded Jopr Issue Type: Bug Components: Web App/Integration Affects Versions: 1.0 Reporter: Ian Springer Priority: Minor It's probably picking up RHQ classes from rhq.ear via the UCL. Here's an example of one of the errors: 16:37:02,716 INFO [RuntimeDiscoveryExecutor] Running runtime discovery scan rooted at platform... 16:37:03,170 ERROR [RuntimeDiscoveryExecutor] Error running runtime report org.rhq.core.clientapi.agent.PluginContainerException: Could not build component for Resource [Resource[id=-39, type=Con nector, key=jboss.web:address=0.0.0.0,port=7443,type=Connector, name=Tomcat Connector (7443)]] at org.rhq.core.pc.inventory.InventoryManager.activateResource(InventoryManager.java:954) at org.rhq.core.pc.inventory.InventoryManager.mergeResourceFromDiscovery(InventoryManager.java:878) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.discoverForResource(RuntimeDiscoveryExecutor.java:225) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.discoverForResource(RuntimeDiscoveryExecutor.java:234) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.runtimeDiscover(RuntimeDiscoveryExecutor.java:136) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:97) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:54) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.j ava:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207 ) 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) Caused by: java.lang.NoClassDefFoundError: org/rhq/core/pluginapi/measurement/MeasurementFacet at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$000(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at org.jboss.mx.loading.RepositoryClassLoader.findClassLocally(RepositoryClassLoader.java:675) at org.jboss.mx.loading.RepositoryClassLoader.findClass(RepositoryClassLoader.java:655) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.jboss.mx.loading.RepositoryClassLoader.loadClassLocally(RepositoryClassLoader.java:193) at org.jboss.mx.loading.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:131) at org.jboss.mx.loading.LoadMgr3.nextTask(LoadMgr3.java:399) at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:520) at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:408) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$000(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at org.jboss.mx.loading.RepositoryClassLoader.findClassLocally(RepositoryClassLoader.java:675) at org.jboss.mx.loading.RepositoryClassLoader.findClass(RepositoryClassLoader.java:655) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.jboss.mx.loading.RepositoryClassLoader.loadClassLocally(RepositoryClassLoader.java:193) at org.jboss.mx.loading.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:131) at org.jboss.mx.loading.LoadMgr3.nextTask(LoadMgr3.java:399) at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:520) at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:408) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at org.rhq.core.pc.plugin.PluginComponentFactory.instantiateClass(PluginComponentFactory.java:128) at org.rhq.core.pc.plugin.PluginComponentFactory.buildResourceComponent(PluginComponentFactory.java:104) at org.rhq.core.pc.inventory.InventoryManager.activateResource(InventoryManager.java:951) ... 13 more Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: org.rhq.core.pluginapi.measurement.MeasurementFa cet at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212) at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:514) at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:408) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) ... 57 more -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (EMBJOPR-24) provide support for viewing update history on Content tab

by Ian Springer (JIRA)

provide support for viewing update history on Content tab --------------------------------------------------------- Key: EMBJOPR-24 URL: https://jira.jboss.org/jira/browse/EMBJOPR-24 Project: Embedded Jopr Issue Type: Feature Request Components: Web App/Integration Affects Versions: 1.0 Reporter: Ian Springer Priority: Minor We could optionally add an Update History section below the above that would look something like this: ----------------------------------------------------------------------------------------------------- Update History Update Time File Size Status User =============================================================== Fri, Oct 31, 4:19pm EST 10397000 bytes Success admin Fri, Oct 31, 10:37am EST 11245692 bytes Failure admin ----------------------------------------------------------------------------------------------------- I really don't see this providing too much value. It wouldn't allow you to revert to the previous versions or even download them, and it is lost when the app server is stopped. However, I'm creating this JIRA to record the idea in case it comes up again in the future. -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (EMBJOPR-23) add support for downloading a WAR or EAR file via the corresponding Resource's Content tab

by Ian Springer (JIRA)

add support for downloading a WAR or EAR file via the corresponding Resource's Content tab ------------------------------------------------------------------------------------------ Key: EMBJOPR-23 URL: https://jira.jboss.org/jira/browse/EMBJOPR-23 Project: Embedded Jopr Issue Type: Feature Request Components: Web App/Integration Affects Versions: 1.0 Reporter: Ian Springer This would be a download link on the Content tab that would link to servlet, which would be dedicated to serving up content files. -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (EMBJOPR-22) add support for updating an existing WAR or EAR file

by Ian Springer (JIRA)

add support for updating an existing WAR or EAR file ---------------------------------------------------- Key: EMBJOPR-22 URL: https://jira.jboss.org/jira/browse/EMBJOPR-22 Project: Embedded Jopr Issue Type: Sub-task Components: Core Infrastructure, Web App/Integration Affects Versions: 1.0 Reporter: Ian Springer Assignee: Ian Springer Fix For: 1.1 -- 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

15 years, 5 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

embjopr-issues November 2008