June 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, 1 month

3
5
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

12 years, 6 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

12 years, 9 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

12 years, 9 months

3
4
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

13 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (EMBJOPR-306) Admin console concurrency crash.

by Julian Coleman (JIRA)

Admin console concurrency crash. -------------------------------- Key: EMBJOPR-306 URL: https://jira.jboss.org/browse/EMBJOPR-306 Project: Embedded Jopr Issue Type: Bug Affects Versions: 1.3.2 Environment: SOA 5.0.2 (based on 5.0.1) Reporter: Julian Coleman Priority: Minor Selecting the same item quickly more than once in the admin console while the server is busy/slow to respond can cause the admin console to generate an error screen, with: 2010-06-17 15:48:09,800 WARN [org.jboss.seam.jsf.SeamPhaseListener] (http-127.0.0.1-8080-1) uncaught exception, passing to exception handler org.jboss.seam.ConcurrentRequestTimeoutException: Concurrent call to conversation and a large stacktrace written to the server.log. Note, that this is hard to reproduce. See SOA-2127 for 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (EMBJOPR-305) Upgrade hornetq-jopr-plugin to 1.0.0.CR2

by Shelly McGowan (JIRA)

Upgrade hornetq-jopr-plugin to 1.0.0.CR2 ---------------------------------------- Key: EMBJOPR-305 URL: https://jira.jboss.org/browse/EMBJOPR-305 Project: Embedded Jopr Issue Type: Bug Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 1.4.0 Attachments: JMSTopic.png When testing the 1.4.0.CR1 candidate, an issue was uncovered where the JMS Topic state was UNKNOWN. This has been fixed but will require an update to 1.0.0.CR2. -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Resolved: (EMBJOPR-296) JSFUnit tests fail due to removal of messaging configuration files in JBoss AS 6

by Shelly McGowan (JIRA)

[ https://jira.jboss.org/browse/EMBJOPR-296?page=com.atlassian.jira.plugin.... ] Shelly McGowan resolved EMBJOPR-296. ------------------------------------ Resolution: Done The jsfunit pom has been adjusted to remove these files being copied. Closing. > JSFUnit tests fail due to removal of messaging configuration files in JBoss AS 6 > -------------------------------------------------------------------------------- > > Key: EMBJOPR-296 > URL: https://jira.jboss.org/browse/EMBJOPR-296 > Project: Embedded Jopr > Issue Type: Bug > Reporter: Shelly McGowan > Assignee: Shelly McGowan > Fix For: 1.4.0 > > > Part of the test set up was to enable message counters in messaging-service.xml. These files no longer exist due to the HornetQ upgrade causing the build to fail. > Error for project: JSFUnit Tests for Embedded Admin Console (during install) > [INFO] ------------------------------------------------------------------------ > [INFO] /mnt/hudson_workspace/workspace/JBoss-AS-6-AdminConsole/jbossas-6.x/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/messaging/messaging-service.xml (No such file or directory) -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (EMBJOPR-280) jboss-as-5 plugin: JTA Metrics not found during discovery scan

by Ian Springer (JIRA)

[ https://jira.jboss.org/browse/EMBJOPR-280?page=com.atlassian.jira.plugin.... ] Ian Springer commented on EMBJOPR-280: -------------------------------------- And here is what AS 5.1 has of type {MCBean:JTA}: +++ ManagedComponent(name=TransactionManager, type=(ComponentType{type=MCBean, subtype=JTA}), compName=TransactionManager, attachment: com.arjuna.ats.jbossatx.jta.TransactionManagerServiceMBean ++++++ properties: [rollbackCount, XATerminator, transactionCount, state, propagateFullContext, transactionStatusManagerInetAddress, timedoutCount, runningTransactionCount, transactionManager, transactionSynchronizationRegistry, transactionStatusManagerPort, userTransaction, nestedTransactonCount, transactionTimeout, socketProcessIdPort, commitCount, statisticsEnabled, applicationRollbackCount, objectStoreDir, recoveryPort, heuristicCount, recoveryInetAddress, runInVMRecoveryManager, resourceRollbackCount] So, to summarize the changes since 5.1, the component that has the tx stats we are interested has been renamed from "TransactionManager" to "TransactionStatistics". On top of that, each of the individual properties has been renamed as well (commitCount -> numberOfCommittedTransactions, etc.). In addition, a new component of the same type but named "TransactionManager" has been added. This component has a completely different set of properties, which is not good. I don't think the Profile Service should even allow multiple components of the same type but with different sets of properties and/or operations to be deployed. A management client should be able to rely on the component's type to know which properties and/or operations should be present. In this case, the name must be used in addition to type to figure that out. I also think that the AS team should try, if at all possible, to keep the managed components APIs backwards-compatible (i.e. so clients written for older versions (such as RHQ) will not break). > jboss-as-5 plugin: JTA Metrics not found during discovery scan > --------------------------------------------------------------- > > Key: EMBJOPR-280 > URL: https://jira.jboss.org/browse/EMBJOPR-280 > Project: Embedded Jopr > Issue Type: Bug > Components: Plugin > Affects Versions: 1.3.2 > Environment: Embedded Jopr version: 1.4.0-20100120.135921-68 > Reporter: Shelly McGowan > Assignee: Ian Springer > Fix For: 1.3.3, 1.4.0 > > Attachments: embjopr280-140CR1.txt > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Performing manual testing of the admin-console snapshot deployed to AS 6, IllegalStateException was thrown during a runtime discovery scan when obtaining JTA metrics, specifically: > 17:07:47,657 INFO [org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor] Running runtime discovery scan rooted at [platform] > 17:07:51,717 INFO [org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor] Scanned [0] servers and found [0] total descendant Resources. > 17:08:11,996 ERROR [org.rhq.plugins.jbossas5.ApplicationServerComponent] Failed to obtain metric 'MCBean|JTA|*|transactionCount'.: java.lang.IllegalStateException: Property named 'transactionCount' not found for ManagedComponent [org.jboss.profileservice.management.client.ManagedComponentDelegate@1de64f6]. > at org.rhq.plugins.jbossas5.util.ManagedComponentUtils.getSimplePropertyValue(ManagedComponentUtils.java:80) > at org.rhq.plugins.jbossas5.ApplicationServerComponent.getValues(ApplicationServerComponent.java:256) > 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:597) > at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > 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) > 17:08:11,996 ERROR [org.rhq.plugins.jbossas5.ApplicationServerComponent] Failed to obtain metric 'MCBean|JTA|*|rollbackCount'.: java.lang.IllegalStateException: Property named 'rollbackCount' not found for ManagedComponent [org.jboss.profileservice.management.client.ManagedComponentDelegate@1de64f6]. > at org.rhq.plugins.jbossas5.util.ManagedComponentUtils.getSimplePropertyValue(ManagedComponentUtils.java:80) > at org.rhq.plugins.jbossas5.ApplicationServerComponent.getValues(ApplicationServerComponent.java:256) > 17:08:12,000 ERROR [org.rhq.plugins.jbossas5.ApplicationServerComponent] Failed to obtain metric 'MCBean|JTA|*|commitCount'.: java.lang.IllegalStateException: Property named 'commitCount' not found for ManagedComponent [org.jboss.profileservice.management.client.ManagedComponentDelegate@1de64f6]. > at org.rhq.plugins.jbossas5.util.ManagedComponentUtils.getSimplePropertyValue(ManagedComponentUtils.java:80) > at org.rhq.plugins.jbossas5.ApplicationServerComponent.getValues(ApplicationServerComponent.java:256) > JBoss TS 4.9.0.GA was integrated into AS 6.0.0.M2 (see: JBAS-7022). > Need to investigate further as I had several apps deployed at the time the error was thrown. -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (EMBJOPR-280) jboss-as-5 plugin: JTA Metrics not found during discovery scan

by Shelly McGowan (JIRA)

[ https://jira.jboss.org/browse/EMBJOPR-280?page=com.atlassian.jira.plugin.... ] Shelly McGowan commented on EMBJOPR-280: ---------------------------------------- ManagedDeployment: vfs:///work/TRUNK/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/all/deploy/transaction-jboss-beans.xml +++ ManagedComponent(name=TransactionManager, type=(ComponentType{type=MCBean, subtype=JTA}), compName=TransactionManager, attachment: com.arjuna.ats.jbossatx.jta.TransactionManagerServiceMBean, state: RUNNING ++++++ properties: {userTransaction="CompositeValueSupport: metaType=[MutableCompositeMetaType{javax.transaction.UserTransaction items=[name=status type=int], [name=transactionTimeout type=int]}] items=[status=SimpleMetaType:int:6,transactionTimeout=null]", XATerminator="CompositeValueSupport: metaType=[MutableCompositeMetaType{org.jboss.tm.JBossXATerminator}] items=[]", state="null", transactionManager="CompositeValueSupport: metaType=[MutableCompositeMetaType{javax.transaction.TransactionManager items=[name=status type=int], [name=transaction type=javax.transaction.Transaction], [name=transactionTimeout type=int]}] items=[status=SimpleMetaType:int:6,transaction=null,transactionTimeout=null]", transactionSynchronizationRegistry="null", } +++ ManagedComponent(name=TransactionStatistics, type=(ComponentType{type=MCBean, subtype=JTA}), compName=TransactionStatistics, attachment: com.arjuna.ats.arjuna.coordinator.TxStatsMBean, state: RUNNING ++++++ properties: {numberOfHeuristics="0", numberOfResourceRollbacks="0", numberOfInflightTransactions="0", numberOfApplicationRollbacks="0", state="null", numberOfTransactions="0", numberOfTimedOutTransactions="0", numberOfNestedTransactions="0", numberOfAbortedTransactions="0", numberOfCommittedTransactions="0", } > jboss-as-5 plugin: JTA Metrics not found during discovery scan > --------------------------------------------------------------- > > Key: EMBJOPR-280 > URL: https://jira.jboss.org/browse/EMBJOPR-280 > Project: Embedded Jopr > Issue Type: Bug > Components: Plugin > Affects Versions: 1.3.2 > Environment: Embedded Jopr version: 1.4.0-20100120.135921-68 > Reporter: Shelly McGowan > Assignee: Ian Springer > Fix For: 1.3.3, 1.4.0 > > Attachments: embjopr280-140CR1.txt > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Performing manual testing of the admin-console snapshot deployed to AS 6, IllegalStateException was thrown during a runtime discovery scan when obtaining JTA metrics, specifically: > 17:07:47,657 INFO [org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor] Running runtime discovery scan rooted at [platform] > 17:07:51,717 INFO [org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor] Scanned [0] servers and found [0] total descendant Resources. > 17:08:11,996 ERROR [org.rhq.plugins.jbossas5.ApplicationServerComponent] Failed to obtain metric 'MCBean|JTA|*|transactionCount'.: java.lang.IllegalStateException: Property named 'transactionCount' not found for ManagedComponent [org.jboss.profileservice.management.client.ManagedComponentDelegate@1de64f6]. > at org.rhq.plugins.jbossas5.util.ManagedComponentUtils.getSimplePropertyValue(ManagedComponentUtils.java:80) > at org.rhq.plugins.jbossas5.ApplicationServerComponent.getValues(ApplicationServerComponent.java:256) > 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:597) > at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > 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) > 17:08:11,996 ERROR [org.rhq.plugins.jbossas5.ApplicationServerComponent] Failed to obtain metric 'MCBean|JTA|*|rollbackCount'.: java.lang.IllegalStateException: Property named 'rollbackCount' not found for ManagedComponent [org.jboss.profileservice.management.client.ManagedComponentDelegate@1de64f6]. > at org.rhq.plugins.jbossas5.util.ManagedComponentUtils.getSimplePropertyValue(ManagedComponentUtils.java:80) > at org.rhq.plugins.jbossas5.ApplicationServerComponent.getValues(ApplicationServerComponent.java:256) > 17:08:12,000 ERROR [org.rhq.plugins.jbossas5.ApplicationServerComponent] Failed to obtain metric 'MCBean|JTA|*|commitCount'.: java.lang.IllegalStateException: Property named 'commitCount' not found for ManagedComponent [org.jboss.profileservice.management.client.ManagedComponentDelegate@1de64f6]. > at org.rhq.plugins.jbossas5.util.ManagedComponentUtils.getSimplePropertyValue(ManagedComponentUtils.java:80) > at org.rhq.plugins.jbossas5.ApplicationServerComponent.getValues(ApplicationServerComponent.java:256) > JBoss TS 4.9.0.GA was integrated into AS 6.0.0.M2 (see: JBAS-7022). > Need to investigate further as I had several apps deployed at the time the error was thrown. -- 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

13 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

embjopr-issues June 2010