August 2012 - embjopr-issues - Jboss List Archives

[JBoss JIRA] (EMBJOPR-367) subtype=QueueManage temporarily disappears from ManagementView compByCompType resulting in "There are currently no numeric metrics available." being displayed on JMS Manager/JMS Queues/* metric page

by Larry O'Leary (JIRA)

Larry O'Leary created EMBJOPR-367: ------------------------------------- Summary: subtype=QueueManage temporarily disappears from ManagementView compByCompType resulting in "There are currently no numeric metrics available." being displayed on JMS Manager/JMS Queues/* metric page Key: EMBJOPR-367 URL: https://issues.jboss.org/browse/EMBJOPR-367 Project: Embedded Jopr Issue Type: Bug Components: Plugin Affects Versions: 1.3.4 Environment: JBoss EAP 5.1.2 with HornetQ installed using the *all* server profile Reporter: Larry O'Leary Priority: Critical Very frequently, the metrics for a queue will fail to be loaded due to the managed component type that represents a queue being dropped from ProfileSerivce's component type list. The result is the admin-consle displays the following message (see screenshot1.png): Numeric Metrics There are currently no numeric metrics available. >From the server.log, the following error is logged at debug: DEBUG [org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler] (http-0.0.0.0-8080-2) Call to [org.jboss.as.integration.hornetq.jopr.JMSQueueComponent.getValues()] with args [[org.rhq.core.domain.measurement.MeasurementReport@560399f8, [MeasurementScheduleRequest[scheduleId=1, name=getDeliveringCount, interval=0, enabled=true, dataType=MEASUREMENT, rawNumericType=null], MeasurementScheduleRequest[scheduleId=1, name=getMessageCount, interval=0, enabled=true, dataType=MEASUREMENT, rawNumericType=null], MeasurementScheduleRequest[scheduleId=1, name=getConsumerCount, interval=0, enabled=true, dataType=MEASUREMENT, rawNumericType=null], MeasurementScheduleRequest[scheduleId=1, name=getMessagesAdded, interval=0, enabled=true, dataType=MEASUREMENT, rawNumericType=null], MeasurementScheduleRequest[scheduleId=1, name=getScheduledCount, interval=0, enabled=true, dataType=MEASUREMENT, rawNumericType=null]]]] failed. java.util.concurrent.ExecutionException: java.lang.NullPointerException at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:262) at java.util.concurrent.FutureTask.get(FutureTask.java:119) at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invokeInNewThreadWithLock(ResourceContainer.java:446) at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invoke(ResourceContainer.java:434) at $Proxy193.getValues(Unknown Source) at org.rhq.core.pc.measurement.MeasurementManager.getRealTimeMeasurementValue(MeasurementManager.java:435) at org.jboss.on.embedded.bean.MeasurementUtils.loadMeasurementData(MeasurementUtils.java:126) at org.jboss.on.embedded.ui.MetricAction.view(MetricAction.java:107) ... Caused by: java.lang.NullPointerException at org.jboss.as.integration.hornetq.jopr.util.ManagementSupport.getOperation(ManagementSupport.java:40) at org.jboss.as.integration.hornetq.jopr.JMSResourceComponent.getValues(JMSResourceComponent.java:86) at sun.reflect.GeneratedMethodAccessor622.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) ... 1 more Upon investigation of the code, the issue is that ComponentType{type=JMSDestinationManage, subtype=QueueManage} temporarily disappears from org.jboss.profileservice.management.ManagementViewImpl.compByCompType resulting in `null` being returned as the component and this component making its way back out to the HornetQ plug-in. I am not certain why the subtype vanishes from the management view. It seems that this is happening during resource discovery so perhaps the resource discovery process is using the same management view object that is being used by the plug-ins from the plug-in container. In either case, this issue occurs quite frequently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
17
0 / 0

[JBoss JIRA] Created: (EMBJOPR-344) Running with no arguments wsprovide.sh fails

by Ondrej Zizka (JIRA)

Running with no arguments wsprovide.sh fails -------------------------------------------- Key: EMBJOPR-344 URL: https://jira.jboss.org/browse/EMBJOPR-344 Project: Embedded Jopr Issue Type: Bug Reporter: Ondrej Zizka Priority: Minor The admin console should show some info about how to use the script, not fail with this generic message. This might apply to all scripts which do not behave so by default (like classpath.sh). java.lang.Exception: Exit code was '1', see operation results for details at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:278) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) -- 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

11 years, 6 months

2
17
0 / 0

[JBoss JIRA] (EMBJOPR-368) Templates for Queues and Topics do not deliver some defaults, but object creation fails without

by Heiko Rupp (JIRA)

Heiko Rupp created EMBJOPR-368: ---------------------------------- Summary: Templates for Queues and Topics do not deliver some defaults, but object creation fails without Key: EMBJOPR-368 URL: https://issues.jboss.org/browse/EMBJOPR-368 Project: Embedded Jopr Issue Type: Bug Components: Plugin Affects Versions: 1.3.4 Reporter: Heiko Rupp Try to create a queue or topic with only the two required properties name and JNDIName. This will fail with "vfsfile:/devel/jboss-eap-5.1/jboss-as/server/default/deploy/java__myT-service.xml -> org.jboss.deployment.DeploymentException: Error configuring attribute DLQ" Same happens for ExpiryQueue and ServerPeer. Those 3 properties need default values set like this: <c:simple-property required="false" name="expiryQueue" default="jboss.messaging.destination:service=Queue,name=ExpiryQueue"> <c:simple-property required="false" name="DLQ" default="jboss.messaging.destination:service=Queue,name=DLQ"> <c:simple-property required="false" name="serverPeer" default="jboss.messaging:service=ServerPeer"> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

3
8
0 / 0

[JBoss JIRA] (EMBJOPR-373) BRMS is not identified as a product by JBoss EAP plug-in

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-373?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on EMBJOPR-373: ------------------------------------------------- Armine <ahovsepy(a)redhat.com> made a comment on [bug 834360|https://bugzilla.redhat.com/show_bug.cgi?id=834360] please ignore my last comment > BRMS is not identified as a product by JBoss EAP plug-in > -------------------------------------------------------- > > Key: EMBJOPR-373 > URL: https://issues.jboss.org/browse/EMBJOPR-373 > Project: Embedded Jopr > Issue Type: Bug > Components: Plugin > Affects Versions: 1.3.4.SP5 > Reporter: Larry O'Leary > Assignee: Stefan Negrea > Labels: admin-console, jopr, rhq > Fix For: 1.3.4.SP6 > > > BRMS gets its branding removed by the JBoss AS plug-in contained in admin-console. Specifically, the plug-in calls the BRMS server AS 5 instead of BRMS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-373) BRMS is not identified as a product by JBoss EAP plug-in

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-373?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on EMBJOPR-373: ------------------------------------------------- Armine <ahovsepy(a)redhat.com> changed the Status of [bug 834360|https://bugzilla.redhat.com/show_bug.cgi?id=834360] from ON_DEV to ON_QA > BRMS is not identified as a product by JBoss EAP plug-in > -------------------------------------------------------- > > Key: EMBJOPR-373 > URL: https://issues.jboss.org/browse/EMBJOPR-373 > Project: Embedded Jopr > Issue Type: Bug > Components: Plugin > Affects Versions: 1.3.4.SP5 > Reporter: Larry O'Leary > Assignee: Stefan Negrea > Labels: admin-console, jopr, rhq > Fix For: 1.3.4.SP6 > > > BRMS gets its branding removed by the JBoss AS plug-in contained in admin-console. Specifically, the plug-in calls the BRMS server AS 5 instead of BRMS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-373) BRMS is not identified as a product by JBoss EAP plug-in

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-373?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on EMBJOPR-373: ------------------------------------------------- Armine <ahovsepy(a)redhat.com> changed the Status of [bug 834360|https://bugzilla.redhat.com/show_bug.cgi?id=834360] from ON_QA to ON_DEV > BRMS is not identified as a product by JBoss EAP plug-in > -------------------------------------------------------- > > Key: EMBJOPR-373 > URL: https://issues.jboss.org/browse/EMBJOPR-373 > Project: Embedded Jopr > Issue Type: Bug > Components: Plugin > Affects Versions: 1.3.4.SP5 > Reporter: Larry O'Leary > Assignee: Stefan Negrea > Labels: admin-console, jopr, rhq > Fix For: 1.3.4.SP6 > > > BRMS gets its branding removed by the JBoss AS plug-in contained in admin-console. Specifically, the plug-in calls the BRMS server AS 5 instead of BRMS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-373) BRMS is not identified as a product by JBoss EAP plug-in

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-373?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on EMBJOPR-373: ------------------------------------------------- Armine <ahovsepy(a)redhat.com> made a comment on [bug 834360|https://bugzilla.redhat.com/show_bug.cgi?id=834360] reopened. clean jon server was installed with only BRMS plugin. BRMS server started. Inventored as EWP server, while in description it is said that it should be BRMS. > BRMS is not identified as a product by JBoss EAP plug-in > -------------------------------------------------------- > > Key: EMBJOPR-373 > URL: https://issues.jboss.org/browse/EMBJOPR-373 > Project: Embedded Jopr > Issue Type: Bug > Components: Plugin > Affects Versions: 1.3.4.SP5 > Reporter: Larry O'Leary > Assignee: Stefan Negrea > Labels: admin-console, jopr, rhq > Fix For: 1.3.4.SP6 > > > BRMS gets its branding removed by the JBoss AS plug-in contained in admin-console. Specifically, the plug-in calls the BRMS server AS 5 instead of BRMS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

embjopr-issues August 2012