[JBoss JIRA] Created: (EJBTHREE-699) StackOverflowError in org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy
by Michael Grübsch (JIRA)
StackOverflowError in org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy
-----------------------------------------------------------------------
Key: EJBTHREE-699
URL: http://jira.jboss.com/jira/browse/EJBTHREE-699
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC7 - FD
Environment: Windows XP
Reporter: Michael Grübsch
Priority: Critical
I refer to source version $Revision: 1.1.4.2 $
This is an excerpt from the stack trace:
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:502)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:114)
at $Proxy398.toString(Unknown Source)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:502)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:114)
at $Proxy398.toString(Unknown Source)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:502)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:114)
You may see, that invoke calls getProxyString which in turn on the proxy calls invoke!
--
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
18 years, 3 months
[JBoss JIRA] Created: (JGRP-408) Expose classes, attributes and operations via @ManagedResource, @ManagedAttribute and @ManagedOperation
by Bela Ban (JIRA)
Expose classes, attributes and operations via @ManagedResource, @ManagedAttribute and @ManagedOperation
-------------------------------------------------------------------------------------------------------
Key: JGRP-408
URL: http://jira.jboss.com/jira/browse/JGRP-408
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.6
We should be able to simply make an object expose management information by annotating it.
Input: annotations and classes
Output: classes which are registered with the platform MBeanServer at runtime using an API (which is also provided). This API
uses the annotations and reflection to create DynamicMBeans (or MXBeans ?) which are then registered with the MBeanServer.
Example:
@ManagedResource(objectName="jgroups:type=protocol;name=UDP")
public class UDP extends Protocol {
@ManagedAttribute(name="Sent", descr="Number of bytes sent")
long sent_msgs=0; // generates a 'public long getSent()' getter, *no* setter !
@ManagedOperation(description="Prints statistics over the last N seconds")
@Parameters({@Parameter(name="timeframe", description="Number of milliseconds (0 for all stats)")})
public String printStats(long timeframe) {
// implement;
}
}
--
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
18 years, 3 months