Yes, viewer for JMXConsole would be a nice feature to be added IMO...
For example, a method returning an array of objects could have a viewer
formatting the result properly.
On JbossProfiler I have a method called Class[] getLoadedClasses() on
JVMTIInterface
If I had a way to add a viewer metadata on xmdesc I would be able to
create a nice tool only using JMX-Console.
Clebert
-----Original Message-----
From: Scott M Stark
Sent: Tuesday, March 21, 2006 11:44 AM
To: Clebert Suconic
Subject: RE: Viewer for JMX/MBeans WAS: [JBoss JIRA] Created:
(JBAS-2972) Find cause of current testsuite OOMEs
We don't have such a notion currently. The way it should be done for the
jmx-console is via an mbean descriptor with a special name ("viewer")
for example as descriptors are the only way to add metadata to an mbean.
> -----Original Message-----
> From: Clebert Suconic
> Sent: Tuesday, March 21, 2006 9:41 AM
> To: Scott M Stark
> Subject: Viewer for JMX/MBeans WAS: [JBoss JIRA] Created:
> (JBAS-2972) Find cause of current testsuite OOMEs
>
> Hey Scott...
>
> Quick question..
>
> I have a method within JVMTIInterface,
> Class[] getAllClasses()
>
>
>
> Do you know if it's possible to associate a method return
> with some sort of special viewer on the JMXConsole.
>
>
> If you have such feature available, it would be a cool thing.
> I would be able to create a nice ClassLeak tool using only
> JMX-Console (since I have a method getReferenceHolders now,
> it would be possible even to find who is holding the reference)
>
>
> Doing like:
>
> <attribute access="read-write" getMethod="getClasses"
> setMethod="setHANamingService">
> <description>The HANamingService service name</description>
> <name>HANamingService</name>
> <type>java.lang.String</type>
> <viewer>org.jboss.profiler.ResultViewer</viewer>
> <!-- by having this, I would format the result the way I want -->
> </attribute>
>
>
>
>
> For now I'm asking this as a simple question, because I
> though we have such feature. If we don't, I will feed this in
> some forum.
>
>
>
> Clebert
>
>
> -----Original Message-----
> From: Scott M Stark (JIRA) [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 21, 2006 11:07 AM
> To: Clebert Suconic
> Subject: [JBoss JIRA] Created: (JBAS-2972) Find cause of
> current testsuite OOMEs
>
> Find cause of current testsuite OOMEs
> -------------------------------------
>
> Key: JBAS-2972
> URL: http://jira.jboss.com/jira/browse/JBAS-2972
> Project: JBoss Application Server
> Type: Task
> Environment:
> http://cruisecontrol.jboss.com:80/cc/artifacts/jboss-4.0-tests
uite/20060320121502/results/index.html
> Reporter: Scott M Stark
> Assigned to: Clebert Suconic
> Priority: Critical
> Fix For: JBossAS-4.0.4.CR2
>
>
> Looking at the the txtimer errors, these are due to previous
> deployments not getting cleaned up due to OOMEs:
>
> 2006-03-20 13:20:21,455 WARN
> [org.jboss.system.ServiceController] Problem start
> ing service jboss.j2ee:jndiName=test/txtimer/TimerTest,service=EJB
> java.lang.OutOfMemoryError
> ...
> 2006-03-20 13:20:25,895 INFO
> [org.jboss.ejb.plugins.StatelessSessionInstancePool]
> Registration is not done -> stop
> 2006-03-20 13:20:25,896 DEBUG
> [org.jboss.ejb.StatelessSessionContainer] Failed to register
> pool as mbean
> javax.management.InstanceAlreadyExistsException:
> jboss.j2ee:jndiName=test/txtimer/TimerTest,plugin=pool,service
> =EJB already registered.
> at
> org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBean
> Registry.java:757)
> at
> org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(
> BasicMBeanRegistry.java:225)
> at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
> odAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedD
> ispatcher.java:155)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> at
> org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIn
> terceptor.java:133)
>
> We need to find out why there OOMEs.
>
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the
> administrators:
> http://jira.jboss.com/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
>
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
