Hi Geeks
Recently this bug was reported on JBoss 2.4 stating that
JBoss server runs out of memory when to many hot-
deployment with big archives.
IMO this is not a bug because when people start to deploy
big archives then they have to deal with it.
- In Production this should not become a proble
>
To: <[EMAIL PROTECTED]>
Sent: Saturday, November 17, 2001 1:58 PM
Subject: [JBoss-dev] Bug #482875: Out of Memory
> Hi Geeks
>
> Recently this bug was reported on JBoss 2.4 stating that
> JBoss server runs out of memory when to many hot-
> deployment with big archives.
>
&g
Hi,
Since I'm the one who opened this bug, I'm obviously biased, but I
repectfully disagree with Andreas's assertion that this isn't a bug. One
of JBoss' most loved features is its slick hot-deploy system. On the
jboss home page it is the first feature listed. It doesn't say "hot
deploy up to seve
jboss.org is afflicted with this bug (i think). in an ideal world a jboss
server should not need to be restarted expect to update core componets or
the vm in which it runs.
I would say that it is a bug. Does the same thing happen when large
deployables are used on 3.0?
--jason
On Sat, 17
can You Please specify Your environment in full !? ...
HW
RAM
Disk
OS
VM
aso.
Thanxs
/peter_f
on 1-11-18 01.05, Joel Boehland at [EMAIL PROTECTED] wrote:
> Hi,
> Since I'm the one who opened this bug, I'm obviously biased, but I
> repectfully disagree with Andreas's assertion that this isn't
on 1-11-18 03.28, Peter Fagerlund at [EMAIL PROTECTED] wrote:
> -400MHz, 196MB RAM
I say You do not have mem to play this game ? ...
What do U think ? ...
/peter_f
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/l
Why is the *slow* Java par with c/c**, in execution at times ? ...
Becouse it is
machinecocetranslatedjustintimewhateverthatmeansforUandYourbrother();
Word up ...
/peter_f
on 1-11-18 03.33, Peter Fagerlund at [EMAIL PROTECTED] wrote:
> on 1-11-18 03.28, Peter Fagerlund at [EMAIL PROTECTED]
I'll add my voice to the chorus that this is a bug. I think it should be
fixed in 3 when the rest of the deployers are refactored, something I am
hoping to do fairly soon. Has anyone verified whether or not it is
reproducible in 3?
david jencks
On 2001.11.17 16:58:29 -0500 Andreas Schaefer wro
Well, while someone is looking at the hot deploy code, please fix the MBean
problem.
When you deploy a SAR that has a bad mbean, ie: jboss-service.xml specifies
an attribute for a MBean that doesn't really exist, you have to restart jboss
to get the mbean to go away.
Removing the SAR only rem
Thanks for pointing this out. Nothing like only testing with correctly
configured mbeans! Should be fixed by this afternoon.
david jencks
On 2001.11.17 23:32:09 -0500 David Budworth wrote:
> Well, while someone is looking at the hot deploy code, please fix the
> MBean
> problem.
>
> When you
I have not seen it in 3.0 and I do quite a bit of redeploying a 12 meg
ear. I have seen some resource unavailables occasionally... Ill try to
remember to copy the error next time i see it.
Al
[EMAIL PROTECTED] wrote:
>I'll add my voice to the chorus that this is a bug. I think it should be
OK, I think I fixed the "can't undeploy broken mbean" problem, with a
testcase too. (in jmx/test/DeployServiceUnitTestCase).
Could you check and make sure I fixed the problem you were seeing?
Thanks
david jencks
On 2001.11.17 23:32:09 -0500 David Budworth wrote:
> Well, while someone is looking
indeed a bug.
CGJ
-Ursprüngliche Nachricht-
Von: Scott M Stark [mailto:[EMAIL PROTECTED]]
Gesendet: Sonntag, 18. November 2001 00:41
An: [EMAIL PROTECTED]
Betreff: Re: [JBoss-dev] Bug #482875: Out of Memory
It is a bug, its just a question of its priority. The deployment code is
getting old
Yep, you fixed it. Thank you.
-David
On Sunday 18 November 2001 11:14pm, David Jencks wrote:
> OK, I think I fixed the "can't undeploy broken mbean" problem, with a
> testcase too. (in jmx/test/DeployServiceUnitTestCase).
>
> Could you check and make sure I fixed the problem you were seeing?
>
14 matches
Mail list logo
