Bugs item #973162, was opened at 2004-06-15 04:02
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=973162&group_id=22866

Category: None
Group: None
>Status: Closed
>Resolution: Works For Me
Priority: 5
Submitted By: Chris Effenberger (pinguine)
>Assigned to: Scott M Stark (starksm)
Summary: OutOfMemoryError  Deployment

Initial Comment:
Java version: 1.4.2_01,Sun Microsystems Inc.
Java VM: Java HotSpot(TM) Client VM 1.4.2_01-b06,Sun 
Microsystems Inc.
Windows NT 4.0,x86, SP6

If I hotdeploy beans (more than 20-30) the following 
ERROR appears:

2004-06-15 12:46:58,472 DEBUG 
[org.jboss.ejb.EJBDeployer](ScannerThread :) create, 
Company.jar
2004-06-15 12:47:01,166 ERROR 
[org.jboss.deployment.MainDeployer](ScannerThread :) 
could not create deployment: 
file:/C:/jboss/server/default/deploy/Company.jar
java.lang.OutOfMemoryError
2004-06-15 12:47:01,176 DEBUG 
[org.jboss.util.NestedThrowable](ScannerThread :) 
org.jboss.util.NestedThrowable.parentTraceEnabled=true
2004-06-15 12:47:01,176 DEBUG 
[org.jboss.util.NestedThrowable](ScannerThread :) 
org.jboss.util.NestedThrowable.nestedTraceEnabled=false
2004-06-15 12:47:01,176 DEBUG 
[org.jboss.util.NestedThrowable](ScannerThread :) 
org.jboss.util.NestedThrowable.detectDuplicateNesting=tr
ue
2004-06-15 12:47:01,176 DEBUG 
[org.jboss.deployment.scanner.URLDeploymentScanner]
(ScannerThread :) Failed to deploy: 
org.jboss.deployment.scanner.URLDeploymentScanner$De
[EMAIL PROTECTED] 
url=file:/C:/jboss/server/default/deploy/Company.jar, 
deployedLastModified=0 }
org.jboss.deployment.DeploymentException: Could not 
create deployment: 
file:/C:/jboss/server/default/deploy/Company.jar; - 
nested throwable: (java.lang.OutOfMemoryError)
        at 
org.jboss.deployment.DeploymentException.rethrowAsDep
loymentException(DeploymentException.java:39)
        at org.jboss.deployment.MainDeployer.create
(MainDeployer.java:806)
        at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:644)
        at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:608)
        at 
sun.reflect.GeneratedMethodAccessor20.invoke
(Unknown Source)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke
(Method.java:324)
        at 
org.jboss.mx.server.ReflectedDispatcher.dispatch
(ReflectedDispatcher.java:60)
        at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:61)
        at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:53)
        at org.jboss.mx.server.Invocation.invoke
(Invocation.java:86)
        at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:185)
        at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:473)
        at org.jboss.mx.util.MBeanProxyExt.invoke
(MBeanProxyExt.java:176)
        at $Proxy7.deploy(Unknown Source)
        at 
org.jboss.deployment.scanner.URLDeploymentScanner.de
ploy(URLDeploymentScanner.java:304)
        at 
org.jboss.deployment.scanner.URLDeploymentScanner.sc
an(URLDeploymentScanner.java:478)
        at 
org.jboss.deployment.scanner.AbstractDeploymentScann
er$ScannerThread.doScan
(AbstractDeploymentScanner.java:201)
        at 
org.jboss.deployment.scanner.AbstractDeploymentScann
er$ScannerThread.loop
(AbstractDeploymentScanner.java:212)
        at 
org.jboss.deployment.scanner.AbstractDeploymentScann
er$ScannerThread.run
(AbstractDeploymentScanner.java:191)
Caused by: java.lang.OutOfMemoryError
2004-06-15 12:47:01,176 DEBUG 
[org.jboss.deployment.scanner.URLDeploymentScanner]
(ScannerThread :) Watch URL for: 
file:/C:/jboss/server/default/deploy/Company.jar -> 
file:/C:/jboss/server/default/deploy/Company.jar

----------------------------------------------------------------------

>Comment By: Scott M Stark (starksm)
Date: 2004-09-07 11:34

Message:
Logged In: YES 
user_id=175228

A trace level log is of no use here. You need to supply an
example if you want use to look at it, or profile the
redeployment yourself. This has been caused by static
classes holding onto class loaders which in turn leak
classes and data via caches in every case investigated so
far. There are no known leaks in the jboss deployment layer
at this time. Reopen with an example or steps to reproduce
the issue.

----------------------------------------------------------------------

Comment By: Alexei Yudichev (sflexus)
Date: 2004-09-07 07:59

Message:
Logged In: YES 
user_id=345880

Welcome to the world of bugs #435958, #576913 and probably 
many others.

----------------------------------------------------------------------

Comment By: Chris Effenberger (pinguine)
Date: 2004-06-15 04:35

Message:
Logged In: YES 
user_id=733943

log with trace level is attached

----------------------------------------------------------------------

Comment By: Chris Effenberger (pinguine)
Date: 2004-06-15 04:04

Message:
Logged In: YES 
user_id=733943

jboss-3.2.4

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=973162&group_id=22866


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to