Erreur GlassFish à répétition

**geforce** · 27/08/2012, 13h38

Bonjour,

j'ai très souvent ce message sur la console de GlassFish que j'utilise pour le développement sur l'IDE NetBeans.

GRAVE: Exception in thread "DynamicReloader"
GRAVE: Exception in thread "Grizzly-kernel-thread(1)"
GRAVE: Exception in thread "AutoDeployer"
GRAVE: Exception in thread "RMI RenewClean-[169.254.11.11:8686]"
GRAVE: java.lang.OutOfMemoryError: Java heap space
at java.util.ArrayList.<init>(ArrayList.java:112)
at java.util.ArrayList.<init>(ArrayList.java:119)
at com.sun.enterprise.v3.server.DynamicReloader.chooseAppsToReload(DynamicReloader.java:150)
at com.sun.enterprise.v3.server.DynamicReloader.reloadApps(DynamicReloader.java:139)
at com.sun.enterprise.v3.server.DynamicReloader.run(DynamicReloader.java:126)
at com.sun.enterprise.v3.server.DynamicReloadService$1.run(DynamicReloadService.java:168)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)

GRAVE: java.lang.OutOfMemoryError: Java heap space

GRAVE: java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2882)
at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:390)
at java.lang.StringBuilder.append(StringBuilder.java:119)
at org.glassfish.deployment.autodeploy.AutoDeployedFilesManager.loadStatus(AutoDeployedFilesManager.java:108)
at org.glassfish.deployment.autodeploy.AutoDeployedFilesManager.loadStatus(AutoDeployedFilesManager.java:103)
at org.glassfish.deployment.autodeploy.AutoDeployDirectoryScanner.getAllDeployableModules(AutoDeployDirectoryScanner.java:140)
at org.glassfish.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:443)
at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:395)
at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:380)
at org.glassfish.deployment.autodeploy.AutoDeployService$1.run(AutoDeployService.java:213)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)

GRAVE: java.lang.OutOfMemoryError: Java heap space

GRAVE: Exception in thread "Grizzly-kernel-thread(1)"
GRAVE: java.lang.OutOfMemoryError: Java heap space

GRAVE: Exception in thread "Grizzly-kernel-thread(1)"
GRAVE: Exception in thread "connector-timer-proxy"
GRAVE: java.lang.OutOfMemoryError: Java heap space

GRAVE: Exception while visiting net/sf/jasperreports/engine/design/JRVerifier.class of size 56836
java.lang.OutOfMemoryError: Java heap space

GRAVE: Exception while visiting javax/faces/validator/LengthValidator.class of size 5061
java.lang.OutOfMemoryError: Java heap space

GRAVE: Exception while deploying the app [Gc-war]
GRAVE: Exception while visiting net/sf/jasperreports/engine/export/AbstractTextRenderer.class of size 11157
java.lang.OutOfMemoryError: Java heap space

GRAVE: doSelect exception
java.lang.OutOfMemoryError: Java heap space

GRAVE: Java heap space
java.lang.OutOfMemoryError: Java heap space

GRAVE: Exception while visiting javax/faces/view/ViewDeclarationLanguage.class of size 3344
java.lang.OutOfMemoryError: Java heap space

GRAVE: Exception while visiting net/sf/jasperreports/engine/export/DefaultElementHandlerBundle.class of size 2828
java.lang.OutOfMemoryError: Java heap space

GRAVE: Exception invoking periodic operation:
java.lang.OutOfMemoryError: Java heap space

GRAVE: Exception while visiting net/sf/jasperreports/engine/export/DefaultExporterFilterFactory.class of size 3723
java.lang.OutOfMemoryError: Java heap space

GRAVE: Exception in thread "ContainerBackgroundProcessor[StandardEngine[glassfish-web]]"
Launching GlassFish on Felix platform
GRAVE: Exception in thread "Grizzly-kernel-thread(1)"
INFO: Registered org.glassfish.ha.store.adapter.cache.ShoalBackingStoreProxy for persistence-type = replicated in BackingStoreFactoryRegistry
INFO: The Admin Console is already installed, but not yet loaded.
INFO: GlassFish Server Open Source Edition 3.1 (43) startup time : Felix (13*872ms), startup services(2*799ms), total(16*671ms)
INFO: Grizzly Framework 1.9.31 started in: 493ms - bound to [0.0.0.0:4848]
INFO: Grizzly Framework 1.9.31 started in: 545ms - bound to [0.0.0.0:8080]
INFO: Grizzly Framework 1.9.31 started in: 505ms - bound to [0.0.0.0:8181]
INFO: Grizzly Framework 1.9.31 started in: 434ms - bound to [0.0.0.0:3700]
INFO: Grizzly Framework 1.9.31 started in: 425ms - bound to [0.0.0.0:7676]
GRAVE: java.rmi.server.ExportException: Port already in use: 8686; nested exception is:
java.net.BindException: Address already in use: JVM_Bind
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:310)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:218)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:393)
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:129)
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:190)
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:68)
at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:222)
at org.glassfish.admin.mbeanserver.RMIConnectorStarter._startRegistry(RMIConnectorStarter.java:236)
at org.glassfish.admin.mbeanserver.RMIConnectorStarter.startRegistry(RMIConnectorStarter.java:217)
at org.glassfish.admin.mbeanserver.RMIConnectorStarter.<init>(RMIConnectorStarter.java:152)
at org.glassfish.admin.mbeanserver.JMXStartupService$JMXConnectorsStarterThread.startConnector(JMXStartupService.java:240)
at org.glassfish.admin.mbeanserver.JMXStartupService$JMXConnectorsStarterThread.run(JMXStartupService.java:283)
Caused by: java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383)
at java.net.ServerSocket.bind(ServerSocket.java:328)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at java.net.ServerSocket.<init>(ServerSocket.java:106)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:27)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:333)
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:649)
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:299)
... 12 more

ATTENTION: Cannot start JMX connector: JmxConnector config: { name = system, Protocol = rmi_jrmp, Address = 0.0.0.0, Port = 8686, AcceptAll = false, AuthRealmName = admin-realm, SecurityEnabled = false}: java.lang.RuntimeException: Port 8686 is not available for the internal rmi registry. This means that a call was made with the same port, without closing earlier registry instance. This has to do with the system jmx connector configuration in admin-service element of the configuration associated with this instance
GRAVE: java.lang.RuntimeException: Port 8686 is not available for the internal rmi registry. This means that a call was made with the same port, without closing earlier registry instance. This has to do with the system jmx connector configuration in admin-service element of the configuration associated with this instance
at org.glassfish.admin.mbeanserver.RMIConnectorStarter._startRegistry(RMIConnectorStarter.java:240)
at org.glassfish.admin.mbeanserver.RMIConnectorStarter.startRegistry(RMIConnectorStarter.java:217)
at org.glassfish.admin.mbeanserver.RMIConnectorStarter.<init>(RMIConnectorStarter.java:152)
at org.glassfish.admin.mbeanserver.JMXStartupService$JMXConnectorsStarterThread.startConnector(JMXStartupService.java:240)
at org.glassfish.admin.mbeanserver.JMXStartupService$JMXConnectorsStarterThread.run(JMXStartupService.java:283)

Comment je peux éviter ça ?, j'ai fait quelque config pour tenter d’arrangés un peux les choses mais pas de net avancé.

Voici les config que j'ai fait (option JVM)
-xms-1024m
-xms-1024m
-client
les autre config son par défaut

**tchize_** · 27/08/2012, 14h23

visiblement ton application web ou j2ee n'est pas entièrement retirée de la mémoire à chaque déploiement, ce qui fait que progressivement toutes ces versions commencent à bouffer la heap. Soit tu accepte le problème en considérant que, de toutes façons, en production, on redémarrerale glassfish à chaque démarrage, soit tu commence à utiliser des outils de profiling pour investiguer l'origine de cette fuite de mémoire.

Ca peut être, par exemple, du à un thread que tu démarrer dans ton applicaiton et que tu ne tue pas lors de l'arrêt. Tant que le thread tourne, il a besoin du classloader et donc tout une partie de l'application reste en mémoire avec ce classloader.