September 2013 - embjopr-issues - Jboss List Archives

[JBoss JIRA] (EMBJOPR-344) If script returns -1, operation fails without details. Let's display stderr.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-344?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on EMBJOPR-344: ------------------------------------------------- John Mazzitelli <mazz(a)redhat.com> changed the Status of [bug 824773|https://bugzilla.redhat.com/show_bug.cgi?id=824773] from ASSIGNED to ON_QA > If script returns -1, operation fails without details. Let's display stderr. > ----------------------------------------------------------------------------- > > Key: EMBJOPR-344 > URL: https://issues.jboss.org/browse/EMBJOPR-344 > Project: Embedded Jopr > Issue Type: Feature Request > Affects Versions: 1.3.4 > Reporter: Ondrej Zizka > Assignee: Charles Crouch > Priority: Minor > > If some shell script returns something else than 0, embjopr operation only says "Exit code was '1', see operation results for details", but there are no op results - that applies for JON. > 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). > STR: > 1) run the wsprovide.sh with no arguments . > 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, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-344) If script returns -1, operation fails without details. Let's display stderr.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-344?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on EMBJOPR-344: ------------------------------------------------- John Mazzitelli <mazz(a)redhat.com> made a comment on [bug 824773|https://bugzilla.redhat.com/show_bug.cgi?id=824773] git master commit : 31ec51e we now show the results (as defined by the plugin metadata) in the UI, even if the operation failed. This is helpful in cases like this where the results contain data that might be helpful to the user to figure out why the failure occurred. > If script returns -1, operation fails without details. Let's display stderr. > ----------------------------------------------------------------------------- > > Key: EMBJOPR-344 > URL: https://issues.jboss.org/browse/EMBJOPR-344 > Project: Embedded Jopr > Issue Type: Feature Request > Affects Versions: 1.3.4 > Reporter: Ondrej Zizka > Assignee: Charles Crouch > Priority: Minor > > If some shell script returns something else than 0, embjopr operation only says "Exit code was '1', see operation results for details", but there are no op results - that applies for JON. > 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). > STR: > 1) run the wsprovide.sh with no arguments . > 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, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-344) If script returns -1, operation fails without details. Let's display stderr.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-344?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on EMBJOPR-344: ------------------------------------------------- John Mazzitelli <mazz(a)redhat.com> made a comment on [bug 824773|https://bugzilla.redhat.com/show_bug.cgi?id=824773] i'm working on this. should be easy to fix > If script returns -1, operation fails without details. Let's display stderr. > ----------------------------------------------------------------------------- > > Key: EMBJOPR-344 > URL: https://issues.jboss.org/browse/EMBJOPR-344 > Project: Embedded Jopr > Issue Type: Feature Request > Affects Versions: 1.3.4 > Reporter: Ondrej Zizka > Assignee: Charles Crouch > Priority: Minor > > If some shell script returns something else than 0, embjopr operation only says "Exit code was '1', see operation results for details", but there are no op results - that applies for JON. > 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). > STR: > 1) run the wsprovide.sh with no arguments . > 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, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-344) If script returns -1, operation fails without details. Let's display stderr.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-344?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on EMBJOPR-344: ------------------------------------------------- John Mazzitelli <mazz(a)redhat.com> changed the Status of [bug 824773|https://bugzilla.redhat.com/show_bug.cgi?id=824773] from NEW to ASSIGNED > If script returns -1, operation fails without details. Let's display stderr. > ----------------------------------------------------------------------------- > > Key: EMBJOPR-344 > URL: https://issues.jboss.org/browse/EMBJOPR-344 > Project: Embedded Jopr > Issue Type: Feature Request > Affects Versions: 1.3.4 > Reporter: Ondrej Zizka > Assignee: Charles Crouch > Priority: Minor > > If some shell script returns something else than 0, embjopr operation only says "Exit code was '1', see operation results for details", but there are no op results - that applies for JON. > 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). > STR: > 1) run the wsprovide.sh with no arguments . > 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, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-344) If script returns -1, operation fails without details. Let's display stderr.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-344?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on EMBJOPR-344: ------------------------------------------------- Heiko W. Rupp <hrupp(a)redhat.com> made a comment on [bug 824773|https://bugzilla.redhat.com/show_bug.cgi?id=824773] Mazz, can you please investigate the effort of a fix here? > If script returns -1, operation fails without details. Let's display stderr. > ----------------------------------------------------------------------------- > > Key: EMBJOPR-344 > URL: https://issues.jboss.org/browse/EMBJOPR-344 > Project: Embedded Jopr > Issue Type: Feature Request > Affects Versions: 1.3.4 > Reporter: Ondrej Zizka > Assignee: Charles Crouch > Priority: Minor > > If some shell script returns something else than 0, embjopr operation only says "Exit code was '1', see operation results for details", but there are no op results - that applies for JON. > 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). > STR: > 1) run the wsprovide.sh with no arguments . > 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, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-374) MySQL datasource type mapping should be present

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-374?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on EMBJOPR-374: ------------------------------------------------- Heiko W. Rupp <hrupp(a)redhat.com> changed the Status of [bug 791142|https://bugzilla.redhat.com/show_bug.cgi?id=791142] from ON_QA to CLOSED > MySQL datasource type mapping should be present > ----------------------------------------------- > > Key: EMBJOPR-374 > URL: https://issues.jboss.org/browse/EMBJOPR-374 > Project: Embedded Jopr > Issue Type: Bug > Components: Plugin > Affects Versions: 1.3.4.SP5 > Environment: JBoss EAP 5.1.2 > Reporter: Larry O'Leary > Assignee: Stefan Negrea > Labels: admin-console, jopr > Fix For: 1.3.4.SP6 > > > From Bugzilla RHQ Project Bug 791142 - Jan Martiska 2012-02-16 05:21:47 EST > When creating a datasource in EAP 5.1.2 admin console, it was found out there was no choice 'MySQL' for type mapping. I wonder why this is not present currently? It is a supported database. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-374) MySQL datasource type mapping should be present

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-374?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on EMBJOPR-374: ------------------------------------------------- Heiko W. Rupp <hrupp(a)redhat.com> made a comment on [bug 791142|https://bugzilla.redhat.com/show_bug.cgi?id=791142] Done very long time ago - closing > MySQL datasource type mapping should be present > ----------------------------------------------- > > Key: EMBJOPR-374 > URL: https://issues.jboss.org/browse/EMBJOPR-374 > Project: Embedded Jopr > Issue Type: Bug > Components: Plugin > Affects Versions: 1.3.4.SP5 > Environment: JBoss EAP 5.1.2 > Reporter: Larry O'Leary > Assignee: Stefan Negrea > Labels: admin-console, jopr > Fix For: 1.3.4.SP6 > > > From Bugzilla RHQ Project Bug 791142 - Jan Martiska 2012-02-16 05:21:47 EST > When creating a datasource in EAP 5.1.2 admin console, it was found out there was no choice 'MySQL' for type mapping. I wonder why this is not present currently? It is a supported database. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[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 RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-367?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on EMBJOPR-367: ------------------------------------------------- Heiko W. Rupp <hrupp(a)redhat.com> made a comment on [bug 833143|https://bugzilla.redhat.com/show_bug.cgi?id=833143] Bulk closing of some old issues > 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.SP5 > Environment: JBoss EAP 5.1.2 with HornetQ installed using the *all* server profile > Reporter: Larry O'Leary > Assignee: Stefan Negrea > Priority: Critical > Labels: admin-console, jon, jopr, rhq > Fix For: 1.3.4.SP6 > > Attachments: failed.log, screenshot1.png > > > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[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 RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-367?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on EMBJOPR-367: ------------------------------------------------- Heiko W. Rupp <hrupp(a)redhat.com> changed the Status of [bug 833143|https://bugzilla.redhat.com/show_bug.cgi?id=833143] from ON_QA to CLOSED > 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.SP5 > Environment: JBoss EAP 5.1.2 with HornetQ installed using the *all* server profile > Reporter: Larry O'Leary > Assignee: Stefan Negrea > Priority: Critical > Labels: admin-console, jon, jopr, rhq > Fix For: 1.3.4.SP6 > > Attachments: failed.log, screenshot1.png > > > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-176?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on EMBJOPR-176: ------------------------------------------------- Heiko W. Rupp <hrupp(a)redhat.com> changed the Status of [bug 707759|https://bugzilla.redhat.com/show_bug.cgi?id=707759] from VERIFIED to CLOSED > Call to org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource() timed out > -------------------------------------------------------------------------------------- > > Key: EMBJOPR-176 > URL: https://issues.jboss.org/browse/EMBJOPR-176 > Project: Embedded Jopr > Issue Type: Bug > Environment: EmbJopr testsuite - testEarDeploymentRepeated() > Reporter: Ondrej Zizka > 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, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

embjopr-issues September 2013