[JBoss JIRA] Created: (EJBTHREE-792) Cyclic @EJB dependency doesn't work anymore
by Frank Cornelis (JIRA)
Cyclic @EJB dependency doesn't work anymore
-------------------------------------------
Key: EJBTHREE-792
URL: http://jira.jboss.com/jira/browse/EJBTHREE-792
Project: EJB 3.0
Issue Type: Bug
Reporter: Frank Cornelis
Next used to work.
@Stateless
public class HelloBean implements HelloLocal, HelloRemote {
@EJB
private Hello2Local hello2;
}
@Stateless
public class Hello2Bean implements Hello2Local, Hello2Remote {
@EJB
private HelloLocal hello;
}
On JBoss AS 4.0.5.GA I now get:
--- MBeans waiting for other MBeans ---
[exec] ObjectName: jboss.j2ee:ear=xxx-ear-1.0-SNAPSHOT.ear,jar=xxx-model-1.0-SNAPSHOT.jar,name=HelloBean,service=EJB3
[exec] State: NOTYETINSTALLED
[exec] I Depend On:
[exec] jboss.j2ee:ear=xxx-ear-1.0-SNAPSHOT.ear,jar=xxx-model-1.0-SNAPSHOT.jar,name=Hello2Bean,service=EJB3
[exec] Depends On Me:
[exec] jboss.j2ee:ear=xxx-ear-1.0-SNAPSHOT.ear,jar=xxx-model-1.0-SNAPSHOT.jar,name=Hello2Bean,service=EJB3
[exec] ObjectName: jboss.j2ee:ear=xxx-ear-1.0-SNAPSHOT.ear,jar=xxx-model-1.0-SNAPSHOT.jar,name=Hello2Bean,service=EJB3
[exec] State: NOTYETINSTALLED
[exec] I Depend On:
[exec] jboss.j2ee:ear=xxx-ear-1.0-SNAPSHOT.ear,jar=xxx-model-1.0-SNAPSHOT.jar,name=HelloBean,service=EJB3
[exec] Depends On Me:
[exec] jboss.j2ee:ear=xxx-ear-1.0-SNAPSHOT.ear,jar=xxx-model-1.0-SNAPSHOT.jar,name=HelloBean,service=EJB3
--
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
[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
[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
[JBoss JIRA] Created: (JBCACHE-890) Custom flags per node, incorporate and consolidate some domain-specific flags
by Elias Ross (JIRA)
Custom flags per node, incorporate and consolidate some domain-specific flags
-----------------------------------------------------------------------------
Key: JBCACHE-890
URL: http://jira.jboss.com/jira/browse/JBCACHE-890
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Elias Ross
Assigned To: Manik Surtani
I believe that with java.util.EnumSet and a list of enumerations, that some of the specific flags we track on a node could be consolidated. Immediately what comes to mind are the CacheLoader flags "childrenLoaded" and "dataLoaded"
Further, I believe that some additional functionality could be incorporated.
For instance:
1. For certain internal nodes, they could be marked as "internal" or "local" and not replicated. Or possibly hidden from access entirely.
2. Some nodes might be marked as "read-only" or "non-persisted" or "non-evictable"
3. Some nodes might have special sorted ordering.
--
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, 1 month
[JBoss JIRA] Created: (JBAS-3981) Statment caching in update query which return value
by erahamim (JIRA)
Statment caching in update query which return value
----------------------------------------------------
Key: JBAS-3981
URL: http://jira.jboss.com/jira/browse/JBAS-3981
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.5.GA
Environment: jboss 4.0.5 on windows xp / linux with database oracle 10.0.2
Reporter: erahamim
Priority: Minor
When I set statements cache in oracle-xa-ds.xml:
<prepared-statement-cache-size>100</prepared-statement-cache-size>
For the following statement:
BEGIN
UPDATE table SET A=? WHERE ID=? AND TIME=? RETURNING TIME INTO ?;
END
con = DataSourceManager.getConnection();
statement = con.prepareCall( 'The above query');
statement.setInt(1,1);
statement.setTimestamp(2, myTime);
statement.registerOutParameter(3, Types.TIMESTAMP);
statement.executeUpdate();
final Timestamp ts = statement.getTimestamp(lastIndex);
In this scenario, I'm always getting back the time result even if the update didn't match any row in database.
When I drop the statement cache I get the result only if there was a row that was updated by this statement.
I can't use the return value from executeUpdate() since it always return 1.
--
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, 1 month