March 2009 - embjopr-issues - Jboss List Archives

[JBoss JIRA] Created: (EMBJOPR-95) Exploded application summary shows "Exploded?: no"

by Ondrej Žižka (JIRA)

Exploded application summary shows "Exploded?: no" --------------------------------------------------- Key: EMBJOPR-95 URL: https://jira.jboss.org/jira/browse/EMBJOPR-95 Project: Embedded Jopr Issue Type: Bug Reporter: Ondrej Žižka Exploded application summary shows "Exploded?: no". See Summary tab for e.g. jmx-remoting.sar . -- 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, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (EMBJOPR-102) Decide whether to continuing have Availability thread running in Embedded

by Charles Crouch (JIRA)

Decide whether to continuing have Availability thread running in Embedded ------------------------------------------------------------------------- Key: EMBJOPR-102 URL: https://jira.jboss.org/jira/browse/EMBJOPR-102 Project: Embedded Jopr Issue Type: Task Reporter: Charles Crouch Fix For: 1.2 Right now we have a thread running an Availability scan once a minute e.g. 2009-03-18 08:42:04,921 DEBUG [org.rhq.core.pc.inventory.AvailabilityExecutor] (InventoryManager.availability-1) Running Availability Scan... I'm wondering if it would be more prudent to have the console kickoff an availability scan at most once a minute based on usage of the console itself (i.e. use the same pattern we do for triggering service scans, i.e. on each request check if 60seconds has passed since the last run) -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Updated: (EMBJOPR-41) Add support for JVM monitoring to the JBAS5 console profile

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/EMBJOPR-41?page=com.atlassian.jira.plu... ] Charles Crouch updated EMBJOPR-41: ---------------------------------- Fix Version/s: (was: 1.2) This has been pushed from the 1.2 release > Add support for JVM monitoring to the JBAS5 console profile > ----------------------------------------------------------- > > Key: EMBJOPR-41 > URL: https://jira.jboss.org/jira/browse/EMBJOPR-41 > Project: Embedded Jopr > Issue Type: Task > Affects Versions: 1.1 > Reporter: Charles Crouch > Assignee: Charles Crouch > > Right now we don't even ship the jmx-plugin with the JBAS5 profile -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (EMBJOPR-67) AS5 plugin: Invoking the "Flush" operation for a datasource results in a "plugin error"

by Farah Juma (JIRA)

AS5 plugin: Invoking the "Flush" operation for a datasource results in a "plugin error" --------------------------------------------------------------------------------------- Key: EMBJOPR-67 URL: https://jira.jboss.org/jira/browse/EMBJOPR-67 Project: Embedded Jopr Issue Type: Bug Components: Plugin Environment: JBoss AS Branch_5_x r83787, embjopr r127 Reporter: Farah Juma When the console is deployed to JBoss AS Branch_5_x, the following error message appears in the console output after invoking the "Flush" operation for a datasource (eg. DefaultDS): ERROR [OperationInvocation] Plugin error: Operation [flush] is defined as returning no results, but it returned non-null results: Configuration[id=0] In the "Previous Operations" table, the status of the "Flush" operation is "Successful". -- 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, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (EMBJOPR-88) JBA5 plugin: Stop reloading entire profile when getting availability of each resource

by Charles Crouch (JIRA)

JBA5 plugin: Stop reloading entire profile when getting availability of each resource ------------------------------------------------------------------------------------- Key: EMBJOPR-88 URL: https://jira.jboss.org/jira/browse/EMBJOPR-88 Project: Embedded Jopr Issue Type: Bug Components: Plugin Reporter: Charles Crouch Priority: Critical Fix For: 1.2 This issue arose from JBAS-6546. Basically our availability checks against JBAS5 resources are timing out after the 5sec limit, because we are calling into load the profile each time (look at the stack traces in JBAS-6546) we need to either cache the profile for some period of time or just request the info we need from the app server -- 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, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (EMBJOPR-69) AS5 plugin: Connection properties no longer get displayed when creating a new datasource

by Farah Juma (JIRA)

AS5 plugin: Connection properties no longer get displayed when creating a new datasource ---------------------------------------------------------------------------------------- Key: EMBJOPR-69 URL: https://jira.jboss.org/jira/browse/EMBJOPR-69 Project: Embedded Jopr Issue Type: Bug Components: Web App/Integration Environment: JBoss AS Branch_5_x r83903, embjopr r137 Reporter: Farah Juma Steps to reproduce when the console is deployed to JBoss AS Branch_5_x: Try to create a new datasource. After selecting a template, none of the connection properties (eg. JNDI name, minimum pool size, maximum pool size, etc.) get displayed. Only "Save" and "Cancel" buttons are displayed, as seen in the attached screenshot. This issue is similar to RHQ-1471. -- 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, 9 months

3
9
0 / 0

[JBoss JIRA] Created: (EMBJOPR-78) More page size options, and make default page size larger (20)

by Ondrej Žižka (JIRA)

More page size options, and make default page size larger (20) -------------------------------------------------------------- Key: EMBJOPR-78 URL: https://jira.jboss.org/jira/browse/EMBJOPR-78 Project: Embedded Jopr Issue Type: Feature Request Affects Versions: 1.1 Reporter: Ondrej Žižka In the nav tree, click e.g. on Applications. Current page size options: 5, 10, 20. More usable would be: 25, 50, 100. And the default of 5 can be good perhaps for pagination testing, but not user-friendly - let's make it 50. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Updated: (EMBJOPR-2) Parent Jira: Add Content to Embedded Console

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/EMBJOPR-2?page=com.atlassian.jira.plug... ] Charles Crouch updated EMBJOPR-2: --------------------------------- Fix Version/s: 1.2 (was: 1.1) Moving to 1.2 where the remainder of this will work will be done. > Parent Jira: Add Content to Embedded Console > -------------------------------------------- > > Key: EMBJOPR-2 > URL: https://jira.jboss.org/jira/browse/EMBJOPR-2 > Project: Embedded Jopr > Issue Type: Feature Request > Components: Web App/Integration > Affects Versions: 1.0 > Reporter: Mark Spritzler > Assignee: Ian Springer > Fix For: 1.2 > > > Parent Jira for all Jiras related to adding Content to the Embedded Console -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (EMBJOPR-51) JBAS4 console: Test script execution from embedded

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/EMBJOPR-51?page=com.atlassian.jira.plu... ] Charles Crouch updated EMBJOPR-51: ---------------------------------- Summary: JBAS4 console: Test script execution from embedded (was: Test script execution from embedded) This issue was targeting the JBAS4 console > JBAS4 console: Test script execution from embedded > -------------------------------------------------- > > Key: EMBJOPR-51 > URL: https://jira.jboss.org/jira/browse/EMBJOPR-51 > Project: Embedded Jopr > Issue Type: Task > Reporter: Charles Crouch > Assignee: Ian Springer > Fix For: 1.1 > > > Lots of the scripts discovered in /bin don't make any sense for embedded (they don't make much sense for JON either), but we should see if the ones that do make sense actually work, e.g. shutdown, twiddle -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (EMBJOPR-34) Customize exceptions instead of exposing JSF internal messages

by Shelly McGowan (JIRA)

Customize exceptions instead of exposing JSF internal messages -------------------------------------------------------------- Key: EMBJOPR-34 URL: https://jira.jboss.org/jira/browse/EMBJOPR-34 Project: Embedded Jopr Issue Type: Bug Components: Plugin Reporter: Shelly McGowan Fix For: 1.1 When an error is encountered during a requested action using the Embedded Console, the internal JSF Error messages are displayed instead of providing to the admin a message indicating the result of the operation and the way to remedy. For example, from the application menu, an attempt to delete the destinations-service.xml results the following Internal Error. The error is accurate that you are not allowed to delete destinations-service.xml but it is not intuitive from this trace. Internal Error: javax.el.ELException: java.lang.RuntimeException: org.rhq.core.clientapi.agent.PluginContainerException: Component does not support the [org.rhq.core.pluginapi.inventory.DeleteResourceFacet] interface: ResourceContainer: resource=[Resource[id=-19, type=JBoss Service (SAR), key=vfsfile:/NotBackedUp/smcgowan/TRUNK/trunk/build/output/jboss-5.0.0.GA/server/default/deploy/messaging/destinations-service.xml, name=destinations-service.xml, version=?]] at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:333) at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:274) at org.jboss.el.parser.AstMethodSuffix.getValue(AstMethodSuffix.java:59) at org.jboss.el.parser.AstMethodSuffix.invoke(AstMethodSuffix.java:65) at org.jboss.el.parser.AstValue.invoke(AstValue.java:96) at org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at org.jboss.seam.core.Expressions$2.invoke(Expressions.java:173) at org.jboss.seam.navigation.Pages.callAction(Pages.java:643) at org.jboss.seam.navigation.Pages.preRender(Pages.java:296) at org.jboss.seam.jsf.SeamPhaseListener.preRenderPage(SeamPhaseListener.java:560) at org.jboss.seam.jsf.SeamPhaseListener.beforeRenderResponse(SeamPhaseListener.java:471) at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:144) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:114) at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:214) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:96) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:93) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) -- 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, 9 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

embjopr-issues March 2009