March 2009 - embjopr-issues - Jboss List Archives

[JBoss JIRA] Created: (EMBJOPR-39) AS5 plugin: After successfully deleting a datasource, this datasource still shows up in the left nav and in the table of datasources

by Farah Juma (JIRA)

AS5 plugin: After successfully deleting a datasource, this datasource still shows up in the left nav and in the table of datasources ------------------------------------------------------------------------------------------------------------------------------------ Key: EMBJOPR-39 URL: https://jira.jboss.org/jira/browse/EMBJOPR-39 Project: Embedded Jopr Issue Type: Bug Components: Web App/Integration Environment: JBoss AS 5 trunk r81039, embjopr r48 Reporter: Farah Juma Steps to reproduce when admin-console.war is deployed to JBoss AS 5 trunk: Under Datasource, go to Local Transaction, delete a datasource. The left nav and the table of datasources are not updated to reflect this change, as seen in the attached screenshot. Refreshing the browser did not resolve it and logging out of the console and then logging back in did not resolve it. However, restarting the server did resolve this. -- 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
7
0 / 0

[JBoss JIRA] Created: (EMBJOPR-93) AS5 plugin: The value of "Connections In Use Count" that gets displayed in the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed

by Farah Juma (JIRA)

AS5 plugin: The value of "Connections In Use Count" that gets displayed in the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: EMBJOPR-93 URL: https://jira.jboss.org/jira/browse/EMBJOPR-93 Project: Embedded Jopr Issue Type: Bug Components: Web App/Integration Environment: JBoss Branch_5_x r85739, embjopr r209 Reporter: Farah Juma Fix For: 1.2 Steps to reproduce: Create a new -ds.xml file. Set values for min-pool-size and max-pool-size. Request multiple connections from the connection pool. Then, close a few of these connections. Perform the "List Formatted Sub Pool Statistics" operation for this datasource. The value of "Connections In Use Count" in the result of the operation is not updated to reflect the closed connections. For example, when min-pool-size=5, max-pool-size=20, and there are 10 connections in use, the following is the result of the "List Formatted Sub Pool Statistics" operation after closing 2 connections: Sub Pool Statistics: Sub Pool Count: 1 ------------------------------------------------------ Track By Transaction: true Available Connections Count: 12 Max Connections In Use Count:10 Connections Destroyed Count:0 **Connections In Use Count:10** Total Block Time:0 Average Block Time For Sub Pool:0 Maximum Wait Time For Sub Pool:0 Total Timed Out:0 The value of "Connections In Use Count" should be 8 in this case. -- 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-90) AS5 plugin: An empty "Metrics Summary" table is displayed on the "Summary" page for queues and topics

by Farah Juma (JIRA)

AS5 plugin: An empty "Metrics Summary" table is displayed on the "Summary" page for queues and topics ----------------------------------------------------------------------------------------------------- Key: EMBJOPR-90 URL: https://jira.jboss.org/jira/browse/EMBJOPR-90 Project: Embedded Jopr Issue Type: Bug Components: Web App/Integration Environment: JBoss AS Branch_5_x r85646, embjopr r193 Reporter: Farah Juma Attachments: QueueSummaryPage.png Steps to reproduce when the console is deployed to JBAS5: Navigate to the "Summary" page for a queue or topic (eg. /queue/DLQ). As shown in the attached screenshot, a "Metrics Summary" table is displayed but there are no values in the table. When the console is deployed to JBAS4, the "Metrics Summary" table for both queues and topics is non-empty. -- 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] Created: (EMBJOPR-91) Applications can be DELETED without confirmation from Applications Summary Tab

by Shelly McGowan (JIRA)

Applications can be DELETED without confirmation from Applications Summary Tab ------------------------------------------------------------------------------ Key: EMBJOPR-91 URL: https://jira.jboss.org/jira/browse/EMBJOPR-91 Project: Embedded Jopr Issue Type: Bug Reporter: Shelly McGowan Fix For: 1.2 DELETE actions are available from the Applications Summary Tab or specifically on the Application Type Summary Tab where Type is Enterprise Application (EAR), Web Applcation (WAR), or JBoss Service (SAR). When the applications are deleted from the Application Type Summary Tab a confirmation dialog pops up: Are you sure you want to Delete this Resource? This confirmation does not happen when deleting the resource from the Applications Summary Tab. Confirmation of a DELETE operation should be required as well as consistent behavior cross pages. -- 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-84) Configuration tab for a deployed Enterprise Archive in Incomplete

by Shelly McGowan (JIRA)

Configuration tab for a deployed Enterprise Archive in Incomplete ----------------------------------------------------------------- Key: EMBJOPR-84 URL: https://jira.jboss.org/jira/browse/EMBJOPR-84 Project: Embedded Jopr Issue Type: Bug Reporter: Shelly McGowan Fix For: 1.2 Once an .ear is deployed (and due to EMBJOPR-80, server restarted), navigating to the Configuration Tab of the enterprise application does not provide any configuration options to the user. All that is provided is: EDIT RESOURCE SAVE CANCEL SAVE returns messsage to client: Successfully updated Enterprise Application (EAR) 'earname.ear'. CANCEL returns to EAR Summary Tab. With EAP 4.3, the Configuration Tab is greyed out for EARs. -- 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
2
0 / 0

[JBoss JIRA] Created: (EMBJOPR-75) WAR deployed, listed in summary, but bad link and not listed in tree

by Ondrej Žižka (JIRA)

WAR deployed, listed in summary, but bad link and not listed in tree -------------------------------------------------------------------- Key: EMBJOPR-75 URL: https://jira.jboss.org/jira/browse/EMBJOPR-75 Project: Embedded Jopr Issue Type: Bug Environment: JBoss AS 5.x, EmbJopr 1.1.1-SNAPSHOT Reporter: Ondrej Žižka When WAR is deployed, it is not listed in the navigation tree. In the web apps Summary tab it is listed, but the link causes the root node summary to be shown. -- 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
5
0 / 0

[JBoss JIRA] Created: (EMBJOPR-80) Attempting to view deployed .ear shows Summary for root node instead

by Shelly McGowan (JIRA)

Attempting to view deployed .ear shows Summary for root node instead -------------------------------------------------------------------- Key: EMBJOPR-80 URL: https://jira.jboss.org/jira/browse/EMBJOPR-80 Project: Embedded Jopr Issue Type: Bug Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 1.2 Deploy an enterprise archive. Resource ".ear" was successfully created status is returned to the client view. Clicking on the .ear name displays summary information for localhost.localdomain. I've attached screen shots to this JIRA to show the sequence. Assigning to myself for now as there is server-side information to add. -- 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
11
0 / 0

[JBoss JIRA] Created: (EMBJOPR-71) AS5 plugin: Datasource metrics are not updated after a connection is requested from a connection pool

by Farah Juma (JIRA)

AS5 plugin: Datasource metrics are not updated after a connection is requested from a connection pool ----------------------------------------------------------------------------------------------------- Key: EMBJOPR-71 URL: https://jira.jboss.org/jira/browse/EMBJOPR-71 Project: Embedded Jopr Issue Type: Bug Components: Web App/Integration Environment: JBoss AS Branch_5_x r83903, embjopr r138 Reporter: Farah Juma Steps to reproduce when the console is deployed to JBoss AS Branch_5_x: Create a new -ds.xml file. Set values for min-pool-size and max-pool-size. After a connection is requested from the connection pool, check the metric values. These values are not updated. These values also remain unchanged after refreshing the page. For example, the following are the metric values that get displayed after the first request for a connection is made when the minimum pool size is 5 and the maximum pool size is 20: Available Connection Count: 20.0 Connection Count: 0.0 Connection Created Count: 0.0 Connection Destroyed Count: 0.0 In Use Connection Count: 0.0 Max Connections In Use Count: 0.0 Max Size: 20.0 Min Size: 5.0 -- 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] Created: (EMBJOPR-68) upgrade RichFaces from 3.2.2.SR1 to the same version used by Jopr/Enterprise (currently 3.3.0.GA)

by Ian Springer (JIRA)

upgrade RichFaces from 3.2.2.SR1 to the same version used by Jopr/Enterprise (currently 3.3.0.GA) ------------------------------------------------------------------------------------------------- Key: EMBJOPR-68 URL: https://jira.jboss.org/jira/browse/EMBJOPR-68 Project: Embedded Jopr Issue Type: Task Components: Core Infrastructure, Web App/Integration Affects Versions: 1.1 Reporter: Ian Springer Fix For: 1.2 -- 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] Created: (EMBJOPR-86) "Add a new resource" button doesn't work after creating a resource

by Charles Crouch (JIRA)

"Add a new resource" button doesn't work after creating a resource ------------------------------------------------------------------ Key: EMBJOPR-86 URL: https://jira.jboss.org/jira/browse/EMBJOPR-86 Project: Embedded Jopr Issue Type: Bug Reporter: Charles Crouch Fix For: 1.2 Steps to reproduce: (I've only tried this in the JBAS5 console but I would expect it is a problem in JBAS4 too) 1) Choose the Queue resource type from the nav 2) Click the "Add a new resource" button 3) Select a template, enter in the required info and you will be reposted to the list page with a success message 4) Click the "Add a new resource" button again 5) Instead of going to the Template page you get reposted to an empty list page and the following exception is output to the console 16:29:54,593 ERROR [SeamPhaseListener] swallowing exception javax.el.ELException: java.lang.IllegalStateException: begin method invoked from a long-running conversation, try using @Beg in(join=true) on method: getTemplateDropDownEntriesByResourceType 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:174) at org.jboss.seam.navigation.Pages.callAction(Pages.java:711) at org.jboss.seam.navigation.Pages.preRender(Pages.java:349) at org.jboss.seam.jsf.SeamPhaseListener.preRenderPage(SeamPhaseListener.java:562) at org.jboss.seam.jsf.SeamPhaseListener.beforeRenderResponse(SeamPhaseListener.java:473) at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:146) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:116) 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:51) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:38) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) 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:56) 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.process(SecurityContextEstablishmentValve.java:12 6) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) 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:829) 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) Caused by: java.lang.IllegalStateException: begin method invoked from a long-running conversation, try using @Begin(join=tru e) on method: getTemplateDropDownEntriesByResourceType at org.jboss.seam.core.ConversationInterceptor.aroundInvoke(ConversationInterceptor.java:47) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) at org.jboss.on.embedded.ui.configuration.resource.TemplateDropDownPopulator_$$_javassist_12.getTemplateDropDownEntr iesByResourceType(TemplateDropDownPopulator_$$_javassist_12.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:329) ... 58 more Looks like we're not properly terminating the conversation when the resource is saved. -- 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
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

embjopr-issues March 2009