Hi Simon, hi Marc,
I have carried out a lot of tests with NoPassivationCachePolicy and no
special -Xmx settings. My machine has 256 MB.
It runs quicker and absolutely stable in this configuration. So is it a
problem with the new cache?
Furthermore I have run very few tests with LRUEnterpriseContextCachePolicy
today. During these tests I coul not reproduce the problem.
BTW questions:
1. How can I force jBoss to delete removed Entity beans from the database
except with ^C using NoPassivationCachePolicy?
2. What happens with the cache during hot deployment of the related jar
file? After removal of about 7000 Entity beans, hot redeployment and ^C I
have found still 100 records in the database?!
3. Sometimes I have to hit ^C twice to shutdown jBoss. Normal?
I wish you all a merry Xmas and a happy New year. I will be back in office
on Jan. 11th. It might be better to CC me directly in order to not loose
your replies.
Andreas
-----Original Message-----
From: Bordet, Simone [mailto:[EMAIL PROTECTED]]
Sent: Freitag, 22. Dezember 2000 00:54
To: 'jBoss'
Subject: RE: [jBoss-User] Exceptions
Hey Andreas,
let's follow Marc's suggestion:
customize your container with jboss.xml and put the entry
<cache-policy>org.jboss.ejb.plugins.NoPassivationCachePolicy</cache-policy>
instead of the entry
<cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-p
olicy>
Refer anyway to
http://www.jboss.org/documentation/contconf_howto.html#CacheConf
Then start your application on a strong machine, something like > 256 MB
RAM, and maybe also specifying the -mx (or -Xmx) appropriately high (the
higher the better).
Let me know.
Simon
> Hi Simon,
>
> I have a jboss.xml, but without the specific settings you
> mentioned. At the
> same time no more than 600 EJB need to be active. So I
> assume, the default
> settings should be sufficient.
>
> When this kind of freeze occurs, the CPU load is nearly 0% on
> the machine
> jBoss is running on and on the database server machine.
>
> In normal state ctrl-break and ctrl-c work. So I agree with
> you that it
> might be a JVM related problem.
>
> Sometimes I have similiar problems with the Oracle 8i tools.
> Old Oracle JVM
> must be terminated hardly before new dialogs can come up ...
>
> Sorry that I cannot report anything else.
>
> Andreas
>
> -----Original Message-----
> From: Bordet, Simone [mailto:[EMAIL PROTECTED]]
> Sent: Mittwoch, 20. Dezember 2000 15:57
> To: 'jBoss'
> Subject: RE: [jBoss-User] Exceptions
>
>
> Hey Andreas,
>
> > Hi Simone,
> >
> > 1. This situation is often repeatable, but not always. The
> > processing stopps
> > at different positions. Sometimes earlier, sometimes later,
> > sometimes it
> > completes.
> >
> > In a test application I have
> >
> > 19999 CMP entity beans LadehilfsmittelEJB,
> > 62375 CMP entity beans LadungEJB,
> > 4870 CMP entity beans AuftragEJB,
> > 23637 CMP entity beans AuftragspositionEJB.
> > Furthermore I have stateless session bean
> > AuftragsdispositionEJB. The method
> > berechnen() of this bean goes trough a subset of AuftragEJB
> > (>250) which it
> > gets by a finder method. Each AuftragEJB has n related
> > AuftragspositionEJB
> > (overall >1000 for touched AuftragEJBs). For each
> AuftragspositionEJB
> > LadungEJBs are searched which meat the requirements. For each
> > fit, a BMP
> > entity bean DispoErgebnisEJB is created (overall >3000 per touched
> > AuftragEJBs).
>
> Big numbers, don't use standardjboss.xml, that is suited for
> 0-1500 bean per
> type. Create your own jboss.xml and specify cache max
> capacity at least
> equals to the approximate number of beans of the same type you have
> contemporarly active.
> Do you already use jboss.xml specific settings ?
>
> > ctrl-break and ctrl-c don't work in this state. java.exe has
> > to be killed
> > hardly.
>
> In case of JBoss deadlock, you have 0% CPU load and
> ctrl-break does show you
> the full VM stack trace, I tested JBoss under heavy load and
> I always got
> it. What is your CPU load ? Possibly try on a hello world example the
> ctrl-break key, it gives vital informations in your case.
> If you cannot ctrl-c the JBoss' console, that seems related
> to something
> else...
>
> > Other clients hang too. It seams to be completely
> > frozen. jBoss runs
> > on Windows 2000 with Suns JVM 1.3.
>
> I have the same configuration, ctrl-break should work and it
> is vital to
> understand your problem.
>
> Let me know about.
>
> HTH,
>
> Simon
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
