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]
