[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, 3 months
[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: (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, 3 months
[JBoss JIRA] Created: (JBAS-3511) JMS ASF integration and JMS Session Pools need resource management improvements
by Weston Price (JIRA)
JMS ASF integration and JMS Session Pools need resource management improvements
-------------------------------------------------------------------------------
Key: JBAS-3511
URL: http://jira.jboss.com/jira/browse/JBAS-3511
Project: JBoss Application Server
Issue Type: Support Patch
Security Level: Public (Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.0.3 SP1
Reporter: Weston Price
Assigned To: Weston Price
Priority: Minor
A client has requested that the JMS applications server integration facilities for resource management and JMS session pooling be improved primarily in two areas:
1) The ability to not create all JMS sessions on container startup.
2) The ability to recycle/release JMS sessions based on a configurable timeout.
Both these features would need to be added to the existing JMSContainerInvoker as well as carried forward to the JBossJCA adapter prior to production release.
--
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