I found a poller method in our code that created new instances of WS client
objects in the poller method. Even though these were not retained they
apparently added data to the classloader's (unifiedclassloader3)
resourceBlackList.
View the original post :
http://www.jboss.org/index.html?modul
Hello!
We are running into the same problem. The JVM runs out of memory and heap
analysis shows huge HashSets containing entries like "JBossWS_..._20342.xsd".
Following the path to GC root shows that resourceBlackList in the unified
classloader holds references to these hashmaps.
We are runnin
What I did to solve my problem was to get the product development team to add a
new session bean in the main product that is injected with a entity manager and
a getEntityManager method that the aaa.ear ejb can call.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopi
Ok.
Then I'll have to figure out a different solution. The bbb-ear is a large
application with slow release cycles. I'm developing a maintenance application
(aaa.ear) that deploys as a stateless EJB that can pull entities from the main
application and send data from them to a client through JM
Sorry, I forgot to add I'm using JBoss 4.2.2GA
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228338#4228338
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228338
___
jboss-us
Hello!
I'm trying to inject a persistencecontext in my ejb that is defined in another
ear.
Project setup:
aaa.ear
|-aaa-ejb.jar
bbb.ear
|-bbb-ejb.par.jar (defines the persistence unit)
In aaa-ejb:
| // Needs to bind to:
| //
persistence.units:ear=bbb.ear,jar=bbb-ejb.par.jar,unitName=MYP
