July 2010 - embjopr-issues - Jboss List Archives

[JBoss JIRA] Created: (EMBJOPR-99) Root node Metrics Trait Values table has inappropriate layout

by Ondrej Žižka (JIRA)

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

12 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (EMBJOPR-312) Repeated EAR Restart operation: javax.el.PropertyNotFoundException: Property 'statusMessages' not found on type org.jboss.seam.Namespace

by Ondrej Žižka (JIRA)

Repeated EAR Restart operation: javax.el.PropertyNotFoundException: Property 'statusMessages' not found on type org.jboss.seam.Namespace ---------------------------------------------------------------------------------------------------------------------------------------- Key: EMBJOPR-312 URL: https://jira.jboss.org/browse/EMBJOPR-312 Project: Embedded Jopr Issue Type: Bug Affects Versions: 1.4.0 Environment: EAP 5.1.0.CR1 Reporter: Ondrej Žižka Priority: Minor STR: 1) Using the console, deploy an ear (e.g. the attached one) 2) Click it, go to controls tab 3) Invoke the Restart operation until you get the error: javax.el.PropertyNotFoundException: Property 'statusMessages' not found on type org.jboss.seam.Namespace See attached log. This is a bit rare use case as you need to click really fast. But the root cause might cause problems somewhere else, esp. for customers with slower machines. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (EMBJOPR-315) Script: shutdown.sh -S does not work

by Ondrej Žižka (JIRA)

Script: shutdown.sh -S does not work ------------------------------------ Key: EMBJOPR-315 URL: https://jira.jboss.org/browse/EMBJOPR-315 Project: Embedded Jopr Issue Type: Bug Affects Versions: 1.4.0 Environment: Linux, AS 6 M4 Reporter: Ondrej Žižka Running the shutdown.sh script with args "-S" does not do it's job, only shows this output: "A JMX client to shutdown (exit or halt) a remote JBoss server." >From the terminal, the command works. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (EMBJOPR-63) Login page content shifted towards the top in IE7

by Charles Crouch (JIRA)

Login page content shifted towards the top in IE7 ------------------------------------------------- Key: EMBJOPR-63 URL: https://jira.jboss.org/jira/browse/EMBJOPR-63 Project: Embedded Jopr Issue Type: Bug Components: Look 'n' Feel (html/css) Affects Versions: 1.1 Reporter: Charles Crouch See 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

13 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (EMBJOPR-106) Add Refresh button to Summary tab of Applications node and subnodes

by Ondrej Žižka (JIRA)

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

13 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (EMBJOPR-101) Nav tree JS object (Tree.Item) is not ready after page refresh, causing ScriptException: TypeError: Cannot call method "fireExpansionEvent"

by Ondrej Žižka (JIRA)

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

13 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (EMBJOPR-307) EAP 5.1: Empty "JMS Destinations" node

by Ondrej Žižka (JIRA)

EAP 5.1: Empty "JMS Destinations" node --------------------------------------- Key: EMBJOPR-307 URL: https://jira.jboss.org/browse/EMBJOPR-307 Project: Embedded Jopr Issue Type: Bug Affects Versions: 1.4.0 Reporter: Ondrej Žižka Priority: Minor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (EMBJOPR-61) Problems with pagination on Applications subcategory

by Charles Crouch (JIRA)

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.1 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

14 years, 4 months

4
5
0 / 0

[JBoss JIRA] Commented: (EMBJOPR-176) Call to org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource() timed out

by Ian Springer (JIRA)

[ https://jira.jboss.org/browse/EMBJOPR-176?page=com.atlassian.jira.plugin.... ] Ian Springer commented on EMBJOPR-176: -------------------------------------- Fixed in RHQ git - commit d242d0c, and pushed to release-3.0.0 branch. This will most likely make it into EmbJopr 1.3.4.GA (for inclusion in EAP 5.1 and EWP 5.1) and EmbJopr 1.4.0.GA (for inclusion in AS 6.0). > Call to org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource() timed out > -------------------------------------------------------------------------------------- > > Key: EMBJOPR-176 > URL: https://jira.jboss.org/browse/EMBJOPR-176 > Project: Embedded Jopr > Issue Type: Bug > Environment: EmbJopr testsuite - testEarDeploymentRepeated() > Reporter: Ondrej Žižka > Assignee: Ian Springer > > After deploying and undeploying the same EAR for several times (around 60), the call to testEarDeploymentRepeated() times out. > Failed to create Resource eardeployment.ear - cause: org.rhq.core.pc.inventory.TimeoutException: Call to [org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource()] with args [[CreateResourceReport: ResourceType=[ResourceType[id=0, category=Service, name=Enterprise Application (EAR), plugin=JBossAS5]], ResourceKey=[null]]] timed out. Invocation thread will be interrupted > at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invokeInNewThreadWithLock(ResourceContainer.java:437) > at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invoke(ResourceContainer.java:406) > at $Proxy264.createResource(Unknown Source) > at org.rhq.core.pc.inventory.CreateResourceRunner.call(CreateResourceRunner.java:113) > 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) > Failed to create Resource eardeployment.ear - cause: org.rhq.core.pc.inventory.TimeoutException: Call to [org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource()] with args [[CreateResourceReport: ResourceType=[ResourceType[id=0, category=Service, name=Enterprise Application (EAR), plugin=JBossAS5]], ResourceKey=[null]]] timed out. Invocation thread will be interrupted > at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invokeInNewThreadWithLock(ResourceContainer.java:437) > at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invoke(ResourceContainer.java:406) > at $Proxy264.createResource(Unknown Source) > at org.rhq.core.pc.inventory.CreateResourceRunner.call(CreateResourceRunner.java:113) > 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (EMBJOPR-176) Call to org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource() timed out

by Ian Springer (JIRA)

[ https://jira.jboss.org/browse/EMBJOPR-176?page=com.atlassian.jira.plugin.... ] Ian Springer commented on EMBJOPR-176: -------------------------------------- I was able to reproduce this on the very first first try using a 180MB EAR file. So the 1 minute timeout is obviously not long enough. I'm going to increase it to 10 minutes. > Call to org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource() timed out > -------------------------------------------------------------------------------------- > > Key: EMBJOPR-176 > URL: https://jira.jboss.org/browse/EMBJOPR-176 > Project: Embedded Jopr > Issue Type: Bug > Environment: EmbJopr testsuite - testEarDeploymentRepeated() > Reporter: Ondrej Žižka > Assignee: Ian Springer > > After deploying and undeploying the same EAR for several times (around 60), the call to testEarDeploymentRepeated() times out. > Failed to create Resource eardeployment.ear - cause: org.rhq.core.pc.inventory.TimeoutException: Call to [org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource()] with args [[CreateResourceReport: ResourceType=[ResourceType[id=0, category=Service, name=Enterprise Application (EAR), plugin=JBossAS5]], ResourceKey=[null]]] timed out. Invocation thread will be interrupted > at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invokeInNewThreadWithLock(ResourceContainer.java:437) > at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invoke(ResourceContainer.java:406) > at $Proxy264.createResource(Unknown Source) > at org.rhq.core.pc.inventory.CreateResourceRunner.call(CreateResourceRunner.java:113) > 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) > Failed to create Resource eardeployment.ear - cause: org.rhq.core.pc.inventory.TimeoutException: Call to [org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource()] with args [[CreateResourceReport: ResourceType=[ResourceType[id=0, category=Service, name=Enterprise Application (EAR), plugin=JBossAS5]], ResourceKey=[null]]] timed out. Invocation thread will be interrupted > at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invokeInNewThreadWithLock(ResourceContainer.java:437) > at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invoke(ResourceContainer.java:406) > at $Proxy264.createResource(Unknown Source) > at org.rhq.core.pc.inventory.CreateResourceRunner.call(CreateResourceRunner.java:113) > 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

embjopr-issues July 2010