As far as I can see, a ClassLoader leak can occur through
org.jboss.util.TimedCachePolicy.resolutionTimer, preventing ClassLoader and
classes from unloading when an EAR is undeployed.
I have debugged undeploy problem in my EAR with jmap -dump and jhat, and one of
the reasons preventing
Forgot to say: JBoss 4.2.1.GA, JDK 1.6.0_04.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4134173#4134173
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4134173
___
jboss-user
There is another, perhaps theoretical leak possibility JBoss authentication
cache implemented using TimedCachePolicy. This is because entries in
TimedCachePolicy are not purged from the cache until they are fetched from the
cache, and are then noticed as expired. The leak occurs when:
1. I
I tested with this patch to TimedCachePolicy. Yay, undeploy now works!
| --- TimedCachePolicy.java
| +++ TimedCachePolicy.java
| @@ -77,7 +77,17 @@ public class TimedCachePolicy
|public Object getValue();
| }
|
| - protected static Timer resolutionTimer = new
EJB 3 tutorial encourages to write non-standard code, at least in the EJB 2.1
adapters bit.
See
http://labs.jboss.com/jbossejb3/docs/tutorial/ejb21_client_adaptors/ejb21_client_adaptors.html
Session1Bean is annotated with the @Remote annotation to designate
Session1Remote as its remote
How can I access EJB 2.1 session from EJB 3 session in JBoss 4.2.1.GA?
The EJB 3 sessions and EJB 2.1 session are deployed in separate EJB jar files,
but they are in the same EAR file, so they are part of the same J2EE
application.
I have tried the following methods:
Injecting EJB 2.1 home
anonymous wrote : The EJB 3 deployer in AS 4.2 can only deploy EJB 2.1 session
beans. 2.1 Entity BMP/CMP beans are not deployable.
OK, this explains the problem. I had no EJB 2.1 sessions, only entities in the
module.
Is there somewhere documentation about AS 4.2 EJB 3 capabilities. I tried to
I'm trying to deploy on JBoss 4.2.1.GA a jar (in ear) that contains EJB 2.1 and
EJB 3 components.
However, only the EJB 3 components are deployed. There are no errors or any
other indication that JBoss even thinks that the jar contains any EJB 2.1
components.
I have understood that EJB 3 +
