Also dropping the parameter -XX:MaxNewSize=256 helps with big JVM’s. We had an big speedup when removing that parameters as it was limiting the tomcat-container from fully using the larger amounts of memory.
Andreas Dijkman On 10 Apr 2018, at 23:55, William H. ten Bensel <whten...@up.com<mailto:whten...@up.com>> wrote: We had to go higher in memory allocation --> # Increase java heap size and logging: https://access.redhat.com/solutions/43122 taskomatic.java.maxmemory=12288 taskomatic.java.initmemory=512 taskomatic.logfile.maxsize=100m java.taskomatic_channel_repodata_workers=4 tomcat6 --> -Xms512m -Xmx8192m From: Ezequiel Sozzi <soz...@gmail.com<mailto:soz...@gmail.com>> To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com> Date: 04/10/2018 02:36 PM Subject: [Spacewalk-list] Java heap space Sent by: spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> ________________________________ This email originated from outside of the company. Please use discretion if opening attachments or clicking on links. ________________________________ Hello, I'm currently having a problem with taskomatic. while is trying to generate the reporsitory metadata for my repository 'rh6-x86_64-os' I'm getting the following error: rhn_taskomatic_daemon.log INFO | jvm 1 | 2018/04/10 14:52:15 | 2018-04-10 14:52:15,756 [Thread-53] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - Generating new repository metadata for channel 'rh6-x86_64-os'(sha1) 28664 packages, 4902 errata INFO | jvm 1 | 2018/04/10 15:00:28 | Exception in thread "Thread-53" java.lang.OutOfMemoryError: Java heap space INFO | jvm 1 | 2018/04/10 15:00:28 | at org.postgresql.util.PGbytea.toBytesHexEscaped(PGbytea.java:40) INFO | jvm 1 | 2018/04/10 15:00:28 | at org.postgresql.util.PGbytea.toBytes(PGbytea.java:35) INFO | jvm 1 | 2018/04/10 15:00:28 | at org.postgresql.jdbc2.AbstractJdbc2ResultSet.getBytes(AbstractJdbc2ResultSet.java:2433) INFO | jvm 1 | 2018/04/10 15:00:28 | at org.postgresql.jdbc2.AbstractJdbc2ResultSet.internalGetObject(AbstractJdbc2ResultSet.java:165) INFO | jvm 1 | 2018/04/10 15:00:28 | at org.postgresql.jdbc3.AbstractJdbc3ResultSet.internalGetObject(AbstractJdbc3ResultSet.java:36) INFO | jvm 1 | 2018/04/10 15:00:28 | at org.postgresql.jdbc4.AbstractJdbc4ResultSet.internalGetObject(AbstractJdbc4ResultSet.java:296) INFO | jvm 1 | 2018/04/10 15:00:28 | at org.postgresql.jdbc2.AbstractJdbc2ResultSet.getObject(AbstractJdbc2ResultSet.java:2703) INFO | jvm 1 | 2018/04/10 15:00:28 | at org.postgresql.jdbc2.AbstractJdbc2ResultSet.getObject(AbstractJdbc2ResultSet.java:2715) INFO | jvm 1 | 2018/04/10 15:00:28 | at com.mchange.v2.c3p0.impl.NewProxyResultSet.getObject(NewProxyResultSet.java:4303) INFO | jvm 1 | 2018/04/10 15:00:28 | at com.redhat.rhn.common.db.datasource.CachedStatement.getObject(CachedStatement.java:732) INFO | jvm 1 | 2018/04/10 15:00:28 | at com.redhat.rhn.common.db.datasource.CachedStatement.addToObject(CachedStatement.java:715) INFO | jvm 1 | 2018/04/10 15:00:28 | at com.redhat.rhn.common.db.datasource.CachedStatement.processResultSet(CachedStatement.java:570) INFO | jvm 1 | 2018/04/10 15:00:28 | at com.redhat.rhn.common.db.datasource.CachedStatement.execute(CachedStatement.java:420) INFO | jvm 1 | 2018/04/10 15:00:28 | at com.redhat.rhn.common.db.datasource.CachedStatement.executeElaboratorBatch(CachedStatement.java:346) INFO | jvm 1 | 2018/04/10 15:00:28 | at com.redhat.rhn.common.db.datasource.CachedStatement.executeElaboratorBatch(CachedStatement.java:373) INFO | jvm 1 | 2018/04/10 15:00:28 | at com.redhat.rhn.common.db.datasource.CachedStatement.executeElaborator(CachedStatement.java:325) INFO | jvm 1 | 2018/04/10 15:00:28 | at com.redhat.rhn.common.db.datasource.SelectMode.elaborate(SelectMode.java:130) INFO | jvm 1 | 2018/04/10 15:00:28 | at com.redhat.rhn.common.db.datasource.DataResult.elaborate(DataResult.java:159) INFO | jvm 1 | 2018/04/10 15:00:28 | at com.redhat.rhn.taskomatic.task.repomd.RpmRepositoryWriter.writeRepomdFiles(RpmRepositoryWriter.java:185) INFO | jvm 1 | 2018/04/10 15:00:28 | at com.redhat.rhn.taskomatic.task.repomd.ChannelRepodataWorker.run(ChannelRepodataWorker.java:104) INFO | jvm 1 | 2018/04/10 15:00:28 | at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748) INFO | jvm 1 | 2018/04/10 15:00:28 | at java.lang.Thread.run(Thread.java:748) I have extended the memory parameter in the /etc/sysconfig/tomcat file from 256 to 1024 JAVA_OPTS="-ea -Xms1024m -Xmx1024m -Djava.awt.headless=true -Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser -Dorg.apache.tomcat.util.http.Parameters.MAX_COUNT=1024 -XX:MaxNewSize=256 -XX:-UseConcMarkSweepGC -Dnet.sf.ehcache.skipUpdateCheck=true" Also I have added the option tasomatic.maxmemory = 4096 to the file /etc/rhn/rhn.conf but the problem persist. Any Ideas how to fix this? This email originated from outside of the company. Please use discretion if opening attachments or clicking on links. _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com<mailto:Spacewalk-list@redhat.com> https://www.redhat.com/mailman/listinfo/spacewalk-list ** This email and any attachments may contain information that is confidential and/or privileged for the sole use of the intended recipient. Any use, review, disclosure, copying, distribution or reliance by others, and any forwarding of this email or its contents, without the express permission of the sender is strictly prohibited by law. If you are not the intended recipient, please contact the sender immediately, delete the e-mail and destroy all copies. ** _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com<mailto:Spacewalk-list@redhat.com> https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
