[gatein-issues] [JBoss JIRA] Updated: (GTNPORTAL-988) Out of memory because of huge log file during Perf Test

Arthur Peltier (JIRA) jira-events at lists.jboss.org
Fri Mar 26 01:28:39 EDT 2010


     [ https://jira.jboss.org/jira/browse/GTNPORTAL-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arthur Peltier updated GTNPORTAL-988:
-------------------------------------

    Affects Version/s: 3.0.0-GA


> Out of memory because of huge log file during Perf Test
> -------------------------------------------------------
>
>                 Key: GTNPORTAL-988
>                 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-988
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.0.0-GA
>            Reporter: Arthur Peltier
>
> I need to create about 150 default users (from testuser1.exo to testuser150.exo) I modified the organization-configuration.xml and add 150 users. Then I run the jboss.
> Can not run successfully, 
> exception in the cygwin:  
> 18:41:20,968 WARN [resources] Cannot load and merge the bundle: Resource 18:41:20,968 WARN [resources] Cannot load and merge the bundle: Resource 18:41:20,984 WARN [resources] Cannot load and merge the bundle: Resource 18:41:20,984 INFO [faces] Init GenericFacesPortlet for portlet WSRPConfigurationPortlet 18:41:20,984 INFO [faces] Bridge class name is org.jboss.portletbridge.AjaxPortletBridge 18:41:21,015 INFO [faces] The bridge does not support doHeaders method 18:41:21,015 INFO [faces] GenericFacesPortlet for portlet WSRPConfigurationPortlet initialized 18:41:21,156 INFO [NodeRepresentationService] NodeRepresentationFactory added nt:file org.exoplatfo rm.services.jcr.ext.resource.representation.NtFileNodeRepresentationFactory 18:41:21,156 INFO [NodeRepresentationService] NodeRepresentationFactory added nt:resource org.exopl atform.services.jcr.ext.resource.representation.NtResourceNodeRepresentationFactory 18:42:22,312 INFO [IndexMerger] merged 55 documents in 47 ms into _1u. 18:42:22,500 INFO [IndexMerger] merged 10 documents in 47 ms into _1v. 18:42:22,609 INFO [IndexMerger] merged 10 documents in 31 ms into _1w. 18:42:22,734 INFO [IndexMerger] merged 10 documents in 31 ms into _1x. 18:42:22,937 INFO [IndexMerger] merged 10 documents in 31 ms into _1y. 18:42:23,109 INFO [IndexMerger] merged 10 documents in 47 ms into _1z. 18:42:23,265 INFO [IndexMerger] merged 100 documents in 47 ms into _20. 18:43:25,921 INFO [IndexMerger] merged 118 documents in 93 ms into _3t. 18:43:26,109 INFO [IndexMerger] merged 10 documents in 31 ms into _3u. 18:43:26,250 INFO [IndexMerger] merged 10 documents in 47 ms into _3v. 18:43:26,406 INFO [IndexMerger] merged 10 documents in 63 ms into _3w. 18:43:26,578 INFO [IndexMerger] merged 10 documents in 47 ms into _3x. 18:43:26,750 INFO [IndexMerger] merged 10 documents in 47 ms into _3y. 18:43:26,890 INFO [IndexMerger] merged 55 documents in 31 ms into _3z. 18:45:11,453 INFO [IndexMerger] merged 2038 documents in 110 ms into _4a. 18:46:09,328 INFO [IndexMerger] merged 631 documents in 94 ms into _4l. 18:46:55,000 INFO [IndexMerger] merged 640 documents in 63 ms into _4w. log4j error: Failed to flush writer, java.io.IOException: There is not enough space on the disk at java.io.FileOutputStream.writeBytes(Native Method) at java.io.FileOutputStream.write(FileOutputStream.java:260) at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202) at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272) at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:276) at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:122) at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:212) at org.apache.log4j.helpers.QuietWriter.flush(QuietWriter.java:57) at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:315) at org.apache.log4j.DailyRollingFileAppender.subAppend(DailyRollingFileAppender.java:358) at org.apache.log4j.WriterAppender.append(WriterAppender.java:159) at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230) at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableI mpl.java:65) at org.apache.log4j.Category.callAppenders(Category.java:203) at org.apache.log4j.Category.forcedLog(Category.java:388) at org.apache.log4j.Category.log(Category.java:853) at org.jboss.logging.log4j.Log4jLoggerPlugin.debug(Log4jLoggerPlugin.java:145) at org.jboss.logging.Logger.debug(Logger.java:228) at org.jboss.slf4j.JBossLoggerAdapter.debug(JBossLoggerAdapter.java:106) at org.hibernate.engine.Collections.processReachableCollection(Collections.java:199) at org.hibernate.event.def.FlushVisitor.processCollection(FlushVisitor.java:60) at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:124) at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:84) at org.hibernate.event.def.AbstractVisitor.processEntityPropertyValues(AbstractVisitor.java: 78) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityE ventListener.java:161) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEvent Listener.java:219) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(Abstrac tFlushingEventListener.java:99) at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventLi stener.java:58) at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:996) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1589) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:306) at org.hibernate.impl.CriteriaImpl.uniqueResult(CriteriaImpl.java:328) at org.picketlink.idm.impl.store.hibernate.HibernateIdentityStoreImpl.findIdentityObject(Hib ernateIdentityStoreImpl.java:607) at org.picketlink.idm.impl.repository.WrapperIdentityStoreRepository.findIdentityObject(Wrap perIdentityStoreRepository.java:155)  
> Check the logs file, there is a huge size one up to 3-4 GB.  I do similarly but with only 10 users for the organization-configuration.xml, there is no problem.  May be, 150 users configured in the organization-configuration.xml is the problem of the huge log file  
> Because of the log file is very big , it can not be opened and uploaded. 
> So, I only spent a short time to run the package in order to get smaller one that can be opened, you can check the log file at: http://www.megafileupload.com/en/file/207855/GateIn-server-zip.html  
> The package with configuration for the performance test, you can download and run to see the big log file in your computer:  http://www.megafileupload.com/en/file/207862/GateIn-3-0-0-GA-FINAL4Test-zip.html (This package was also configured with Javamelody) 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the gatein-issues mailing list