From jira-events at lists.jboss.org Tue Mar 3 13:43:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Tue, 3 Mar 2009 13:43:24 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-85) Investigate
impact of deploying embedded jopr in jbas5 on start up time
Message-ID: <9509053.1236105804775.JavaMail.jira@cloud.prod.atl2.jboss.com>
Investigate impact of deploying embedded jopr in jbas5 on start up time
-----------------------------------------------------------------------
Key: EMBJOPR-85
URL: https://jira.jboss.org/jira/browse/EMBJOPR-85
Project: Embedded Jopr
Issue Type: Task
Components: Web App/Integration
Affects Versions: 1.1
Reporter: Charles Crouch
Priority: Critical
Fix For: 1.2
Things to look at:
a) reducing start up time and moving more processing to initial page request
b) how much does Seam initialization contribute
--
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
From jira-events at lists.jboss.org Tue Mar 3 16:38:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Tue, 3 Mar 2009 16:38:24 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-69) AS5 plugin:
Connection
properties no longer get displayed when creating a new datasource
In-Reply-To: <32158737.1233857326007.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19054144.1236116304657.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-69:
-------------------------------------
Assignee: Charles Crouch
> 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
> Assignee: Charles Crouch
> Priority: Blocker
> Fix For: 1.2
>
> Attachments: createDatasource.png, ListStatisticsResults.png
>
>
> 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
From jira-events at lists.jboss.org Tue Mar 3 16:42:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Tue, 3 Mar 2009 16:42:24 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-69) Connection
properties no longer get displayed when creating a new datasource
In-Reply-To: <32158737.1233857326007.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9993607.1236116544611.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-69:
----------------------------------
Summary: Connection properties no longer get displayed when creating a new datasource (was: AS5 plugin: Connection properties no longer get displayed when creating a new datasource)
r175 of embjopr/core fixes this. It was happening in jbas4 too. Just needed to update the JSF component-family attribute to the new value which RHQ is using.
> 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
> Assignee: Charles Crouch
> Priority: Blocker
> Fix For: 1.2
>
> Attachments: createDatasource.png, ListStatisticsResults.png
>
>
> 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
From jira-events at lists.jboss.org Tue Mar 3 16:51:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Tue, 3 Mar 2009 16:51:24 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-69) Connection
properties no longer get displayed when creating a new datasource
In-Reply-To: <32158737.1233857326007.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24291045.1236117084504.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch resolved EMBJOPR-69.
-----------------------------------
Resolution: Done
> 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
> Assignee: Charles Crouch
> Priority: Blocker
> Fix For: 1.2
>
> Attachments: createDatasource.png, ListStatisticsResults.png
>
>
> 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
From jira-events at lists.jboss.org Tue Mar 3 17:33:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Tue, 3 Mar 2009 17:33:24 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-86) "Add a new
resource" button doesn't work after creating a resource
Message-ID: <28227804.1236119604971.JavaMail.jira@cloud.prod.atl2.jboss.com>
"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
From jira-events at lists.jboss.org Wed Mar 4 14:55:26 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 4 Mar 2009 14:55:26 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-87) Operations
history list broken for specific pairs of operations
Message-ID: <27639330.1236196526089.JavaMail.jira@cloud.prod.atl2.jboss.com>
Operations history list broken for specific pairs of operations
---------------------------------------------------------------
Key: EMBJOPR-87
URL: https://jira.jboss.org/jira/browse/EMBJOPR-87
Project: Embedded Jopr
Issue Type: Bug
Components: Web App/Integration
Reporter: Charles Crouch
Fix For: 1.2
Steps to reproduce
1) Pick a Datasource resource, e.g. DefaultDS
2) Execute the "List Formatted Sub Pool Statistics" operation, taking the defaults
3) Try to execute the "List Statistics" operation, and you will get the following:
After this even going to the Control tab on this resource will throw the exception below.
javax.faces.FacesException: javax.el.PropertyNotFoundException: Property 'map' not found on type org.rhq.core.domain.configuration.PropertySimple
at javax.faces.component.UIOutput.getValue(UIOutput.java:187)
at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getValue(HtmlBasicInputRenderer.java:201)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getCurrentValue(HtmlBasicRenderer.java:284)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeEnd(HtmlBasicRenderer.java:154)
at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:242)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:239)
at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
at com.sun.faces.renderkit.html_basic.GridRenderer.renderRow(GridRenderer.java:180)
at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:127)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:239)
at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
at org.richfaces.renderkit.html.TogglePanelRenderer.handleFacets(TogglePanelRenderer.java:120)
at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:124)
at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:132)
at org.ajax4jsf.renderkit.RendererBase.encodeEnd(RendererBase.java:135)
at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:286)
at org.ajax4jsf.renderkit.RendererBase.renderChildren(RendererBase.java:262)
at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:284)
at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
at org.richfaces.renderkit.html.ColgroupRenderer.encodeChildren(ColgroupRenderer.java:98)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
at org.richfaces.renderkit.AbstractTableRenderer.encodeOneRow(AbstractTableRenderer.java:361)
at org.richfaces.renderkit.AbstractRowsRenderer.process(AbstractRowsRenderer.java:86)
at org.ajax4jsf.model.SequenceDataModel.walk(SequenceDataModel.java:101)
at org.ajax4jsf.component.UIDataAdaptor.walk(UIDataAdaptor.java:1151)
at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:106)
at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:91)
at org.richfaces.renderkit.AbstractTableRenderer.encodeTBody(AbstractTableRenderer.java:73)
at org.richfaces.renderkit.AbstractTableRenderer.encodeChildren(AbstractTableRenderer.java:80)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
at javax.faces.render.Renderer.encodeChildren(Renderer.java:148)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933)
at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592)
at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
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:126)
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: javax.el.PropertyNotFoundException: Property 'map' not found on type org.rhq.core.domain.configuration.PropertySimple
at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193)
at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170)
at javax.el.BeanELResolver.property(BeanELResolver.java:279)
at javax.el.BeanELResolver.getValue(BeanELResolver.java:60)
at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54)
at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72)
at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53)
at org.jboss.el.parser.AstValue.getValue(AstValue.java:67)
at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
at javax.faces.component.UIOutput.getValue(UIOutput.java:184)
... 105 more
If you swap steps 2) and 3)...
2) Execute the "List Statistics"operation
3) Try to execute the "List Formatted Sub Pool Statistics" operation, when you hit the OK button on the arguments page you will get the following:
After this even going to the Control tab on this resource will throw the exception below:
javax.faces.FacesException: javax.el.PropertyNotFoundException: Property 'stringValue' not found on type org.rhq.core.domain.configuration.PropertyMap
at javax.faces.component.UIOutput.getValue(UIOutput.java:187)
at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getValue(HtmlBasicInputRenderer.java:201)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getCurrentValue(HtmlBasicRenderer.java:284)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeEnd(HtmlBasicRenderer.java:154)
at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:242)
at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:239)
at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
at org.richfaces.renderkit.html.TogglePanelRenderer.handleFacets(TogglePanelRenderer.java:120)
at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:124)
at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:132)
at org.ajax4jsf.renderkit.RendererBase.encodeEnd(RendererBase.java:135)
at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:286)
at org.ajax4jsf.renderkit.RendererBase.renderChildren(RendererBase.java:262)
at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:284)
at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
at org.richfaces.renderkit.html.ColgroupRenderer.encodeChildren(ColgroupRenderer.java:98)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
at org.richfaces.renderkit.AbstractTableRenderer.encodeOneRow(AbstractTableRenderer.java:361)
at org.richfaces.renderkit.AbstractRowsRenderer.process(AbstractRowsRenderer.java:86)
at org.ajax4jsf.model.SequenceDataModel.walk(SequenceDataModel.java:101)
at org.ajax4jsf.component.UIDataAdaptor.walk(UIDataAdaptor.java:1151)
at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:106)
at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:91)
at org.richfaces.renderkit.AbstractTableRenderer.encodeTBody(AbstractTableRenderer.java:73)
at org.richfaces.renderkit.AbstractTableRenderer.encodeChildren(AbstractTableRenderer.java:80)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
at javax.faces.render.Renderer.encodeChildren(Renderer.java:148)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933)
at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592)
at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
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:126)
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: javax.el.PropertyNotFoundException: Property 'stringValue' not found on type org.rhq.core.domain.configuration.PropertyMap
at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193)
at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170)
at javax.el.BeanELResolver.property(BeanELResolver.java:279)
at javax.el.BeanELResolver.getValue(BeanELResolver.java:60)
at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54)
at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72)
at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53)
at org.jboss.el.parser.AstValue.getValue(AstValue.java:67)
at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
at javax.faces.component.UIOutput.getValue(UIOutput.java:184)
... 97 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
From jira-events at lists.jboss.org Wed Mar 4 15:54:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 4 Mar 2009 15:54:25 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-62)
NavigationAction Seam component
being recreated whenever an Event it is listening for is raised from
EmbeddedInventoryEventListener
In-Reply-To: <19238391.1229730057000.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25958701.1236200065274.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-62:
----------------------------------
Priority: Critical (was: Major)
> NavigationAction Seam component being recreated whenever an Event it is listening for is raised from EmbeddedInventoryEventListener
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-62
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-62
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Affects Versions: 1.1
> Environment: jbas4 console in jbas 4.2.2
> Reporter: Charles Crouch
> Priority: Critical
> Fix For: 1.2
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Found this while investigating why NavigationAction.updateNavWithDeletedResource could never find the resource in the navigation that it was trying to remove. It turns out that before the event is received NavigationAction is recreated so its rootNode member variable holding the navigation is recreated. The existing inventory is used to recreate the nav, which obviously doesn't include the deleted resource, so when updateNavWithDeletedResource looks in this new nav it doesn't find the resource.
> Not sure if this is our bug or a bug in Seam. The following log snippet shows the resource being removed, then the event dispatched, then the navigationAction component being re-intialized.
> I saw this same reinit happen when resources were created too, so its not delete specific. The easiest way to reproduce is to add a breakpoint to
> NavigationAction.createJONTreeNode() and then either remove or add resources to the filesystem and trigger a rediscovery by clicking around the UI.
> 2008-12-19 16:25:12,421 INFO [org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor] (InventoryManager.discovery-1) Removing stale Resource[id=-76, type=Script, key=C:\usr\apps\jboss\jboss-4.2.2.GA\bin\wsconsume.bat, name=wsconsume.bat]...
> 2008-12-19 16:25:12,421 DEBUG [org.rhq.core.pc.inventory.InventoryManager] (InventoryManager.discovery-1) Removing Resource[id=-76, type=Script, key=C:\usr\apps\jboss\jboss-4.2.2.GA\bin\wsconsume.bat, name=wsconsume.bat] from local inventory...
> 2008-12-19 16:25:12,421 DEBUG [org.rhq.core.pc.inventory.InventoryManager] (InventoryManager.discovery-1) Successfully deactivated resource with id [-76].
> 2008-12-19 16:25:12,421 DEBUG [org.rhq.core.pc.inventory.InventoryManager] (InventoryManager.discovery-1) Set component state to STOPPED for resource with id [-76].
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.on.embedded.LoggingInventoryEventListener] (InventoryManager.discovery-1) The following resources have been removed
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.on.embedded.LoggingInventoryEventListener] (InventoryManager.discovery-1) Resource[-76]: wsconsume.bat
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.contexts.Lifecycle] (InventoryManager.discovery-1) >>> Begin call
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) instantiating Seam component: org.jboss.seam.core.events
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.core.events
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) initializing new instance of: org.jboss.seam.core.events
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) done initializing: org.jboss.seam.core.events
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postCreate.org.jboss.seam.core.events
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.inventoryEventListener
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.inventoryEventListener
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.this
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.this
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.method
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.method
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.parameters
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.parameters
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.component
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.component
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:resourceDeleted
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) instantiating Seam component: navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) initializing new instance of: navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) done initializing: navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postCreate.navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.this
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.this
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.method
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.method
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.parameters
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.parameters
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.component
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.component
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) trying to inject from specified context: navTree, scope: SESSION
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) trying to inject with hierarchical context search: rootNode
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.contexts.Contexts] (InventoryManager.discovery-1) found in method context: navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:navTreeInitialized
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.contexts.Contexts] (InventoryManager.discovery-1) found in application context: inventoryEventListener
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.inventoryEventListener
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.inventoryEventListener
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.this
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.this
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.method
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.method
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.parameters
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.parameters
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.component
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.component
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.rootNode
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.rootNode
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) instantiating Seam component: org.jboss.seam.web.parameters
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) initializing new instance of: org.jboss.seam.web.parameters
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) done initializing: org.jboss.seam.web.parameters
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) instantiating Seam component: org.jboss.seam.web.servletContexts
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.web.servletContexts
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.web.servletContexts
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) initializing new instance of: org.jboss.seam.web.servletContexts
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) done initializing: org.jboss.seam.web.servletContexts
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postCreate.org.jboss.seam.web.servletContexts
> 2008-12-19 16:25:12,437 INFO [org.jboss.on.embedded.ui.NavigationAction] (InventoryManager.discovery-1) Resource [Resource[id=-76, type=Script, key=C:\usr\apps\jboss\jboss-4.2.2.GA\bin\wsconsume.bat, name=wsconsume.bat]] deleted.
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
--
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
From jira-events at lists.jboss.org Wed Mar 4 15:56:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 4 Mar 2009 15:56:25 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Closed: (EMBJOPR-66) AS5 plugin:
Invoking the "List
Statistics" operation for a datasource after invoking the "List Formatted
Sub Pool Statistics" operation results in a "PropertyNotFoundException"
In-Reply-To: <14285297.1233674866027.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16280388.1236200185127.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch closed EMBJOPR-66.
---------------------------------
Resolution: Duplicate Issue
There is a bit more information in EMBJOPR-87, so closing this one.
> AS5 plugin: Invoking the "List Statistics" operation for a datasource after invoking the "List Formatted Sub Pool Statistics" operation results in a "PropertyNotFoundException"
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-66
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-66
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS Branch_5_x r83787, embjopr r127
> Reporter: Farah Juma
> Fix For: 1.2
>
>
> Steps to reproduce when the console is deployed to JBoss AS Branch_5_x:
> Invoke the "List Formatted Sub Pool Statistics" operation for a datasource (eg. DefaultDS) and then, invoke the "List Statistics" operation. The following error occurs:
> "An Error Occurred:
> javax.el.PropertyNotFoundException: Property 'map' not found on type org.rhq.core.domain.configuration.PropertySimple"
> The following error message appears in the console output:
> 16:33:00,847 ERROR [viewhandler] Error Rendering View[/secure/resourceInstanceOperation.xhtml]
> javax.faces.FacesException: javax.el.PropertyNotFoundException: Property 'map' not found on type org.rhq.core.domain.configuration.PropertySimple
> at javax.faces.component.UIOutput.getValue(UIOutput.java:187)
> at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getValue(HtmlBasicInputRenderer.java:201)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getCurrentValue(HtmlBasicRenderer.java:284)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeEnd(HtmlBasicRenderer.java:154)
> at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:242)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GridRenderer.renderRow(GridRenderer.java:180)
> at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:127)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:239)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
> at org.richfaces.renderkit.html.TogglePanelRenderer.handleFacets(TogglePanelRenderer.java:120)
> at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:124)
> at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:132)
> at org.ajax4jsf.renderkit.RendererBase.encodeEnd(RendererBase.java:135)
> at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:286)
> at org.ajax4jsf.renderkit.RendererBase.renderChildren(RendererBase.java:262)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:284)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
> at org.richfaces.renderkit.html.ColgroupRenderer.encodeChildren(ColgroupRenderer.java:98)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeOneRow(AbstractTableRenderer.java:361)
> at org.richfaces.renderkit.AbstractRowsRenderer.process(AbstractRowsRenderer.java:86)
> at org.ajax4jsf.model.SequenceDataModel.walk(SequenceDataModel.java:101)
> at org.ajax4jsf.component.UIDataAdaptor.walk(UIDataAdaptor.java:1151)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:106)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:91)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeTBody(AbstractTableRenderer.java:73)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeChildren(AbstractTableRenderer.java:80)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
> at javax.faces.render.Renderer.encodeChildren(Renderer.java:148)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933)
> at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592)
> at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
> at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196)
> at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
> 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:126)
> 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: javax.el.PropertyNotFoundException: Property 'map' not found on type org.rhq.core.domain.configuration.PropertySimple
> at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193)
> at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170)
> at javax.el.BeanELResolver.property(BeanELResolver.java:279)
> at javax.el.BeanELResolver.getValue(BeanELResolver.java:60)
> at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54)
> at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72)
> at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53)
> at org.jboss.el.parser.AstValue.getValue(AstValue.java:67)
> at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
> at javax.faces.component.UIOutput.getValue(UIOutput.java:184)
> ... 110 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
From jira-events at lists.jboss.org Wed Mar 4 16:00:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 4 Mar 2009 16:00:25 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Closed: (EMBJOPR-82) Not all
Applications are shown when navigating via pagination options
In-Reply-To: <970531.1235150567870.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4642377.1236200425348.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch closed EMBJOPR-82.
---------------------------------
Resolution: Duplicate Issue
Duplicate of EMBJOPR-61
> Not all Applications are shown when navigating via pagination options
> ---------------------------------------------------------------------
>
> Key: EMBJOPR-82
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-82
> Project: Embedded Jopr
> Issue Type: Bug
> Environment: JBoss AS Branch_5_x r84532, embjopr r162
> Reporter: Shelly McGowan
> Fix For: 1.2
>
>
> After logging in to EMBJOPR, there are a total of 31 default applications available (25 SARs, 6 WARs). From the Applications Summary Tab, the available applications are viewable using a default of 5 per page. Attempting to view the total of 31 using the pagination options is not successful.
> 1. From page 1, click 2. 5 more deployed SARs are shown. click 3. At this point the Application Summary is shown with no items in the list but shows total of 31. At this point, only 10 SARs have been displayed.
> 2. There is no prev button to return to the last viewed page.
> 3. If you go from page 1, click last it shows the web-console.war. There is a prev button but attempt to use that results in the the summary showing no applications in the list.
> Viewing SAR or WAR types individually shows the correct pagination sequence including prev.
--
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
From jira-events at lists.jboss.org Wed Mar 4 16:06:40 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 4 Mar 2009 16:06:40 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-58) AS5 plugin:
Clicking on the "Configuration" tab for a Datasource results in a
"PluginContainerException"
In-Reply-To: <19037367.1229613896768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5046113.1236200800106.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch resolved EMBJOPR-58.
-----------------------------------
Resolution: Out of Date
Not seeing this any longer, Farah please re-open if you are still getting this.
> AS5 plugin: Clicking on the "Configuration" tab for a Datasource results in a "PluginContainerException"
> --------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-58
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-58
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS 5 trunk r82369, embjopr r76
> Reporter: Farah Juma
> Priority: Critical
> Fix For: 1.2
>
>
> When the console is deployed to JBoss AS 5 trunk, the following error message gets displayed after clicking on the "Configuration" tab for any Datasource (eg. DefaultDS):
> "There was an error retrieving the configuration for this resource"
> The following error message appears in the console output:
> 09:14:13,572 ERROR [PluginContainerResourceManager] Error retrieving configuration for resource: Resource[id=-4, type=Local TX Datasource, key=DataSource:LocalTx:DefaultDS, name=DefaultDS, version=?]
> org.rhq.core.clientapi.agent.PluginContainerException: Cannot load Resource configuration for [-4]
> at org.rhq.core.pc.configuration.ConfigurationManager.loadResourceConfiguration(ConfigurationManager.java:174)
> at org.jboss.on.embedded.manager.pc.PluginContainerResourceManager.getResourceConfiguration(PluginContainerResourceManager.java:234)
> at org.jboss.on.embedded.ui.configuration.resource.ResourceConfigurationUIBean.resourceConfiguration(ResourceConfigurationUIBean.java:144)
> 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.seam.util.Reflections.invoke(Reflections.java:22)
> at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
> at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
> at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28)
> at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
> at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77)
> at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
> at org.jboss.seam.core.ConversationInterceptor.aroundInvoke(ConversationInterceptor.java:56)
> 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.ResourceConfigurationUIBean_$$_javassist_10.resourceConfiguration(ResourceConfigurationUIBean_$$_javassist_10.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)
> 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:126)
> 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: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)
> Caused by: java.lang.ClassCastException: [Warning] org.rhq.core.domain.configuration.definition.PropertyDefinitionList
> ... 85 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
From jira-events at lists.jboss.org Wed Mar 4 18:33:28 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 4 Mar 2009 18:33:28 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-55) Rebuild
content behind navigation nodes using InventoryEventListener
Message-ID: <14842329.1236209608245.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch resolved EMBJOPR-55.
-----------------------------------
Resolution: Done
Since EMBJOPR-62 is resolved this is fixed too
> Rebuild content behind navigation nodes using InventoryEventListener
> --------------------------------------------------------------------
>
> Key: EMBJOPR-55
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-55
> Project: Embedded Jopr
> Issue Type: Feature Request
> Affects Versions: 1.0, 1.1
> Reporter: Charles Crouch
> Assignee: Ian Springer
> Fix For: 1.2
>
>
> Right now we rebuild the content behind a node in the navigation using the following method on NavigationAction
> public void changeExpandListener(org.richfaces.event.NodeExpandedEvent event) {
> UIComponent comp = event.getComponent();
> UITree tree = (UITree) comp;
> JONTreeNode data = (JONTreeNode) (tree.getTreeNode().getData());
>
> data.reInitializeChildrenMap();
> }
> This isnt great because it requires the user to close/open the node inorder to have its children refreshed to match whats in the PC. This is problematic when resources are deployed/undeployed directly to the filesystem, see JBMANCON-419. An alternative would be to use an implementation of InventoryEventListener to listen to resource added events from the PC and then behind the scenes rebuild the appropriate Nodes. For this to work a bug will need to be fixed in the RuntimeDiscoveryExecutor which is causing resourceAdd events to get fired for every discovery.
--
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
From jira-events at lists.jboss.org Wed Mar 4 18:33:26 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 4 Mar 2009 18:33:26 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-62)
NavigationAction Seam component
being recreated whenever an Event it is listening for is raised from
EmbeddedInventoryEventListener
In-Reply-To: <19238391.1229730057000.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17140168.1236209606323.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch resolved EMBJOPR-62.
-----------------------------------
Resolution: Done
Fixed in embjopr r176, can now remove/add resources and the nav is updated in realtime
> NavigationAction Seam component being recreated whenever an Event it is listening for is raised from EmbeddedInventoryEventListener
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-62
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-62
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Affects Versions: 1.1
> Environment: jbas4 console in jbas 4.2.2
> Reporter: Charles Crouch
> Priority: Critical
> Fix For: 1.2
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Found this while investigating why NavigationAction.updateNavWithDeletedResource could never find the resource in the navigation that it was trying to remove. It turns out that before the event is received NavigationAction is recreated so its rootNode member variable holding the navigation is recreated. The existing inventory is used to recreate the nav, which obviously doesn't include the deleted resource, so when updateNavWithDeletedResource looks in this new nav it doesn't find the resource.
> Not sure if this is our bug or a bug in Seam. The following log snippet shows the resource being removed, then the event dispatched, then the navigationAction component being re-intialized.
> I saw this same reinit happen when resources were created too, so its not delete specific. The easiest way to reproduce is to add a breakpoint to
> NavigationAction.createJONTreeNode() and then either remove or add resources to the filesystem and trigger a rediscovery by clicking around the UI.
> 2008-12-19 16:25:12,421 INFO [org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor] (InventoryManager.discovery-1) Removing stale Resource[id=-76, type=Script, key=C:\usr\apps\jboss\jboss-4.2.2.GA\bin\wsconsume.bat, name=wsconsume.bat]...
> 2008-12-19 16:25:12,421 DEBUG [org.rhq.core.pc.inventory.InventoryManager] (InventoryManager.discovery-1) Removing Resource[id=-76, type=Script, key=C:\usr\apps\jboss\jboss-4.2.2.GA\bin\wsconsume.bat, name=wsconsume.bat] from local inventory...
> 2008-12-19 16:25:12,421 DEBUG [org.rhq.core.pc.inventory.InventoryManager] (InventoryManager.discovery-1) Successfully deactivated resource with id [-76].
> 2008-12-19 16:25:12,421 DEBUG [org.rhq.core.pc.inventory.InventoryManager] (InventoryManager.discovery-1) Set component state to STOPPED for resource with id [-76].
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.on.embedded.LoggingInventoryEventListener] (InventoryManager.discovery-1) The following resources have been removed
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.on.embedded.LoggingInventoryEventListener] (InventoryManager.discovery-1) Resource[-76]: wsconsume.bat
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.contexts.Lifecycle] (InventoryManager.discovery-1) >>> Begin call
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) instantiating Seam component: org.jboss.seam.core.events
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.core.events
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) initializing new instance of: org.jboss.seam.core.events
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) done initializing: org.jboss.seam.core.events
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postCreate.org.jboss.seam.core.events
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.inventoryEventListener
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.inventoryEventListener
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.this
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.this
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.method
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.method
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.parameters
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.parameters
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.component
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.component
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:resourceDeleted
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) instantiating Seam component: navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) initializing new instance of: navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) done initializing: navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postCreate.navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.this
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.this
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.method
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.method
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.parameters
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.parameters
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.component
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.component
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) trying to inject from specified context: navTree, scope: SESSION
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) trying to inject with hierarchical context search: rootNode
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.contexts.Contexts] (InventoryManager.discovery-1) found in method context: navigationAction
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:navTreeInitialized
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.contexts.Contexts] (InventoryManager.discovery-1) found in application context: inventoryEventListener
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.inventoryEventListener
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.inventoryEventListener
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.this
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.this
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.method
> 2008-12-19 16:25:12,421 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.method
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.parameters
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.parameters
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.component
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.component
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.rootNode
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.rootNode
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) instantiating Seam component: org.jboss.seam.web.parameters
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) initializing new instance of: org.jboss.seam.web.parameters
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) done initializing: org.jboss.seam.web.parameters
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) instantiating Seam component: org.jboss.seam.web.servletContexts
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.web.servletContexts
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.web.servletContexts
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) initializing new instance of: org.jboss.seam.web.servletContexts
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.Component] (InventoryManager.discovery-1) done initializing: org.jboss.seam.web.servletContexts
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.seam.core.Events] (InventoryManager.discovery-1) Processing event:org.jboss.seam.postCreate.org.jboss.seam.web.servletContexts
> 2008-12-19 16:25:12,437 INFO [org.jboss.on.embedded.ui.NavigationAction] (InventoryManager.discovery-1) Resource [Resource[id=-76, type=Script, key=C:\usr\apps\jboss\jboss-4.2.2.GA\bin\wsconsume.bat, name=wsconsume.bat]] deleted.
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
> 2008-12-19 16:25:12,437 DEBUG [org.jboss.on.embedded.ui.nav.BaseTreeNode] (InventoryManager.discovery-1) About to call initChildrenMap()
--
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
From jira-events at lists.jboss.org Wed Mar 4 18:35:29 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 4 Mar 2009 18:35:29 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-80) EAR:
Attempting to view deployed .ear shows Summary for root node instead
In-Reply-To: <104175.1235145590157.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25850625.1236209729684.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12455532#action_12455532 ]
Charles Crouch commented on EMBJOPR-80:
---------------------------------------
Now I've fixed EMBJOPR-62 can you retest this? It should be fixed.
> EAR: 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
> Environment: JBoss AS Branch_5_x r84532, embjopr r162
> Reporter: Shelly McGowan
> Fix For: 1.2
>
> Attachments: click-earname.png, ear-created.png, manual-nav-to-ears.png
>
>
> 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
From jira-events at lists.jboss.org Wed Mar 4 18:35:31 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 4 Mar 2009 18:35:31 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-80) EAR:
Attempting to view deployed .ear shows Summary for root node instead
In-Reply-To: <104175.1235145590157.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1540622.1236209731642.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-80:
-------------------------------------
Assignee: Shelly McGowan
> EAR: 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
> Environment: JBoss AS Branch_5_x r84532, embjopr r162
> Reporter: Shelly McGowan
> Assignee: Shelly McGowan
> Fix For: 1.2
>
> Attachments: click-earname.png, ear-created.png, manual-nav-to-ears.png
>
>
> 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
From jira-events at lists.jboss.org Wed Mar 4 18:35:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 4 Mar 2009 18:35:25 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-75) WAR deployed,
listed in summary, but bad link and not listed in tree
In-Reply-To: <4413336.1234818109606.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25313399.1236209725752.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12455531#action_12455531 ]
Charles Crouch commented on EMBJOPR-75:
---------------------------------------
Now I've fixed EMBJOPR-62 can you retest this? It should be fixed.
> 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
> Affects Versions: 1.1
> Environment: JBoss AS 5.x, EmbJopr 1.1.1-SNAPSHOT
> Reporter: Ondrej ?i?ka
> Fix For: 1.2
>
>
> 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
From jira-events at lists.jboss.org Wed Mar 4 18:35:27 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 4 Mar 2009 18:35:27 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-75) WAR deployed,
listed in summary, but bad link and not listed in tree
In-Reply-To: <4413336.1234818109606.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21588114.1236209727852.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-75:
-------------------------------------
Assignee: Ondrej ?i?ka
> 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
> Affects Versions: 1.1
> Environment: JBoss AS 5.x, EmbJopr 1.1.1-SNAPSHOT
> Reporter: Ondrej ?i?ka
> Assignee: Ondrej ?i?ka
> Fix For: 1.2
>
>
> 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
From jira-events at lists.jboss.org Thu Mar 5 12:50:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 5 Mar 2009 12:50:25 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-39) AS5 plugin:
After successfully
deleting a datasource, this datasource still shows up in the left nav and
in the table of datasources
In-Reply-To: <33019941.1226676818282.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3646402.1236275425893.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-39:
----------------------------------
Assignee: Farah Juma (was: Ian Springer)
Since EMBJOPR-62 is fixed this should also be resolved, please retest.
> 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
> Assignee: Farah Juma
> Fix For: 1.2
>
> Attachments: deleteDataSource.png
>
>
> 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
From jira-events at lists.jboss.org Thu Mar 5 16:44:30 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 5 Mar 2009 16:44:30 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-86) "Add a new
resource" button doesn't work after creating a resource
In-Reply-To: <28227804.1236119604971.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19976229.1236289470937.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch resolved EMBJOPR-86.
-----------------------------------
Resolution: Done
r179 @End(ifOutcome...) annotation wasnt working (the long running conversation was continuing after the save) so replace it with Conversation.end()
> "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
> Assignee: 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
From jira-events at lists.jboss.org Thu Mar 5 16:44:27 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 5 Mar 2009 16:44:27 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-86) "Add a new
resource" button doesn't work after creating a resource
In-Reply-To: <28227804.1236119604971.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21605909.1236289468035.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-86:
-------------------------------------
Assignee: Charles Crouch
> "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
> Assignee: 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
From jira-events at lists.jboss.org Thu Mar 5 18:09:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 5 Mar 2009 18:09:24 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-68) upgrade
RichFaces from
3.2.2.SR1 to the same version used by Jopr/Enterprise (currently 3.3.0.GA)
In-Reply-To: <28341810.1233842216306.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23154808.1236294564228.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-68:
-------------------------------------
Assignee: Charles Crouch
> 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
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
--
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
From jira-events at lists.jboss.org Thu Mar 5 18:11:37 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 5 Mar 2009 18:11:37 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-68) upgrade
RichFaces from
3.2.2.SR1 to the same version used by Jopr/Enterprise (currently 3.3.0.GA)
In-Reply-To: <28341810.1233842216306.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5211671.1236294697272.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch resolved EMBJOPR-68.
-----------------------------------
Resolution: Done
Fixed in embjopr r186
> 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
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
--
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
From jira-events at lists.jboss.org Thu Mar 5 18:11:40 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 5 Mar 2009 18:11:40 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-87) Operations
history list broken for specific pairs of operations
In-Reply-To: <27639330.1236196526089.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4141744.1236294700350.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12455756#action_12455756 ]
Charles Crouch commented on EMBJOPR-87:
---------------------------------------
This is still a problem after the upgrade to RF 3.3
> Operations history list broken for specific pairs of operations
> ---------------------------------------------------------------
>
> Key: EMBJOPR-87
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-87
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Reporter: Charles Crouch
> Fix For: 1.2
>
>
> Steps to reproduce
> 1) Pick a Datasource resource, e.g. DefaultDS
> 2) Execute the "List Formatted Sub Pool Statistics" operation, taking the defaults
> 3) Try to execute the "List Statistics" operation, and you will get the following:
> After this even going to the Control tab on this resource will throw the exception below.
> javax.faces.FacesException: javax.el.PropertyNotFoundException: Property 'map' not found on type org.rhq.core.domain.configuration.PropertySimple
> at javax.faces.component.UIOutput.getValue(UIOutput.java:187)
> at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getValue(HtmlBasicInputRenderer.java:201)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getCurrentValue(HtmlBasicRenderer.java:284)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeEnd(HtmlBasicRenderer.java:154)
> at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:242)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:239)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GridRenderer.renderRow(GridRenderer.java:180)
> at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:127)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:239)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
> at org.richfaces.renderkit.html.TogglePanelRenderer.handleFacets(TogglePanelRenderer.java:120)
> at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:124)
> at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:132)
> at org.ajax4jsf.renderkit.RendererBase.encodeEnd(RendererBase.java:135)
> at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:286)
> at org.ajax4jsf.renderkit.RendererBase.renderChildren(RendererBase.java:262)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:284)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
> at org.richfaces.renderkit.html.ColgroupRenderer.encodeChildren(ColgroupRenderer.java:98)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeOneRow(AbstractTableRenderer.java:361)
> at org.richfaces.renderkit.AbstractRowsRenderer.process(AbstractRowsRenderer.java:86)
> at org.ajax4jsf.model.SequenceDataModel.walk(SequenceDataModel.java:101)
> at org.ajax4jsf.component.UIDataAdaptor.walk(UIDataAdaptor.java:1151)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:106)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:91)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeTBody(AbstractTableRenderer.java:73)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeChildren(AbstractTableRenderer.java:80)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
> at javax.faces.render.Renderer.encodeChildren(Renderer.java:148)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933)
> at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592)
> at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
> at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196)
> at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
> 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:126)
> 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: javax.el.PropertyNotFoundException: Property 'map' not found on type org.rhq.core.domain.configuration.PropertySimple
> at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193)
> at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170)
> at javax.el.BeanELResolver.property(BeanELResolver.java:279)
> at javax.el.BeanELResolver.getValue(BeanELResolver.java:60)
> at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54)
> at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72)
> at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53)
> at org.jboss.el.parser.AstValue.getValue(AstValue.java:67)
> at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
> at javax.faces.component.UIOutput.getValue(UIOutput.java:184)
> ... 105 more
> If you swap steps 2) and 3)...
> 2) Execute the "List Statistics"operation
> 3) Try to execute the "List Formatted Sub Pool Statistics" operation, when you hit the OK button on the arguments page you will get the following:
> After this even going to the Control tab on this resource will throw the exception below:
> javax.faces.FacesException: javax.el.PropertyNotFoundException: Property 'stringValue' not found on type org.rhq.core.domain.configuration.PropertyMap
> at javax.faces.component.UIOutput.getValue(UIOutput.java:187)
> at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getValue(HtmlBasicInputRenderer.java:201)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getCurrentValue(HtmlBasicRenderer.java:284)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeEnd(HtmlBasicRenderer.java:154)
> at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:242)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:239)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
> at org.richfaces.renderkit.html.TogglePanelRenderer.handleFacets(TogglePanelRenderer.java:120)
> at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:124)
> at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:132)
> at org.ajax4jsf.renderkit.RendererBase.encodeEnd(RendererBase.java:135)
> at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:286)
> at org.ajax4jsf.renderkit.RendererBase.renderChildren(RendererBase.java:262)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:284)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
> at org.richfaces.renderkit.html.ColgroupRenderer.encodeChildren(ColgroupRenderer.java:98)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeOneRow(AbstractTableRenderer.java:361)
> at org.richfaces.renderkit.AbstractRowsRenderer.process(AbstractRowsRenderer.java:86)
> at org.ajax4jsf.model.SequenceDataModel.walk(SequenceDataModel.java:101)
> at org.ajax4jsf.component.UIDataAdaptor.walk(UIDataAdaptor.java:1151)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:106)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:91)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeTBody(AbstractTableRenderer.java:73)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeChildren(AbstractTableRenderer.java:80)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
> at javax.faces.render.Renderer.encodeChildren(Renderer.java:148)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933)
> at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592)
> at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
> at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196)
> at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
> 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:126)
> 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: javax.el.PropertyNotFoundException: Property 'stringValue' not found on type org.rhq.core.domain.configuration.PropertyMap
> at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193)
> at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170)
> at javax.el.BeanELResolver.property(BeanELResolver.java:279)
> at javax.el.BeanELResolver.getValue(BeanELResolver.java:60)
> at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54)
> at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72)
> at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53)
> at org.jboss.el.parser.AstValue.getValue(AstValue.java:67)
> at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
> at javax.faces.component.UIOutput.getValue(UIOutput.java:184)
> ... 97 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
From jira-events at lists.jboss.org Thu Mar 5 18:11:42 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 5 Mar 2009 18:11:42 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-71) AS5 plugin:
Datasource metrics
are not updated after a connection is requested from a connection pool
In-Reply-To: <6039451.1234363066227.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3657413.1236294702061.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-71:
----------------------------------
Priority: Critical (was: Major)
> 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
> Priority: Critical
> Fix For: 1.2
>
>
> 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
From jira-events at lists.jboss.org Fri Mar 6 10:59:24 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Fri, 6 Mar 2009 10:59:24 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-39) AS5 plugin:
After successfully
deleting a datasource, this datasource still shows up in the left nav and
in the table of datasources
In-Reply-To: <33019941.1226676818282.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31170194.1236355164902.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Farah Juma updated EMBJOPR-39:
------------------------------
Attachment: BeforeDatasourceDeletion.png
AfterDatasourceDeletion.png
AfterRefreshingResourcesNode.png
I'm seeing some strange behaviour after deleting a datasource. Now, after deleting a datasource, the left nav and the table of datasources are updated to reflect this change. (See BeforeDatasourceDeletion.png and AfterDatasourceDeletion.png.) However, if I then collapse and then expand the "Resources" nav tree node, and then navigate to the datasources, the deleted datasource shows up again in both the left nav and in the table of datasources (see AfterRefreshingResourcesNode.png).
I have attached the console output. I used embjopr r187 and JBoss AS Branch_5_x r85318.
> 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
> Assignee: Farah Juma
> Fix For: 1.2
>
> Attachments: AfterDatasourceDeletion.png, AfterRefreshingResourcesNode.png, BeforeDatasourceDeletion.png, deleteDataSource.png
>
>
> 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
From jira-events at lists.jboss.org Fri Mar 6 11:01:25 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Fri, 6 Mar 2009 11:01:25 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-39) AS5 plugin:
After successfully
deleting a datasource, this datasource still shows up in the left nav and
in the table of datasources
In-Reply-To: <33019941.1226676818282.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1184621.1236355285112.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Farah Juma updated EMBJOPR-39:
------------------------------
Attachment: consoleOutputAfterDeletion.txt
> 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
> Assignee: Farah Juma
> Fix For: 1.2
>
> Attachments: AfterDatasourceDeletion.png, AfterRefreshingResourcesNode.png, BeforeDatasourceDeletion.png, consoleOutputAfterDeletion.txt, deleteDataSource.png
>
>
> 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
From jira-events at lists.jboss.org Fri Mar 6 11:39:26 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Fri, 6 Mar 2009 11:39:26 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-87) Operations
history list broken for specific pairs of operations
In-Reply-To: <27639330.1236196526089.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32999102.1236357566293.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-87:
-------------------------------------
Assignee: Ian Springer
> Operations history list broken for specific pairs of operations
> ---------------------------------------------------------------
>
> Key: EMBJOPR-87
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-87
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Reporter: Charles Crouch
> Assignee: Ian Springer
> Fix For: 1.2
>
>
> Steps to reproduce
> 1) Pick a Datasource resource, e.g. DefaultDS
> 2) Execute the "List Formatted Sub Pool Statistics" operation, taking the defaults
> 3) Try to execute the "List Statistics" operation, and you will get the following:
> After this even going to the Control tab on this resource will throw the exception below.
> javax.faces.FacesException: javax.el.PropertyNotFoundException: Property 'map' not found on type org.rhq.core.domain.configuration.PropertySimple
> at javax.faces.component.UIOutput.getValue(UIOutput.java:187)
> at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getValue(HtmlBasicInputRenderer.java:201)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getCurrentValue(HtmlBasicRenderer.java:284)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeEnd(HtmlBasicRenderer.java:154)
> at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:242)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:239)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GridRenderer.renderRow(GridRenderer.java:180)
> at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:127)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:239)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
> at org.richfaces.renderkit.html.TogglePanelRenderer.handleFacets(TogglePanelRenderer.java:120)
> at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:124)
> at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:132)
> at org.ajax4jsf.renderkit.RendererBase.encodeEnd(RendererBase.java:135)
> at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:286)
> at org.ajax4jsf.renderkit.RendererBase.renderChildren(RendererBase.java:262)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:284)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
> at org.richfaces.renderkit.html.ColgroupRenderer.encodeChildren(ColgroupRenderer.java:98)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeOneRow(AbstractTableRenderer.java:361)
> at org.richfaces.renderkit.AbstractRowsRenderer.process(AbstractRowsRenderer.java:86)
> at org.ajax4jsf.model.SequenceDataModel.walk(SequenceDataModel.java:101)
> at org.ajax4jsf.component.UIDataAdaptor.walk(UIDataAdaptor.java:1151)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:106)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:91)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeTBody(AbstractTableRenderer.java:73)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeChildren(AbstractTableRenderer.java:80)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
> at javax.faces.render.Renderer.encodeChildren(Renderer.java:148)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933)
> at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592)
> at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
> at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196)
> at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
> 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:126)
> 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: javax.el.PropertyNotFoundException: Property 'map' not found on type org.rhq.core.domain.configuration.PropertySimple
> at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193)
> at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170)
> at javax.el.BeanELResolver.property(BeanELResolver.java:279)
> at javax.el.BeanELResolver.getValue(BeanELResolver.java:60)
> at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54)
> at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72)
> at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53)
> at org.jboss.el.parser.AstValue.getValue(AstValue.java:67)
> at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
> at javax.faces.component.UIOutput.getValue(UIOutput.java:184)
> ... 105 more
> If you swap steps 2) and 3)...
> 2) Execute the "List Statistics"operation
> 3) Try to execute the "List Formatted Sub Pool Statistics" operation, when you hit the OK button on the arguments page you will get the following:
> After this even going to the Control tab on this resource will throw the exception below:
> javax.faces.FacesException: javax.el.PropertyNotFoundException: Property 'stringValue' not found on type org.rhq.core.domain.configuration.PropertyMap
> at javax.faces.component.UIOutput.getValue(UIOutput.java:187)
> at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getValue(HtmlBasicInputRenderer.java:201)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getCurrentValue(HtmlBasicRenderer.java:284)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeEnd(HtmlBasicRenderer.java:154)
> at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:242)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:239)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
> at org.richfaces.renderkit.html.TogglePanelRenderer.handleFacets(TogglePanelRenderer.java:120)
> at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:124)
> at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:132)
> at org.ajax4jsf.renderkit.RendererBase.encodeEnd(RendererBase.java:135)
> at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:286)
> at org.ajax4jsf.renderkit.RendererBase.renderChildren(RendererBase.java:262)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:284)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
> at org.richfaces.renderkit.html.ColgroupRenderer.encodeChildren(ColgroupRenderer.java:98)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeOneRow(AbstractTableRenderer.java:361)
> at org.richfaces.renderkit.AbstractRowsRenderer.process(AbstractRowsRenderer.java:86)
> at org.ajax4jsf.model.SequenceDataModel.walk(SequenceDataModel.java:101)
> at org.ajax4jsf.component.UIDataAdaptor.walk(UIDataAdaptor.java:1151)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:106)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:91)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeTBody(AbstractTableRenderer.java:73)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeChildren(AbstractTableRenderer.java:80)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
> at javax.faces.render.Renderer.encodeChildren(Renderer.java:148)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933)
> at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592)
> at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
> at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196)
> at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
> 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:126)
> 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: javax.el.PropertyNotFoundException: Property 'stringValue' not found on type org.rhq.core.domain.configuration.PropertyMap
> at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193)
> at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170)
> at javax.el.BeanELResolver.property(BeanELResolver.java:279)
> at javax.el.BeanELResolver.getValue(BeanELResolver.java:60)
> at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54)
> at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72)
> at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53)
> at org.jboss.el.parser.AstValue.getValue(AstValue.java:67)
> at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
> at javax.faces.component.UIOutput.getValue(UIOutput.java:184)
> ... 97 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
From jira-events at lists.jboss.org Fri Mar 6 11:45:30 2009
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Fri, 6 Mar 2009 11:45:30 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Closed: (EMBJOPR-80) EAR: Attempting
to view deployed .ear shows Summary for root node instead
In-Reply-To: <104175.1235145590157.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16408795.1236357930258.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shelly McGowan closed EMBJOPR-80.
---------------------------------
> EAR: 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
> Environment: JBoss AS Branch_5_x r84532, embjopr r162
> Reporter: Shelly McGowan
> Assignee: Shelly McGowan
> Fix For: 1.2
>
> Attachments: click-earname.png, ear-created.png, manual-nav-to-ears.png
>
>
> 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
From jira-events at lists.jboss.org Fri Mar 6 11:45:33 2009
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Fri, 6 Mar 2009 11:45:33 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Closed: (EMBJOPR-75) WAR deployed,
listed in summary, but bad link and not listed in tree
In-Reply-To: <4413336.1234818109606.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26549826.1236357933391.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shelly McGowan closed EMBJOPR-75.
---------------------------------
Resolution: Done
Resolved.
> 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
> Affects Versions: 1.1
> Environment: JBoss AS 5.x, EmbJopr 1.1.1-SNAPSHOT
> Reporter: Ondrej ?i?ka
> Assignee: Ondrej ?i?ka
> Fix For: 1.2
>
>
> 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
From jira-events at lists.jboss.org Fri Mar 6 11:45:26 2009
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Fri, 6 Mar 2009 11:45:26 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-80) EAR:
Attempting to view deployed .ear shows Summary for root node instead
In-Reply-To: <104175.1235145590157.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26566616.1236357926981.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shelly McGowan resolved EMBJOPR-80.
-----------------------------------
Resolution: Done
Resolved.
> EAR: 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
> Environment: JBoss AS Branch_5_x r84532, embjopr r162
> Reporter: Shelly McGowan
> Assignee: Shelly McGowan
> Fix For: 1.2
>
> Attachments: click-earname.png, ear-created.png, manual-nav-to-ears.png
>
>
> 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
From jira-events at lists.jboss.org Fri Mar 6 11:51:24 2009
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Fri, 6 Mar 2009 11:51:24 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Closed: (EMBJOPR-84) Configuration
tab for a deployed Enterprise Archive in Incomplete
In-Reply-To: <11151781.1235426627287.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28409297.1236358284666.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shelly McGowan closed EMBJOPR-84.
---------------------------------
Resolution: Cannot Reproduce Bug
The Configuration tab is now available. embjopr, rev 176
> 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
>
> Attachments: EAR-Configuration.png
>
>
> 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
From jira-events at lists.jboss.org Fri Mar 6 18:33:23 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Fri, 6 Mar 2009 18:33:23 -0500 (EST)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-88) JBA5 plugin:
Stop reloading
entire profile when getting availability of each resource
Message-ID: <30568408.1236382403959.JavaMail.jira@cloud.prod.atl2.jboss.com>
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
From jira-events at lists.jboss.org Mon Mar 9 11:06:32 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Mon, 9 Mar 2009 11:06:32 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-89) After creating
a new resource, the success message no longer gets displayed
Message-ID: <23611569.1236611192242.JavaMail.jira@cloud.prod.atl2.jboss.com>
After creating a new resource, the success message no longer gets displayed
---------------------------------------------------------------------------
Key: EMBJOPR-89
URL: https://jira.jboss.org/jira/browse/EMBJOPR-89
Project: Embedded Jopr
Issue Type: Bug
Components: Web App/Integration
Environment: JBoss AS Branch_5_x r85646, embjopr r193
Reporter: Farah Juma
Attachments: AfterDatasourceCreation.png
Steps to reproduce:
Add a new resource (eg. Local TX Datasource). After clicking on the "Save" button, the resource shows up in the table of resources. However, the success message (eg. "Successfully added new Local TX Datasource") no longer gets displayed.
eg. AfterDatasourceCreation.png shows the Summary page for "Local TX Datasources" after adding "CreationTest".
--
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
From jira-events at lists.jboss.org Mon Mar 9 11:06:36 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Mon, 9 Mar 2009 11:06:36 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-89) After creating
a new resource, the success message no longer gets displayed
In-Reply-To: <23611569.1236611192242.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25783728.1236611196585.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Farah Juma updated EMBJOPR-89:
------------------------------
Attachment: AfterDatasourceCreation.png
> After creating a new resource, the success message no longer gets displayed
> ---------------------------------------------------------------------------
>
> Key: EMBJOPR-89
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-89
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS Branch_5_x r85646, embjopr r193
> Reporter: Farah Juma
> Attachments: AfterDatasourceCreation.png
>
>
> Steps to reproduce:
> Add a new resource (eg. Local TX Datasource). After clicking on the "Save" button, the resource shows up in the table of resources. However, the success message (eg. "Successfully added new Local TX Datasource") no longer gets displayed.
> eg. AfterDatasourceCreation.png shows the Summary page for "Local TX Datasources" after adding "CreationTest".
--
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
From jira-events at lists.jboss.org Mon Mar 9 11:52:27 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Mon, 9 Mar 2009 11:52:27 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Reopened: (EMBJOPR-58) AS5 plugin:
Clicking on the "Configuration" tab for a Datasource results in a
"PluginContainerException"
In-Reply-To: <19037367.1229613896768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19809399.1236613947072.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Farah Juma reopened EMBJOPR-58:
-------------------------------
I'm still seeing this with JBoss AS Branch_5_x r85646 and embjopr r193. However, clicking on the "Configuration" tab for other types of resources (both connection factories and JMS destinations) seems to work fine.
> AS5 plugin: Clicking on the "Configuration" tab for a Datasource results in a "PluginContainerException"
> --------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-58
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-58
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS 5 trunk r82369, embjopr r76
> Reporter: Farah Juma
> Priority: Critical
> Fix For: 1.2
>
>
> When the console is deployed to JBoss AS 5 trunk, the following error message gets displayed after clicking on the "Configuration" tab for any Datasource (eg. DefaultDS):
> "There was an error retrieving the configuration for this resource"
> The following error message appears in the console output:
> 09:14:13,572 ERROR [PluginContainerResourceManager] Error retrieving configuration for resource: Resource[id=-4, type=Local TX Datasource, key=DataSource:LocalTx:DefaultDS, name=DefaultDS, version=?]
> org.rhq.core.clientapi.agent.PluginContainerException: Cannot load Resource configuration for [-4]
> at org.rhq.core.pc.configuration.ConfigurationManager.loadResourceConfiguration(ConfigurationManager.java:174)
> at org.jboss.on.embedded.manager.pc.PluginContainerResourceManager.getResourceConfiguration(PluginContainerResourceManager.java:234)
> at org.jboss.on.embedded.ui.configuration.resource.ResourceConfigurationUIBean.resourceConfiguration(ResourceConfigurationUIBean.java:144)
> 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.seam.util.Reflections.invoke(Reflections.java:22)
> at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
> at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
> at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28)
> at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
> at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77)
> at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
> at org.jboss.seam.core.ConversationInterceptor.aroundInvoke(ConversationInterceptor.java:56)
> 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.ResourceConfigurationUIBean_$$_javassist_10.resourceConfiguration(ResourceConfigurationUIBean_$$_javassist_10.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)
> 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:126)
> 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: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)
> Caused by: java.lang.ClassCastException: [Warning] org.rhq.core.domain.configuration.definition.PropertyDefinitionList
> ... 85 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
From jira-events at lists.jboss.org Mon Mar 9 12:04:35 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Mon, 9 Mar 2009 12:04:35 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-90) AS5 plugin: An
empty "Metrics
Summary" table is displayed on the "Summary" page for queues and topics
In-Reply-To: <23313651.1236614666757.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24668662.1236614675414.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Farah Juma updated EMBJOPR-90:
------------------------------
Attachment: QueueSummaryPage.png
> 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
From jira-events at lists.jboss.org Mon Mar 9 12:04:26 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Mon, 9 Mar 2009 12:04:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-90) AS5 plugin: An
empty "Metrics
Summary" table is displayed on the "Summary" page for queues and topics
Message-ID: <23313651.1236614666757.JavaMail.jira@cloud.prod.atl2.jboss.com>
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
From jira-events at lists.jboss.org Mon Mar 9 12:26:27 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Mon, 9 Mar 2009 12:26:27 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-89) After
creating a new resource,
the success message no longer gets displayed
In-Reply-To: <23611569.1236611192242.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20750002.1236615987105.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12456243#action_12456243 ]
Charles Crouch commented on EMBJOPR-89:
---------------------------------------
I'm wondering if this could have been the result of fixing EMBJOPR-86. Terminating the conversation after the redirect should fix this.
> After creating a new resource, the success message no longer gets displayed
> ---------------------------------------------------------------------------
>
> Key: EMBJOPR-89
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-89
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS Branch_5_x r85646, embjopr r193
> Reporter: Farah Juma
> Attachments: AfterDatasourceCreation.png
>
>
> Steps to reproduce:
> Add a new resource (eg. Local TX Datasource). After clicking on the "Save" button, the resource shows up in the table of resources. However, the success message (eg. "Successfully added new Local TX Datasource") no longer gets displayed.
> eg. AfterDatasourceCreation.png shows the Summary page for "Local TX Datasources" after adding "CreationTest".
--
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
From jira-events at lists.jboss.org Mon Mar 9 17:27:24 2009
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Mon, 9 Mar 2009 17:27:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-91) Applications
can be DELETED without confirmation from Applications Summary Tab
Message-ID: <2254840.1236634044669.JavaMail.jira@cloud.prod.atl2.jboss.com>
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
From jira-events at lists.jboss.org Tue Mar 10 09:46:42 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Tue, 10 Mar 2009 09:46:42 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-61) Problems with
pagination on Applications subcategory
In-Reply-To: <13607628.1229726875762.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6869868.1236692802858.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12456397#action_12456397 ]
Farah Juma commented on EMBJOPR-61:
-----------------------------------
There is a similar problem with pagination on the "Datasources" subcategory. I have a total of 13 datasources. When I click on the "Datasources" node and start paging through the results, I can only view the first two pages of the table. When I click on the third page, an empty table gets displayed. Pagination on the "Local TX Datasources", "No TX Datasources", and "XA Datasources" subcategories works fine though.
I used JBoss Branch_5_x r85646 and embjopr r197.
> Problems with pagination on Applications subcategory
> ----------------------------------------------------
>
> Key: EMBJOPR-61
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-61
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: jbas4 console in JBAS4.2.2
> Reporter: Charles Crouch
> Priority: Critical
> Fix For: 1.2
>
>
> I have 21 "application" resources, web apps, ejbs, ears etc. When I choose the Applications node and start paging through the results I can only click on page numbers twice before I get the following message in the console, and an entirely empty table is rendered in the UI
> 16:39:59,156 WARN [UIDatascroller] Datascroller categorySummaryForm:dataTableScroller: The requested page #3 isn't found in
> the model containing 1 pages. Paging is reset to page #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
From jira-events at lists.jboss.org Tue Mar 10 20:17:25 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Tue, 10 Mar 2009 20:17:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-61) Problems with
pagination on Applications subcategory
In-Reply-To: <13607628.1229726875762.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19047531.1236730645124.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12456553#action_12456553 ]
Ondrej ?i?ka commented on EMBJOPR-61:
-------------------------------------
Test case created - as5/ApplicationsPageTest.java - testAppsPagination()
> Problems with pagination on Applications subcategory
> ----------------------------------------------------
>
> Key: EMBJOPR-61
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-61
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: jbas4 console in JBAS4.2.2
> Reporter: Charles Crouch
> Priority: Critical
> Fix For: 1.2
>
>
> I have 21 "application" resources, web apps, ejbs, ears etc. When I choose the Applications node and start paging through the results I can only click on page numbers twice before I get the following message in the console, and an entirely empty table is rendered in the UI
> 16:39:59,156 WARN [UIDatascroller] Datascroller categorySummaryForm:dataTableScroller: The requested page #3 isn't found in
> the model containing 1 pages. Paging is reset to page #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
From jira-events at lists.jboss.org Wed Mar 11 11:11:38 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 11 Mar 2009 11:11:38 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-89) After creating
a new resource, the success message no longer gets displayed
In-Reply-To: <23611569.1236611192242.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33499840.1236784298656.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-89:
----------------------------------
Fix Version/s: 1.2
> After creating a new resource, the success message no longer gets displayed
> ---------------------------------------------------------------------------
>
> Key: EMBJOPR-89
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-89
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS Branch_5_x r85646, embjopr r193
> Reporter: Farah Juma
> Fix For: 1.2
>
> Attachments: AfterDatasourceCreation.png
>
>
> Steps to reproduce:
> Add a new resource (eg. Local TX Datasource). After clicking on the "Save" button, the resource shows up in the table of resources. However, the success message (eg. "Successfully added new Local TX Datasource") no longer gets displayed.
> eg. AfterDatasourceCreation.png shows the Summary page for "Local TX Datasources" after adding "CreationTest".
--
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
From jira-events at lists.jboss.org Wed Mar 11 11:11:57 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 11 Mar 2009 11:11:57 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-90) AS5 plugin: An
empty "Metrics
Summary" table is displayed on the "Summary" page for queues and topics
In-Reply-To: <23313651.1236614666757.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32385540.1236784317255.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-90:
----------------------------------
Fix Version/s: 1.2
> 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
> Fix For: 1.2
>
> 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
From jira-events at lists.jboss.org Wed Mar 11 13:56:33 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Wed, 11 Mar 2009 13:56:33 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-92) Nav tree is not
filled right after login
Message-ID: <8413057.1236794193967.JavaMail.jira@cloud.prod.atl2.jboss.com>
Nav tree is not filled right after login
----------------------------------------
Key: EMBJOPR-92
URL: https://jira.jboss.org/jira/browse/EMBJOPR-92
Project: Embedded Jopr
Issue Type: Bug
Reporter: Ondrej ?i?ka
Sometimes, after logging in, the nav tree is empty - i.e. no 2nd level nodes.
Possible cause: "hmm, it sounds like discovery hasnt run" (ccrouch)
--
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
From jira-events at lists.jboss.org Wed Mar 11 14:36:25 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Wed, 11 Mar 2009 14:36:25 -0400 (EDT)
Subject: [embjopr-issues] [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
Message-ID: <26943821.1236796585070.JavaMail.jira@cloud.prod.atl2.jboss.com>
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
From jira-events at lists.jboss.org Thu Mar 12 08:51:41 2009
From: jira-events at lists.jboss.org (Juergen Zimmermann (JIRA))
Date: Thu, 12 Mar 2009 08:51:41 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-94)
NoSuchMethodError:
org.jboss.deployers.spi.management.ManagementView.load()V
Message-ID: <22354006.1236862301505.JavaMail.jira@cloud.prod.atl2.jboss.com>
NoSuchMethodError: org.jboss.deployers.spi.management.ManagementView.load()V
----------------------------------------------------------------------------
Key: EMBJOPR-94
URL: https://jira.jboss.org/jira/browse/EMBJOPR-94
Project: Embedded Jopr
Issue Type: Bug
Environment: JBossAS 5.0.1, Embjopr trunk
Reporter: Juergen Zimmermann
When I start JBossAS 5.0.1 (with deploy/jbas5-admin-console.war) I get this stacktrace:
...
13:42:55,230 INFO [ServletContextListener] Welcome to Seam 2.1.0.SP1
13:43:05,843 WARN [Initialization] has been deprecated, use instead
13:43:05,843 WARN [Initialization] has been deprecated, use instead
13:43:07,439 WARN [Component] Component class should be serializable: contentDisplayAction
13:43:07,450 WARN [Component] Component class should be serializable: createContentBackedResourceAction
13:43:07,482 WARN [Component] Component class should be serializable: navigationAction
13:43:07,492 WARN [Component] Component class should be serializable: operationAction
13:43:07,649 WARN [Component] Component class should be serializable: org.jboss.seam.ui.facelet.mockHttpSession
13:43:07,670 WARN [Component] Component class should be serializable: resourceConfigurationUIBean
13:43:07,683 WARN [Component] Component class should be serializable: updateBackingContentAction
13:43:07,694 WARN [PersistentPermissionResolver] no permission store available - please install a PermissionStore with the name 'org.jboss.seam.security.jpaPermissionStore' if persistent permissions are required.
13:43:07,761 INFO [BootstrapAction] Bootstrapping Administration Console v1.2.0-SNAPSHOT...
13:43:07,993 INFO [PluginContainer] Initializing Plugin Container v1.2.0-SNAPSHOT...
13:43:09,332 INFO [InventoryManager] Initializing Inventory Manager...
13:43:09,472 WARN [SystemInfoFactory] System info API not accessible on this platform (native shared library not found in java.library.path).
13:43:09,520 INFO [InventoryManager] Detected new Platform [Resource[id=-2, type=Windows, key=iwi-w-ziju01-a.ads.hs-karlsruhe.de, name=iwi-w-ziju01-a.ads.hs-karlsruhe.de, parent=, version=Windows Vista 6.0]] - adding to local inventory...
13:43:09,553 INFO [InventoryManager] Inventory Manager initialized.
13:43:09,562 INFO [ResourceFactoryManager] Initializing
13:43:09,562 INFO [ContentManager] Initializing Content Manager...
13:43:09,563 INFO [ContentManager] Content Manager initialized...
13:43:09,567 INFO [BootstrapAction] Loaded RHQ plugin [JBossAS5].
13:43:09,567 INFO [BootstrapAction] Loaded RHQ plugin [Platforms].
13:43:09,571 INFO [PluginContainerResourceManager] Discovering Resources...
13:43:09,571 INFO [AutoDiscoveryExecutor] Executing server discovery scan...
13:43:09,649 INFO [ApplicationServerDiscoveryComponent] Discovering JBossAS Server Resources...
13:43:09,676 INFO [ProfileServiceFactory] About to load profile
13:43:09,676 WARN [InventoryManager] Failure during discovery for [JBossAS Server] Resources - failed after 28 ms.
java.lang.NoSuchMethodError: org.jboss.deployers.spi.management.ManagementView.load()V
at org.rhq.plugins.jbossas5.factory.ProfileServiceFactory.loadProfile(ProfileServiceFactory.java:135)
at org.rhq.plugins.jbossas5.factory.ProfileServiceFactory.refreshCurrentProfileView(ProfileServiceFactory.java:113)
at org.rhq.plugins.jbossas5.factory.ProfileServiceFactory.getCurrentProfileView(ProfileServiceFactory.java:100)
at org.rhq.plugins.jbossas5.factory.ProfileServiceFactory.refreshCurrentProfileView(ProfileServiceFactory.java:113)
at org.rhq.plugins.jbossas5.ApplicationServerDiscoveryComponent.discoverResources(ApplicationServerDiscoveryComponent.java:74)
at org.rhq.core.pc.inventory.InventoryManager.executeComponentDiscovery(InventoryManager.java:1542)
at org.rhq.core.pc.inventory.AutoDiscoveryExecutor.pluginDiscovery(AutoDiscoveryExecutor.java:185)
at org.rhq.core.pc.inventory.AutoDiscoveryExecutor.call(AutoDiscoveryExecutor.java:104)
at org.rhq.core.pc.inventory.AutoDiscoveryExecutor.call(AutoDiscoveryExecutor.java:70)
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.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
--
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
From jira-events at lists.jboss.org Thu Mar 12 12:21:25 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Thu, 12 Mar 2009 12:21:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-95) Exploded
application summary shows "Exploded?: no"
Message-ID: <11604562.1236874885612.JavaMail.jira@cloud.prod.atl2.jboss.com>
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
From jira-events at lists.jboss.org Thu Mar 12 13:51:25 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Thu, 12 Mar 2009 13:51:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-96) Read-only
properties should be marked as read-only
Message-ID: <15056342.1236880285024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Read-only properties should be marked as read-only
--------------------------------------------------
Key: EMBJOPR-96
URL: https://jira.jboss.org/jira/browse/EMBJOPR-96
Project: Embedded Jopr
Issue Type: Bug
Affects Versions: 1.2
Reporter: Ondrej ?i?ka
Currently, read-only properties appear the same as editable ones.
See e.g. any EAR Configuration, property Name.
If you edit such property, it simply returns to previous value.
It should be noted somehow that they are readonly,
and their input should be disabled.
--
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
From jira-events at lists.jboss.org Thu Mar 12 13:57:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 12 Mar 2009 13:57:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-58) AS5 plugin:
Clicking on the "Configuration" tab for a Datasource results in a
"PluginContainerException"
In-Reply-To: <19037367.1229613896768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23854986.1236880645527.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-58:
-------------------------------------
Assignee: Charles Crouch
> AS5 plugin: Clicking on the "Configuration" tab for a Datasource results in a "PluginContainerException"
> --------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-58
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-58
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS 5 trunk r82369, embjopr r76
> Reporter: Farah Juma
> Assignee: Charles Crouch
> Priority: Critical
> Fix For: 1.2
>
>
> When the console is deployed to JBoss AS 5 trunk, the following error message gets displayed after clicking on the "Configuration" tab for any Datasource (eg. DefaultDS):
> "There was an error retrieving the configuration for this resource"
> The following error message appears in the console output:
> 09:14:13,572 ERROR [PluginContainerResourceManager] Error retrieving configuration for resource: Resource[id=-4, type=Local TX Datasource, key=DataSource:LocalTx:DefaultDS, name=DefaultDS, version=?]
> org.rhq.core.clientapi.agent.PluginContainerException: Cannot load Resource configuration for [-4]
> at org.rhq.core.pc.configuration.ConfigurationManager.loadResourceConfiguration(ConfigurationManager.java:174)
> at org.jboss.on.embedded.manager.pc.PluginContainerResourceManager.getResourceConfiguration(PluginContainerResourceManager.java:234)
> at org.jboss.on.embedded.ui.configuration.resource.ResourceConfigurationUIBean.resourceConfiguration(ResourceConfigurationUIBean.java:144)
> 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.seam.util.Reflections.invoke(Reflections.java:22)
> at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
> at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
> at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28)
> at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
> at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77)
> at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
> at org.jboss.seam.core.ConversationInterceptor.aroundInvoke(ConversationInterceptor.java:56)
> 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.ResourceConfigurationUIBean_$$_javassist_10.resourceConfiguration(ResourceConfigurationUIBean_$$_javassist_10.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)
> 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:126)
> 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: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)
> Caused by: java.lang.ClassCastException: [Warning] org.rhq.core.domain.configuration.definition.PropertyDefinitionList
> ... 85 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
From jira-events at lists.jboss.org Thu Mar 12 14:01:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 12 Mar 2009 14:01:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-58) AS5 plugin:
Clicking on the "Configuration" tab for a Datasource results in a
"PluginContainerException"
In-Reply-To: <19037367.1229613896768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1877180.1236880885443.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch resolved EMBJOPR-58.
-----------------------------------
Resolution: Done
The problem was that the "config-property" resource configuration property had changed from a List to a Map, so it didnt match what we had in the plugin descriptor.
Looking at
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214634#4214634
it implies we should not be using the config-property element to retrieve other values anyway. Instead we should use other top level properties for them, e.g. username rather than config-property.username.
Looking at the contents of the config-property map, the only property we seem to be missing is ConnectionProperties, I'll raise another jira for adding that to the DS configuration
> AS5 plugin: Clicking on the "Configuration" tab for a Datasource results in a "PluginContainerException"
> --------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-58
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-58
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS 5 trunk r82369, embjopr r76
> Reporter: Farah Juma
> Assignee: Charles Crouch
> Priority: Critical
> Fix For: 1.2
>
>
> When the console is deployed to JBoss AS 5 trunk, the following error message gets displayed after clicking on the "Configuration" tab for any Datasource (eg. DefaultDS):
> "There was an error retrieving the configuration for this resource"
> The following error message appears in the console output:
> 09:14:13,572 ERROR [PluginContainerResourceManager] Error retrieving configuration for resource: Resource[id=-4, type=Local TX Datasource, key=DataSource:LocalTx:DefaultDS, name=DefaultDS, version=?]
> org.rhq.core.clientapi.agent.PluginContainerException: Cannot load Resource configuration for [-4]
> at org.rhq.core.pc.configuration.ConfigurationManager.loadResourceConfiguration(ConfigurationManager.java:174)
> at org.jboss.on.embedded.manager.pc.PluginContainerResourceManager.getResourceConfiguration(PluginContainerResourceManager.java:234)
> at org.jboss.on.embedded.ui.configuration.resource.ResourceConfigurationUIBean.resourceConfiguration(ResourceConfigurationUIBean.java:144)
> 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.seam.util.Reflections.invoke(Reflections.java:22)
> at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
> at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
> at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28)
> at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
> at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77)
> at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
> at org.jboss.seam.core.ConversationInterceptor.aroundInvoke(ConversationInterceptor.java:56)
> 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.ResourceConfigurationUIBean_$$_javassist_10.resourceConfiguration(ResourceConfigurationUIBean_$$_javassist_10.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)
> 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:126)
> 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: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)
> Caused by: java.lang.ClassCastException: [Warning] org.rhq.core.domain.configuration.definition.PropertyDefinitionList
> ... 85 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
From jira-events at lists.jboss.org Thu Mar 12 14:03:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 12 Mar 2009 14:03:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-97) Add
ConnectionProperties resource config property to all Datasources
Message-ID: <24370956.1236881004408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Add ConnectionProperties resource config property to all Datasources
--------------------------------------------------------------------
Key: EMBJOPR-97
URL: https://jira.jboss.org/jira/browse/EMBJOPR-97
Project: Embedded Jopr
Issue Type: Bug
Components: Plugin
Reporter: Charles Crouch
Fix For: 1.2
See EMBJOPR-58 for how we noticed this was missing. Need to work out what type it should map to. Right now it seems to a simple one:
ConnectionProperties.type=SimpleMetaType:java.lang.String:,
--
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
From jira-events at lists.jboss.org Thu Mar 12 14:05:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 12 Mar 2009 14:05:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-98) Add
config-property resource
configuration property to connection factories
Message-ID: <6780440.1236881124395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Add config-property resource configuration property to connection factories
---------------------------------------------------------------------------
Key: EMBJOPR-98
URL: https://jira.jboss.org/jira/browse/EMBJOPR-98
Project: Embedded Jopr
Issue Type: Bug
Components: Plugin
Reporter: Charles Crouch
Fix For: 1.2
Looking at
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214634#4214634
implies config-property should only be available for connection factory resource types. Right now its on the "XA ConnectionFactory" service, but I think it should be on the "No TX ConnectionFactory" service too.
--
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
From jira-events at lists.jboss.org Thu Mar 12 15:06:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 12 Mar 2009 15:06:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-96) Read-only
properties should be marked as read-only
In-Reply-To: <15056342.1236880285024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13130026.1236884785608.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12457002#action_12457002 ]
Charles Crouch commented on EMBJOPR-96:
---------------------------------------
Let me know which ones are meant to be readonly and I'll make the necessary updates.
> Read-only properties should be marked as read-only
> --------------------------------------------------
>
> Key: EMBJOPR-96
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-96
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
> Fix For: 1.2
>
>
> Currently, read-only properties appear the same as editable ones.
> See e.g. any EAR Configuration, property Name.
> If you edit such property, it simply returns to previous value.
> It should be noted somehow that they are readonly,
> and their input should be disabled.
--
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
From jira-events at lists.jboss.org Thu Mar 12 15:06:28 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 12 Mar 2009 15:06:28 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-96) Read-only
properties should be marked as read-only
In-Reply-To: <15056342.1236880285024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31266141.1236884788084.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-96:
-------------------------------------
Assignee: Ondrej ?i?ka
> Read-only properties should be marked as read-only
> --------------------------------------------------
>
> Key: EMBJOPR-96
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-96
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
> Assignee: Ondrej ?i?ka
> Fix For: 1.2
>
>
> Currently, read-only properties appear the same as editable ones.
> See e.g. any EAR Configuration, property Name.
> If you edit such property, it simply returns to previous value.
> It should be noted somehow that they are readonly,
> and their input should be disabled.
--
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
From jira-events at lists.jboss.org Thu Mar 12 15:06:30 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 12 Mar 2009 15:06:30 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-96) Read-only
properties should be marked as read-only
In-Reply-To: <15056342.1236880285024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23888385.1236884790026.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-96:
----------------------------------
Fix Version/s: 1.2
Affects Version/s: (was: 1.2)
> Read-only properties should be marked as read-only
> --------------------------------------------------
>
> Key: EMBJOPR-96
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-96
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
> Assignee: Ondrej ?i?ka
> Fix For: 1.2
>
>
> Currently, read-only properties appear the same as editable ones.
> See e.g. any EAR Configuration, property Name.
> If you edit such property, it simply returns to previous value.
> It should be noted somehow that they are readonly,
> and their input should be disabled.
--
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
From jira-events at lists.jboss.org Thu Mar 12 15:28:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 12 Mar 2009 15:28:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-39) AS5 plugin:
After successfully
deleting a datasource, this datasource still shows up in the left nav and
in the table of datasources
In-Reply-To: <33019941.1226676818282.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23117117.1236886104916.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12457011#action_12457011 ]
Charles Crouch commented on EMBJOPR-39:
---------------------------------------
We should take a look at this once Emanuel has completed the attachment persistence work, i.e. letting you delete a component not just a deployment
> 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
> Assignee: Farah Juma
> Fix For: 1.2
>
> Attachments: AfterDatasourceDeletion.png, AfterRefreshingResourcesNode.png, BeforeDatasourceDeletion.png, consoleOutputAfterDeletion.txt, deleteDataSource.png
>
>
> 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
From jira-events at lists.jboss.org Thu Mar 12 16:58:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 12 Mar 2009 16:58:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-92) Nav tree is
not filled right after login
In-Reply-To: <8413057.1236794193967.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23677317.1236891504220.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12457026#action_12457026 ]
Charles Crouch commented on EMBJOPR-92:
---------------------------------------
It sounds like the discovery run which gets kicked off when the console is first accessed hasn't completed by the time you are trying to use the nav. I've never seen this in actual usage of the app.
> Nav tree is not filled right after login
> ----------------------------------------
>
> Key: EMBJOPR-92
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-92
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
>
> Sometimes, after logging in, the nav tree is empty - i.e. no 2nd level nodes.
> Possible cause: "hmm, it sounds like discovery hasnt run" (ccrouch)
--
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
From jira-events at lists.jboss.org Thu Mar 12 18:49:24 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Thu, 12 Mar 2009 18:49:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-96) Read-only
properties should be marked as read-only
In-Reply-To: <15056342.1236880285024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32634204.1236898164316.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ondrej ?i?ka updated EMBJOPR-96:
--------------------------------
JBoss Forum Reference: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217668
> Read-only properties should be marked as read-only
> --------------------------------------------------
>
> Key: EMBJOPR-96
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-96
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
> Assignee: Ondrej ?i?ka
> Fix For: 1.2
>
>
> Currently, read-only properties appear the same as editable ones.
> See e.g. any EAR Configuration, property Name.
> If you edit such property, it simply returns to previous value.
> It should be noted somehow that they are readonly,
> and their input should be disabled.
--
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
From jira-events at lists.jboss.org Thu Mar 12 19:06:24 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Thu, 12 Mar 2009 19:06:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-96) Read-only
properties should be marked as read-only
In-Reply-To: <15056342.1236880285024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22948338.1236899184264.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12457037#action_12457037 ]
Ondrej ?i?ka commented on EMBJOPR-96:
-------------------------------------
ips: ozizka: there is a concept of property type
ips: that determines whether the prop is read-only (i.e. a metric) or not (i.e. a configuration prop)
ips: see ManagedProperty.hasViewUse()
ozizka: ips, I see, so, all props in the Configuration are supposed to be editable?
ips: if (managedProperty.hasViewUse(ViewUse.STATISTIC)) returns true, the prop is read-only
ips: no, only the ones w/ a view use other than stat should be editable
> Read-only properties should be marked as read-only
> --------------------------------------------------
>
> Key: EMBJOPR-96
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-96
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
> Assignee: Ondrej ?i?ka
> Fix For: 1.2
>
>
> Currently, read-only properties appear the same as editable ones.
> See e.g. any EAR Configuration, property Name.
> If you edit such property, it simply returns to previous value.
> It should be noted somehow that they are readonly,
> and their input should be disabled.
--
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
From jira-events at lists.jboss.org Thu Mar 12 19:52:24 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Thu, 12 Mar 2009 19:52:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-89) After
creating a new resource,
the success message no longer gets displayed
In-Reply-To: <23611569.1236611192242.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <639158.1236901944650.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12457041#action_12457041 ]
Ondrej ?i?ka commented on EMBJOPR-89:
-------------------------------------
The same for apps - EAR, SAR, ...
> After creating a new resource, the success message no longer gets displayed
> ---------------------------------------------------------------------------
>
> Key: EMBJOPR-89
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-89
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS Branch_5_x r85646, embjopr r193
> Reporter: Farah Juma
> Fix For: 1.2
>
> Attachments: AfterDatasourceCreation.png
>
>
> Steps to reproduce:
> Add a new resource (eg. Local TX Datasource). After clicking on the "Save" button, the resource shows up in the table of resources. However, the success message (eg. "Successfully added new Local TX Datasource") no longer gets displayed.
> eg. AfterDatasourceCreation.png shows the Summary page for "Local TX Datasources" after adding "CreationTest".
--
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
From jira-events at lists.jboss.org Fri Mar 13 11:25:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Fri, 13 Mar 2009 11:25:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-67) AS5 plugin:
Invoking the
"Flush" operation for a datasource results in a "plugin error"
In-Reply-To: <5194688.1233677216290.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1528355.1236957924668.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-67:
-------------------------------------
Assignee: Ian Springer
> 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
> Assignee: Ian Springer
> Fix For: 1.2
>
>
> 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
From jira-events at lists.jboss.org Fri Mar 13 17:09:24 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Fri, 13 Mar 2009 17:09:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-96) Read-only
properties should be marked as read-only
In-Reply-To: <15056342.1236880285024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <667913.1236978564317.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12457246#action_12457246 ]
Ondrej ?i?ka commented on EMBJOPR-96:
-------------------------------------
The following properties are re-set to original value after being set.
I don't guarantee they are all intended to be read-only.
They are all from class-loading area.
exportAll: expected 'ALL', found 'NON_EMPTY'
cache: expected 'false', found 'true'
blackList: expected 'false', found 'true'
importAll: expected 'false', found 'true'
name: expected 'my.name', found 'eardeployment.ear'
parentFirst: expected 'false', found 'true'
version: expected '10.9.8.7', found '0.0.0'
> Read-only properties should be marked as read-only
> --------------------------------------------------
>
> Key: EMBJOPR-96
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-96
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
> Assignee: Ondrej ?i?ka
> Fix For: 1.2
>
>
> Currently, read-only properties appear the same as editable ones.
> See e.g. any EAR Configuration, property Name.
> If you edit such property, it simply returns to previous value.
> It should be noted somehow that they are readonly,
> and their input should be disabled.
--
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
From jira-events at lists.jboss.org Fri Mar 13 17:11:24 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Fri, 13 Mar 2009 17:11:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-96) Read-only
properties should be marked as read-only
In-Reply-To: <15056342.1236880285024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8095080.1236978684279.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ondrej ?i?ka reassigned EMBJOPR-96:
-----------------------------------
Assignee: Charles Crouch (was: Ondrej ?i?ka)
> Read-only properties should be marked as read-only
> --------------------------------------------------
>
> Key: EMBJOPR-96
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-96
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
> Assignee: Charles Crouch
> Fix For: 1.2
>
>
> Currently, read-only properties appear the same as editable ones.
> See e.g. any EAR Configuration, property Name.
> If you edit such property, it simply returns to previous value.
> It should be noted somehow that they are readonly,
> and their input should be disabled.
--
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
From jira-events at lists.jboss.org Mon Mar 16 12:12:25 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Mon, 16 Mar 2009 12:12:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-99) Root node
Metrics Trait Values table has inappropriate layout
Message-ID: <6094435.1237219945920.JavaMail.jira@cloud.prod.atl2.jboss.com>
Root node Metrics Trait Values table has inappropriate layout
-------------------------------------------------------------
Key: EMBJOPR-99
URL: https://jira.jboss.org/jira/browse/EMBJOPR-99
Project: Embedded Jopr
Issue Type: Bug
Reporter: Ondrej ?i?ka
The table has 2 rows with 3 rows, making it too wide:
Trait Values
----------------------
Hostname: jawa12.englab.brq.redhat.com | OS Name: Linux | OS Version: 2.6.18-92.1.18.el5xen
Architecture: amd64 | Distribution Name: Red Hat Enterprise Linux Server | Distribution Version: release 5.3 (Tikanga)
Why not simply put it in a single column...
--
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
From jira-events at lists.jboss.org Mon Mar 16 12:20:27 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Mon, 16 Mar 2009 12:20:27 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-99) Root node
Metrics Trait Values table has inappropriate layout
In-Reply-To: <6094435.1237219945920.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19836393.1237220427495.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12457480#action_12457480 ]
Ondrej ?i?ka commented on EMBJOPR-99:
-------------------------------------
resourceInstanceMetrics.xhtml was perhaps intended to show short string or numeric values...
But many of them are long strings.
And it's much more convenient to scroll up/down than to sides.
> Root node Metrics Trait Values table has inappropriate layout
> -------------------------------------------------------------
>
> Key: EMBJOPR-99
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-99
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
>
> The table has 2 rows with 3 rows, making it too wide:
> Trait Values
> ----------------------
> Hostname: jawa12.englab.brq.redhat.com | OS Name: Linux | OS Version: 2.6.18-92.1.18.el5xen
> Architecture: amd64 | Distribution Name: Red Hat Enterprise Linux Server | Distribution Version: release 5.3 (Tikanga)
> Why not simply put it in a single column...
--
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
From jira-events at lists.jboss.org Mon Mar 16 12:59:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Mon, 16 Mar 2009 12:59:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Closed: (EMBJOPR-94)
NoSuchMethodError:
org.jboss.deployers.spi.management.ManagementView.load()V
In-Reply-To: <22354006.1236862301505.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4485246.1237222765924.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch closed EMBJOPR-94.
---------------------------------
Resolution: Out of Date
The JBAS5 console is targetting the 5.1.x branch of JBAS, try the new 5.1beta release that should work better for you.
> NoSuchMethodError: org.jboss.deployers.spi.management.ManagementView.load()V
> ----------------------------------------------------------------------------
>
> Key: EMBJOPR-94
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-94
> Project: Embedded Jopr
> Issue Type: Bug
> Environment: JBossAS 5.0.1, Embjopr trunk
> Reporter: Juergen Zimmermann
>
> When I start JBossAS 5.0.1 (with deploy/jbas5-admin-console.war) I get this stacktrace:
> ...
> 13:42:55,230 INFO [ServletContextListener] Welcome to Seam 2.1.0.SP1
> 13:43:05,843 WARN [Initialization] has been deprecated, use instead
> 13:43:05,843 WARN [Initialization] has been deprecated, use instead
> 13:43:07,439 WARN [Component] Component class should be serializable: contentDisplayAction
> 13:43:07,450 WARN [Component] Component class should be serializable: createContentBackedResourceAction
> 13:43:07,482 WARN [Component] Component class should be serializable: navigationAction
> 13:43:07,492 WARN [Component] Component class should be serializable: operationAction
> 13:43:07,649 WARN [Component] Component class should be serializable: org.jboss.seam.ui.facelet.mockHttpSession
> 13:43:07,670 WARN [Component] Component class should be serializable: resourceConfigurationUIBean
> 13:43:07,683 WARN [Component] Component class should be serializable: updateBackingContentAction
> 13:43:07,694 WARN [PersistentPermissionResolver] no permission store available - please install a PermissionStore with the name 'org.jboss.seam.security.jpaPermissionStore' if persistent permissions are required.
> 13:43:07,761 INFO [BootstrapAction] Bootstrapping Administration Console v1.2.0-SNAPSHOT...
> 13:43:07,993 INFO [PluginContainer] Initializing Plugin Container v1.2.0-SNAPSHOT...
> 13:43:09,332 INFO [InventoryManager] Initializing Inventory Manager...
> 13:43:09,472 WARN [SystemInfoFactory] System info API not accessible on this platform (native shared library not found in java.library.path).
> 13:43:09,520 INFO [InventoryManager] Detected new Platform [Resource[id=-2, type=Windows, key=iwi-w-ziju01-a.ads.hs-karlsruhe.de, name=iwi-w-ziju01-a.ads.hs-karlsruhe.de, parent=, version=Windows Vista 6.0]] - adding to local inventory...
> 13:43:09,553 INFO [InventoryManager] Inventory Manager initialized.
> 13:43:09,562 INFO [ResourceFactoryManager] Initializing
> 13:43:09,562 INFO [ContentManager] Initializing Content Manager...
> 13:43:09,563 INFO [ContentManager] Content Manager initialized...
> 13:43:09,567 INFO [BootstrapAction] Loaded RHQ plugin [JBossAS5].
> 13:43:09,567 INFO [BootstrapAction] Loaded RHQ plugin [Platforms].
> 13:43:09,571 INFO [PluginContainerResourceManager] Discovering Resources...
> 13:43:09,571 INFO [AutoDiscoveryExecutor] Executing server discovery scan...
> 13:43:09,649 INFO [ApplicationServerDiscoveryComponent] Discovering JBossAS Server Resources...
> 13:43:09,676 INFO [ProfileServiceFactory] About to load profile
> 13:43:09,676 WARN [InventoryManager] Failure during discovery for [JBossAS Server] Resources - failed after 28 ms.
> java.lang.NoSuchMethodError: org.jboss.deployers.spi.management.ManagementView.load()V
> at org.rhq.plugins.jbossas5.factory.ProfileServiceFactory.loadProfile(ProfileServiceFactory.java:135)
> at org.rhq.plugins.jbossas5.factory.ProfileServiceFactory.refreshCurrentProfileView(ProfileServiceFactory.java:113)
> at org.rhq.plugins.jbossas5.factory.ProfileServiceFactory.getCurrentProfileView(ProfileServiceFactory.java:100)
> at org.rhq.plugins.jbossas5.factory.ProfileServiceFactory.refreshCurrentProfileView(ProfileServiceFactory.java:113)
> at org.rhq.plugins.jbossas5.ApplicationServerDiscoveryComponent.discoverResources(ApplicationServerDiscoveryComponent.java:74)
> at org.rhq.core.pc.inventory.InventoryManager.executeComponentDiscovery(InventoryManager.java:1542)
> at org.rhq.core.pc.inventory.AutoDiscoveryExecutor.pluginDiscovery(AutoDiscoveryExecutor.java:185)
> at org.rhq.core.pc.inventory.AutoDiscoveryExecutor.call(AutoDiscoveryExecutor.java:104)
> at org.rhq.core.pc.inventory.AutoDiscoveryExecutor.call(AutoDiscoveryExecutor.java:70)
> 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.java:98)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
--
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
From jira-events at lists.jboss.org Mon Mar 16 13:01:26 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Mon, 16 Mar 2009 13:01:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-95) Exploded
application summary shows "Exploded?: no"
In-Reply-To: <11604562.1236874885612.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18067058.1237222886443.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-95:
----------------------------------
Fix Version/s: 1.2
> 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
> Fix For: 1.2
>
>
> 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
From jira-events at lists.jboss.org Mon Mar 16 13:01:28 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Mon, 16 Mar 2009 13:01:28 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-99) Root node
Metrics Trait Values table has inappropriate layout
In-Reply-To: <6094435.1237219945920.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19227429.1237222888804.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-99:
----------------------------------
Component/s: Look 'n' Feel (html/css)
Fix Version/s: 1.2
Assignee: James Cobb
Priority: Minor (was: Major)
Assigning to James for consideration.
> Root node Metrics Trait Values table has inappropriate layout
> -------------------------------------------------------------
>
> Key: EMBJOPR-99
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-99
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Look 'n' Feel (html/css)
> Reporter: Ondrej ?i?ka
> Assignee: James Cobb
> Priority: Minor
> Fix For: 1.2
>
>
> The table has 2 rows with 3 rows, making it too wide:
> Trait Values
> ----------------------
> Hostname: jawa12.englab.brq.redhat.com | OS Name: Linux | OS Version: 2.6.18-92.1.18.el5xen
> Architecture: amd64 | Distribution Name: Red Hat Enterprise Linux Server | Distribution Version: release 5.3 (Tikanga)
> Why not simply put it in a single column...
--
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
From jira-events at lists.jboss.org Mon Mar 16 13:03:30 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Mon, 16 Mar 2009 13:03:30 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-99) Root node
Metrics Trait Values table has inappropriate layout
In-Reply-To: <6094435.1237219945920.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25641945.1237223010644.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12457502#action_12457502 ]
Charles Crouch commented on EMBJOPR-99:
---------------------------------------
Ondrej, could you add a screenshot to help James see the exact issue.
> Root node Metrics Trait Values table has inappropriate layout
> -------------------------------------------------------------
>
> Key: EMBJOPR-99
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-99
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Look 'n' Feel (html/css)
> Reporter: Ondrej ?i?ka
> Assignee: James Cobb
> Priority: Minor
> Fix For: 1.2
>
>
> The table has 2 rows with 3 rows, making it too wide:
> Trait Values
> ----------------------
> Hostname: jawa12.englab.brq.redhat.com | OS Name: Linux | OS Version: 2.6.18-92.1.18.el5xen
> Architecture: amd64 | Distribution Name: Red Hat Enterprise Linux Server | Distribution Version: release 5.3 (Tikanga)
> Why not simply put it in a single column...
--
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
From jira-events at lists.jboss.org Mon Mar 16 13:33:27 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Mon, 16 Mar 2009 13:33:27 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-99) Root node
Metrics Trait Values table has inappropriate layout
In-Reply-To: <6094435.1237219945920.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7883700.1237224807991.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ondrej ?i?ka updated EMBJOPR-99:
--------------------------------
Attachment: Obrazovka-Embedded Jopr Core - Mozilla Firefox.png
Sure, attaching.
> Root node Metrics Trait Values table has inappropriate layout
> -------------------------------------------------------------
>
> Key: EMBJOPR-99
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-99
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Look 'n' Feel (html/css)
> Reporter: Ondrej ?i?ka
> Assignee: James Cobb
> Priority: Minor
> Fix For: 1.2
>
> Attachments: Obrazovka-Embedded Jopr Core - Mozilla Firefox.png
>
>
> The table has 2 rows with 3 rows, making it too wide:
> Trait Values
> ----------------------
> Hostname: jawa12.englab.brq.redhat.com | OS Name: Linux | OS Version: 2.6.18-92.1.18.el5xen
> Architecture: amd64 | Distribution Name: Red Hat Enterprise Linux Server | Distribution Version: release 5.3 (Tikanga)
> Why not simply put it in a single column...
--
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
From jira-events at lists.jboss.org Mon Mar 16 17:37:59 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Mon, 16 Mar 2009 17:37:59 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-88) JBA5 plugin:
Stop reloading
entire profile when getting availability of each resource
In-Reply-To: <30568408.1236382403959.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26784709.1237239479959.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12457559#action_12457559 ]
Charles Crouch commented on EMBJOPR-88:
---------------------------------------
After talking to Scott we don't need to be reloading the profile in order to pickup changes in stats or configurations, only new deployments.
Also when accessing the profile remotely, loading the profile doesnt pull all of the mgmt data across the wire each time, its only when you query for a particular managed object that it is brought from the JBAS instance.
> 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
From jira-events at lists.jboss.org Tue Mar 17 13:46:24 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Tue, 17 Mar 2009 13:46:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-100) After
cancelling Configuration editation, navigate back to Config tab
Message-ID: <6583746.1237311984040.JavaMail.jira@cloud.prod.atl2.jboss.com>
After cancelling Configuration editation, navigate back to Config tab
---------------------------------------------------------------------
Key: EMBJOPR-100
URL: https://jira.jboss.org/jira/browse/EMBJOPR-100
Project: Embedded Jopr
Issue Type: Bug
Reporter: Ondrej ?i?ka
Currently, we get back to Summary tab.
This is both true for Save and Cancel buttons.
Perhaps related to EMBJOPR-89.
--
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
From jira-events at lists.jboss.org Tue Mar 17 15:16:24 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Tue, 17 Mar 2009 15:16:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-92) Nav tree is
not filled right after login
In-Reply-To: <8413057.1236794193967.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17935920.1237317384031.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12457752#action_12457752 ]
Ondrej ?i?ka commented on EMBJOPR-92:
-------------------------------------
Afaik, we have never seen the nav tree being empty after login.
So this is probably not a big issue.
We don't know yet whether the tree will load using AJAX. If so, it's not an issue at all as we can deal with it in tests.
> Nav tree is not filled right after login
> ----------------------------------------
>
> Key: EMBJOPR-92
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-92
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
>
> Sometimes, after logging in, the nav tree is empty - i.e. no 2nd level nodes.
> Possible cause: "hmm, it sounds like discovery hasnt run" (ccrouch)
--
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
From jira-events at lists.jboss.org Tue Mar 17 15:28:23 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Tue, 17 Mar 2009 15:28:23 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-101) Nav tree JS
object (Tree.Item)
is not ready after page refresh, causing ScriptException: TypeError: Cannot
call method "fireExpansionEvent"
Message-ID: <29561323.1237318103990.JavaMail.jira@cloud.prod.atl2.jboss.com>
Nav tree JS object (Tree.Item) is not ready after page refresh, causing ScriptException: TypeError: Cannot call method "fireExpansionEvent"
-------------------------------------------------------------------------------------------------------------------------------------------
Key: EMBJOPR-101
URL: https://jira.jboss.org/jira/browse/EMBJOPR-101
Project: Embedded Jopr
Issue Type: Task
Reporter: Ondrej ?i?ka
Right after page is loaded and test thread is running, JavaScript function object `Tree.Item` is not initialized yet.
This function is created in an externally loaded file, admin-console/a4j/g/3_3_0.GAorg/richfaces/renderkit/html/scripts/tree-item.js .
This problem appears when we click() in tests on some tree node after page load.
It is unlikely that user will be clicking fast enough to trigger this error, moreover IMHO Firefox blocks JS execution until external JS files are all loaded (but not sure), so this is only problem for QA.
Currently we solve this by calling NavTree#waitUntilReady( int intervalMs, int retries ) - e.g. in getNavTreeArrow():
ejtt.navTree.waitUntilReady(100, 15);
--
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
From jira-events at lists.jboss.org Tue Mar 17 15:54:24 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Tue, 17 Mar 2009 15:54:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-101) Nav tree JS
object (Tree.Item)
is not ready after page refresh, causing ScriptException: TypeError: Cannot
call method "fireExpansionEvent"
In-Reply-To: <29561323.1237318103990.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1626551.1237319664385.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ondrej ?i?ka updated EMBJOPR-101:
---------------------------------
Description:
Right after page is loaded and test thread is running, JavaScript function object `Tree.Item` is not initialized yet.
This function is created in an externally loaded file, admin-console/a4j/g/3_3_0.GAorg/richfaces/renderkit/html/scripts/tree-item.js .
This problem appears when we click() in tests on some tree node after page load.
It is unlikely that user will be clicking fast enough to trigger this error, moreover IMHO Firefox blocks JS execution until external JS files are all loaded (but not sure), so this is only problem for QA.
Currently we solve this by calling NavTree#waitUntilReady( int intervalMs, int retries ) - e.g. in getNavTreeArrow():
ejtt.navTree.waitUntilReady(100, 15);
HTMLUnit's JavaScriptEngine#isScriptRunning() doesn't solve this, because AJAX's async calls' TimeOuts are not considered as running javascript (only when the timer's handler is called).
was:
Right after page is loaded and test thread is running, JavaScript function object `Tree.Item` is not initialized yet.
This function is created in an externally loaded file, admin-console/a4j/g/3_3_0.GAorg/richfaces/renderkit/html/scripts/tree-item.js .
This problem appears when we click() in tests on some tree node after page load.
It is unlikely that user will be clicking fast enough to trigger this error, moreover IMHO Firefox blocks JS execution until external JS files are all loaded (but not sure), so this is only problem for QA.
Currently we solve this by calling NavTree#waitUntilReady( int intervalMs, int retries ) - e.g. in getNavTreeArrow():
ejtt.navTree.waitUntilReady(100, 15);
> Nav tree JS object (Tree.Item) is not ready after page refresh, causing ScriptException: TypeError: Cannot call method "fireExpansionEvent"
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-101
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-101
> Project: Embedded Jopr
> Issue Type: Task
> Reporter: Ondrej ?i?ka
>
> Right after page is loaded and test thread is running, JavaScript function object `Tree.Item` is not initialized yet.
> This function is created in an externally loaded file, admin-console/a4j/g/3_3_0.GAorg/richfaces/renderkit/html/scripts/tree-item.js .
> This problem appears when we click() in tests on some tree node after page load.
> It is unlikely that user will be clicking fast enough to trigger this error, moreover IMHO Firefox blocks JS execution until external JS files are all loaded (but not sure), so this is only problem for QA.
> Currently we solve this by calling NavTree#waitUntilReady( int intervalMs, int retries ) - e.g. in getNavTreeArrow():
> ejtt.navTree.waitUntilReady(100, 15);
> HTMLUnit's JavaScriptEngine#isScriptRunning() doesn't solve this, because AJAX's async calls' TimeOuts are not considered as running javascript (only when the timer's handler is called).
--
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
From jira-events at lists.jboss.org Tue Mar 17 17:15:24 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Tue, 17 Mar 2009 17:15:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-89) After
creating a new resource,
the success message no longer gets displayed
In-Reply-To: <23611569.1236611192242.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6817495.1237324524239.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12457775#action_12457775 ]
Farah Juma commented on EMBJOPR-89:
-----------------------------------
Similarly, after successfully configuring a resource, the success message (eg. "Successfully updated...") no longer gets displayed.
> After creating a new resource, the success message no longer gets displayed
> ---------------------------------------------------------------------------
>
> Key: EMBJOPR-89
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-89
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS Branch_5_x r85646, embjopr r193
> Reporter: Farah Juma
> Fix For: 1.2
>
> Attachments: AfterDatasourceCreation.png
>
>
> Steps to reproduce:
> Add a new resource (eg. Local TX Datasource). After clicking on the "Save" button, the resource shows up in the table of resources. However, the success message (eg. "Successfully added new Local TX Datasource") no longer gets displayed.
> eg. AfterDatasourceCreation.png shows the Summary page for "Local TX Datasources" after adding "CreationTest".
--
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
From jira-events at lists.jboss.org Wed Mar 18 09:50:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 18 Mar 2009 09:50:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-102) Decide whether
to continuing have Availability thread running in Embedded
Message-ID: <5012979.1237384224315.JavaMail.jira@cloud.prod.atl2.jboss.com>
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
From jira-events at lists.jboss.org Wed Mar 18 10:32:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 18 Mar 2009 10:32:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-89) After creating
a new resource, the success message no longer gets displayed
In-Reply-To: <23611569.1236611192242.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18749776.1237386745786.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-89:
-------------------------------------
Assignee: Charles Crouch
> After creating a new resource, the success message no longer gets displayed
> ---------------------------------------------------------------------------
>
> Key: EMBJOPR-89
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-89
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS Branch_5_x r85646, embjopr r193
> Reporter: Farah Juma
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Attachments: AfterDatasourceCreation.png
>
>
> Steps to reproduce:
> Add a new resource (eg. Local TX Datasource). After clicking on the "Save" button, the resource shows up in the table of resources. However, the success message (eg. "Successfully added new Local TX Datasource") no longer gets displayed.
> eg. AfterDatasourceCreation.png shows the Summary page for "Local TX Datasources" after adding "CreationTest".
--
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
From jira-events at lists.jboss.org Wed Mar 18 10:32:27 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 18 Mar 2009 10:32:27 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-89) After creating
a new resource, the success message no longer gets displayed
In-Reply-To: <23611569.1236611192242.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23303029.1237386747604.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch resolved EMBJOPR-89.
-----------------------------------
Resolution: Done
r240 don't end the conversation until after the redirect
> After creating a new resource, the success message no longer gets displayed
> ---------------------------------------------------------------------------
>
> Key: EMBJOPR-89
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-89
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS Branch_5_x r85646, embjopr r193
> Reporter: Farah Juma
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Attachments: AfterDatasourceCreation.png
>
>
> Steps to reproduce:
> Add a new resource (eg. Local TX Datasource). After clicking on the "Save" button, the resource shows up in the table of resources. However, the success message (eg. "Successfully added new Local TX Datasource") no longer gets displayed.
> eg. AfterDatasourceCreation.png shows the Summary page for "Local TX Datasources" after adding "CreationTest".
--
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
From jira-events at lists.jboss.org Wed Mar 18 12:19:40 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 18 Mar 2009 12:19:40 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-97) Add
ConnectionProperties resource config property to all Datasources
In-Reply-To: <24370956.1236881004408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32801961.1237393180439.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12457956#action_12457956 ]
Charles Crouch commented on EMBJOPR-97:
---------------------------------------
(10:59:41 AM) ccrouch: you are just exposing the ConnectionProperties attribute as a string ?
(11:00:17 AM) jpederse: yeah, that should be ok for the first pass
(11:00:30 AM) jpederse: the user will get the idea
(11:01:53 AM) ccrouch: have you got an example of what multiple properties would look like?
(11:02:00 AM) ccrouch: what delimiter are you using?
(11:02:56 AM) jpederse: the delimiter can be set by the user
(11:03:20 AM) ccrouch: hmm
(11:04:27 AM) ccrouch: so if i specify a -ds.xml with some conn props in, what is the default delimiter which is used?
(11:04:39 AM) jpederse: wait - I can see that the structure you are properly talking about is a java.util.Properties internally
(11:05:03 AM) jpederse: which gets rendered out by properties.toString()
(11:05:05 AM) ccrouch: that sounds like it
(11:05:57 AM) jpederse: oh ,ok :)
(11:06:46 AM) ccrouch: the hashtable.tostring() method which gets used i dont think is very helpful
(11:07:24 AM) ccrouch: people are going to have parse all the braces and stuff
(11:07:56 AM) ccrouch: i think we should look at making it map, or at least a newline separated string, that would go well in a text box
> Add ConnectionProperties resource config property to all Datasources
> --------------------------------------------------------------------
>
> Key: EMBJOPR-97
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-97
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Reporter: Charles Crouch
> Fix For: 1.2
>
>
> See EMBJOPR-58 for how we noticed this was missing. Need to work out what type it should map to. Right now it seems to a simple one:
> ConnectionProperties.type=SimpleMetaType:java.lang.String:,
--
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
From jira-events at lists.jboss.org Wed Mar 18 12:19:38 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 18 Mar 2009 12:19:38 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-58) AS5 plugin:
Clicking on the "Configuration" tab for a Datasource results in a
"PluginContainerException"
In-Reply-To: <19037367.1229613896768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21867776.1237393178434.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12457955#action_12457955 ]
Charles Crouch commented on EMBJOPR-58:
---------------------------------------
(10:53:32 AM) ccrouch: we should never be accessing stuff through
(10:53:43 AM) ccrouch: config-property.ATTRIBUTE
(10:53:45 AM) ccrouch: right?
(10:54:31 AM) jpederse: right - that is what I told Scott today - we need a READ_ONLY definition
(10:54:55 AM) jpederse: config-property should be read only for datasource
(10:54:56 AM) ccrouch: ah, so config-property would just be read-only?
(10:54:59 AM) ccrouch: gotya
(10:55:07 AM) ccrouch: but used for conn facs?
(10:55:07 AM) jpederse: only read-write for txconnectionfactory
(10:55:12 AM) ccrouch: gotya
(10:55:38 AM) jpederse: the property is there due to the JCA deployers
(10:56:04 AM) jpederse: so I need to mark it as read only - so you dont create code for it
(10:56:31 AM) jpederse: well, you can provide the user with a list of its current content - but that should be all
(10:56:38 AM) ccrouch: right
> AS5 plugin: Clicking on the "Configuration" tab for a Datasource results in a "PluginContainerException"
> --------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-58
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-58
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS 5 trunk r82369, embjopr r76
> Reporter: Farah Juma
> Assignee: Charles Crouch
> Priority: Critical
> Fix For: 1.2
>
>
> When the console is deployed to JBoss AS 5 trunk, the following error message gets displayed after clicking on the "Configuration" tab for any Datasource (eg. DefaultDS):
> "There was an error retrieving the configuration for this resource"
> The following error message appears in the console output:
> 09:14:13,572 ERROR [PluginContainerResourceManager] Error retrieving configuration for resource: Resource[id=-4, type=Local TX Datasource, key=DataSource:LocalTx:DefaultDS, name=DefaultDS, version=?]
> org.rhq.core.clientapi.agent.PluginContainerException: Cannot load Resource configuration for [-4]
> at org.rhq.core.pc.configuration.ConfigurationManager.loadResourceConfiguration(ConfigurationManager.java:174)
> at org.jboss.on.embedded.manager.pc.PluginContainerResourceManager.getResourceConfiguration(PluginContainerResourceManager.java:234)
> at org.jboss.on.embedded.ui.configuration.resource.ResourceConfigurationUIBean.resourceConfiguration(ResourceConfigurationUIBean.java:144)
> 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.seam.util.Reflections.invoke(Reflections.java:22)
> at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
> at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
> at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28)
> at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
> at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77)
> at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
> at org.jboss.seam.core.ConversationInterceptor.aroundInvoke(ConversationInterceptor.java:56)
> 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.ResourceConfigurationUIBean_$$_javassist_10.resourceConfiguration(ResourceConfigurationUIBean_$$_javassist_10.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)
> 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:126)
> 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: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)
> Caused by: java.lang.ClassCastException: [Warning] org.rhq.core.domain.configuration.definition.PropertyDefinitionList
> ... 85 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
From jira-events at lists.jboss.org Wed Mar 18 13:10:24 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Wed, 18 Mar 2009 13:10:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-103) add favicon to
webapp
Message-ID: <31283176.1237396224098.JavaMail.jira@cloud.prod.atl2.jboss.com>
add favicon to webapp
---------------------
Key: EMBJOPR-103
URL: https://jira.jboss.org/jira/browse/EMBJOPR-103
Project: Embedded Jopr
Issue Type: Task
Components: Web App/Integration
Affects Versions: 1.1
Reporter: Ian Springer
Assignee: Ian Springer
Priority: Minor
Fix For: 1.2
We can use the same favicon that enterprise uses (see http://jira.rhq-project.org/browse/RHQ-1806).
--
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
From jira-events at lists.jboss.org Wed Mar 18 13:12:24 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Wed, 18 Mar 2009 13:12:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-103) add favicon to
webapp
In-Reply-To: <31283176.1237396224098.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8488289.1237396344419.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer updated EMBJOPR-103:
---------------------------------
Attachment: favicon.png
Favicon PNG file is attached, and here is the HTML to include it:
> add favicon to webapp
> ---------------------
>
> Key: EMBJOPR-103
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-103
> Project: Embedded Jopr
> Issue Type: Task
> Components: Web App/Integration
> Affects Versions: 1.1
> Reporter: Ian Springer
> Assignee: Ian Springer
> Priority: Minor
> Fix For: 1.2
>
> Attachments: favicon.png
>
> Original Estimate: 10 minutes
> Remaining Estimate: 10 minutes
>
> We can use the same favicon that enterprise uses (see http://jira.rhq-project.org/browse/RHQ-1806).
--
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
From jira-events at lists.jboss.org Wed Mar 18 14:33:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 18 Mar 2009 14:33:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-97) Add
ConnectionProperties resource config property to all Datasources
In-Reply-To: <24370956.1236881004408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14397927.1237401204675.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-97:
----------------------------------
Attachment: screenshot-1.jpg
screenshot-1 is an example of the connection properties element we have in the JBAS4 console. We should investigate having something similar for JBAS5.
> Add ConnectionProperties resource config property to all Datasources
> --------------------------------------------------------------------
>
> Key: EMBJOPR-97
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-97
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Reporter: Charles Crouch
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> See EMBJOPR-58 for how we noticed this was missing. Need to work out what type it should map to. Right now it seems to a simple one:
> ConnectionProperties.type=SimpleMetaType:java.lang.String:,
--
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
From jira-events at lists.jboss.org Wed Mar 18 14:59:26 2009
From: jira-events at lists.jboss.org (Jesper Pedersen (JIRA))
Date: Wed, 18 Mar 2009 14:59:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-97) Add
ConnectionProperties resource config property to all Datasources
In-Reply-To: <24370956.1236881004408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17656673.1237402766682.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458020#action_12458020 ]
Jesper Pedersen commented on EMBJOPR-97:
----------------------------------------
The above comment refers to another property - the properties in question is
@ManagementProperty(name="connection-properties",
description="The DataSource connection properties",
managed=true, includeInTemplate=true)
@ManagementPropertyFactory(ConnectionFactoryProperty.class)
public List getDataSourceConnectionProperties()
backed by org.jboss.resource.deployers.management.ConnectionFactoryProperty
> Add ConnectionProperties resource config property to all Datasources
> --------------------------------------------------------------------
>
> Key: EMBJOPR-97
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-97
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Reporter: Charles Crouch
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> See EMBJOPR-58 for how we noticed this was missing. Need to work out what type it should map to. Right now it seems to a simple one:
> ConnectionProperties.type=SimpleMetaType:java.lang.String:,
--
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
From jira-events at lists.jboss.org Wed Mar 18 16:41:23 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 18 Mar 2009 16:41:23 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-104) Should not be
displaying full stacktraces in the failure message boxes
Message-ID: <29833803.1237408883904.JavaMail.jira@cloud.prod.atl2.jboss.com>
Should not be displaying full stacktraces in the failure message boxes
----------------------------------------------------------------------
Key: EMBJOPR-104
URL: https://jira.jboss.org/jira/browse/EMBJOPR-104
Project: Embedded Jopr
Issue Type: Bug
Components: Web App/Integration
Reporter: Charles Crouch
Fix For: 1.2
See screenshot for an example. We should only be showing a brief message in the message box. We should also log this exception when we catch it, since from looking at the server.log it doesnt look like we're doing that right now.
--
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
From jira-events at lists.jboss.org Wed Mar 18 16:43:37 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 18 Mar 2009 16:43:37 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-104) Should not be
displaying full stacktraces in the failure message boxes
In-Reply-To: <29833803.1237408883904.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16215811.1237409017170.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-104:
-----------------------------------
Attachment: screenshot-1.jpg
> Should not be displaying full stacktraces in the failure message boxes
> ----------------------------------------------------------------------
>
> Key: EMBJOPR-104
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-104
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Reporter: Charles Crouch
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> See screenshot for an example. We should only be showing a brief message in the message box. We should also log this exception when we catch it, since from looking at the server.log it doesnt look like we're doing that right now.
--
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
From jira-events at lists.jboss.org Wed Mar 18 18:52:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 18 Mar 2009 18:52:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-97) Add
ConnectionProperties resource config property to all Datasources
In-Reply-To: <24370956.1236881004408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21335968.1237416744248.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-97:
-------------------------------------
Assignee: Charles Crouch
> Add ConnectionProperties resource config property to all Datasources
> --------------------------------------------------------------------
>
> Key: EMBJOPR-97
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-97
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Reporter: Charles Crouch
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> See EMBJOPR-58 for how we noticed this was missing. Need to work out what type it should map to. Right now it seems to a simple one:
> ConnectionProperties.type=SimpleMetaType:java.lang.String:,
--
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
From jira-events at lists.jboss.org Wed Mar 18 19:01:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 18 Mar 2009 19:01:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-97) Add
ConnectionProperties resource config property to all Datasources
In-Reply-To: <24370956.1236881004408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13961417.1237417284390.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458047#action_12458047 ]
Charles Crouch commented on EMBJOPR-97:
---------------------------------------
I got this partially working locally by specifying
in the rhq-plugin.xml and then fixing AbstractPropertyMapToCompositeValueAdapter Line 61:
MetaType mapMemberMetaType = compositeValue.getMetaType().getType(mapMemberPropName);
so that it is never null. Before when you add a new connection property item then mapMemberMetaType was getting set to null before because compositeValue doesnt contain the new item, e.g. it looks like
MapCompositeMetaType{java.util.Map items=[name=char.encoding type=java.lang.String], [name=something type=java.lang.String]}:{char.encoding=SimpleMetaType:java.lang.String:UTF-8, something=SimpleMetaType:java.lang.String:else}
Next problem is that changes don't appear to be persisting across server restarts. This seems to work for top level simple types, so this could be a specific problem with how we're handling maps, or it could be a PS issue.
> Add ConnectionProperties resource config property to all Datasources
> --------------------------------------------------------------------
>
> Key: EMBJOPR-97
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-97
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Reporter: Charles Crouch
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> See EMBJOPR-58 for how we noticed this was missing. Need to work out what type it should map to. Right now it seems to a simple one:
> ConnectionProperties.type=SimpleMetaType:java.lang.String:,
--
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
From jira-events at lists.jboss.org Wed Mar 18 19:01:26 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 18 Mar 2009 19:01:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Work started: (EMBJOPR-97) Add
ConnectionProperties resource config property to all Datasources
In-Reply-To: <24370956.1236881004408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4207737.1237417286022.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on EMBJOPR-97 started by Charles Crouch.
> Add ConnectionProperties resource config property to all Datasources
> --------------------------------------------------------------------
>
> Key: EMBJOPR-97
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-97
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Reporter: Charles Crouch
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> See EMBJOPR-58 for how we noticed this was missing. Need to work out what type it should map to. Right now it seems to a simple one:
> ConnectionProperties.type=SimpleMetaType:java.lang.String:,
--
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
From jira-events at lists.jboss.org Wed Mar 18 19:08:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 18 Mar 2009 19:08:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-97) Add
ConnectionProperties resource config property to all Datasources
In-Reply-To: <24370956.1236881004408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25709318.1237417704246.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458048#action_12458048 ]
Charles Crouch commented on EMBJOPR-97:
---------------------------------------
Interestingly when you create a new DS the conn props are saved fine, both at the time and after a restart.
> Add ConnectionProperties resource config property to all Datasources
> --------------------------------------------------------------------
>
> Key: EMBJOPR-97
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-97
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Reporter: Charles Crouch
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> See EMBJOPR-58 for how we noticed this was missing. Need to work out what type it should map to. Right now it seems to a simple one:
> ConnectionProperties.type=SimpleMetaType:java.lang.String:,
--
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
From jira-events at lists.jboss.org Wed Mar 18 19:29:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 18 Mar 2009 19:29:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-105) Need service
discovery to run
before filesystem based config changes get picked up
Message-ID: <18129329.1237418964219.JavaMail.jira@cloud.prod.atl2.jboss.com>
Need service discovery to run before filesystem based config changes get picked up
----------------------------------------------------------------------------------
Key: EMBJOPR-105
URL: https://jira.jboss.org/jira/browse/EMBJOPR-105
Project: Embedded Jopr
Issue Type: Task
Reporter: Charles Crouch
Fix For: 1.2
Dont think this is super bad, just making a note of it for now
(6:23:54 PM) ccrouch: yes i edited the ds.xml and then went to the config page and it was updated
(6:25:32 PM) ccrouch: ah, but it needs the discovery to run before it gets updated.
(6:26:10 PM) ccrouch: if you make the change to the ds.xml quickly and reload the config page, it doesnt get updated
--
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
From jira-events at lists.jboss.org Wed Mar 18 20:10:24 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Wed, 18 Mar 2009 20:10:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-106) Add Refresh
button to Summary tab of Applications node and subnodes
Message-ID: <12112208.1237421424334.JavaMail.jira@cloud.prod.atl2.jboss.com>
Add Refresh button to Summary tab of Applications node and subnodes
-------------------------------------------------------------------
Key: EMBJOPR-106
URL: https://jira.jboss.org/jira/browse/EMBJOPR-106
Project: Embedded Jopr
Issue Type: Feature Request
Reporter: Ondrej ?i?ka
Summary tab of Applications node and specific types' subnodes (Wep Applications, etc.) lists the apps and shows their status. It would be convenient to have a refresh button that would stay on the same page (in both meanings - embjopr's page and pagination's page), only re-reading the actual state.
--
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
From jira-events at lists.jboss.org Wed Mar 18 23:11:23 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Wed, 18 Mar 2009 23:11:23 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-107) EmbJopr should
not allow to deploy app that is already deployed
Message-ID: <28914616.1237432283868.JavaMail.jira@cloud.prod.atl2.jboss.com>
EmbJopr should not allow to deploy app that is already deployed
---------------------------------------------------------------
Key: EMBJOPR-107
URL: https://jira.jboss.org/jira/browse/EMBJOPR-107
Project: Embedded Jopr
Issue Type: Feature Request
Reporter: Ondrej ?i?ka
Currently, when app is deployed over an identical app of the same name, EmbJopr fails with an ugly message from JBoss AS (see bellow).
Would be nice if EmbJopr checked if an app of the same name is already deployed, and then, either show readible error message, without attempting to deploy, or even better, ask the user if it should try to re-deploy, and eventually do so.
--------------------------------------------------------------------------------
Failed to create Resource hellothere.war - cause: java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/jbas5-admin-console.war/
-> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/jbas5-admin-console.war/
--------------------------------------------------------------------------------
--
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
From jira-events at lists.jboss.org Thu Mar 19 11:24:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 11:24:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-106) Add Refresh
button to Summary tab of Applications node and subnodes
In-Reply-To: <12112208.1237421424334.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16188505.1237476264769.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458153#action_12458153 ]
Charles Crouch commented on EMBJOPR-106:
----------------------------------------
I think a regular browser refresh should do this. The only thing that doesnt work right now is the pagination, doing F5 results in going back to page 1
> Add Refresh button to Summary tab of Applications node and subnodes
> -------------------------------------------------------------------
>
> Key: EMBJOPR-106
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-106
> Project: Embedded Jopr
> Issue Type: Feature Request
> Reporter: Ondrej ?i?ka
>
> Summary tab of Applications node and specific types' subnodes (Wep Applications, etc.) lists the apps and shows their status. It would be convenient to have a refresh button that would stay on the same page (in both meanings - embjopr's page and pagination's page), only re-reading the actual state.
--
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
From jira-events at lists.jboss.org Thu Mar 19 11:32:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 11:32:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-107) EmbJopr
should not allow to deploy app that is already deployed
In-Reply-To: <28914616.1237432283868.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31041061.1237476745261.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458157#action_12458157 ]
Charles Crouch commented on EMBJOPR-107:
----------------------------------------
I think this would be a useful enhancement in the future. I guess the work flow is something like:
1) users attempt to deploy a new app with the same name as an existing one
2) DeploymentManager responds with a message saying deployment name is duplicated
3) console responds to the user saying the app already exists, please go and update the existing app rather than add a new one
> EmbJopr should not allow to deploy app that is already deployed
> ---------------------------------------------------------------
>
> Key: EMBJOPR-107
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-107
> Project: Embedded Jopr
> Issue Type: Feature Request
> Reporter: Ondrej ?i?ka
>
> Currently, when app is deployed over an identical app of the same name, EmbJopr fails with an ugly message from JBoss AS (see bellow).
> Would be nice if EmbJopr checked if an app of the same name is already deployed, and then, either show readible error message, without attempting to deploy, or even better, ask the user if it should try to re-deploy, and eventually do so.
> --------------------------------------------------------------------------------
> Failed to create Resource hellothere.war - cause: java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS MISSING DEPLOYERS: Name
> vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/jbas5-admin-console.war/
> -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS MISSING DEPLOYERS: Name
> vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/jbas5-admin-console.war/
> --------------------------------------------------------------------------------
--
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
From jira-events at lists.jboss.org Thu Mar 19 11:40:26 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 11:40:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-106) Add Refresh
button to Summary tab of Applications node and subnodes
In-Reply-To: <12112208.1237421424334.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28552688.1237477226266.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458163#action_12458163 ]
Charles Crouch commented on EMBJOPR-106:
----------------------------------------
In JON a browser refresh keeps you on the same page, just need to see if there is any special magic need to get this to work on the regular RF pagination component
> Add Refresh button to Summary tab of Applications node and subnodes
> -------------------------------------------------------------------
>
> Key: EMBJOPR-106
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-106
> Project: Embedded Jopr
> Issue Type: Feature Request
> Reporter: Ondrej ?i?ka
>
> Summary tab of Applications node and specific types' subnodes (Wep Applications, etc.) lists the apps and shows their status. It would be convenient to have a refresh button that would stay on the same page (in both meanings - embjopr's page and pagination's page), only re-reading the actual state.
--
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
From jira-events at lists.jboss.org Thu Mar 19 11:42:29 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 11:42:29 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-105) Need service
discovery to run
before filesystem based config changes get picked up
In-Reply-To: <18129329.1237418964219.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21929932.1237477349851.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-105:
-----------------------------------
Priority: Minor (was: Major)
> Need service discovery to run before filesystem based config changes get picked up
> ----------------------------------------------------------------------------------
>
> Key: EMBJOPR-105
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-105
> Project: Embedded Jopr
> Issue Type: Task
> Reporter: Charles Crouch
> Priority: Minor
> Fix For: 1.2
>
>
> Dont think this is super bad, just making a note of it for now
> (6:23:54 PM) ccrouch: yes i edited the ds.xml and then went to the config page and it was updated
> (6:25:32 PM) ccrouch: ah, but it needs the discovery to run before it gets updated.
> (6:26:10 PM) ccrouch: if you make the change to the ds.xml quickly and reload the config page, it doesnt get updated
--
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
From jira-events at lists.jboss.org Thu Mar 19 11:44:26 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 11:44:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-103) add favicon
to webapp
In-Reply-To: <31283176.1237396224098.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4257500.1237477466534.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458167#action_12458167 ]
Charles Crouch commented on EMBJOPR-103:
----------------------------------------
But shouldn't we use the Embedded Jopr logo, rather than the Jopr one?
> add favicon to webapp
> ---------------------
>
> Key: EMBJOPR-103
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-103
> Project: Embedded Jopr
> Issue Type: Task
> Components: Web App/Integration
> Affects Versions: 1.1
> Reporter: Ian Springer
> Assignee: Ian Springer
> Priority: Minor
> Fix For: 1.2
>
> Attachments: favicon.png
>
> Original Estimate: 10 minutes
> Remaining Estimate: 10 minutes
>
> We can use the same favicon that enterprise uses (see http://jira.rhq-project.org/browse/RHQ-1806).
--
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
From jira-events at lists.jboss.org Thu Mar 19 11:46:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 11:46:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-100) After
cancelling Configuration editation, navigate back to Config tab
In-Reply-To: <6583746.1237311984040.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30969128.1237477584595.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458169#action_12458169 ]
Charles Crouch commented on EMBJOPR-100:
----------------------------------------
This is not related to EMBJOPR-89. This is the expected behaviour. I'm not seeing the pressing need to change it right now, what don't you like?
> After cancelling Configuration editation, navigate back to Config tab
> ---------------------------------------------------------------------
>
> Key: EMBJOPR-100
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-100
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
>
> Currently, we get back to Summary tab.
> This is both true for Save and Cancel buttons.
> Perhaps related to EMBJOPR-89.
--
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
From jira-events at lists.jboss.org Thu Mar 19 11:48:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 11:48:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-97) Add
ConnectionProperties resource config property to all Datasources
In-Reply-To: <24370956.1236881004408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7859916.1237477704149.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458171#action_12458171 ]
Charles Crouch commented on EMBJOPR-97:
---------------------------------------
"Next problem is that changes don't appear to be persisting across server restarts. "
I double checked this and it seems to be failing for all properties so I don't think this is related to conn props.
> Add ConnectionProperties resource config property to all Datasources
> --------------------------------------------------------------------
>
> Key: EMBJOPR-97
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-97
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Reporter: Charles Crouch
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> See EMBJOPR-58 for how we noticed this was missing. Need to work out what type it should map to. Right now it seems to a simple one:
> ConnectionProperties.type=SimpleMetaType:java.lang.String:,
--
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
From jira-events at lists.jboss.org Thu Mar 19 11:52:46 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 11:52:46 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-104) Should not be
displaying full stacktraces in the failure message boxes
In-Reply-To: <29833803.1237408883904.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7290293.1237477966404.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-104:
-----------------------------------
Priority: Minor (was: Major)
> Should not be displaying full stacktraces in the failure message boxes
> ----------------------------------------------------------------------
>
> Key: EMBJOPR-104
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-104
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Reporter: Charles Crouch
> Priority: Minor
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> See screenshot for an example. We should only be showing a brief message in the message box. We should also log this exception when we catch it, since from looking at the server.log it doesnt look like we're doing that right now.
--
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
From jira-events at lists.jboss.org Thu Mar 19 12:11:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 12:11:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-98) Add
config-property resource
configuration property to connection factories
In-Reply-To: <6780440.1236881124395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23517576.1237479085514.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-98:
-------------------------------------
Assignee: Ian Springer
> Add config-property resource configuration property to connection factories
> ---------------------------------------------------------------------------
>
> Key: EMBJOPR-98
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-98
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Reporter: Charles Crouch
> Assignee: Ian Springer
> Fix For: 1.2
>
>
> Looking at
> http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214634#4214634
> implies config-property should only be available for connection factory resource types. Right now its on the "XA ConnectionFactory" service, but I think it should be on the "No TX ConnectionFactory" service too.
--
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
From jira-events at lists.jboss.org Thu Mar 19 12:15:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 12:15:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-108) Add support
for local-tx connection factories
Message-ID: <32885034.1237479324602.JavaMail.jira@cloud.prod.atl2.jboss.com>
Add support for local-tx connection factories
---------------------------------------------
Key: EMBJOPR-108
URL: https://jira.jboss.org/jira/browse/EMBJOPR-108
Project: Embedded Jopr
Issue Type: Task
Reporter: Charles Crouch
Assignee: Ian Springer
Fix For: 1.2
We have support for XA and no-tx ones, we should add local-tx. This page describes the different varieties http://www.jboss.org/community/docs/DOC-9326
--
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
From jira-events at lists.jboss.org Thu Mar 19 13:41:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 13:41:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-37) AS5 plugin:
add support for
the deployDir and deployExploded deploy-time config options when creating
an EAR or WAR (just like we have in the AS4 plugin)
In-Reply-To: <29933902.1226598218791.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26839710.1237484484602.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458212#action_12458212 ]
Charles Crouch commented on EMBJOPR-37:
---------------------------------------
Does the underlying DeploymentManager we are using have support for this?
> AS5 plugin: add support for the deployDir and deployExploded deploy-time config options when creating an EAR or WAR (just like we have in the AS4 plugin)
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-37
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-37
> Project: Embedded Jopr
> Issue Type: Sub-task
> Components: Plugin
> Affects Versions: 1.0
> Reporter: Ian Springer
> Assignee: Ian Springer
> Fix For: 1.2
>
> Original Estimate: 2 hours, 45 minutes
> Remaining Estimate: 2 hours, 45 minutes
>
--
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
From jira-events at lists.jboss.org Thu Mar 19 13:47:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 13:47:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-48) Re-enable
actions on sub-category summary page
Message-ID: <20871703.1237484845439.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-48:
----------------------------------
Fix Version/s: 1.2
(was: 1.1)
Priority: Minor (was: Major)
> Re-enable actions on sub-category summary page
> ----------------------------------------------
>
> Key: EMBJOPR-48
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-48
> Project: Embedded Jopr
> Issue Type: Task
> Affects Versions: 1.0
> Reporter: Charles Crouch
> Assignee: Ian Springer
> Priority: Minor
> Fix For: 1.2
>
> Original Estimate: 5 hours
> Remaining Estimate: 5 hours
>
> Backout the fix for JBMANCON-437 once WAR/EAR creation support is complete.
--
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
From jira-events at lists.jboss.org Thu Mar 19 13:50:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 13:50:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-34) Customize
exceptions instead of exposing JSF internal messages
In-Reply-To: <6605546.1226433589547.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6765025.1237485025128.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458215#action_12458215 ]
Charles Crouch commented on EMBJOPR-34:
---------------------------------------
Ian, didnt you put in place a generic error handling page which would prevent this sort of error from getting displayed?
> 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
> Assignee: Ian Springer
> Fix For: 1.2
>
>
> 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
From jira-events at lists.jboss.org Thu Mar 19 13:52:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 13:52:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-51) JBAS4 console:
Test script execution from embedded
Message-ID: <1331239.1237485144709.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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
From jira-events at lists.jboss.org Thu Mar 19 13:54:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 13:54:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-2) Parent Jira: Add
Content to Embedded Console
Message-ID: <25724169.1237485264978.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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
From jira-events at lists.jboss.org Thu Mar 19 14:05:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 14:05:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-95) Exploded
application summary shows "Exploded?: no"
In-Reply-To: <11604562.1236874885612.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18176654.1237485925328.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-95:
----------------------------------
Attachment: screenshot-1.jpg
Attached screenshot-1 showing the expected result
> 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
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> 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
From jira-events at lists.jboss.org Thu Mar 19 14:05:27 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 14:05:27 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-95) Exploded
application summary shows "Exploded?: no"
In-Reply-To: <11604562.1236874885612.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30256913.1237485927302.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch resolved EMBJOPR-95.
-----------------------------------
Resolution: Cannot Reproduce Bug
Appears to be working now, see screenshot.
> 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
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> 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
From jira-events at lists.jboss.org Thu Mar 19 14:13:24 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Thu, 19 Mar 2009 14:13:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Work started: (EMBJOPR-67) AS5
plugin: Invoking the
"Flush" operation for a datasource results in a "plugin error"
In-Reply-To: <5194688.1233677216290.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28996939.1237486404419.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on EMBJOPR-67 started by Ian Springer.
> 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
> Assignee: Ian Springer
> Fix For: 1.2
>
>
> 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
From jira-events at lists.jboss.org Thu Mar 19 14:17:53 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 14:17:53 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-78) More page size
options, and make default page size larger (20)
In-Reply-To: <22613683.1234999666250.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1516489.1237486673334.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-78:
----------------------------------
Priority: Minor (was: Major)
> 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
> Priority: Minor
> Fix For: 1.2
>
>
> 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
From jira-events at lists.jboss.org Thu Mar 19 14:17:58 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 14:17:58 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-81) Exception
thrown when UPDATING .ear from Content Tab
In-Reply-To: <32547805.1235148710204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7280124.1237486678906.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-81:
-------------------------------------
Assignee: Ian Springer
With Ian for investigation
> Exception thrown when UPDATING .ear from Content Tab
> ----------------------------------------------------
>
> Key: EMBJOPR-81
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-81
> Project: Embedded Jopr
> Issue Type: Bug
> Environment: Boss AS Branch_5_x r84532, embjopr r162
> Reporter: Shelly McGowan
> Assignee: Ian Springer
> Fix For: 1.2
>
> Attachments: jbossas-default-server.log, resourceInstanceContent.seam.log
>
>
> Navigating to the Content Tab to update an existing resource results in a ServletException (see attached file, resourceInstanceContent.seam.log. While the exception is thrown on this action, it appears to be the result of a previous exception during the navigation to the Content tab. The Content tab is not consistently available but is during a specific navigation sequence. I'll identify the specific navigation sequence to reproduce and update this issue. I've also attached the jbossas server.log snippet.
--
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
From jira-events at lists.jboss.org Thu Mar 19 14:18:01 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 14:18:01 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-81) Exception
thrown when UPDATING .ear from Content Tab
In-Reply-To: <32547805.1235148710204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15410710.1237486681145.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-81:
----------------------------------
Priority: Critical (was: Major)
> Exception thrown when UPDATING .ear from Content Tab
> ----------------------------------------------------
>
> Key: EMBJOPR-81
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-81
> Project: Embedded Jopr
> Issue Type: Bug
> Environment: Boss AS Branch_5_x r84532, embjopr r162
> Reporter: Shelly McGowan
> Assignee: Ian Springer
> Priority: Critical
> Fix For: 1.2
>
> Attachments: jbossas-default-server.log, resourceInstanceContent.seam.log
>
>
> Navigating to the Content Tab to update an existing resource results in a ServletException (see attached file, resourceInstanceContent.seam.log. While the exception is thrown on this action, it appears to be the result of a previous exception during the navigation to the Content tab. The Content tab is not consistently available but is during a specific navigation sequence. I'll identify the specific navigation sequence to reproduce and update this issue. I've also attached the jbossas server.log snippet.
--
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
From jira-events at lists.jboss.org Thu Mar 19 14:50:37 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 14:50:37 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-88) JBA5 plugin:
Stop reloading
entire profile when getting availability of each resource
In-Reply-To: <30568408.1236382403959.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12059596.1237488637264.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-88:
-------------------------------------
Assignee: Charles Crouch
> 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
> Assignee: 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
From jira-events at lists.jboss.org Thu Mar 19 15:03:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 15:03:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-69) Configuration
properties no longer get displayed when creating a new datasource
In-Reply-To: <32158737.1233857326007.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26602964.1237489404664.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-69:
----------------------------------
Summary: Configuration properties no longer get displayed when creating a new datasource (was: Connection properties no longer get displayed when creating a new datasource)
> Configuration 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
> Assignee: Charles Crouch
> Priority: Blocker
> Fix For: 1.2
>
> Attachments: createDatasource.png, ListStatisticsResults.png
>
>
> 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
From jira-events at lists.jboss.org Thu Mar 19 15:05:28 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 15:05:28 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-97) Add
ConnectionProperties resource config property to all Datasources
In-Reply-To: <24370956.1236881004408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32102743.1237489528058.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458232#action_12458232 ]
Charles Crouch commented on EMBJOPR-97:
---------------------------------------
Jopr r287 add support for connection properties
> Add ConnectionProperties resource config property to all Datasources
> --------------------------------------------------------------------
>
> Key: EMBJOPR-97
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-97
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Reporter: Charles Crouch
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> See EMBJOPR-58 for how we noticed this was missing. Need to work out what type it should map to. Right now it seems to a simple one:
> ConnectionProperties.type=SimpleMetaType:java.lang.String:,
--
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
From jira-events at lists.jboss.org Thu Mar 19 15:12:41 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 15:12:41 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Work started: (EMBJOPR-88) JBA5
plugin: Stop reloading
entire profile when getting availability of each resource
In-Reply-To: <30568408.1236382403959.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1508868.1237489961327.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on EMBJOPR-88 started by Charles Crouch.
> 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
> Assignee: 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
From jira-events at lists.jboss.org Thu Mar 19 15:12:39 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 15:12:39 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-97) Add
ConnectionProperties resource config property to all Datasources
In-Reply-To: <24370956.1236881004408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14803418.1237489959340.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458235#action_12458235 ]
Charles Crouch commented on EMBJOPR-97:
---------------------------------------
Speaking to emanuel there appears to be a bug around updated properties when the app server is restarted. So I think this issue is as complete as its going to get until that is resolved.
(10:46:02 AM) ccrouch: so when I create a new Datasource, that all gets saved across a restart fine
(10:46:15 AM) ccrouch: its only when i update an existing one when i see the problem
(10:52:33 AM) emuckenhuber: trying that right now
(10:54:06 AM) emuckenhuber: true that's gone
(10:54:59 AM) emuckenhuber: although the persisted information has the correct value
(10:55:16 AM) ccrouch: ok well i guess thats a good thing
(10:55:23 AM) ccrouch: that you can reproduce it
(10:57:19 AM) emuckenhuber: hmm okay this seems to be a bug
(10:57:41 AM) ccrouch: ok, will you raise a jira? and link it to 6620?
(10:57:50 AM) ccrouch: or do you want me to?
(10:58:49 AM) emuckenhuber: hmm i can do that myself - i just need to figure out, what you are doing differently :)
(10:59:28 AM) ccrouch: oh, so in your tests this works?
(10:59:35 AM) emuckenhuber: yes
(10:59:39 AM) ccrouch: with both new and existing resources?
(11:00:23 AM) emuckenhuber: hmm in the end it should not matter - but i'm just testing existing datasources
(11:01:13 AM) ccrouch: rats, thats where i see the problem
(11:01:28 AM) ccrouch: that sounds like its an issue with our usage :-(
(11:02:16 AM) emuckenhuber: okay, but that's good to know i'll add some tests for applyTemplate and updateComponent
(11:02:57 AM) ccrouch: ok cool
(11:03:30 AM) emuckenhuber: and i think i know where it's failing
(11:03:45 AM) ccrouch: where?
(11:04:39 AM) emuckenhuber: well it's failing when trying to reconstruct a null managed object
(11:05:08 AM) ccrouch: hmm
(11:05:21 AM) ccrouch: this is inside the PS?
(11:05:28 AM) ccrouch: as opposed to the console?
(11:06:29 AM) emuckenhuber: well this happens in the attachment persistence, when restoring the attachment
(11:06:45 AM) emuckenhuber: it should not try to reconstruct it when it's null
(11:06:53 AM) ccrouch: ok
(11:24:04 AM) emuckenhuber: okay, easy to fix - now i need an testcase :)
(11:25:09 AM) ccrouch: yep, i'd really like to know what the console is doing differently from your tests
(11:28:10 AM) emuckenhuber: looks like the only difference is that there is no security domain created
> Add ConnectionProperties resource config property to all Datasources
> --------------------------------------------------------------------
>
> Key: EMBJOPR-97
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-97
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Reporter: Charles Crouch
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> See EMBJOPR-58 for how we noticed this was missing. Need to work out what type it should map to. Right now it seems to a simple one:
> ConnectionProperties.type=SimpleMetaType:java.lang.String:,
--
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
From jira-events at lists.jboss.org Thu Mar 19 15:12:43 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 15:12:43 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-88) JBA5 plugin:
Stop reloading
entire profile when getting availability of each resource
In-Reply-To: <30568408.1236382403959.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9724511.1237489963800.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458237#action_12458237 ]
Charles Crouch commented on EMBJOPR-88:
---------------------------------------
Jopr r286 starts this work
> 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
> Assignee: 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
From jira-events at lists.jboss.org Thu Mar 19 15:14:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 15:14:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-88) JBA5 plugin:
Stop reloading
entire profile when getting availability of each resource
In-Reply-To: <30568408.1236382403959.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20203725.1237490065688.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458238#action_12458238 ]
Charles Crouch commented on EMBJOPR-88:
---------------------------------------
starts this work... by commenting out seemingly unnecessary calls to refreshCurrentProfileView
> 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
> Assignee: 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
From jira-events at lists.jboss.org Thu Mar 19 15:22:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 15:22:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-85) Investigate
impact of deploying embedded jopr in jbas5 on start up time
In-Reply-To: <9509053.1236105804775.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29912291.1237490544591.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458240#action_12458240 ]
Charles Crouch commented on EMBJOPR-85:
---------------------------------------
One optimization is to remove the call to generatePluginDescriptor(resourceDiscoveryContext); from ApplicationServerDiscoveryComponent
> Investigate impact of deploying embedded jopr in jbas5 on start up time
> -----------------------------------------------------------------------
>
> Key: EMBJOPR-85
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-85
> Project: Embedded Jopr
> Issue Type: Task
> Components: Web App/Integration
> Affects Versions: 1.1
> Reporter: Charles Crouch
> Priority: Critical
> Fix For: 1.2
>
>
> Things to look at:
> a) reducing start up time and moving more processing to initial page request
> b) how much does Seam initialization contribute
--
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
From jira-events at lists.jboss.org Thu Mar 19 15:48:25 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Thu, 19 Mar 2009 15:48:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-67) AS5 plugin:
Invoking the
"Flush" operation for a datasource results in a "plugin error"
In-Reply-To: <5194688.1233677216290.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14897204.1237492105049.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer resolved EMBJOPR-67.
---------------------------------
Resolution: Done
Done - RHQ r3459 and EmbJopr r288.
> 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
> Assignee: Ian Springer
> Fix For: 1.2
>
>
> 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
From jira-events at lists.jboss.org Thu Mar 19 15:50:25 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Thu, 19 Mar 2009 15:50:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Work started: (EMBJOPR-81) Exception
thrown when UPDATING .ear from Content Tab
In-Reply-To: <32547805.1235148710204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22531035.1237492225022.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on EMBJOPR-81 started by Ian Springer.
> Exception thrown when UPDATING .ear from Content Tab
> ----------------------------------------------------
>
> Key: EMBJOPR-81
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-81
> Project: Embedded Jopr
> Issue Type: Bug
> Environment: Boss AS Branch_5_x r84532, embjopr r162
> Reporter: Shelly McGowan
> Assignee: Ian Springer
> Priority: Critical
> Fix For: 1.2
>
> Attachments: jbossas-default-server.log, resourceInstanceContent.seam.log
>
>
> Navigating to the Content Tab to update an existing resource results in a ServletException (see attached file, resourceInstanceContent.seam.log. While the exception is thrown on this action, it appears to be the result of a previous exception during the navigation to the Content tab. The Content tab is not consistently available but is during a specific navigation sequence. I'll identify the specific navigation sequence to reproduce and update this issue. I've also attached the jbossas server.log snippet.
--
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
From jira-events at lists.jboss.org Thu Mar 19 15:58:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 15:58:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-41) Add support for
JVM monitoring to the JBAS5 console profile
Message-ID: <23096795.1237492705264.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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
From jira-events at lists.jboss.org Thu Mar 19 15:58:28 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Thu, 19 Mar 2009 15:58:28 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-102) Decide whether
to continuing have Availability thread running in Embedded
In-Reply-To: <5012979.1237384224315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12422418.1237492708863.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-102:
-----------------------------------
Priority: Critical (was: Major)
Making this critical so we make sure to triage it.
> 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
> Priority: Critical
> 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
From jira-events at lists.jboss.org Thu Mar 19 19:39:26 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Thu, 19 Mar 2009 19:39:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-81) Exception
thrown when UPDATING .ear from Content Tab
In-Reply-To: <32547805.1235148710204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14280233.1237505966307.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer reassigned EMBJOPR-81:
-----------------------------------
Assignee: Shelly McGowan (was: Ian Springer)
> Exception thrown when UPDATING .ear from Content Tab
> ----------------------------------------------------
>
> Key: EMBJOPR-81
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-81
> Project: Embedded Jopr
> Issue Type: Bug
> Environment: Boss AS Branch_5_x r84532, embjopr r162
> Reporter: Shelly McGowan
> Assignee: Shelly McGowan
> Priority: Critical
> Fix For: 1.2
>
> Attachments: jbossas-default-server.log, resourceInstanceContent.seam.log
>
>
> Navigating to the Content Tab to update an existing resource results in a ServletException (see attached file, resourceInstanceContent.seam.log. While the exception is thrown on this action, it appears to be the result of a previous exception during the navigation to the Content tab. The Content tab is not consistently available but is during a specific navigation sequence. I'll identify the specific navigation sequence to reproduce and update this issue. I've also attached the jbossas server.log snippet.
--
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
From jira-events at lists.jboss.org Thu Mar 19 19:39:24 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Thu, 19 Mar 2009 19:39:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-81) Exception
thrown when UPDATING .ear from Content Tab
In-Reply-To: <32547805.1235148710204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <343159.1237505964689.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458281#action_12458281 ]
Ian Springer commented on EMBJOPR-81:
-------------------------------------
Shelly, I wasn't able to reproduce. I was able to successfully update an EAR. So it looks like I'm going to need the navigation sequence that gets things into the bad state.
> Exception thrown when UPDATING .ear from Content Tab
> ----------------------------------------------------
>
> Key: EMBJOPR-81
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-81
> Project: Embedded Jopr
> Issue Type: Bug
> Environment: Boss AS Branch_5_x r84532, embjopr r162
> Reporter: Shelly McGowan
> Assignee: Ian Springer
> Priority: Critical
> Fix For: 1.2
>
> Attachments: jbossas-default-server.log, resourceInstanceContent.seam.log
>
>
> Navigating to the Content Tab to update an existing resource results in a ServletException (see attached file, resourceInstanceContent.seam.log. While the exception is thrown on this action, it appears to be the result of a previous exception during the navigation to the Content tab. The Content tab is not consistently available but is during a specific navigation sequence. I'll identify the specific navigation sequence to reproduce and update this issue. I've also attached the jbossas server.log snippet.
--
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
From jira-events at lists.jboss.org Thu Mar 19 22:08:24 2009
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Thu, 19 Mar 2009 22:08:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-81) Exception
thrown when UPDATING .ear from Content Tab
In-Reply-To: <32547805.1235148710204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9577923.1237514904845.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shelly McGowan updated EMBJOPR-81:
----------------------------------
Environment:
JBoss AS Branch_5_x r84532, embjopr r162
Still seen with: JBoss AS Branch 5_x r86127, embjopr r242
was:Boss AS Branch_5_x r84532, embjopr r162
Ian, the navigation to the Content Tab previously was not consistently accessible. That has since been resolved. This issue, however, is still reproducable using these steps.
Navigate to Applications ==> Enterprise Applications
Add New Resource
When the .ear is "UP", click on the .ear name which brings you to the .ear Summary Tab.
Select the Content Tab
BROWSE to update the .ear - selecting the same .ear
click UPDATE
Which provokes:
The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
root cause
org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
org.jboss.seam.Component.newInstance(Component.java:2096)
root cause
java.lang.NullPointerException
org.jboss.seam.exception.Exceptions.parse(Exceptions.java:195)
org.jboss.seam.exception.Exceptions.initialize(Exceptions.java:119)
Server side:
javax.el.ELException: org.jboss.seam.RequiredException: @Out attribute requires non-null value: updateBackingContentAction.packageDetails
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.Page.preRender(Page.java:289)
at org.jboss.seam.navigation.Pages.preRender(Pages.java:369)
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)
javax.servlet.ServletException: /secure/resourceInstanceContent.xhtml @67,56 contentType="#{updateBackingContentAction.fileContentType}": Error writing 'fileContentType' on type org.jboss.on.embedded.ui.content.UpdateBackingContentAction_$$_javassist_13
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:277)
Caused by: javax.el.ELException: /secure/resourceInstanceContent.xhtml @67,56 contentType="#{updateBackingContentAction.fileContentType}": Error writing 'fileContentType' on type org.jboss.on.embedded.ui.content.UpdateBackingContentAction_$$_javassist_13
at com.sun.facelets.el.TagValueExpression.setValue(TagValueExpression.java:101)
at org.jboss.seam.ui.component.UIFileUpload.processUpdates(UIFileUpload.java:38)
at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081)
at javax.faces.component.UIForm.processUpdates(UIForm.java:261)
at org.ajax4jsf.component.AjaxViewRoot$2.invokeContextCallback(AjaxViewRoot.java:416)
at org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:238)
at org.ajax4jsf.component.AjaxViewRoot.processUpdates(AjaxViewRoot.java:432)
at com.sun.faces.lifecycle.UpdateModelValuesPhase.execute(UpdateModelValuesPhase.java:78)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
> Exception thrown when UPDATING .ear from Content Tab
> ----------------------------------------------------
>
> Key: EMBJOPR-81
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-81
> Project: Embedded Jopr
> Issue Type: Bug
> Environment: JBoss AS Branch_5_x r84532, embjopr r162
> Still seen with: JBoss AS Branch 5_x r86127, embjopr r242
> Reporter: Shelly McGowan
> Assignee: Shelly McGowan
> Priority: Critical
> Fix For: 1.2
>
> Attachments: jbossas-default-server.log, resourceInstanceContent.seam.log
>
>
> Navigating to the Content Tab to update an existing resource results in a ServletException (see attached file, resourceInstanceContent.seam.log. While the exception is thrown on this action, it appears to be the result of a previous exception during the navigation to the Content tab. The Content tab is not consistently available but is during a specific navigation sequence. I'll identify the specific navigation sequence to reproduce and update this issue. I've also attached the jbossas server.log snippet.
--
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
From jira-events at lists.jboss.org Thu Mar 19 22:14:31 2009
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Thu, 19 Mar 2009 22:14:31 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-81) Exception
thrown when UPDATING .ear from Content Tab
In-Reply-To: <32547805.1235148710204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32186097.1237515271964.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shelly McGowan updated EMBJOPR-81:
----------------------------------
Assignee: Ian Springer (was: Shelly McGowan)
> Exception thrown when UPDATING .ear from Content Tab
> ----------------------------------------------------
>
> Key: EMBJOPR-81
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-81
> Project: Embedded Jopr
> Issue Type: Bug
> Environment: JBoss AS Branch_5_x r84532, embjopr r162
> Still seen with: JBoss AS Branch 5_x r86127, embjopr r242
> Reporter: Shelly McGowan
> Assignee: Ian Springer
> Priority: Critical
> Fix For: 1.2
>
> Attachments: jbossas-default-server.log, resourceInstanceContent.seam.log
>
>
> Navigating to the Content Tab to update an existing resource results in a ServletException (see attached file, resourceInstanceContent.seam.log. While the exception is thrown on this action, it appears to be the result of a previous exception during the navigation to the Content tab. The Content tab is not consistently available but is during a specific navigation sequence. I'll identify the specific navigation sequence to reproduce and update this issue. I've also attached the jbossas server.log snippet.
--
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
From jira-events at lists.jboss.org Thu Mar 19 22:16:28 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Thu, 19 Mar 2009 22:16:28 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-109) HTTP Status
500 - Error in Seam/JSF
In-Reply-To: <31887082.1237515384829.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27439087.1237515388862.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ondrej ?i?ka updated EMBJOPR-109:
---------------------------------
Attachment: formNotFound-navTreeForm.html
> HTTP Status 500 - Error in Seam/JSF
> -----------------------------------
>
> Key: EMBJOPR-109
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-109
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
> Attachments: formNotFound-navTreeForm.html, log.txt
>
>
> Following exception appears occasionally in WAR tests.
> Here's only what goes to HTTP output; Relevant log part attached.
> HTTP Status 500 -
> type Exception report
> message
> description The server encountered an internal error () that prevented it from fulfilling this request.
> exception
> javax.servlet.ServletException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:126)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> root cause
> org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
> org.jboss.seam.Component.newInstance(Component.java:2096)
> org.jboss.seam.Component.getInstance(Component.java:1978)
> org.jboss.seam.Component.getInstance(Component.java:1957)
> org.jboss.seam.Component.getInstance(Component.java:1951)
> org.jboss.seam.Component.getInstance(Component.java:1924)
> org.jboss.seam.Component.getInstance(Component.java:1919)
> org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256)
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> root cause
> java.lang.NullPointerException
> org.jboss.seam.exception.Exceptions.parse(Exceptions.java:195)
> org.jboss.seam.exception.Exceptions.initialize(Exceptions.java:119)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:585)
> org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
> org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138)
> org.jboss.seam.Component.callComponentMethod(Component.java:2201)
> org.jboss.seam.Component.callCreateMethod(Component.java:2124)
> org.jboss.seam.Component.newInstance(Component.java:2084)
> org.jboss.seam.Component.getInstance(Component.java:1978)
> org.jboss.seam.Component.getInstance(Component.java:1957)
> org.jboss.seam.Component.getInstance(Component.java:1951)
> org.jboss.seam.Component.getInstance(Component.java:1924)
> org.jboss.seam.Component.getInstance(Component.java:1919)
> org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256)
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> note The full stack trace of the root cause is available in the JBoss Web/2.1.2.GA logs.
> JBoss Web/2.1.2.GA
--
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
From jira-events at lists.jboss.org Thu Mar 19 22:16:24 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Thu, 19 Mar 2009 22:16:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-109) HTTP Status
500 - Error in Seam/JSF
Message-ID: <31887082.1237515384829.JavaMail.jira@cloud.prod.atl2.jboss.com>
HTTP Status 500 - Error in Seam/JSF
-----------------------------------
Key: EMBJOPR-109
URL: https://jira.jboss.org/jira/browse/EMBJOPR-109
Project: Embedded Jopr
Issue Type: Bug
Reporter: Ondrej ?i?ka
Attachments: formNotFound-navTreeForm.html, log.txt
Following exception appears occasionally in WAR tests.
Here's only what goes to HTTP output; Relevant log part attached.
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:126)
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
org.jboss.seam.Component.newInstance(Component.java:2096)
org.jboss.seam.Component.getInstance(Component.java:1978)
org.jboss.seam.Component.getInstance(Component.java:1957)
org.jboss.seam.Component.getInstance(Component.java:1951)
org.jboss.seam.Component.getInstance(Component.java:1924)
org.jboss.seam.Component.getInstance(Component.java:1919)
org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256)
org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
java.lang.NullPointerException
org.jboss.seam.exception.Exceptions.parse(Exceptions.java:195)
org.jboss.seam.exception.Exceptions.initialize(Exceptions.java:119)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138)
org.jboss.seam.Component.callComponentMethod(Component.java:2201)
org.jboss.seam.Component.callCreateMethod(Component.java:2124)
org.jboss.seam.Component.newInstance(Component.java:2084)
org.jboss.seam.Component.getInstance(Component.java:1978)
org.jboss.seam.Component.getInstance(Component.java:1957)
org.jboss.seam.Component.getInstance(Component.java:1951)
org.jboss.seam.Component.getInstance(Component.java:1924)
org.jboss.seam.Component.getInstance(Component.java:1919)
org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256)
org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
note The full stack trace of the root cause is available in the JBoss Web/2.1.2.GA logs.
JBoss Web/2.1.2.GA
--
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
From jira-events at lists.jboss.org Thu Mar 19 22:16:27 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Thu, 19 Mar 2009 22:16:27 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-109) HTTP Status
500 - Error in Seam/JSF
In-Reply-To: <31887082.1237515384829.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27764509.1237515387015.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ondrej ?i?ka updated EMBJOPR-109:
---------------------------------
Attachment: log.txt
> HTTP Status 500 - Error in Seam/JSF
> -----------------------------------
>
> Key: EMBJOPR-109
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-109
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
> Attachments: formNotFound-navTreeForm.html, log.txt
>
>
> Following exception appears occasionally in WAR tests.
> Here's only what goes to HTTP output; Relevant log part attached.
> HTTP Status 500 -
> type Exception report
> message
> description The server encountered an internal error () that prevented it from fulfilling this request.
> exception
> javax.servlet.ServletException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:126)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> root cause
> org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
> org.jboss.seam.Component.newInstance(Component.java:2096)
> org.jboss.seam.Component.getInstance(Component.java:1978)
> org.jboss.seam.Component.getInstance(Component.java:1957)
> org.jboss.seam.Component.getInstance(Component.java:1951)
> org.jboss.seam.Component.getInstance(Component.java:1924)
> org.jboss.seam.Component.getInstance(Component.java:1919)
> org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256)
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> root cause
> java.lang.NullPointerException
> org.jboss.seam.exception.Exceptions.parse(Exceptions.java:195)
> org.jboss.seam.exception.Exceptions.initialize(Exceptions.java:119)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:585)
> org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
> org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138)
> org.jboss.seam.Component.callComponentMethod(Component.java:2201)
> org.jboss.seam.Component.callCreateMethod(Component.java:2124)
> org.jboss.seam.Component.newInstance(Component.java:2084)
> org.jboss.seam.Component.getInstance(Component.java:1978)
> org.jboss.seam.Component.getInstance(Component.java:1957)
> org.jboss.seam.Component.getInstance(Component.java:1951)
> org.jboss.seam.Component.getInstance(Component.java:1924)
> org.jboss.seam.Component.getInstance(Component.java:1919)
> org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256)
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> note The full stack trace of the root cause is available in the JBoss Web/2.1.2.GA logs.
> JBoss Web/2.1.2.GA
--
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
From jira-events at lists.jboss.org Thu Mar 19 23:16:37 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Thu, 19 Mar 2009 23:16:37 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-95) Exploded
application summary shows "Exploded?: no"
In-Reply-To: <11604562.1236874885612.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9758860.1237518997401.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ondrej ?i?ka resolved EMBJOPR-95.
---------------------------------
Resolution: Cannot Reproduce Bug
Sorry for bogus report, bad test.
> 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
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> 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
From jira-events at lists.jboss.org Thu Mar 19 23:34:25 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Thu, 19 Mar 2009 23:34:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-85) Investigate
impact of deploying embedded jopr in jbas5 on start up time
In-Reply-To: <9509053.1236105804775.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30555217.1237520065947.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458321#action_12458321 ]
Ian Springer commented on EMBJOPR-85:
-------------------------------------
generatePluginDescriptor() is now only called if jbmancon.debug sysprop is set to "true" - Jopr r294.
> Investigate impact of deploying embedded jopr in jbas5 on start up time
> -----------------------------------------------------------------------
>
> Key: EMBJOPR-85
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-85
> Project: Embedded Jopr
> Issue Type: Task
> Components: Web App/Integration
> Affects Versions: 1.1
> Reporter: Charles Crouch
> Priority: Critical
> Fix For: 1.2
>
>
> Things to look at:
> a) reducing start up time and moving more processing to initial page request
> b) how much does Seam initialization contribute
--
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
From jira-events at lists.jboss.org Thu Mar 19 22:55:24 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Thu, 19 Mar 2009 22:55:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Reopened: (EMBJOPR-95) Exploded
application summary shows "Exploded?: no"
In-Reply-To: <11604562.1236874885612.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <868601.1237517724383.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ondrej ?i?ka reopened EMBJOPR-95:
---------------------------------
Assignee: Charles Crouch
See testUnzippedWarReportedAsExploded of WarTest and EarTest.
I test it by hot-deploying a directory - see testdata/*ar/*.zip
testUnzippedWarReportedAsExploded(org.jboss.jopr.jsfunit.as5.WarTest) Time elapsed: 242.447 sec <<< FAILURE!
junit.framework.ComparisonFailure: 'Exploded?' should be 'yes' expected: but was:
at junit.framework.Assert.assertEquals(Assert.java:81)
at org.jboss.jopr.jsfunit.as5.WarTest.testUnzippedWarReportedAsExploded(WarTest.java:540)
> 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
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> 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
From jira-events at lists.jboss.org Thu Mar 19 23:24:24 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Thu, 19 Mar 2009 23:24:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-109) HTTP Status
500 - Error in Seam/JSF
In-Reply-To: <31887082.1237515384829.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10295397.1237519464694.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458318#action_12458318 ]
Ondrej ?i?ka commented on EMBJOPR-109:
--------------------------------------
Also reproduced manually.
> HTTP Status 500 - Error in Seam/JSF
> -----------------------------------
>
> Key: EMBJOPR-109
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-109
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
> Attachments: formNotFound-navTreeForm.html, log.txt
>
>
> Following exception appears occasionally in WAR tests.
> Here's only what goes to HTTP output; Relevant log part attached.
> HTTP Status 500 -
> type Exception report
> message
> description The server encountered an internal error () that prevented it from fulfilling this request.
> exception
> javax.servlet.ServletException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:126)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> root cause
> org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
> org.jboss.seam.Component.newInstance(Component.java:2096)
> org.jboss.seam.Component.getInstance(Component.java:1978)
> org.jboss.seam.Component.getInstance(Component.java:1957)
> org.jboss.seam.Component.getInstance(Component.java:1951)
> org.jboss.seam.Component.getInstance(Component.java:1924)
> org.jboss.seam.Component.getInstance(Component.java:1919)
> org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256)
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> root cause
> java.lang.NullPointerException
> org.jboss.seam.exception.Exceptions.parse(Exceptions.java:195)
> org.jboss.seam.exception.Exceptions.initialize(Exceptions.java:119)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:585)
> org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
> org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138)
> org.jboss.seam.Component.callComponentMethod(Component.java:2201)
> org.jboss.seam.Component.callCreateMethod(Component.java:2124)
> org.jboss.seam.Component.newInstance(Component.java:2084)
> org.jboss.seam.Component.getInstance(Component.java:1978)
> org.jboss.seam.Component.getInstance(Component.java:1957)
> org.jboss.seam.Component.getInstance(Component.java:1951)
> org.jboss.seam.Component.getInstance(Component.java:1924)
> org.jboss.seam.Component.getInstance(Component.java:1919)
> org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256)
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> note The full stack trace of the root cause is available in the JBoss Web/2.1.2.GA logs.
> JBoss Web/2.1.2.GA
--
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
From jira-events at lists.jboss.org Thu Mar 19 22:47:24 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Thu, 19 Mar 2009 22:47:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-110) WAR Path
property leading slash trimmed: Path: home/brq/...
Message-ID: <10894404.1237517244540.JavaMail.jira@cloud.prod.atl2.jboss.com>
WAR Path property leading slash trimmed: Path: home/brq/...
------------------------------------------------------------
Key: EMBJOPR-110
URL: https://jira.jboss.org/jira/browse/EMBJOPR-110
Project: Embedded Jopr
Issue Type: Bug
Reporter: Ondrej ?i?ka
"Path" property of WAR (and perhaps other app types) is incorrect - the leading slash is trimmed:
Path: home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war
--
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
From jira-events at lists.jboss.org Thu Mar 19 22:49:27 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Thu, 19 Mar 2009 22:49:27 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-110) App's Path
property leading slash trimmed: Path: home/brq/...
In-Reply-To: <10894404.1237517244540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5844022.1237517367292.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ondrej ?i?ka updated EMBJOPR-110:
---------------------------------
Summary: App's Path property leading slash trimmed: Path: home/brq/... (was: WAR Path property leading slash trimmed: Path: home/brq/...)
> App's Path property leading slash trimmed: Path: home/brq/...
> --------------------------------------------------------------
>
> Key: EMBJOPR-110
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-110
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
>
> In Summary tab of applications, the "Path" property is incorrect - the leading slash is trimmed:
> Path: home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war
--
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
From jira-events at lists.jboss.org Thu Mar 19 22:49:25 2009
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ondrej_=C5=BDi=C5=BEka_=28JIRA=29?=)
Date: Thu, 19 Mar 2009 22:49:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-110) WAR Path
property leading slash trimmed: Path: home/brq/...
In-Reply-To: <10894404.1237517244540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <264157.1237517365495.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ondrej ?i?ka updated EMBJOPR-110:
---------------------------------
Description:
In Summary tab of applications, the "Path" property is incorrect - the leading slash is trimmed:
Path: home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war
was:
"Path" property of WAR (and perhaps other app types) is incorrect - the leading slash is trimmed:
Path: home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war
> WAR Path property leading slash trimmed: Path: home/brq/...
> ------------------------------------------------------------
>
> Key: EMBJOPR-110
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-110
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
>
> In Summary tab of applications, the "Path" property is incorrect - the leading slash is trimmed:
> Path: home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war
--
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
From jira-events at lists.jboss.org Fri Mar 20 13:01:24 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Fri, 20 Mar 2009 13:01:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-81) Exception
thrown when UPDATING .ear from Content Tab
In-Reply-To: <32547805.1235148710204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10269984.1237568484691.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer resolved EMBJOPR-81.
---------------------------------
Resolution: Done
This was caused by a couple bugs in the jboss-as-5 plugin. Fixed - Jopr r298.
> Exception thrown when UPDATING .ear from Content Tab
> ----------------------------------------------------
>
> Key: EMBJOPR-81
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-81
> Project: Embedded Jopr
> Issue Type: Bug
> Environment: JBoss AS Branch_5_x r84532, embjopr r162
> Still seen with: JBoss AS Branch 5_x r86127, embjopr r242
> Reporter: Shelly McGowan
> Assignee: Ian Springer
> Priority: Critical
> Fix For: 1.2
>
> Attachments: jbossas-default-server.log, resourceInstanceContent.seam.log
>
>
> Navigating to the Content Tab to update an existing resource results in a ServletException (see attached file, resourceInstanceContent.seam.log. While the exception is thrown on this action, it appears to be the result of a previous exception during the navigation to the Content tab. The Content tab is not consistently available but is during a specific navigation sequence. I'll identify the specific navigation sequence to reproduce and update this issue. I've also attached the jbossas server.log snippet.
--
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
From jira-events at lists.jboss.org Fri Mar 20 14:40:25 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Fri, 20 Mar 2009 14:40:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-108) Add support
for local-tx connection factories
In-Reply-To: <32885034.1237479324602.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5220443.1237574425439.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458435#action_12458435 ]
Ian Springer commented on EMBJOPR-108:
--------------------------------------
I based the Resource types I exposed off of the ConnectionFactoryTypes enum from org.jboss.deployers.spi.management.KnownComponentTypes:
/**
* Enums for generic ConnectionFactory types
*/
public enum ConnectionFactoryTypes
{
XA("ConnectionFactory", "XA"), NoTx("ConnectionFactory", "NoTx");
private final String type;
private final String subtype;
private ConnectionFactoryTypes(String type, String subtype)
{
this.type = type;
this.subtype = subtype;
}
public String type()
{
return type;
}
public String subtype()
{
return subtype;
}
public ComponentType getType()
{
return new ComponentType(type, subtype);
}
};
If there is also a LocalTX type, then this enum should probably be updated. Scott, can you comment?
> Add support for local-tx connection factories
> ---------------------------------------------
>
> Key: EMBJOPR-108
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-108
> Project: Embedded Jopr
> Issue Type: Task
> Reporter: Charles Crouch
> Assignee: Ian Springer
> Fix For: 1.2
>
>
> We have support for XA and no-tx ones, we should add local-tx. This page describes the different varieties http://www.jboss.org/community/docs/DOC-9326
--
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
From jira-events at lists.jboss.org Fri Mar 20 14:48:27 2009
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Fri, 20 Mar 2009 14:48:27 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-108) Add support
for local-tx connection factories
In-Reply-To: <32885034.1237479324602.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7724119.1237574907309.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458438#action_12458438 ]
Scott M Stark commented on EMBJOPR-108:
---------------------------------------
The current profileservice-spi version of KnownComponentTypes used in the JBAS 5.x branch (5.1.0.CR1 of the integration project) does include a LocalTx value:
public enum DataSourceTypes
{
XA("DataSource", "XA"), LocalTx("DataSource", "LocalTx"), NoTx("DataSource", "NoTx");
...
> Add support for local-tx connection factories
> ---------------------------------------------
>
> Key: EMBJOPR-108
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-108
> Project: Embedded Jopr
> Issue Type: Task
> Reporter: Charles Crouch
> Assignee: Ian Springer
> Fix For: 1.2
>
>
> We have support for XA and no-tx ones, we should add local-tx. This page describes the different varieties http://www.jboss.org/community/docs/DOC-9326
--
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
From jira-events at lists.jboss.org Fri Mar 20 14:48:25 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Fri, 20 Mar 2009 14:48:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-64) request for
committing embedded JOPR Japanese resource bundle
In-Reply-To: <27271316.1231517466051.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20562824.1237574905840.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer resolved EMBJOPR-64.
---------------------------------
Fix Version/s: 1.2
Resolution: Done
Assignee: Ian Springer
Patch applied - r248. Thanks!
> request for committing embedded JOPR Japanese resource bundle
> -------------------------------------------------------------
>
> Key: EMBJOPR-64
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-64
> Project: Embedded Jopr
> Issue Type: Task
> Components: Look 'n' Feel (html/css)
> Reporter: Yusuke Yamamoto
> Assignee: Ian Springer
> Fix For: 1.2
>
> Attachments: messages_ja.properties.patch
>
>
> Please commit the attached japanese message bundle.
--
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
From jira-events at lists.jboss.org Fri Mar 20 14:52:26 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Fri, 20 Mar 2009 14:52:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-19) Need to verify
config pages produce good xhtml i.e. well formed xml
Message-ID: <15325876.1237575146877.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer resolved EMBJOPR-19.
---------------------------------
Resolution: Done
Assignee: Ian Springer
I believe this is resolved.
> Need to verify config pages produce good xhtml i.e. well formed xml
> -------------------------------------------------------------------
>
> Key: EMBJOPR-19
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-19
> Project: Embedded Jopr
> Issue Type: Task
> Components: Look 'n' Feel (html/css)
> Affects Versions: 1.0
> Reporter: Charles Crouch
> Assignee: Ian Springer
> Fix For: 1.1
>
>
> We need to back out the following change and check that all the pages, especially the configuration related pages dont error out when viewed in Firefox.
> Author: jsant
> Date: 2007-07-18 16:12:26 -0400 (Wed, 18 Jul 2007)
> New Revision: 5814
> Modified:
> trunk/modules/embedded/src/main/webapp/layout.xhtml
> trunk/modules/embedded/src/main/webapp/login.xhtml
> Log:
> re-added contentType="text/html" so that firefox will be able to render pages correctly.
> Modified: trunk/modules/embedded/src/main/webapp/layout.xhtml
> ===================================================================
> --- trunk/modules/embedded/src/main/webapp/layout.xhtml 2007-07-18 19:59:30 UTC (rev 5813)
> +++ trunk/modules/embedded/src/main/webapp/layout.xhtml 2007-07-18 20:12:26 UTC (rev 5814)
> @@ -6,7 +6,7 @@
> xmlns:s="http://jboss.com/products/seam/taglib"
> xmlns:ui="http://java.sun.com/jsf/facelets"
> >
> -
> +
>
>
>
> Modified: trunk/modules/embedded/src/main/webapp/login.xhtml
> ===================================================================
> --- trunk/modules/embedded/src/main/webapp/login.xhtml 2007-07-18 19:59:30 UTC (rev 5813)
> +++ trunk/modules/embedded/src/main/webapp/login.xhtml 2007-07-18 20:12:26 UTC (rev 5814)
> @@ -6,7 +6,7 @@
> xmlns:s="http://jboss.com/products/seam/taglib"
> xmlns:ui="http://java.sun.com/jsf/facelets"
> >
> -
> +
>
>
>
--
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
From jira-events at lists.jboss.org Fri Mar 20 15:02:25 2009
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Fri, 20 Mar 2009 15:02:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-108) Add support
for local-tx connection factories
In-Reply-To: <32885034.1237479324602.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19530179.1237575745083.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458440#action_12458440 ]
Scott M Stark commented on EMBJOPR-108:
---------------------------------------
I did not catch the ConnectionFactoryTypes vs DataSourceTypes. There is a new jira issue to review the enums:
https://jira.jboss.org/jira/browse/JBAS-6646
> Add support for local-tx connection factories
> ---------------------------------------------
>
> Key: EMBJOPR-108
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-108
> Project: Embedded Jopr
> Issue Type: Task
> Reporter: Charles Crouch
> Assignee: Ian Springer
> Fix For: 1.2
>
>
> We have support for XA and no-tx ones, we should add local-tx. This page describes the different varieties http://www.jboss.org/community/docs/DOC-9326
--
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
From jira-events at lists.jboss.org Fri Mar 20 16:13:37 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Fri, 20 Mar 2009 16:13:37 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-101) Nav tree JS
object (Tree.Item)
is not ready after page refresh, causing ScriptException: TypeError: Cannot
call method "fireExpansionEvent"
In-Reply-To: <29561323.1237318103990.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24013172.1237580017528.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Farah Juma reassigned EMBJOPR-101:
----------------------------------
Assignee: Stan Silvert
> Nav tree JS object (Tree.Item) is not ready after page refresh, causing ScriptException: TypeError: Cannot call method "fireExpansionEvent"
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-101
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-101
> Project: Embedded Jopr
> Issue Type: Task
> Reporter: Ondrej ?i?ka
> Assignee: Stan Silvert
>
> Right after page is loaded and test thread is running, JavaScript function object `Tree.Item` is not initialized yet.
> This function is created in an externally loaded file, admin-console/a4j/g/3_3_0.GAorg/richfaces/renderkit/html/scripts/tree-item.js .
> This problem appears when we click() in tests on some tree node after page load.
> It is unlikely that user will be clicking fast enough to trigger this error, moreover IMHO Firefox blocks JS execution until external JS files are all loaded (but not sure), so this is only problem for QA.
> Currently we solve this by calling NavTree#waitUntilReady( int intervalMs, int retries ) - e.g. in getNavTreeArrow():
> ejtt.navTree.waitUntilReady(100, 15);
> HTMLUnit's JavaScriptEngine#isScriptRunning() doesn't solve this, because AJAX's async calls' TimeOuts are not considered as running javascript (only when the timer's handler is called).
--
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
From jira-events at lists.jboss.org Fri Mar 20 16:28:24 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Fri, 20 Mar 2009 16:28:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-101) Nav tree JS
object
(Tree.Item) is not ready after page refresh, causing ScriptException:
TypeError: Cannot call method "fireExpansionEvent"
In-Reply-To: <29561323.1237318103990.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24995013.1237580904818.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458448#action_12458448 ]
Farah Juma commented on EMBJOPR-101:
------------------------------------
Ondrej has also added a method called waitUntilNodeLoadedByAjax(String resourceName, int intervalMs, int retries) which waits for the node with the given label to appear in the nav tree. He has added navTree.waitUntilReady(100, 15) and navTree.waitUntilNodeLoadedByAjax(resourceName, 200, 10) to the beginning of getNavTreeArrow() in EmbjoprTestCase.java. However, the "fireExpansionEvent" exception still occurs.
> Nav tree JS object (Tree.Item) is not ready after page refresh, causing ScriptException: TypeError: Cannot call method "fireExpansionEvent"
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-101
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-101
> Project: Embedded Jopr
> Issue Type: Task
> Reporter: Ondrej ?i?ka
> Assignee: Stan Silvert
>
> Right after page is loaded and test thread is running, JavaScript function object `Tree.Item` is not initialized yet.
> This function is created in an externally loaded file, admin-console/a4j/g/3_3_0.GAorg/richfaces/renderkit/html/scripts/tree-item.js .
> This problem appears when we click() in tests on some tree node after page load.
> It is unlikely that user will be clicking fast enough to trigger this error, moreover IMHO Firefox blocks JS execution until external JS files are all loaded (but not sure), so this is only problem for QA.
> Currently we solve this by calling NavTree#waitUntilReady( int intervalMs, int retries ) - e.g. in getNavTreeArrow():
> ejtt.navTree.waitUntilReady(100, 15);
> HTMLUnit's JavaScriptEngine#isScriptRunning() doesn't solve this, because AJAX's async calls' TimeOuts are not considered as running javascript (only when the timer's handler is called).
--
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
From jira-events at lists.jboss.org Fri Mar 20 17:16:26 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Fri, 20 Mar 2009 17:16:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Closed: (EMBJOPR-108) Add support for
local-tx connection factories
In-Reply-To: <32885034.1237479324602.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17278791.1237583786402.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer closed EMBJOPR-108.
--------------------------------
Resolution: Duplicate Issue
I've created an issue for this under the JOPR project, since it's a jboss-as-5 plugin issue - see JOPR-108. Closing this issue as a dup.
> Add support for local-tx connection factories
> ---------------------------------------------
>
> Key: EMBJOPR-108
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-108
> Project: Embedded Jopr
> Issue Type: Task
> Reporter: Charles Crouch
> Assignee: Ian Springer
> Fix For: 1.2
>
>
> We have support for XA and no-tx ones, we should add local-tx. This page describes the different varieties http://www.jboss.org/community/docs/DOC-9326
--
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
From jira-events at lists.jboss.org Fri Mar 20 19:29:24 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Fri, 20 Mar 2009 19:29:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Reopened: (EMBJOPR-81) Exception
thrown when UPDATING .ear from Content Tab
In-Reply-To: <32547805.1235148710204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8032879.1237591764641.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer reopened EMBJOPR-81:
---------------------------------
Shelly said she's still seeing this, so apparently I didn't fix it.
> Exception thrown when UPDATING .ear from Content Tab
> ----------------------------------------------------
>
> Key: EMBJOPR-81
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-81
> Project: Embedded Jopr
> Issue Type: Bug
> Environment: JBoss AS Branch_5_x r84532, embjopr r162
> Still seen with: JBoss AS Branch 5_x r86127, embjopr r242
> Reporter: Shelly McGowan
> Assignee: Ian Springer
> Priority: Critical
> Fix For: 1.2
>
> Attachments: jbossas-default-server.log, resourceInstanceContent.seam.log
>
>
> Navigating to the Content Tab to update an existing resource results in a ServletException (see attached file, resourceInstanceContent.seam.log. While the exception is thrown on this action, it appears to be the result of a previous exception during the navigation to the Content tab. The Content tab is not consistently available but is during a specific navigation sequence. I'll identify the specific navigation sequence to reproduce and update this issue. I've also attached the jbossas server.log snippet.
--
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
From jira-events at lists.jboss.org Fri Mar 20 20:56:24 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Fri, 20 Mar 2009 20:56:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Work started: (EMBJOPR-103) add
favicon to webapp
In-Reply-To: <31283176.1237396224098.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10091109.1237596984823.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on EMBJOPR-103 started by Ian Springer.
> add favicon to webapp
> ---------------------
>
> Key: EMBJOPR-103
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-103
> Project: Embedded Jopr
> Issue Type: Task
> Components: Web App/Integration
> Affects Versions: 1.1
> Reporter: Ian Springer
> Assignee: Ian Springer
> Priority: Minor
> Fix For: 1.2
>
> Attachments: favicon.png
>
> Original Estimate: 10 minutes
> Remaining Estimate: 10 minutes
>
> We can use the same favicon that enterprise uses (see http://jira.rhq-project.org/browse/RHQ-1806).
--
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
From jira-events at lists.jboss.org Fri Mar 20 20:56:26 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Fri, 20 Mar 2009 20:56:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-103) add favicon
to webapp
In-Reply-To: <31283176.1237396224098.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <892084.1237596986405.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458475#action_12458475 ]
Ian Springer commented on EMBJOPR-103:
--------------------------------------
Sure, do we have a color version of the EmbJopr logo somewhere or should I use the black and white one that's part of the current page header?
r250 adds the Jopr logo as the favicon for now.
> add favicon to webapp
> ---------------------
>
> Key: EMBJOPR-103
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-103
> Project: Embedded Jopr
> Issue Type: Task
> Components: Web App/Integration
> Affects Versions: 1.1
> Reporter: Ian Springer
> Assignee: Ian Springer
> Priority: Minor
> Fix For: 1.2
>
> Attachments: favicon.png
>
> Original Estimate: 10 minutes
> Remaining Estimate: 10 minutes
>
> We can use the same favicon that enterprise uses (see http://jira.rhq-project.org/browse/RHQ-1806).
--
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
From jira-events at lists.jboss.org Sat Mar 21 19:22:24 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Sat, 21 Mar 2009 19:22:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-81) Exception
thrown when UPDATING .ear from Content Tab
In-Reply-To: <32547805.1235148710204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8737140.1237677744242.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458498#action_12458498 ]
Ian Springer commented on EMBJOPR-81:
-------------------------------------
Shelly, I'm unable to reproduce this using Jopr r302 and EmbJopr r250. Are you sure you rebuilt the jboss-as-5 plugin and then embjopr post Jopr r298?
> Exception thrown when UPDATING .ear from Content Tab
> ----------------------------------------------------
>
> Key: EMBJOPR-81
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-81
> Project: Embedded Jopr
> Issue Type: Bug
> Environment: JBoss AS Branch_5_x r84532, embjopr r162
> Still seen with: JBoss AS Branch 5_x r86127, embjopr r242
> Reporter: Shelly McGowan
> Assignee: Ian Springer
> Priority: Critical
> Fix For: 1.2
>
> Attachments: jbossas-default-server.log, resourceInstanceContent.seam.log
>
>
> Navigating to the Content Tab to update an existing resource results in a ServletException (see attached file, resourceInstanceContent.seam.log. While the exception is thrown on this action, it appears to be the result of a previous exception during the navigation to the Content tab. The Content tab is not consistently available but is during a specific navigation sequence. I'll identify the specific navigation sequence to reproduce and update this issue. I've also attached the jbossas server.log snippet.
--
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
From jira-events at lists.jboss.org Sat Mar 21 19:24:36 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Sat, 21 Mar 2009 19:24:36 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-81) Exception
thrown when UPDATING .ear from Content Tab
In-Reply-To: <32547805.1235148710204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2783566.1237677876250.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer reassigned EMBJOPR-81:
-----------------------------------
Assignee: Shelly McGowan (was: Ian Springer)
> Exception thrown when UPDATING .ear from Content Tab
> ----------------------------------------------------
>
> Key: EMBJOPR-81
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-81
> Project: Embedded Jopr
> Issue Type: Bug
> Environment: JBoss AS Branch_5_x r84532, embjopr r162
> Still seen with: JBoss AS Branch 5_x r86127, embjopr r242
> Reporter: Shelly McGowan
> Assignee: Shelly McGowan
> Priority: Critical
> Fix For: 1.2
>
> Attachments: jbossas-default-server.log, resourceInstanceContent.seam.log
>
>
> Navigating to the Content Tab to update an existing resource results in a ServletException (see attached file, resourceInstanceContent.seam.log. While the exception is thrown on this action, it appears to be the result of a previous exception during the navigation to the Content tab. The Content tab is not consistently available but is during a specific navigation sequence. I'll identify the specific navigation sequence to reproduce and update this issue. I've also attached the jbossas server.log snippet.
--
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
From jira-events at lists.jboss.org Mon Mar 23 09:11:30 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Mon, 23 Mar 2009 09:11:30 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Work started: (EMBJOPR-98) Add
config-property
resource configuration property to connection factories
In-Reply-To: <6780440.1236881124395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20693375.1237813890326.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on EMBJOPR-98 started by Ian Springer.
> Add config-property resource configuration property to connection factories
> ---------------------------------------------------------------------------
>
> Key: EMBJOPR-98
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-98
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Reporter: Charles Crouch
> Assignee: Ian Springer
> Fix For: 1.2
>
>
> Looking at
> http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214634#4214634
> implies config-property should only be available for connection factory resource types. Right now its on the "XA ConnectionFactory" service, but I think it should be on the "No TX ConnectionFactory" service too.
--
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
From jira-events at lists.jboss.org Mon Mar 23 10:31:41 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Mon, 23 Mar 2009 10:31:41 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-103) add favicon
to webapp
In-Reply-To: <31283176.1237396224098.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23827877.1237818701662.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-103:
--------------------------------------
Assignee: James Cobb (was: Ian Springer)
James can you point us at where the favicon sized Embedded Jopr logo images are located?
> add favicon to webapp
> ---------------------
>
> Key: EMBJOPR-103
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-103
> Project: Embedded Jopr
> Issue Type: Task
> Components: Web App/Integration
> Affects Versions: 1.1
> Reporter: Ian Springer
> Assignee: James Cobb
> Priority: Minor
> Fix For: 1.2
>
> Attachments: favicon.png
>
> Original Estimate: 10 minutes
> Remaining Estimate: 10 minutes
>
> We can use the same favicon that enterprise uses (see http://jira.rhq-project.org/browse/RHQ-1806).
--
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
From jira-events at lists.jboss.org Mon Mar 23 10:49:32 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Mon, 23 Mar 2009 10:49:32 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-109) HTTP Status
500 - Error in Seam/JSF
In-Reply-To: <31887082.1237515384829.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14872500.1237819772972.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458566#action_12458566 ]
Charles Crouch commented on EMBJOPR-109:
----------------------------------------
So can this still be reproduced after the fix for EMBJOPR-81 went in?
> HTTP Status 500 - Error in Seam/JSF
> -----------------------------------
>
> Key: EMBJOPR-109
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-109
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
> Attachments: formNotFound-navTreeForm.html, log.txt
>
>
> Following exception appears occasionally in WAR tests.
> Here's only what goes to HTTP output; Relevant log part attached.
> HTTP Status 500 -
> type Exception report
> message
> description The server encountered an internal error () that prevented it from fulfilling this request.
> exception
> javax.servlet.ServletException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:126)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> root cause
> org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
> org.jboss.seam.Component.newInstance(Component.java:2096)
> org.jboss.seam.Component.getInstance(Component.java:1978)
> org.jboss.seam.Component.getInstance(Component.java:1957)
> org.jboss.seam.Component.getInstance(Component.java:1951)
> org.jboss.seam.Component.getInstance(Component.java:1924)
> org.jboss.seam.Component.getInstance(Component.java:1919)
> org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256)
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> root cause
> java.lang.NullPointerException
> org.jboss.seam.exception.Exceptions.parse(Exceptions.java:195)
> org.jboss.seam.exception.Exceptions.initialize(Exceptions.java:119)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:585)
> org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
> org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138)
> org.jboss.seam.Component.callComponentMethod(Component.java:2201)
> org.jboss.seam.Component.callCreateMethod(Component.java:2124)
> org.jboss.seam.Component.newInstance(Component.java:2084)
> org.jboss.seam.Component.getInstance(Component.java:1978)
> org.jboss.seam.Component.getInstance(Component.java:1957)
> org.jboss.seam.Component.getInstance(Component.java:1951)
> org.jboss.seam.Component.getInstance(Component.java:1924)
> org.jboss.seam.Component.getInstance(Component.java:1919)
> org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256)
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> note The full stack trace of the root cause is available in the JBoss Web/2.1.2.GA logs.
> JBoss Web/2.1.2.GA
--
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
From jira-events at lists.jboss.org Mon Mar 23 10:49:39 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Mon, 23 Mar 2009 10:49:39 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-109) HTTP Status
500 - Error in Seam/JSF
In-Reply-To: <31887082.1237515384829.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13990634.1237819779665.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-109:
--------------------------------------
Assignee: Ondrej ?i?ka
> HTTP Status 500 - Error in Seam/JSF
> -----------------------------------
>
> Key: EMBJOPR-109
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-109
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
> Assignee: Ondrej ?i?ka
> Attachments: formNotFound-navTreeForm.html, log.txt
>
>
> Following exception appears occasionally in WAR tests.
> Here's only what goes to HTTP output; Relevant log part attached.
> HTTP Status 500 -
> type Exception report
> message
> description The server encountered an internal error () that prevented it from fulfilling this request.
> exception
> javax.servlet.ServletException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:126)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> root cause
> org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
> org.jboss.seam.Component.newInstance(Component.java:2096)
> org.jboss.seam.Component.getInstance(Component.java:1978)
> org.jboss.seam.Component.getInstance(Component.java:1957)
> org.jboss.seam.Component.getInstance(Component.java:1951)
> org.jboss.seam.Component.getInstance(Component.java:1924)
> org.jboss.seam.Component.getInstance(Component.java:1919)
> org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256)
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> root cause
> java.lang.NullPointerException
> org.jboss.seam.exception.Exceptions.parse(Exceptions.java:195)
> org.jboss.seam.exception.Exceptions.initialize(Exceptions.java:119)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:585)
> org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
> org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138)
> org.jboss.seam.Component.callComponentMethod(Component.java:2201)
> org.jboss.seam.Component.callCreateMethod(Component.java:2124)
> org.jboss.seam.Component.newInstance(Component.java:2084)
> org.jboss.seam.Component.getInstance(Component.java:1978)
> org.jboss.seam.Component.getInstance(Component.java:1957)
> org.jboss.seam.Component.getInstance(Component.java:1951)
> org.jboss.seam.Component.getInstance(Component.java:1924)
> org.jboss.seam.Component.getInstance(Component.java:1919)
> org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256)
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> note The full stack trace of the root cause is available in the JBoss Web/2.1.2.GA logs.
> JBoss Web/2.1.2.GA
--
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
From jira-events at lists.jboss.org Mon Mar 23 10:51:36 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Mon, 23 Mar 2009 10:51:36 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-110) App's Path
property leading slash trimmed: Path: home/brq/...
In-Reply-To: <10894404.1237517244540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7997589.1237819896810.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-110:
-----------------------------------
Fix Version/s: 1.2
Priority: Minor (was: Major)
> App's Path property leading slash trimmed: Path: home/brq/...
> --------------------------------------------------------------
>
> Key: EMBJOPR-110
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-110
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
> Priority: Minor
> Fix For: 1.2
>
>
> In Summary tab of applications, the "Path" property is incorrect - the leading slash is trimmed:
> Path: home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war
--
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
From jira-events at lists.jboss.org Mon Mar 23 10:51:28 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Mon, 23 Mar 2009 10:51:28 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-109) HTTP Status
500 - Error in Seam/JSF
In-Reply-To: <31887082.1237515384829.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12050185.1237819888514.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-109:
-----------------------------------
Fix Version/s: 1.2
> HTTP Status 500 - Error in Seam/JSF
> -----------------------------------
>
> Key: EMBJOPR-109
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-109
> Project: Embedded Jopr
> Issue Type: Bug
> Reporter: Ondrej ?i?ka
> Assignee: Ondrej ?i?ka
> Fix For: 1.2
>
> Attachments: formNotFound-navTreeForm.html, log.txt
>
>
> Following exception appears occasionally in WAR tests.
> Here's only what goes to HTTP output; Relevant log part attached.
> HTTP Status 500 -
> type Exception report
> message
> description The server encountered an internal error () that prevented it from fulfilling this request.
> exception
> javax.servlet.ServletException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:126)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> root cause
> org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions
> org.jboss.seam.Component.newInstance(Component.java:2096)
> org.jboss.seam.Component.getInstance(Component.java:1978)
> org.jboss.seam.Component.getInstance(Component.java:1957)
> org.jboss.seam.Component.getInstance(Component.java:1951)
> org.jboss.seam.Component.getInstance(Component.java:1924)
> org.jboss.seam.Component.getInstance(Component.java:1919)
> org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256)
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> root cause
> java.lang.NullPointerException
> org.jboss.seam.exception.Exceptions.parse(Exceptions.java:195)
> org.jboss.seam.exception.Exceptions.initialize(Exceptions.java:119)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:585)
> org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
> org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138)
> org.jboss.seam.Component.callComponentMethod(Component.java:2201)
> org.jboss.seam.Component.callCreateMethod(Component.java:2124)
> org.jboss.seam.Component.newInstance(Component.java:2084)
> org.jboss.seam.Component.getInstance(Component.java:1978)
> org.jboss.seam.Component.getInstance(Component.java:1957)
> org.jboss.seam.Component.getInstance(Component.java:1951)
> org.jboss.seam.Component.getInstance(Component.java:1924)
> org.jboss.seam.Component.getInstance(Component.java:1919)
> org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256)
> org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>
> note The full stack trace of the root cause is available in the JBoss Web/2.1.2.GA logs.
> JBoss Web/2.1.2.GA
--
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
From jira-events at lists.jboss.org Mon Mar 23 11:12:31 2009
From: jira-events at lists.jboss.org (James Cobb (JIRA))
Date: Mon, 23 Mar 2009 11:12:31 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-103) add favicon to
webapp
In-Reply-To: <31283176.1237396224098.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11842789.1237821151544.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Cobb updated EMBJOPR-103:
-------------------------------
Attachment: embeddedjpr_favicon.png
We never created one. I put one together and attached it to this JIRA.
> add favicon to webapp
> ---------------------
>
> Key: EMBJOPR-103
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-103
> Project: Embedded Jopr
> Issue Type: Task
> Components: Web App/Integration
> Affects Versions: 1.1
> Reporter: Ian Springer
> Assignee: James Cobb
> Priority: Minor
> Fix For: 1.2
>
> Attachments: embeddedjpr_favicon.png, favicon.png
>
> Original Estimate: 10 minutes
> Remaining Estimate: 10 minutes
>
> We can use the same favicon that enterprise uses (see http://jira.rhq-project.org/browse/RHQ-1806).
--
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
From jira-events at lists.jboss.org Mon Mar 23 11:14:25 2009
From: jira-events at lists.jboss.org (James Cobb (JIRA))
Date: Mon, 23 Mar 2009 11:14:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-103) add favicon
to webapp
In-Reply-To: <31283176.1237396224098.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <660324.1237821265913.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Cobb reassigned EMBJOPR-103:
----------------------------------
Assignee: Charles Crouch (was: James Cobb)
I created the favicon and attached it to the jira.
> add favicon to webapp
> ---------------------
>
> Key: EMBJOPR-103
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-103
> Project: Embedded Jopr
> Issue Type: Task
> Components: Web App/Integration
> Affects Versions: 1.1
> Reporter: Ian Springer
> Assignee: Charles Crouch
> Priority: Minor
> Fix For: 1.2
>
> Attachments: embeddedjpr_favicon.png, favicon.png
>
> Original Estimate: 10 minutes
> Remaining Estimate: 10 minutes
>
> We can use the same favicon that enterprise uses (see http://jira.rhq-project.org/browse/RHQ-1806).
--
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
From jira-events at lists.jboss.org Mon Mar 23 11:32:29 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Mon, 23 Mar 2009 11:32:29 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-50) Stopping an
web application causes it to be removed from inventory
Message-ID: <20560135.1237822349159.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-50:
-------------------------------------
Assignee: Ondrej ?i?ka
Assigning to Ondrej for re-testing.
> Stopping an web application causes it to be removed from inventory
> ------------------------------------------------------------------
>
> Key: EMBJOPR-50
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-50
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Affects Versions: 1.0
> Environment: Running with SOA-P IR3 release
> Console version: 2.1.0.0
> Reporter: Len DiMaggio
> Assignee: Ondrej ?i?ka
> Fix For: 1.2
>
> Attachments: server.log, server.log.zip
>
>
> Tried stopping the jBPM console - see the attached server.log
--
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
From jira-events at lists.jboss.org Mon Mar 23 11:32:26 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Mon, 23 Mar 2009 11:32:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-50) Stopping an
web application causes it to be removed from inventory
Message-ID: <9708564.1237822346995.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458588#action_12458588 ]
Charles Crouch commented on EMBJOPR-50:
---------------------------------------
This was originally related to the JBAS4 plugin, we need to check whether this is still a problem with the JBAS5 plugin.
> Stopping an web application causes it to be removed from inventory
> ------------------------------------------------------------------
>
> Key: EMBJOPR-50
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-50
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Affects Versions: 1.0
> Environment: Running with SOA-P IR3 release
> Console version: 2.1.0.0
> Reporter: Len DiMaggio
> Fix For: 1.2
>
> Attachments: server.log, server.log.zip
>
>
> Tried stopping the jBPM console - see the attached server.log
--
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
From jira-events at lists.jboss.org Mon Mar 23 13:47:27 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Mon, 23 Mar 2009 13:47:27 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-111) AS5 plugin:
Unsetting a
property value for a Topic or Queue during a config update results in an
"UndeclaredThrowableException"
Message-ID: <27281444.1237830447169.JavaMail.jira@cloud.prod.atl2.jboss.com>
AS5 plugin: Unsetting a property value for a Topic or Queue during a config update results in an "UndeclaredThrowableException"
-------------------------------------------------------------------------------------------------------------------------------
Key: EMBJOPR-111
URL: https://jira.jboss.org/jira/browse/EMBJOPR-111
Project: Embedded Jopr
Issue Type: Bug
Components: Web App/Integration
Environment: JBoss AS Branch_5_x r86203, embjopr r251
Reporter: Farah Juma
Fix For: 1.2
Steps to reproduce:
Click on the "Configuration" tab for a Queue or Topic. Attempt to unset a property (eg. "Redelivery Delay"). The update fails with the following error:
java.lang.reflect.UndeclaredThrowableException at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.set(KernelBusRuntimeComponentDispatcher.java:91) at org.jboss.profileservice.management.ManagementViewImpl.updateComponent(ManagementViewImpl.java:1097) 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.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aop.generatedproxies.AOPProxy$1.updateComponent(AOPProxy$1.java) at org.rhq.plugins.jbossas5.ManagedComponentComponent.updateComponent(ManagedComponentComponent.java:174) at org.rhq.plugins.jbossas5.AbstractManagedComponent.updateResourceConfiguration(AbstractManagedComponent.java:84) 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.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: javax.management.ReflectionException at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:189) at org.jboss.mx.interceptor.AttributeDispatcher.invoke(AttributeDispatcher.java:140) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:103) at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.server.AbstractMBeanInvoker.setAttribute(AbstractMBeanInvoker.java:461) at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:617) at org.jboss.system.microcontainer.ServiceControllerContext.set(ServiceControllerContext.java:182) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus$2.dispatch(BasicKernelBus.java:79) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus$2.dispatch(BasicKernelBus.java:83) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.execute(BasicKernelBus.java:54) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.set(BasicKernelBus.java:75) at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.set(KernelBusRuntimeComponentDispatcher.java:87) at org.jboss.profileservice.management.ManagementViewImpl.updateComponent(ManagementViewImpl.java:1097) 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.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aop.generatedproxies.AOPProxy$1.updateComponent(AOPProxy$1.java) at org.rhq.plugins.jbossas5.ManagedComponentComponent.updateComponent(ManagedComponentComponent.java:174) at org.rhq.plugins.jbossas5.AbstractManagedComponent.updateResourceConfiguration(AbstractManagedComponent.java:84) 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.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72) ... 18 more Caused by: java.lang.IllegalArgumentException 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.mx.interceptor.AttributeDispatcher.invoke(AttributeDispatcher.java:136) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:103) at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.server.AbstractMBeanInvoker.setAttribute(AbstractMBeanInvoker.java:461) at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:617) at org.jboss.system.microcontainer.ServiceControllerContext.set(ServiceControllerContext.java:182) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus$2.dispatch(BasicKernelBus.java:79) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus$2.dispatch(BasicKernelBus.java:83) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.execute(BasicKernelBus.java:54) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.set(BasicKernelBus.java:75) at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.set(KernelBusRuntimeComponentDispatcher.java:87) at org.jboss.profileservice.management.ManagementViewImpl.updateComponent(ManagementViewImpl.java:1097) 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.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) ... 18 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
From jira-events at lists.jboss.org Mon Mar 23 13:51:27 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Mon, 23 Mar 2009 13:51:27 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-103) add favicon
to webapp
In-Reply-To: <31283176.1237396224098.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2273600.1237830687250.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer resolved EMBJOPR-103.
----------------------------------
Resolution: Done
Updated to use EmbJopr favicon - r252. Thanks, James.
> add favicon to webapp
> ---------------------
>
> Key: EMBJOPR-103
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-103
> Project: Embedded Jopr
> Issue Type: Task
> Components: Web App/Integration
> Affects Versions: 1.1
> Reporter: Ian Springer
> Assignee: Charles Crouch
> Priority: Minor
> Fix For: 1.2
>
> Attachments: embeddedjpr_favicon.png, favicon.png
>
> Original Estimate: 10 minutes
> Remaining Estimate: 10 minutes
>
> We can use the same favicon that enterprise uses (see http://jira.rhq-project.org/browse/RHQ-1806).
--
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
From jira-events at lists.jboss.org Mon Mar 23 13:51:32 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Mon, 23 Mar 2009 13:51:32 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-103) add favicon
to webapp
In-Reply-To: <31283176.1237396224098.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21498231.1237830692733.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer reassigned EMBJOPR-103:
------------------------------------
Assignee: Ian Springer (was: Charles Crouch)
> add favicon to webapp
> ---------------------
>
> Key: EMBJOPR-103
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-103
> Project: Embedded Jopr
> Issue Type: Task
> Components: Web App/Integration
> Affects Versions: 1.1
> Reporter: Ian Springer
> Assignee: Ian Springer
> Priority: Minor
> Fix For: 1.2
>
> Attachments: embeddedjpr_favicon.png, favicon.png
>
> Original Estimate: 10 minutes
> Remaining Estimate: 10 minutes
>
> We can use the same favicon that enterprise uses (see http://jira.rhq-project.org/browse/RHQ-1806).
--
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
From jira-events at lists.jboss.org Mon Mar 23 14:23:27 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Mon, 23 Mar 2009 14:23:27 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-112) AS5 plugin:
After creating a
new Topic or Queue, the configuration properties are set to their default
values instead of to the values that were specified during creation
Message-ID: <5521467.1237832607224.JavaMail.jira@cloud.prod.atl2.jboss.com>
AS5 plugin: After creating a new Topic or Queue, the configuration properties are set to their default values instead of to the values that were specified during creation
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: EMBJOPR-112
URL: https://jira.jboss.org/jira/browse/EMBJOPR-112
Project: Embedded Jopr
Issue Type: Bug
Components: Web App/Integration
Environment: JBoss AS Branch_5_x r86203, embjopr r251
Reporter: Farah Juma
Fix For: 1.2
Steps to reproduce:
Create a new Topic or Queue and set values for each of the properties (eg. Clustered, Down Cache Size, Full Size, Max Delivery Attempts, etc.). After clicking "Save", navigate to the "Configuration" page for the new resource. The property values that appear on the page seem to be the default values instead of the values that were specified during creation.
--
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
From jira-events at lists.jboss.org Mon Mar 23 14:50:26 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Mon, 23 Mar 2009 14:50:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-113) AS5 plugin:
When invoking the
"List All Messages" operation for a Topic or Queue, "Arg#0" gets displayed
as the operation parameter name instead of the actual parameter name
Message-ID: <24228326.1237834226598.JavaMail.jira@cloud.prod.atl2.jboss.com>
AS5 plugin: When invoking the "List All Messages" operation for a Topic or Queue, "Arg#0" gets displayed as the operation parameter name instead of the actual parameter name
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: EMBJOPR-113
URL: https://jira.jboss.org/jira/browse/EMBJOPR-113
Project: Embedded Jopr
Issue Type: Bug
Components: Web App/Integration
Environment: JBoss AS Branch_5_x r86203, embjopr r251
Reporter: Farah Juma
Fix For: 1.2
Attachments: ListAllMessagesOperation.png
Steps to reproduce:
Navigate to the "Control" page for a Queue. Click on the "List All Messages" button. The operation parameter name that gets displayed is "Arg#0", as seen in the attached screenshot.
--
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
From jira-events at lists.jboss.org Mon Mar 23 14:50:30 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Mon, 23 Mar 2009 14:50:30 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-113) AS5 plugin:
When invoking the
"List All Messages" operation for a Topic or Queue, "Arg#0" gets displayed
as the operation parameter name instead of the actual parameter name
In-Reply-To: <24228326.1237834226598.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6148897.1237834230080.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Farah Juma updated EMBJOPR-113:
-------------------------------
Attachment: ListAllMessagesOperation.png
> AS5 plugin: When invoking the "List All Messages" operation for a Topic or Queue, "Arg#0" gets displayed as the operation parameter name instead of the actual parameter name
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-113
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-113
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS Branch_5_x r86203, embjopr r251
> Reporter: Farah Juma
> Fix For: 1.2
>
> Attachments: ListAllMessagesOperation.png
>
>
> Steps to reproduce:
> Navigate to the "Control" page for a Queue. Click on the "List All Messages" button. The operation parameter name that gets displayed is "Arg#0", as seen in the attached screenshot.
--
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
From jira-events at lists.jboss.org Mon Mar 23 15:24:26 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Mon, 23 Mar 2009 15:24:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-114) AS5 plugin:
The "List All
Subscriptions" operation for a Topic fails due to a NullPointerException
Message-ID: <18431109.1237836266567.JavaMail.jira@cloud.prod.atl2.jboss.com>
AS5 plugin: The "List All Subscriptions" operation for a Topic fails due to a NullPointerException
--------------------------------------------------------------------------------------------------
Key: EMBJOPR-114
URL: https://jira.jboss.org/jira/browse/EMBJOPR-114
Project: Embedded Jopr
Issue Type: Bug
Components: Web App/Integration
Environment: JBoss AS Branch_5_x r86203, embjopr r251
Reporter: Farah Juma
Fix For: 1.2
Attachments: ListAllSubscriptions.png
Steps to reproduce:
Navigate to the "Control" page for a Topic. Click on the "List All Subscriptions" button. The operations history table shows that the operation failed. Click on the "Show/Hide Details" link. The following error message gets displayed, as seen in the attached screenshot:
java.lang.NullPointerException
at org.rhq.plugins.jbossas5.util.ConversionUtils.instanceOf(ConversionUtils.java:438)
at org.rhq.plugins.jbossas5.util.ConversionUtils.convertManagedOperationResults(ConversionUtils.java:427)
at org.rhq.plugins.jbossas5.ManagedComponentComponent.invokeOperation(ManagedComponentComponent.java:136)
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.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
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
From jira-events at lists.jboss.org Mon Mar 23 15:24:34 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Mon, 23 Mar 2009 15:24:34 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-114) AS5 plugin:
The "List All
Subscriptions" operation for a Topic fails due to a NullPointerException
In-Reply-To: <18431109.1237836266567.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11889809.1237836274864.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Farah Juma updated EMBJOPR-114:
-------------------------------
Attachment: ListAllSubscriptions.png
> AS5 plugin: The "List All Subscriptions" operation for a Topic fails due to a NullPointerException
> --------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-114
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-114
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS Branch_5_x r86203, embjopr r251
> Reporter: Farah Juma
> Fix For: 1.2
>
> Attachments: ListAllSubscriptions.png
>
>
> Steps to reproduce:
> Navigate to the "Control" page for a Topic. Click on the "List All Subscriptions" button. The operations history table shows that the operation failed. Click on the "Show/Hide Details" link. The following error message gets displayed, as seen in the attached screenshot:
> java.lang.NullPointerException
> at org.rhq.plugins.jbossas5.util.ConversionUtils.instanceOf(ConversionUtils.java:438)
> at org.rhq.plugins.jbossas5.util.ConversionUtils.convertManagedOperationResults(ConversionUtils.java:427)
> at org.rhq.plugins.jbossas5.ManagedComponentComponent.invokeOperation(ManagedComponentComponent.java:136)
> 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.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 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
From jira-events at lists.jboss.org Mon Mar 23 16:44:25 2009
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Mon, 23 Mar 2009 16:44:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-115) WARs cannot be
Deleted
Message-ID: <29019912.1237841065439.JavaMail.jira@cloud.prod.atl2.jboss.com>
WARs cannot be Deleted
----------------------
Key: EMBJOPR-115
URL: https://jira.jboss.org/jira/browse/EMBJOPR-115
Project: Embedded Jopr
Issue Type: Bug
Components: Web App/Integration
Environment: JBoss AS r 86207, EMBJOPR r251
Reporter: Shelly McGowan
Fix For: 1.2
Navigation:
>From Applications ==> Web Applications
Add New Resource
Enter Resource name, CONTINUE
Wait till the web archive status shows it is 'UP'.
Delete the WAR archive.
Confirmation Message: Successfully deleted Web Application (WAR) 'hellothere.war'.
Server side:
2009-03-23 16:06:08,276 DEBUG [org.jboss.on.embedded.ui.SingleResourceAction] (http-127.0.0.1-8080-1) Removing Resource Resource[id=-39, type=Web Application (WAR), key=vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/embjopr/hellothere.war/, name=hellothere.war, parent=JBAS (default), version=?]...
2009-03-23 16:06:08,281 INFO [org.rhq.core.pc.inventory.DeleteResourceRunner] (ResourceFactory.executor-1) Deleting resource from request: 1
2009-03-23 16:06:08,282 DEBUG [org.rhq.plugins.jbossas5.ManagedDeploymentComponent] (ResourceContainer.invoker.nonDaemon-1) Undeploying deployment [vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/embjopr/hellothere.war/]...
The console shows the WAR status as UNKNOWN. Refreshing the page, then shows the WAR application status as 'UP'.
Attempting to Delete the same resource again, results in the same message to the client. The server, however, returns:
16:33:28,549 INFO [DeleteResourceRunner] Deleting resource from request: 1
16:33:28,553 INFO [DeployHandler] Remove, [vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/embjopr/hellothere.war/]
16:33:28,553 INFO [DeployHandler] Failed to complete command: [remove] for deployment: names=[vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/embjopr/hellothere.war/], copyContent=true
org.jboss.profileservice.spi.NoSuchDeploymentException: Failed to find deployment in file: vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/embjopr/hellothere.war/
at org.jboss.system.server.profileservice.repository.AbstractDeploymentRepository.getDeployment(AbstractDeploymentRepository.java:134)
at org.jboss.system.server.profileservice.repository.BasicDeploymentRepository.removeDeployment(BasicDeploymentRepository.java:208)
at org.jboss.profileservice.management.upload.remoting.DeployHandler.removeDeployment(DeployHandler.java:171)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.remove(AbstractDeployHandler.java:322)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:185)
--
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
From jira-events at lists.jboss.org Mon Mar 23 20:32:24 2009
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Mon, 23 Mar 2009 20:32:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-115) Applications
cannot be Deleted
In-Reply-To: <29019912.1237841065439.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26105008.1237854744529.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shelly McGowan updated EMBJOPR-115:
-----------------------------------
Summary: Applications cannot be Deleted (was: WARs cannot be Deleted)
The same behavior is seen with Enterprise Archives.
> Applications cannot be Deleted
> ------------------------------
>
> Key: EMBJOPR-115
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-115
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS r 86207, EMBJOPR r251
> Reporter: Shelly McGowan
> Fix For: 1.2
>
>
> Navigation:
> From Applications ==> Web Applications
> Add New Resource
> Enter Resource name, CONTINUE
> Wait till the web archive status shows it is 'UP'.
> Delete the WAR archive.
> Confirmation Message: Successfully deleted Web Application (WAR) 'hellothere.war'.
> Server side:
> 2009-03-23 16:06:08,276 DEBUG [org.jboss.on.embedded.ui.SingleResourceAction] (http-127.0.0.1-8080-1) Removing Resource Resource[id=-39, type=Web Application (WAR), key=vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/embjopr/hellothere.war/, name=hellothere.war, parent=JBAS (default), version=?]...
> 2009-03-23 16:06:08,281 INFO [org.rhq.core.pc.inventory.DeleteResourceRunner] (ResourceFactory.executor-1) Deleting resource from request: 1
> 2009-03-23 16:06:08,282 DEBUG [org.rhq.plugins.jbossas5.ManagedDeploymentComponent] (ResourceContainer.invoker.nonDaemon-1) Undeploying deployment [vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/embjopr/hellothere.war/]...
> The console shows the WAR status as UNKNOWN. Refreshing the page, then shows the WAR application status as 'UP'.
> Attempting to Delete the same resource again, results in the same message to the client. The server, however, returns:
> 16:33:28,549 INFO [DeleteResourceRunner] Deleting resource from request: 1
> 16:33:28,553 INFO [DeployHandler] Remove, [vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/embjopr/hellothere.war/]
> 16:33:28,553 INFO [DeployHandler] Failed to complete command: [remove] for deployment: names=[vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/embjopr/hellothere.war/], copyContent=true
> org.jboss.profileservice.spi.NoSuchDeploymentException: Failed to find deployment in file: vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/embjopr/hellothere.war/
> at org.jboss.system.server.profileservice.repository.AbstractDeploymentRepository.getDeployment(AbstractDeploymentRepository.java:134)
> at org.jboss.system.server.profileservice.repository.BasicDeploymentRepository.removeDeployment(BasicDeploymentRepository.java:208)
> at org.jboss.profileservice.management.upload.remoting.DeployHandler.removeDeployment(DeployHandler.java:171)
> at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.remove(AbstractDeployHandler.java:322)
> at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:185)
--
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
From jira-events at lists.jboss.org Mon Mar 23 21:19:24 2009
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Mon, 23 Mar 2009 21:19:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-81) Exception
thrown when UPDATING .ear from Content Tab
In-Reply-To: <32547805.1235148710204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6266549.1237857564827.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shelly McGowan updated EMBJOPR-81:
----------------------------------
I can reproduce this with the latest jboss-as-5-plugin SNAPSHOT: jopr-jboss-as-5-plugin-2.2.0-20090323.091917-124.jar
> Exception thrown when UPDATING .ear from Content Tab
> ----------------------------------------------------
>
> Key: EMBJOPR-81
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-81
> Project: Embedded Jopr
> Issue Type: Bug
> Environment: JBoss AS Branch_5_x r84532, embjopr r162
> Still seen with: JBoss AS Branch 5_x r86127, embjopr r242
> Reporter: Shelly McGowan
> Assignee: Shelly McGowan
> Priority: Critical
> Fix For: 1.2
>
> Attachments: jbossas-default-server.log, resourceInstanceContent.seam.log
>
>
> Navigating to the Content Tab to update an existing resource results in a ServletException (see attached file, resourceInstanceContent.seam.log. While the exception is thrown on this action, it appears to be the result of a previous exception during the navigation to the Content tab. The Content tab is not consistently available but is during a specific navigation sequence. I'll identify the specific navigation sequence to reproduce and update this issue. I've also attached the jbossas server.log snippet.
--
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
From jira-events at lists.jboss.org Mon Mar 23 21:32:24 2009
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Mon, 23 Mar 2009 21:32:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-116)
java.lang.RuntimeException
thrown adding resource that was previously Deleted
Message-ID: <25665242.1237858344478.JavaMail.jira@cloud.prod.atl2.jboss.com>
java.lang.RuntimeException thrown adding resource that was previously Deleted
-----------------------------------------------------------------------------
Key: EMBJOPR-116
URL: https://jira.jboss.org/jira/browse/EMBJOPR-116
Project: Embedded Jopr
Issue Type: Bug
Components: Web App/Integration
Reporter: Shelly McGowan
Assignee: Shelly McGowan
Fix For: 1.2
Navigation:
Applications ==> Web Applications
Add new Resource
Browse to Resource
CONTINUE
When war archive status is 'UP', Delete .war from applications list
Confirmation: Successfully deleted Web Application (WAR) 'hellothere.war'.
Server side shows war was undeployed.
Follow the same navigation steps, but this time upon Adding Resource, the following is displayed to client (and server.log):
Failed to create Resource hellothere.war - cause: java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed DEPLOYMENTS IN ERROR: Deployment "vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed DEPLOYMENTS IN ERROR: Deployment "vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed
Reproducing this issue is blocked due to EMBJOPR-115. Assigning to myself for tracking.
--
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
From jira-events at lists.jboss.org Mon Mar 23 22:07:24 2009
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Mon, 23 Mar 2009 22:07:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-117) Control
operations not available for Application Resources
Message-ID: <26725600.1237860444503.JavaMail.jira@cloud.prod.atl2.jboss.com>
Control operations not available for Application Resources
----------------------------------------------------------
Key: EMBJOPR-117
URL: https://jira.jboss.org/jira/browse/EMBJOPR-117
Project: Embedded Jopr
Issue Type: Bug
Components: Plugin
Reporter: Shelly McGowan
Fix For: 1.2
The Control operations tab is not available (greyed out) to Applications types. The JBAS 4 plugin provides the following Control operations:
EAR:
REVERT
Tries to restore state of enterprise application from a saved backup.
WAR:
START - Start Web App
STOP - Stop Web App
RELOAD - Reloads Web App
REVERT - Tries to restore state of web app from a saved backup.
--
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
From jira-events at lists.jboss.org Mon Mar 23 22:11:29 2009
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Mon, 23 Mar 2009 22:11:29 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-118) Deployment
options not available when adding new application resource
Message-ID: <3412153.1237860689683.JavaMail.jira@cloud.prod.atl2.jboss.com>
Deployment options not available when adding new application resource
---------------------------------------------------------------------
Key: EMBJOPR-118
URL: https://jira.jboss.org/jira/browse/EMBJOPR-118
Project: Embedded Jopr
Issue Type: Bug
Affects Versions: 1.2
Reporter: Shelly McGowan
When adding a new resource (EAR or WAR), the only available option is to select the archive to be deployed. JBAS 4 plugin provides Deployment options that are not present in the JBAS 5 plugin; specifically,
Deploy Zipped - Indicates if deployed zipped or exploded.
Deploy Directory - Path to deploy the file
Create Backup - Should an existing file with this name be moved to backup ending in .bak
--
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
From jira-events at lists.jboss.org Mon Mar 23 23:48:24 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Mon, 23 Mar 2009 23:48:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-118) Deployment
options not available when adding new application resource
In-Reply-To: <3412153.1237860689683.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6988982.1237866504274.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer resolved EMBJOPR-118.
----------------------------------
Resolution: Duplicate Issue
This is a dup of https://jira.jboss.org/jira/browse/EMBJOPR-37.
> Deployment options not available when adding new application resource
> ---------------------------------------------------------------------
>
> Key: EMBJOPR-118
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-118
> Project: Embedded Jopr
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Shelly McGowan
>
> When adding a new resource (EAR or WAR), the only available option is to select the archive to be deployed. JBAS 4 plugin provides Deployment options that are not present in the JBAS 5 plugin; specifically,
> Deploy Zipped - Indicates if deployed zipped or exploded.
> Deploy Directory - Path to deploy the file
> Create Backup - Should an existing file with this name be moved to backup ending in .bak
--
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
From jira-events at lists.jboss.org Mon Mar 23 23:50:30 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Mon, 23 Mar 2009 23:50:30 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-37) AS5 plugin: add
support for the
deployDir and deployExploded deploy-time config options when creating an
EAR or WAR (just like we have in the AS4 plugin)
In-Reply-To: <29933902.1226598218791.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20358928.1237866630412.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer updated EMBJOPR-37:
--------------------------------
Description:
Another option was also recently added to the AS4 plugin:
Create Backup - Should an existing file with this name be moved to backup ending in .bak?
> AS5 plugin: add support for the deployDir and deployExploded deploy-time config options when creating an EAR or WAR (just like we have in the AS4 plugin)
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-37
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-37
> Project: Embedded Jopr
> Issue Type: Sub-task
> Components: Plugin
> Affects Versions: 1.0
> Reporter: Ian Springer
> Assignee: Ian Springer
> Fix For: 1.2
>
> Original Estimate: 2 hours, 45 minutes
> Remaining Estimate: 2 hours, 45 minutes
>
> Another option was also recently added to the AS4 plugin:
> Create Backup - Should an existing file with this name be moved to backup ending in .bak?
--
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
From jira-events at lists.jboss.org Tue Mar 24 16:30:24 2009
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Tue, 24 Mar 2009 16:30:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-119) Applications
are deployed to
server/default/tmp/embjopr directory instead of expected
server/default/deploy
Message-ID: <19060610.1237926624479.JavaMail.jira@cloud.prod.atl2.jboss.com>
Applications are deployed to server/default/tmp/embjopr directory instead of expected server/default/deploy
-----------------------------------------------------------------------------------------------------------
Key: EMBJOPR-119
URL: https://jira.jboss.org/jira/browse/EMBJOPR-119
Project: Embedded Jopr
Issue Type: Bug
Components: Plugin
Environment: JBoss AS r 86263, EMBJOPR r 253
Reporter: Shelly McGowan
Fix For: 1.2
Applications are typically deployed to JBoss AS in the server/${config}/deploy directory. Using the versions of JBossAS/EMBJOPR shown in the Environment field, the applications deployed via EMBJOPR get deployed to:
$JBOSS_HOME/server/${config}/tmp/embjopr directory. It is not clear why this change occurred but is affecting tests verifying successful deployment of applications including the view from the JMX console.
Tests failuring due to above:
testBasicEarDeployment
testEarSummaryTab
testDeployUnpackedEar
testWarSummaryTab
--
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
From jira-events at lists.jboss.org Tue Mar 24 17:58:24 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Tue, 24 Mar 2009 17:58:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-97) Add
ConnectionProperties resource config property to all Datasources
In-Reply-To: <24370956.1236881004408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6220972.1237931904710.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer resolved EMBJOPR-97.
---------------------------------
Resolution: Done
I confirmed JBAS-6643 is fixed in JBAS r86273.
> Add ConnectionProperties resource config property to all Datasources
> --------------------------------------------------------------------
>
> Key: EMBJOPR-97
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-97
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Reporter: Charles Crouch
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Attachments: screenshot-1.jpg
>
>
> See EMBJOPR-58 for how we noticed this was missing. Need to work out what type it should map to. Right now it seems to a simple one:
> ConnectionProperties.type=SimpleMetaType:java.lang.String:,
--
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
From jira-events at lists.jboss.org Wed Mar 25 09:43:26 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Wed, 25 Mar 2009 09:43:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-51) JBAS4 console:
Test script execution from embedded
Message-ID: <7612405.1237988606552.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer updated EMBJOPR-51:
--------------------------------
Fix Version/s: (was: 1.1)
Affects Version/s: 1.1
> 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
> Affects Versions: 1.1
> Reporter: Charles Crouch
> Assignee: Ian Springer
>
> 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
From jira-events at lists.jboss.org Wed Mar 25 09:43:30 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Wed, 25 Mar 2009 09:43:30 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Work started: (EMBJOPR-87) Operations
history list broken for specific pairs of operations
In-Reply-To: <27639330.1236196526089.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29190142.1237988610426.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on EMBJOPR-87 started by Ian Springer.
> Operations history list broken for specific pairs of operations
> ---------------------------------------------------------------
>
> Key: EMBJOPR-87
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-87
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Reporter: Charles Crouch
> Assignee: Ian Springer
> Fix For: 1.2
>
>
> Steps to reproduce
> 1) Pick a Datasource resource, e.g. DefaultDS
> 2) Execute the "List Formatted Sub Pool Statistics" operation, taking the defaults
> 3) Try to execute the "List Statistics" operation, and you will get the following:
> After this even going to the Control tab on this resource will throw the exception below.
> javax.faces.FacesException: javax.el.PropertyNotFoundException: Property 'map' not found on type org.rhq.core.domain.configuration.PropertySimple
> at javax.faces.component.UIOutput.getValue(UIOutput.java:187)
> at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getValue(HtmlBasicInputRenderer.java:201)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getCurrentValue(HtmlBasicRenderer.java:284)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeEnd(HtmlBasicRenderer.java:154)
> at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:242)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:239)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GridRenderer.renderRow(GridRenderer.java:180)
> at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:127)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:239)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
> at org.richfaces.renderkit.html.TogglePanelRenderer.handleFacets(TogglePanelRenderer.java:120)
> at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:124)
> at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:132)
> at org.ajax4jsf.renderkit.RendererBase.encodeEnd(RendererBase.java:135)
> at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:286)
> at org.ajax4jsf.renderkit.RendererBase.renderChildren(RendererBase.java:262)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:284)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
> at org.richfaces.renderkit.html.ColgroupRenderer.encodeChildren(ColgroupRenderer.java:98)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeOneRow(AbstractTableRenderer.java:361)
> at org.richfaces.renderkit.AbstractRowsRenderer.process(AbstractRowsRenderer.java:86)
> at org.ajax4jsf.model.SequenceDataModel.walk(SequenceDataModel.java:101)
> at org.ajax4jsf.component.UIDataAdaptor.walk(UIDataAdaptor.java:1151)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:106)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:91)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeTBody(AbstractTableRenderer.java:73)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeChildren(AbstractTableRenderer.java:80)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
> at javax.faces.render.Renderer.encodeChildren(Renderer.java:148)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933)
> at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592)
> at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
> at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196)
> at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
> 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:126)
> 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: javax.el.PropertyNotFoundException: Property 'map' not found on type org.rhq.core.domain.configuration.PropertySimple
> at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193)
> at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170)
> at javax.el.BeanELResolver.property(BeanELResolver.java:279)
> at javax.el.BeanELResolver.getValue(BeanELResolver.java:60)
> at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54)
> at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72)
> at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53)
> at org.jboss.el.parser.AstValue.getValue(AstValue.java:67)
> at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
> at javax.faces.component.UIOutput.getValue(UIOutput.java:184)
> ... 105 more
> If you swap steps 2) and 3)...
> 2) Execute the "List Statistics"operation
> 3) Try to execute the "List Formatted Sub Pool Statistics" operation, when you hit the OK button on the arguments page you will get the following:
> After this even going to the Control tab on this resource will throw the exception below:
> javax.faces.FacesException: javax.el.PropertyNotFoundException: Property 'stringValue' not found on type org.rhq.core.domain.configuration.PropertyMap
> at javax.faces.component.UIOutput.getValue(UIOutput.java:187)
> at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getValue(HtmlBasicInputRenderer.java:201)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getCurrentValue(HtmlBasicRenderer.java:284)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeEnd(HtmlBasicRenderer.java:154)
> at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:242)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:239)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:234)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:106)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
> at org.richfaces.renderkit.html.TogglePanelRenderer.handleFacets(TogglePanelRenderer.java:120)
> at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:124)
> at org.richfaces.renderkit.html.TogglePanelTemplate.doEncodeEnd(TogglePanelTemplate.java:132)
> at org.ajax4jsf.renderkit.RendererBase.encodeEnd(RendererBase.java:135)
> at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:286)
> at org.ajax4jsf.renderkit.RendererBase.renderChildren(RendererBase.java:262)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:284)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
> at org.richfaces.renderkit.html.ColgroupRenderer.encodeChildren(ColgroupRenderer.java:98)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeCellChildren(AbstractRowsRenderer.java:285)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeOneRow(AbstractTableRenderer.java:361)
> at org.richfaces.renderkit.AbstractRowsRenderer.process(AbstractRowsRenderer.java:86)
> at org.ajax4jsf.model.SequenceDataModel.walk(SequenceDataModel.java:101)
> at org.ajax4jsf.component.UIDataAdaptor.walk(UIDataAdaptor.java:1151)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:106)
> at org.richfaces.renderkit.AbstractRowsRenderer.encodeRows(AbstractRowsRenderer.java:91)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeTBody(AbstractTableRenderer.java:73)
> at org.richfaces.renderkit.AbstractTableRenderer.encodeChildren(AbstractTableRenderer.java:80)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
> at javax.faces.render.Renderer.encodeChildren(Renderer.java:148)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933)
> at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592)
> at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
> at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196)
> at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
> 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:126)
> 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: javax.el.PropertyNotFoundException: Property 'stringValue' not found on type org.rhq.core.domain.configuration.PropertyMap
> at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193)
> at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170)
> at javax.el.BeanELResolver.property(BeanELResolver.java:279)
> at javax.el.BeanELResolver.getValue(BeanELResolver.java:60)
> at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54)
> at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72)
> at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53)
> at org.jboss.el.parser.AstValue.getValue(AstValue.java:67)
> at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
> at javax.faces.component.UIOutput.getValue(UIOutput.java:184)
> ... 97 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
From jira-events at lists.jboss.org Wed Mar 25 11:01:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 25 Mar 2009 11:01:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-119) Applications
are deployed to
server/default/tmp/embjopr directory instead of expected
server/default/deploy
In-Reply-To: <19060610.1237926624479.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28084585.1237993285490.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-119:
--------------------------------------
Assignee: Charles Crouch
> Applications are deployed to server/default/tmp/embjopr directory instead of expected server/default/deploy
> -----------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-119
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-119
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Environment: JBoss AS r 86263, EMBJOPR r 253
> Reporter: Shelly McGowan
> Assignee: Charles Crouch
> Fix For: 1.2
>
>
> Applications are typically deployed to JBoss AS in the server/${config}/deploy directory. Using the versions of JBossAS/EMBJOPR shown in the Environment field, the applications deployed via EMBJOPR get deployed to:
> $JBOSS_HOME/server/${config}/tmp/embjopr directory. It is not clear why this change occurred but is affecting tests verifying successful deployment of applications including the view from the JMX console.
> Tests failuring due to above:
> testBasicEarDeployment
> testEarSummaryTab
> testDeployUnpackedEar
> testWarSummaryTab
--
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
From jira-events at lists.jboss.org Wed Mar 25 11:01:27 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 25 Mar 2009 11:01:27 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Work started: (EMBJOPR-119)
Applications are deployed
to server/default/tmp/embjopr directory instead of expected
server/default/deploy
In-Reply-To: <19060610.1237926624479.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28563393.1237993287632.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on EMBJOPR-119 started by Charles Crouch.
> Applications are deployed to server/default/tmp/embjopr directory instead of expected server/default/deploy
> -----------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-119
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-119
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Environment: JBoss AS r 86263, EMBJOPR r 253
> Reporter: Shelly McGowan
> Assignee: Charles Crouch
> Fix For: 1.2
>
>
> Applications are typically deployed to JBoss AS in the server/${config}/deploy directory. Using the versions of JBossAS/EMBJOPR shown in the Environment field, the applications deployed via EMBJOPR get deployed to:
> $JBOSS_HOME/server/${config}/tmp/embjopr directory. It is not clear why this change occurred but is affecting tests verifying successful deployment of applications including the view from the JMX console.
> Tests failuring due to above:
> testBasicEarDeployment
> testEarSummaryTab
> testDeployUnpackedEar
> testWarSummaryTab
--
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
From jira-events at lists.jboss.org Wed Mar 25 11:03:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 25 Mar 2009 11:03:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-119) Applications
are deployed to
server/default/tmp/embjopr directory instead of expected
server/default/deploy
In-Reply-To: <19060610.1237926624479.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33528989.1237993405469.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12459034#action_12459034 ]
Charles Crouch commented on EMBJOPR-119:
----------------------------------------
Inside the PC I'm seeing this
ContentSourcePackageDetailsKey[PackageDetailsKey[Name=C:\usr\apps\jboss\jboss-5.1.0.Beta1\server\default\tmp\embjopr\servlets-examples.war, Version=1.0 Arch=no-arch Type=file], ResourceTypeName=Web Application (WAR), PluginName=JBossAS5]
So it looks like we're setting the tmp\embjopr bit in the console, which doesnt look right. Regardless, I would have expected the deployment manager to have but the file in the correct place in the end.
> Applications are deployed to server/default/tmp/embjopr directory instead of expected server/default/deploy
> -----------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-119
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-119
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Environment: JBoss AS r 86263, EMBJOPR r 253
> Reporter: Shelly McGowan
> Assignee: Charles Crouch
> Fix For: 1.2
>
>
> Applications are typically deployed to JBoss AS in the server/${config}/deploy directory. Using the versions of JBossAS/EMBJOPR shown in the Environment field, the applications deployed via EMBJOPR get deployed to:
> $JBOSS_HOME/server/${config}/tmp/embjopr directory. It is not clear why this change occurred but is affecting tests verifying successful deployment of applications including the view from the JMX console.
> Tests failuring due to above:
> testBasicEarDeployment
> testEarSummaryTab
> testDeployUnpackedEar
> testWarSummaryTab
--
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
From jira-events at lists.jboss.org Wed Mar 25 12:04:26 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 25 Mar 2009 12:04:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-37) AS5 plugin:
add support for the
deployDir and deployExploded deploy-time config options when creating an
EAR or WAR (just like we have in the AS4 plugin)
In-Reply-To: <29933902.1226598218791.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7213590.1237997066073.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-37:
-------------------------------------
Assignee: Emanuel Muckenhuber (was: Ian Springer)
> AS5 plugin: add support for the deployDir and deployExploded deploy-time config options when creating an EAR or WAR (just like we have in the AS4 plugin)
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-37
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-37
> Project: Embedded Jopr
> Issue Type: Sub-task
> Components: Plugin
> Affects Versions: 1.0
> Reporter: Ian Springer
> Assignee: Emanuel Muckenhuber
> Fix For: 1.2
>
> Original Estimate: 2 hours, 45 minutes
> Remaining Estimate: 2 hours, 45 minutes
>
> Another option was also recently added to the AS4 plugin:
> Create Backup - Should an existing file with this name be moved to backup ending in .bak?
--
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
From jira-events at lists.jboss.org Wed Mar 25 12:10:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 25 Mar 2009 12:10:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-37) AS5 plugin:
add support for
the deployDir and deployExploded deploy-time config options when creating
an EAR or WAR (just like we have in the AS4 plugin)
In-Reply-To: <29933902.1226598218791.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2367908.1237997425010.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12459051#action_12459051 ]
Charles Crouch commented on EMBJOPR-37:
---------------------------------------
Create Backup: I don't think this is going to be supported in JBAS5 plugin
deployDir: this needs to be setup as a trait
deployExploded: Emanuel, can you investigate whether we could add another argument to the DeploymentManager, e.g. boolean deployedExploded, true means the archive gets unzipped before its deployed.
> AS5 plugin: add support for the deployDir and deployExploded deploy-time config options when creating an EAR or WAR (just like we have in the AS4 plugin)
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-37
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-37
> Project: Embedded Jopr
> Issue Type: Sub-task
> Components: Plugin
> Affects Versions: 1.0
> Reporter: Ian Springer
> Assignee: Emanuel Muckenhuber
> Fix For: 1.2
>
> Original Estimate: 2 hours, 45 minutes
> Remaining Estimate: 2 hours, 45 minutes
>
> Another option was also recently added to the AS4 plugin:
> Create Backup - Should an existing file with this name be moved to backup ending in .bak?
--
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
From jira-events at lists.jboss.org Wed Mar 25 12:10:26 2009
From: jira-events at lists.jboss.org (Ian Springer (JIRA))
Date: Wed, 25 Mar 2009 12:10:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-112) AS5 plugin:
After creating a
new Topic or Queue, the configuration properties are set to their default
values instead of to the values that were specified during creation
In-Reply-To: <5521467.1237832607224.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16929598.1237997426883.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer reassigned EMBJOPR-112:
------------------------------------
Assignee: Ian Springer
> AS5 plugin: After creating a new Topic or Queue, the configuration properties are set to their default values instead of to the values that were specified during creation
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-112
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-112
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS Branch_5_x r86203, embjopr r251
> Reporter: Farah Juma
> Assignee: Ian Springer
> Fix For: 1.2
>
>
> Steps to reproduce:
> Create a new Topic or Queue and set values for each of the properties (eg. Clustered, Down Cache Size, Full Size, Max Delivery Attempts, etc.). After clicking "Save", navigate to the "Configuration" page for the new resource. The property values that appear on the page seem to be the default values instead of the values that were specified during creation.
--
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
From jira-events at lists.jboss.org Wed Mar 25 14:27:24 2009
From: jira-events at lists.jboss.org (Farah Juma (JIRA))
Date: Wed, 25 Mar 2009 14:27:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-120) AS5 plugin: If
the
"use-java-context" property is left unset when creating a datasource, it
now gets set to "false" by default instead of to "true"
Message-ID: <32949621.1238005644403.JavaMail.jira@cloud.prod.atl2.jboss.com>
AS5 plugin: If the "use-java-context" property is left unset when creating a datasource, it now gets set to "false" by default instead of to "true"
---------------------------------------------------------------------------------------------------------------------------------------------------
Key: EMBJOPR-120
URL: https://jira.jboss.org/jira/browse/EMBJOPR-120
Project: Embedded Jopr
Issue Type: Bug
Components: Web App/Integration
Environment: JBoss AS Branch_5_x r86370, embjopr r256
Reporter: Farah Juma
Fix For: 1.2
Steps to reproduce:
Create a new datasource and leave the "Use Java Context" property unset. If you check the "use-java-context" property of the ManagedComponent or look at the -ds.xml file that was created, you'll see that "use-java-context" is set to "false". Until recently, this property was being set to "true" by default.
--
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
From jira-events at lists.jboss.org Wed Mar 25 15:15:26 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 25 Mar 2009 15:15:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-119) Applications
are deployed to
server/default/tmp/embjopr directory instead of expected
server/default/deploy
In-Reply-To: <19060610.1237926624479.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20656252.1238008526112.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12459078#action_12459078 ]
Charles Crouch commented on EMBJOPR-119:
----------------------------------------
So the /server/${config}/tmp/embjopr value coming from the console is fine. The deployment manager wasnt putting the file in the right place because we were telling it to not copy the deployment to /deploy, telling it to do the copy and everything works great.
Ian fixed this in JOPR r323.
> Applications are deployed to server/default/tmp/embjopr directory instead of expected server/default/deploy
> -----------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-119
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-119
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Environment: JBoss AS r 86263, EMBJOPR r 253
> Reporter: Shelly McGowan
> Assignee: Charles Crouch
> Fix For: 1.2
>
>
> Applications are typically deployed to JBoss AS in the server/${config}/deploy directory. Using the versions of JBossAS/EMBJOPR shown in the Environment field, the applications deployed via EMBJOPR get deployed to:
> $JBOSS_HOME/server/${config}/tmp/embjopr directory. It is not clear why this change occurred but is affecting tests verifying successful deployment of applications including the view from the JMX console.
> Tests failuring due to above:
> testBasicEarDeployment
> testEarSummaryTab
> testDeployUnpackedEar
> testWarSummaryTab
--
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
From jira-events at lists.jboss.org Wed Mar 25 15:15:28 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 25 Mar 2009 15:15:28 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-119) Applications
are deployed to
server/default/tmp/embjopr directory instead of expected
server/default/deploy
In-Reply-To: <19060610.1237926624479.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28488730.1238008528013.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch resolved EMBJOPR-119.
------------------------------------
Resolution: Done
> Applications are deployed to server/default/tmp/embjopr directory instead of expected server/default/deploy
> -----------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-119
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-119
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Environment: JBoss AS r 86263, EMBJOPR r 253
> Reporter: Shelly McGowan
> Assignee: Charles Crouch
> Fix For: 1.2
>
>
> Applications are typically deployed to JBoss AS in the server/${config}/deploy directory. Using the versions of JBossAS/EMBJOPR shown in the Environment field, the applications deployed via EMBJOPR get deployed to:
> $JBOSS_HOME/server/${config}/tmp/embjopr directory. It is not clear why this change occurred but is affecting tests verifying successful deployment of applications including the view from the JMX console.
> Tests failuring due to above:
> testBasicEarDeployment
> testEarSummaryTab
> testDeployUnpackedEar
> testWarSummaryTab
--
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
From jira-events at lists.jboss.org Wed Mar 25 15:15:30 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 25 Mar 2009 15:15:30 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-119) Applications
are deployed to
server/default/tmp/embjopr directory instead of expected
server/default/deploy
In-Reply-To: <19060610.1237926624479.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10215117.1238008530615.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-119:
--------------------------------------
Assignee: Ian Springer (was: Charles Crouch)
> Applications are deployed to server/default/tmp/embjopr directory instead of expected server/default/deploy
> -----------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-119
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-119
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Plugin
> Environment: JBoss AS r 86263, EMBJOPR r 253
> Reporter: Shelly McGowan
> Assignee: Ian Springer
> Fix For: 1.2
>
>
> Applications are typically deployed to JBoss AS in the server/${config}/deploy directory. Using the versions of JBossAS/EMBJOPR shown in the Environment field, the applications deployed via EMBJOPR get deployed to:
> $JBOSS_HOME/server/${config}/tmp/embjopr directory. It is not clear why this change occurred but is affecting tests verifying successful deployment of applications including the view from the JMX console.
> Tests failuring due to above:
> testBasicEarDeployment
> testEarSummaryTab
> testDeployUnpackedEar
> testWarSummaryTab
--
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
From jira-events at lists.jboss.org Wed Mar 25 15:31:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 25 Mar 2009 15:31:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Resolved: (EMBJOPR-115) Applications
cannot be Deleted
In-Reply-To: <29019912.1237841065439.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32991648.1238009485129.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch resolved EMBJOPR-115.
------------------------------------
Resolution: Done
After EMBJOPR-119 was fixed, I'm no longer seeing this for Web archives. I wouldnt expect to see it for EARs either.
On delete, the app is undeployed and disappears from the list.
> Applications cannot be Deleted
> ------------------------------
>
> Key: EMBJOPR-115
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-115
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS r 86207, EMBJOPR r251
> Reporter: Shelly McGowan
> Fix For: 1.2
>
>
> Navigation:
> From Applications ==> Web Applications
> Add New Resource
> Enter Resource name, CONTINUE
> Wait till the web archive status shows it is 'UP'.
> Delete the WAR archive.
> Confirmation Message: Successfully deleted Web Application (WAR) 'hellothere.war'.
> Server side:
> 2009-03-23 16:06:08,276 DEBUG [org.jboss.on.embedded.ui.SingleResourceAction] (http-127.0.0.1-8080-1) Removing Resource Resource[id=-39, type=Web Application (WAR), key=vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/embjopr/hellothere.war/, name=hellothere.war, parent=JBAS (default), version=?]...
> 2009-03-23 16:06:08,281 INFO [org.rhq.core.pc.inventory.DeleteResourceRunner] (ResourceFactory.executor-1) Deleting resource from request: 1
> 2009-03-23 16:06:08,282 DEBUG [org.rhq.plugins.jbossas5.ManagedDeploymentComponent] (ResourceContainer.invoker.nonDaemon-1) Undeploying deployment [vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/embjopr/hellothere.war/]...
> The console shows the WAR status as UNKNOWN. Refreshing the page, then shows the WAR application status as 'UP'.
> Attempting to Delete the same resource again, results in the same message to the client. The server, however, returns:
> 16:33:28,549 INFO [DeleteResourceRunner] Deleting resource from request: 1
> 16:33:28,553 INFO [DeployHandler] Remove, [vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/embjopr/hellothere.war/]
> 16:33:28,553 INFO [DeployHandler] Failed to complete command: [remove] for deployment: names=[vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/embjopr/hellothere.war/], copyContent=true
> org.jboss.profileservice.spi.NoSuchDeploymentException: Failed to find deployment in file: vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/embjopr/hellothere.war/
> at org.jboss.system.server.profileservice.repository.AbstractDeploymentRepository.getDeployment(AbstractDeploymentRepository.java:134)
> at org.jboss.system.server.profileservice.repository.BasicDeploymentRepository.removeDeployment(BasicDeploymentRepository.java:208)
> at org.jboss.profileservice.management.upload.remoting.DeployHandler.removeDeployment(DeployHandler.java:171)
> at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.remove(AbstractDeployHandler.java:322)
> at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:185)
--
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
From jira-events at lists.jboss.org Wed Mar 25 15:37:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 25 Mar 2009 15:37:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-116)
java.lang.RuntimeException
thrown adding resource that was previously Deleted
In-Reply-To: <25665242.1237858344478.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7990447.1238009845823.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12459082#action_12459082 ]
Charles Crouch commented on EMBJOPR-116:
----------------------------------------
Even after EMBJOPR-119 was fixed I'm still seeing this. The underlying exception is below. This log includes deploying the war (servlets-examples.war) originally, deleting it, then trying to deploy it again (where it fails).
13:59:38,359 INFO [CreateResourceRunner] Creating resource through report: CreateResourceReport: ResourceType=[ResourceType
[id=0, category=Service, name=Web Application (WAR), plugin=JBossAS5]], ResourceKey=[null]
13:59:38,453 INFO [DeployHandler] Handle stream, deploymentTarget: names=[servlets-examples.war], copyContent=true, descrip
tion=file:/C:/usr/apps/jboss/jboss-5.1.0.Beta1/server/default/tmp/embjopr/servlets-examples.war
13:59:38,484 INFO [DeployHandler] End handle stream, repositoryName: vfszip:/C:/usr/apps/jboss/jboss-5.1.0.Beta1/server/def
ault/deploy/servlets-examples.war/
13:59:38,500 INFO [DeployHandler] Begin start, [vfszip:/C:/usr/apps/jboss/jboss-5.1.0.Beta1/server/default/deploy/servlets-
examples.war/]
13:59:38,968 INFO [TomcatDeployment] deploy, ctxPath=/servlets-examples
13:59:39,062 INFO [STDOUT] ContextListener: attributeAdded('com.sun.faces.config.WebConfiguration', 'com.sun.faces.config.W
ebConfiguration at 629cf0')
13:59:39,062 INFO [STDOUT] ContextListener: attributeRemoved('com.sun.faces.config.WebConfiguration', 'com.sun.faces.config
.WebConfiguration at 629cf0')
13:59:39,078 INFO [[/servlets-examples]] ContextListener: contextInitialized()
13:59:39,078 INFO [[/servlets-examples]] SessionListener: contextInitialized()
13:59:39,093 INFO [DeployHandler] End start, [vfszip:/C:/usr/apps/jboss/jboss-5.1.0.Beta1/server/default/deploy/servlets-ex
amples.war/]
13:59:39,093 INFO [CreateResourceRunner] Sending create response to server: CreateResourceResponse[RequestId=1, Status=Succ
ess]
13:59:39,093 INFO [RuntimeDiscoveryExecutor] Running runtime discovery scan rooted at platform...
13:59:42,109 WARN [ManagementViewImpl] Failed to merged the following runtime ManagedObjects: {jboss.web:name=http-127.0.0.
1-8080,type=ThreadPool/=ManagedObject{jboss.web:name=http-127.0.0.1-8080,type=ThreadPool}, jboss.system:type=ServerInfo/jbos
s.system:type=ServerInfo=ManagedObject{jboss.system:type=ServerInfo}, jboss.web:name=http-127.0.0.1-8080,type=GlobalRequestP
rocessor/=ManagedObject{jboss.web:name=http-127.0.0.1-8080,type=GlobalRequestProcessor}, jboss.web:host=127.0.0.1,type=Host/
=ManagedObject{jboss.web:host=127.0.0.1,type=Host}}
13:59:42,562 WARN [InventoryManager] ***PERF*** discovery for [No Tx Datasource] Resources took 3437 ms.
13:59:42,609 INFO [NavigationContent] Resource of type [ResourceType[id=0, category=Service, name=Web Application (WAR), pl
ugin=JBossAS5]] added beneath Resource [Resource[id=-3, type=JBossAS Server, key=/usr/bin/jboss, name=JBAS (default), parent
=LENOVO-A4A86477, version=5.0 CR1]].
13:59:42,625 INFO [ContentManager] Discovered 1 new packages for Resource with id [-45].
13:59:42,718 INFO [RuntimeDiscoveryExecutor] Scanned 0 servers and found 0 total descendant Resources.
14:06:43,921 INFO [RuntimeDiscoveryExecutor] Running runtime discovery scan rooted at platform...
14:06:44,343 INFO [RuntimeDiscoveryExecutor] Scanned 0 servers and found 0 total descendant Resources.
14:06:57,656 INFO [DeleteResourceRunner] Deleting resource from request: 1
14:06:57,656 INFO [DeployHandler] Remove, [vfszip:/C:/usr/apps/jboss/jboss-5.1.0.Beta1/server/default/deploy/servlets-examp
les.war/]
14:06:57,671 INFO [NavigationContent] Resource [Resource[id=-45, type=Web Application (WAR), key=vfszip:/C:/usr/apps/jboss/
jboss-5.1.0.Beta1/server/default/deploy/servlets-examples.war/, name=servlets-examples.war, parent=JBAS (default), version=?
]] deleted.
14:06:57,687 INFO [RuntimeDiscoveryExecutor] Running runtime discovery scan rooted at platform...
14:07:00,906 WARN [ManagementViewImpl] Failed to merged the following runtime ManagedObjects: {jboss.web:name=http-127.0.0.
1-8080,type=ThreadPool/=ManagedObject{jboss.web:name=http-127.0.0.1-8080,type=ThreadPool}, jboss.system:type=ServerInfo/jbos
s.system:type=ServerInfo=ManagedObject{jboss.system:type=ServerInfo}, jboss.web:name=http-127.0.0.1-8080,type=GlobalRequestP
rocessor/=ManagedObject{jboss.web:name=http-127.0.0.1-8080,type=GlobalRequestProcessor}, jboss.web:host=127.0.0.1,type=Host/
=ManagedObject{jboss.web:host=127.0.0.1,type=Host}}
14:07:01,265 WARN [InventoryManager] ***PERF*** discovery for [No Tx Datasource] Resources took 3422 ms.
14:07:01,406 INFO [RuntimeDiscoveryExecutor] Scanned 0 servers and found 0 total descendant Resources.
14:07:39,140 INFO [CreateResourceRunner] Creating resource through report: CreateResourceReport: ResourceType=[ResourceType
[id=0, category=Service, name=Web Application (WAR), plugin=JBossAS5]], ResourceKey=[null]
14:07:39,156 INFO [DeployHandler] Handle stream, deploymentTarget: names=[servlets-examples.war], copyContent=true, descrip
tion=file:/C:/usr/apps/jboss/jboss-5.1.0.Beta1/server/default/tmp/embjopr/servlets-examples.war
14:07:39,156 INFO [DeployHandler] End handle stream, repositoryName: vfszip:/C:/usr/apps/jboss/jboss-5.1.0.Beta1/server/def
ault/deploy/servlets-examples.war/
14:07:39,187 INFO [DeployHandler] Begin start, [vfszip:/C:/usr/apps/jboss/jboss-5.1.0.Beta1/server/default/deploy/servlets-
examples.war/]
14:07:39,203 INFO [TomcatDeployment] undeploy, ctxPath=/servlets-examples
14:07:39,203 INFO [[/servlets-examples]] SessionListener: contextDestroyed()
14:07:39,203 INFO [[/servlets-examples]] ContextListener: contextDestroyed()
14:07:39,281 INFO [TomcatDeployment] deploy, ctxPath=/servlets-examples
14:07:39,328 ERROR [StandardContext] Error starting static Resources
java.lang.IllegalArgumentException: Document base C:\usr\apps\jboss\jboss-5.1.0.Beta1\server\default\tmp\awa37-77ezjb-fsq4pb
ys-1-fsqdqxcf-8wy\servlets-examples.war does not exist or is not a readable directory
at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:148)
at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4021)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4188)
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:312)
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:144)
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461)
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
at org.jboss.web.deployers.WebModule.start(WebModule.java:97)
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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
at $Proxy36.start(Unknown Source)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextActi
on.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
at org.jboss.system.ServiceController.start(ServiceController.java:460)
at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.jav
a:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.processCheckComplete(AbstractDeployHand
ler.java:330)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:240)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:169)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1708)
at org.jboss.remoting.Client.invoke(Client.java:612)
at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.ja
va:285)
at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.start(StreamingDeploymentTarget.jav
a:170)
at org.jboss.profileservice.management.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:222)
at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:85)
at org.rhq.plugins.jbossas5.util.DeploymentUtils.deployArchive(DeploymentUtils.java:75)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createContentBasedResource(ApplicationServerComponent.java:26
9)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:129)
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.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
14:07:39,343 ERROR [StandardContext] Error in resourceStart()
14:07:39,343 ERROR [StandardContext] Context [/servlets-examples] startup failed due to previous errors
> java.lang.RuntimeException thrown adding resource that was previously Deleted
> -----------------------------------------------------------------------------
>
> Key: EMBJOPR-116
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-116
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Reporter: Shelly McGowan
> Assignee: Shelly McGowan
> Fix For: 1.2
>
>
> Navigation:
> Applications ==> Web Applications
> Add new Resource
> Browse to Resource
> CONTINUE
> When war archive status is 'UP', Delete .war from applications list
> Confirmation: Successfully deleted Web Application (WAR) 'hellothere.war'.
> Server side shows war was undeployed.
> Follow the same navigation steps, but this time upon Adding Resource, the following is displayed to client (and server.log):
> Failed to create Resource hellothere.war - cause: java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed DEPLOYMENTS IN ERROR: Deployment "vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed DEPLOYMENTS IN ERROR: Deployment "vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed
> Reproducing this issue is blocked due to EMBJOPR-115. Assigning to myself for tracking.
--
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
From jira-events at lists.jboss.org Wed Mar 25 15:39:24 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 25 Mar 2009 15:39:24 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-116)
java.lang.RuntimeException
thrown adding resource that was previously Deleted
In-Reply-To: <25665242.1237858344478.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6555467.1238009964802.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-116:
--------------------------------------
Assignee: Emanuel Muckenhuber (was: Shelly McGowan)
Assigning to Emanuel to investigate
> java.lang.RuntimeException thrown adding resource that was previously Deleted
> -----------------------------------------------------------------------------
>
> Key: EMBJOPR-116
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-116
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Reporter: Shelly McGowan
> Assignee: Emanuel Muckenhuber
> Fix For: 1.2
>
> Attachments: servlets-examples.war
>
>
> Navigation:
> Applications ==> Web Applications
> Add new Resource
> Browse to Resource
> CONTINUE
> When war archive status is 'UP', Delete .war from applications list
> Confirmation: Successfully deleted Web Application (WAR) 'hellothere.war'.
> Server side shows war was undeployed.
> Follow the same navigation steps, but this time upon Adding Resource, the following is displayed to client (and server.log):
> Failed to create Resource hellothere.war - cause: java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed DEPLOYMENTS IN ERROR: Deployment "vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed DEPLOYMENTS IN ERROR: Deployment "vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed
> Reproducing this issue is blocked due to EMBJOPR-115. Assigning to myself for tracking.
--
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
From jira-events at lists.jboss.org Wed Mar 25 15:39:26 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 25 Mar 2009 15:39:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-116)
java.lang.RuntimeException
thrown adding resource that was previously Deleted
In-Reply-To: <25665242.1237858344478.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12624849.1238009966595.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch updated EMBJOPR-116:
-----------------------------------
Attachment: servlets-examples.war
Attaching the simple servlets-examples.war file used to reproduce this issue. Using the embedded console: add the .war, delete it, try to add it again, bang...
> java.lang.RuntimeException thrown adding resource that was previously Deleted
> -----------------------------------------------------------------------------
>
> Key: EMBJOPR-116
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-116
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Reporter: Shelly McGowan
> Assignee: Emanuel Muckenhuber
> Fix For: 1.2
>
> Attachments: servlets-examples.war
>
>
> Navigation:
> Applications ==> Web Applications
> Add new Resource
> Browse to Resource
> CONTINUE
> When war archive status is 'UP', Delete .war from applications list
> Confirmation: Successfully deleted Web Application (WAR) 'hellothere.war'.
> Server side shows war was undeployed.
> Follow the same navigation steps, but this time upon Adding Resource, the following is displayed to client (and server.log):
> Failed to create Resource hellothere.war - cause: java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed DEPLOYMENTS IN ERROR: Deployment "vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed DEPLOYMENTS IN ERROR: Deployment "vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed
> Reproducing this issue is blocked due to EMBJOPR-115. Assigning to myself for tracking.
--
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
From jira-events at lists.jboss.org Wed Mar 25 16:00:26 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 25 Mar 2009 16:00:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-116)
java.lang.RuntimeException
thrown adding resource that was previously Deleted
In-Reply-To: <25665242.1237858344478.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31066217.1238011226409.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12459086#action_12459086 ]
Charles Crouch commented on EMBJOPR-116:
----------------------------------------
I'm seeing this with AS5 Beta1 + HEAD of RHQ/Jopr/EmbJopr as of 3/25
> java.lang.RuntimeException thrown adding resource that was previously Deleted
> -----------------------------------------------------------------------------
>
> Key: EMBJOPR-116
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-116
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Reporter: Shelly McGowan
> Assignee: Emanuel Muckenhuber
> Fix For: 1.2
>
> Attachments: servlets-examples.war
>
>
> Navigation:
> Applications ==> Web Applications
> Add new Resource
> Browse to Resource
> CONTINUE
> When war archive status is 'UP', Delete .war from applications list
> Confirmation: Successfully deleted Web Application (WAR) 'hellothere.war'.
> Server side shows war was undeployed.
> Follow the same navigation steps, but this time upon Adding Resource, the following is displayed to client (and server.log):
> Failed to create Resource hellothere.war - cause: java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed DEPLOYMENTS IN ERROR: Deployment "vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed DEPLOYMENTS IN ERROR: Deployment "vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed
> Reproducing this issue is blocked due to EMBJOPR-115. Assigning to myself for tracking.
--
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
From jira-events at lists.jboss.org Wed Mar 25 16:33:25 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 25 Mar 2009 16:33:25 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-114) AS5 plugin:
The "List All
Subscriptions" operation for a Topic fails due to a NullPointerException
In-Reply-To: <18431109.1237836266567.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28258543.1238013205161.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch reassigned EMBJOPR-114:
--------------------------------------
Assignee: Charles Crouch
> AS5 plugin: The "List All Subscriptions" operation for a Topic fails due to a NullPointerException
> --------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-114
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-114
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS Branch_5_x r86203, embjopr r251
> Reporter: Farah Juma
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Attachments: ListAllSubscriptions.png
>
>
> Steps to reproduce:
> Navigate to the "Control" page for a Topic. Click on the "List All Subscriptions" button. The operations history table shows that the operation failed. Click on the "Show/Hide Details" link. The following error message gets displayed, as seen in the attached screenshot:
> java.lang.NullPointerException
> at org.rhq.plugins.jbossas5.util.ConversionUtils.instanceOf(ConversionUtils.java:438)
> at org.rhq.plugins.jbossas5.util.ConversionUtils.convertManagedOperationResults(ConversionUtils.java:427)
> at org.rhq.plugins.jbossas5.ManagedComponentComponent.invokeOperation(ManagedComponentComponent.java:136)
> 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.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 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
From jira-events at lists.jboss.org Wed Mar 25 16:33:26 2009
From: jira-events at lists.jboss.org (Charles Crouch (JIRA))
Date: Wed, 25 Mar 2009 16:33:26 -0400 (EDT)
Subject: [embjopr-issues] [JBoss JIRA] Work started: (EMBJOPR-114) AS5
plugin: The "List All
Subscriptions" operation for a Topic fails due to a NullPointerException
In-Reply-To: <18431109.1237836266567.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15847157.1238013206852.JavaMail.jira@cloud.prod.atl2.jboss.com>
[ https://jira.jboss.org/jira/browse/EMBJOPR-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on EMBJOPR-114 started by Charles Crouch.
> AS5 plugin: The "List All Subscriptions" operation for a Topic fails due to a NullPointerException
> --------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-114
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-114
> Project: Embedded Jopr
> Issue Type: Bug
> Components: Web App/Integration
> Environment: JBoss AS Branch_5_x r86203, embjopr r251
> Reporter: Farah Juma
> Assignee: Charles Crouch
> Fix For: 1.2
>
> Attachments: ListAllSubscriptions.png
>
>
> Steps to reproduce:
> Navigate to the "Control" page for a Topic. Click on the "List All Subscriptions" button. The operations history table shows that the operation failed. Click on the "Show/Hide Details" link. The following error message gets displayed, as seen in the attached screenshot:
> java.lang.NullPointerException
> at org.rhq.plugins.jbossas5.util.ConversionUtils.instanceOf(ConversionUtils.java:438)
> at org.rhq.plugins.jbossas5.util.ConversionUtils.convertManagedOperationResults(ConversionUtils.java:427)
> at org.rhq.plugins.jbossas5.ManagedComponentComponent.invokeOperation(ManagedComponentComponent.java:136)
> 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.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 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