[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
12 years, 1 month
[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
12 years, 3 months
[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
12 years, 3 months
[JBoss JIRA] Created: (EMBJOPR-362) Tag SP5 release on 1.3.4 for inclusion in EAP 5.1.2
by Larry O'Leary (JIRA)
Tag SP5 release on 1.3.4 for inclusion in EAP 5.1.2
---------------------------------------------------
Key: EMBJOPR-362
URL: https://issues.jboss.org/browse/EMBJOPR-362
Project: Embedded Jopr
Issue Type: Release
Affects Versions: 1.3.4
Reporter: Larry O'Leary
Priority: Blocker
Fix For: 1.3.4
There are a few issues that affect admin-console in EAP 5 that have been addressed since the release of EAP 5.0.1, EAP 5.1, and EAP 5.1.1. We need to get these fixes pushed into admin-console for EAP 5.1.2. This will require a new tag on the 1.3.4 release branch. Currently, EAP 5.1.1 is using Embedded JOPR 1.3.4.SP4. We need to get the appropriate fixes committed to the Embedded JOPR branch and the tag created (1.3.4.SP5) and get the tag into the downstream EAP 5.1 CP branch being tracked by JBPAPP-6766
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (EMBJOPR-371) admin-console fails to load when unexploded EAR containing an EJB module JAR exists in the deploy directory
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/EMBJOPR-371?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on EMBJOPR-371:
-------------------------------------------------
Larry O'Leary <loleary(a)redhat.com> made a comment on [bug 795918|https://bugzilla.redhat.com/show_bug.cgi?id=795918]
Tagging for 1.3.4.SP6 is complete
> admin-console fails to load when unexploded EAR containing an EJB module JAR exists in the deploy directory
> -----------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-371
> URL: https://issues.jboss.org/browse/EMBJOPR-371
> Project: Embedded Jopr
> Issue Type: Bug
> Affects Versions: 1.3.4.SP5
> Reporter: Larry O'Leary
> Assignee: Stefan Negrea
> Fix For: 1.3.4.SP6
>
>
> When an EAP instance has an EAR deployed to it which contains an EJB module JAR and the EAR is in an unexploded form (archived), attempting to access the admin-console results in the following exception:
> ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/admin-console]] (http-0.0.0.0-8080-1) Exception sending request initialized lifecycle event to listener instance of class org.jboss.on.embedded.LazyStartupListener
> java.lang.RuntimeException: Error handling file /opt/jboss/jboss-eap-5.1/jboss-as/server/production/deploy/exolgan-legacy-ejb.ear/exolgan-legacy-ejb.jar
> at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:134)
> at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107)
> at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90)
> at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119)
> at org.jboss.seam.init.Initialization.create(Initialization.java:130)
> at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36)
> at org.jboss.on.embedded.LazyStartupListener.initialize(LazyStartupListener.java:182)
> at org.jboss.on.embedded.LazyStartupListener.requestInitialized(LazyStartupListener.java:240)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:180)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
> 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:599)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451)
> at java.lang.Thread.run(Thread.java:636)
> Caused by: java.util.zip.ZipException: error in opening zip file
> at java.util.zip.ZipFile.open(Native Method)
> at java.util.zip.ZipFile.<init>(ZipFile.java:131)
> at java.util.zip.ZipFile.<init>(ZipFile.java:148)
> at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123)
> ... 21 more
> The issue can be resolved by adding the following files to admin-console.war/META-INF/
> Empty File (seam.properties)
> seam-deployment.properties:
> org.jboss.seam.deployment.scanners=org.jboss.seam.integration.jbossas.vfs.VFSScanner
--
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
12 years, 5 months
[JBoss JIRA] Created: (EMBJOPR-360) JarURLConnection default cache disabled globally
by Jason Shepherd (JIRA)
JarURLConnection default cache disabled globally
------------------------------------------------
Key: EMBJOPR-360
URL: https://issues.jboss.org/browse/EMBJOPR-360
Project: Embedded Jopr
Issue Type: Bug
Components: Core Infrastructure
Affects Versions: 1.3.4
Environment: JBoss Enterprise Application Platform (EAP) 5.1
Embedded Jopr 1.3.4.SP1
Reporter: Jason Shepherd
Attachments: URLConnectionCache.war, URLConnectionCache.zip
The admin-console in EAP 5.1 is turning off caching of resources contained within jars globally. This is causing a serious performance impact in using standard java functions, such as creating DocumentBuilderFactory instances.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (EMBJOPR-371) admin-console fails to load when unexploded EAR containing an EJB module JAR exists in the deploy directory
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/EMBJOPR-371?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on EMBJOPR-371:
-------------------------------------------------
Larry O'Leary <loleary(a)redhat.com> changed the Status of [bug 795918|https://bugzilla.redhat.com/show_bug.cgi?id=795918] from ON_DEV to CLOSED
> admin-console fails to load when unexploded EAR containing an EJB module JAR exists in the deploy directory
> -----------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-371
> URL: https://issues.jboss.org/browse/EMBJOPR-371
> Project: Embedded Jopr
> Issue Type: Bug
> Affects Versions: 1.3.4.SP5
> Reporter: Larry O'Leary
> Assignee: Stefan Negrea
> Fix For: 1.3.4.SP6
>
>
> When an EAP instance has an EAR deployed to it which contains an EJB module JAR and the EAR is in an unexploded form (archived), attempting to access the admin-console results in the following exception:
> ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/admin-console]] (http-0.0.0.0-8080-1) Exception sending request initialized lifecycle event to listener instance of class org.jboss.on.embedded.LazyStartupListener
> java.lang.RuntimeException: Error handling file /opt/jboss/jboss-eap-5.1/jboss-as/server/production/deploy/exolgan-legacy-ejb.ear/exolgan-legacy-ejb.jar
> at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:134)
> at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107)
> at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90)
> at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119)
> at org.jboss.seam.init.Initialization.create(Initialization.java:130)
> at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36)
> at org.jboss.on.embedded.LazyStartupListener.initialize(LazyStartupListener.java:182)
> at org.jboss.on.embedded.LazyStartupListener.requestInitialized(LazyStartupListener.java:240)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:180)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
> 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:599)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451)
> at java.lang.Thread.run(Thread.java:636)
> Caused by: java.util.zip.ZipException: error in opening zip file
> at java.util.zip.ZipFile.open(Native Method)
> at java.util.zip.ZipFile.<init>(ZipFile.java:131)
> at java.util.zip.ZipFile.<init>(ZipFile.java:148)
> at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123)
> ... 21 more
> The issue can be resolved by adding the following files to admin-console.war/META-INF/
> Empty File (seam.properties)
> seam-deployment.properties:
> org.jboss.seam.deployment.scanners=org.jboss.seam.integration.jbossas.vfs.VFSScanner
--
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
12 years, 5 months
[JBoss JIRA] Created: (EMBJOPR-357) Error when creating connection factory
by John Ament (JIRA)
Error when creating connection factory
--------------------------------------
Key: EMBJOPR-357
URL: https://issues.jboss.org/browse/EMBJOPR-357
Project: Embedded Jopr
Issue Type: Bug
Reporter: John Ament
When creating a new JMS ConnectionFactory, an exception gets thrown by the application. Stack trace:
08:31:14,535 INFO [org.rhq.core.pc.inventory.CreateResourceRunner] Creating resource through report: CreateResourceReport: ResourceType=[ResourceType[id=0, category=Service, name=JMS Connection Factory, plugin=HornetQ]], ResourceKey=[null]
08:31:14,538 ERROR [STDERR] java.lang.reflect.UndeclaredThrowableException: Failed to invoke method 'createConnectionFactory' on component 'JMSConnectionFactoryManageMO' with parameters [SimpleMetaType:java.lang.String:FlashSalesMQ, SimpleMetaType:boolean:true, SimpleMetaType:boolean:false, SimpleMetaType:int:2, SimpleMetaType:java.lang.String:netty, SimpleMetaType:java.lang.String:jms/FlashMQ, SimpleMetaType:java.lang.String:null, SimpleMetaType:int:1048576, SimpleMetaType:int:1048576, SimpleMetaType:long:30000, SimpleMetaType:long:60000, SimpleMetaType:long:30000, SimpleMetaType:int:1048576, SimpleMetaType:int:-1, SimpleMetaType:int:-1, SimpleMetaType:int:65536, SimpleMetaType:boolean:false, SimpleMetaType:int:102400, SimpleMetaType:boolean:false, SimpleMetaType:boolean:false, SimpleMetaType:boolean:true, SimpleMetaType:boolean:true, SimpleMetaType:boolean:true, SimpleMetaType:long:2000, SimpleMetaType:double:1.0, SimpleMetaType:int:0, SimpleMetaType:int:5, SimpleMetaType:int:-1, SimpleMetaType:java.lang.String:null, SimpleMetaType:int:1500, SimpleMetaType:boolean:true, SimpleMetaType:long:2000, SimpleMetaType:java.lang.String:org.hornetq.api.core.client.loadbalance.RoundRobinConnectionLoadBalancingPolicy].
08:31:14,539 ERROR [STDERR] at org.jboss.profileservice.plugins.management.util.AbstractManagedComponentRuntimeDispatcher.invoke(AbstractManagedComponentRuntimeDispatcher.java:148)
08:31:14,539 ERROR [STDERR] at org.jboss.profileservice.management.DelegatingComponentDispatcherImpl.invoke(DelegatingComponentDispatcherImpl.java:93)
08:31:14,539 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
08:31:14,539 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
08:31:14,539 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
08:31:14,540 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597)
08:31:14,540 ERROR [STDERR] at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
08:31:14,540 ERROR [STDERR] at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
08:31:14,540 ERROR [STDERR] at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:99)
08:31:14,540 ERROR [STDERR] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:898)
08:31:14,540 ERROR [STDERR] at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
08:31:14,540 ERROR [STDERR] at org.jboss.remoting.Client.invoke(Client.java:1961)
08:31:14,541 ERROR [STDERR] at org.jboss.remoting.Client.invoke(Client.java:804)
08:31:14,541 ERROR [STDERR] at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
08:31:14,541 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
08:31:14,541 ERROR [STDERR] at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
08:31:14,541 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
08:31:14,541 ERROR [STDERR] at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
08:31:14,541 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
08:31:14,541 ERROR [STDERR] at org.jboss.aop.generatedproxies.AOPProxy$1.invoke(AOPProxy$1.java)
08:31:14,542 ERROR [STDERR] at org.jboss.profileservice.management.client.ManagedOperationDelegate.invoke(ManagedOperationDelegate.java:63)
08:31:14,542 ERROR [STDERR] at org.jboss.as.integration.hornetq.jopr.JMSManagerComponent.createConnectionFactory(JMSManagerComponent.java:219)
08:31:14,542 ERROR [STDERR] at org.jboss.as.integration.hornetq.jopr.JMSManagerComponent.createResource(JMSManagerComponent.java:130)
08:31:14,542 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
08:31:14,542 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
08:31:14,542 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
08:31:14,543 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597)
08:31:14,543 ERROR [STDERR] at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525)
08:31:14,543 ERROR [STDERR] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
08:31:14,543 ERROR [STDERR] at java.util.concurrent.FutureTask.run(FutureTask.java:138)
08:31:14,543 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
08:31:14,543 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
08:31:14,543 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619)
08:31:14,544 ERROR [STDERR] Caused by: org.jboss.joinpoint.spi.JoinpointException: Method not found createConnectionFactory[java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, int, long, java.lang.String, int, int, long, long, long, int, int, int, int, boolean, int, boolean, boolean, boolean, boolean, boolean, long, double, int, boolean, int, int, java.lang.String] for class org.jboss.as.integration.hornetq.management.jms.ConnectionFactoryManageMO
08:31:14,544 ERROR [STDERR] at org.jboss.joinpoint.plugins.Config.findMethodInfo(Config.java:400)
08:31:14,544 ERROR [STDERR] at org.jboss.joinpoint.plugins.Config.findMethodInfo(Config.java:366)
08:31:14,544 ERROR [STDERR] at org.jboss.joinpoint.plugins.Config.findMethodInfo(Config.java:335)
08:31:14,544 ERROR [STDERR] at org.jboss.joinpoint.plugins.Config.getMethodJoinpoint(Config.java:223)
08:31:14,544 ERROR [STDERR] at org.jboss.beans.info.plugins.AbstractBeanInfo.invoke(AbstractBeanInfo.java:299)
08:31:14,544 ERROR [STDERR] at org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.invoke(AbstractKernelControllerContext.java:305)
08:31:14,544 ERROR [STDERR] at org.jboss.kernel.plugins.registry.basic.LifecycleAwareKernelBus$1.dispatch(LifecycleAwareKernelBus.java:61)
08:31:14,545 ERROR [STDERR] at org.jboss.kernel.plugins.registry.basic.LifecycleAwareKernelBus$1.dispatch(LifecycleAwareKernelBus.java:58)
08:31:14,545 ERROR [STDERR] at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.execute(BasicKernelBus.java:71)
08:31:14,545 ERROR [STDERR] at org.jboss.kernel.plugins.registry.basic.LifecycleAwareKernelBus.invoke(LifecycleAwareKernelBus.java:57)
08:31:14,545 ERROR [STDERR] at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.invoke(KernelBusRuntimeComponentDispatcher.java:85)
08:31:14,545 ERROR [STDERR] at org.jboss.profileservice.plugins.management.util.AbstractManagedComponentRuntimeDispatcher.invoke(AbstractManagedComponentRuntimeDispatcher.java:135)
08:31:14,545 ERROR [STDERR] at org.jboss.profileservice.management.DelegatingComponentDispatcherImpl.invoke(DelegatingComponentDispatcherImpl.java:93)
08:31:14,545 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
08:31:14,546 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
08:31:14,546 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
08:31:14,546 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597)
08:31:14,546 ERROR [STDERR] at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
08:31:14,550 ERROR [STDERR] at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
08:31:14,550 ERROR [STDERR] at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:99)
08:31:14,550 ERROR [STDERR] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:898)
08:31:14,550 ERROR [STDERR] at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
08:31:14,550 ERROR [STDERR] at org.jboss.remoting.Client.invoke(Client.java:1961)
08:31:14,551 ERROR [STDERR] at org.jboss.remoting.Client.invoke(Client.java:804)
08:31:14,551 ERROR [STDERR] at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
08:31:14,551 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
08:31:14,551 ERROR [STDERR] at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
08:31:14,551 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
08:31:14,551 ERROR [STDERR] at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
08:31:14,551 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
08:31:14,552 ERROR [STDERR] at org.jboss.aop.generatedproxies.AOPProxy$1.invoke(AOPProxy$1.java)
08:31:14,552 ERROR [STDERR] at org.jboss.profileservice.management.client.ManagedOperationDelegate.invoke(ManagedOperationDelegate.java:63)
08:31:14,552 ERROR [STDERR] at org.jboss.as.integration.hornetq.jopr.JMSManagerComponent.createConnectionFactory(JMSManagerComponent.java:219)
08:31:14,552 ERROR [STDERR] at org.jboss.as.integration.hornetq.jopr.JMSManagerComponent.createResource(JMSManagerComponent.java:130)
08:31:14,552 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
08:31:14,552 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
08:31:14,552 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
08:31:14,553 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597)
08:31:14,553 ERROR [STDERR] at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525)
08:31:14,553 ERROR [STDERR] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
08:31:14,553 ERROR [STDERR] at java.util.concurrent.FutureTask.run(FutureTask.java:138)
08:31:14,553 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
08:31:14,553 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
08:31:14,553 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619)
08:31:14,554 ERROR [STDERR] at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72)
08:31:14,554 ERROR [STDERR] ... 19 more
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months