[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Ethan Thornburg edited a comment on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java Is there any other resolutions for this?-Xmx1025m in jenkins.xml didn't resolve the issue for me. Using force clean does, but my builds all take a very long time now. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Ethan Thornburg commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java Is there any other resolutions for this? -Xmx1025m in jenkins.xml didn't resolve the issue for me. Using force clean does, but my builds all take a very long time now. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Staffan Forsell edited a comment on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java We switched force sync a while ago and it actually faster than the smart algorithm so well keep using it for now. So I will won't be adding more info to this case. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Paul Allen commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java I wouldn't worry about Monday morning blindness - I have only just got back from a weeks skiing, so it will take me a while to get plugged back in. When you start the slave agent you can add arguments to the JVM -Xmx1024m (e.g. 1GB for the heap); this all depends on how you start the slave, the StackOverflow link discusses some of the options: http://stackoverflow.com/questions/5936519/how-to-give-jenkins-more-heap-space-when-it%C2%B4s-started-as-a-service-under-windows An alternative is to use the ForceClean option (it might be slower, but potentially uses less memory than reconcile). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Heiko Nardmann commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java Looks like I got that this morning, too: 09:54:57 p4 reconcile -w -f -e -d D:\ci\workspace\some_job/... 09:54:57 09:57:36 P4 Task: attempt: 1 09:57:39 P4 Task: failed: com.perforce.p4java.exception.ConnectionException: Java heap space 09:57:39 ERROR: P4 Task: failed: com.perforce.p4java.exception.ConnectionException: Java heap space I do not see a Java stack trace. Jenkins v2.21, P4 plugin v1.4.12. Jenkins runs on CentOS 7.2.1511 (64Bit). The slave system is Windows Server 2008 R2 Standard (64Bit). I'm not sure whether the Windows Java (jre1.8.0_121) is 32Bit or 64Bit. DependencyWalker says x86, so probably this is 32Bit. Is 64Bit recommended? The failed job is a freestyle job. Acc. to /proc/.../maps the Java executable is /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.111-2.6.7.2.el7_2.x86_64/jre-abrt/bin/java So this is the following package (see rpm -qif ...): Name: java-1.7.0-openjdk-headless Epoch : 1 Version : 1.7.0.111 Release : 2.6.7.2.el7_2 Architecture: x86_64 Install Date: Tue 15 Nov 2016 03:01:46 PM CET Group : Development/Languages Size: 9015 License : ASL 1.1 and ASL 2.0 and GPL+ and GPLv2 and GPLv2 with exceptions and LGPL+ and LGPLv2 and MPLv1.0 and MPLv1.1 and Public Domain and W3C Signature : RSA/SHA256, Wed 27 Jul 2016 01:39:38 PM CEST, Key ID 24c6a8a7f4a80eb5 Source RPM : java-1.7.0-openjdk-1.7.0.111-2.6.7.2.el7_2.src.rpm Build Date : Wed 27 Jul 2016 01:07:19 PM CEST Build Host : worker1.bsys.centos.org Relocations : (not relocatable) Packager: CentOS BuildSystem Vendor : CentOS URL : http://openjdk.java.net/ Summary : The OpenJDK runtime environment without audio and video support Description : The OpenJDK runtime environment without audio and video What is not clear to me: is this an issue on the server or on the slave agent? Ahh ... forget last question: acc. to slave agent error log: Feb 06, 2017 9:57:37 AM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTask SEVERE: P4 Task: attempt: 1 com.perforce.p4java.exception.ConnectionException: Java heap space at com.perforce.p4java.impl.mapbased.rpc.packet.RpcPacketDispatcher.dispatch(RpcPacketDispatcher.java:225) at com.perforce.p4java.impl.mapbased.rpc.OneShotServerImpl.execMapCmdList(OneShotServerImpl.java:350) at com.perforce.p4java.impl.mapbased.rpc.OneShotServerImpl.execStreamingMapCommand(OneShotServerImpl.java:415) at
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Staffan Forsell commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java We switched force sync a while ago and it actually faster than the smart algorithm so well keep using it for now. So I will be adding more info to this case. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Paul Allen commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java A possible work around is to use the 'Force clean' option, this avoids the reconcile command and should use less memory. Enabling parallel sync should speed sync time and my use less memory in the Java Heap. If you are using slaves then parallel sync will require the 'p4' executable installed on the slave. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title
Staffan Forsell edited a comment on JENKINS-31683
Re: p4-plugin out of memory with large depots on 32 bit java
This is all I got in console output{noformat}P4 Task: cleaning workspace to match have list p4 reconcile -w -f /home/run/jenkins/workspace/jobXXX/... -p4 reconcile -w -f /home/run/jenkins/workspace/jobXXX/...P4 Task: attempt: 1P4 Task: failed: com.perforce.p4java.exception.ConnectionException: Java heap space[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: P4 Task: failed: com.perforce.p4java.exception.ConnectionException: Java heap spaceFinished: FAILURE{noformat}Maybe the lack of a stacktrace has to do with it being a pipeline job.{noformat}p4 sizes -s .//... 16649 files 2476092266 bytes {noformat}This is failed on a 64-bit debian server with 4Gb memory . But , but it does not always fail.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Paul Allen started work on JENKINS-31683 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Staffan Forsell commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java This is all I got in console output P4 Task: cleaning workspace to match have list. ... p4 reconcile -w -f /home/run/jenkins/workspace/jobXXX/... - p4 reconcile -w -f /home/run/jenkins/workspace/jobXXX/... P4 Task: attempt: 1 P4 Task: failed: com.perforce.p4java.exception.ConnectionException: Java heap space [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: P4 Task: failed: com.perforce.p4java.exception.ConnectionException: Java heap space Finished: FAILURE Maybe the lack of a stacktrace has to do with it being a pipeline job. p4 sizes -s ./... ./... 16649 files 2476092266 bytes This is failed on a 64-bit debian server with 4Gb memory. But it does not always fail. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Paul Allen commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java 1.4.4 added streaming support for reconcile (should significantly reduce the memory) and yes 1.4.8 uses an updated p4java. So anything between the 1.4.4 and 1.4.8 would be useful. Unfortunately the slave can run out of memory at any point and sometimes it's not able to get a stacktrace, however the console log might suggest where it failed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Staffan Forsell commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java I'm pretty sure this happened on 1.4.7 for me, but the slave seems to have been restarted and the logs are gone. Isn't it from 1.4.8 or later we should be checking? That's were the new p4java is according to the change logs. Is there a way to get the stack trace in the normal console output? For me it just prints the exception message. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Paul Allen commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java With version 1.4.7 or later, can someone please let me know where the plugin runs out of memory? For example: during the 'p4 reconcile -w' or a later stage. Another stack trace would be helpful. In addition please let me know the number of files and size in the scope of the Perforce workspace: p4 sizes -s //client_name/... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Sidney Brown commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java I'm running into the same problem. Have a depot with a large number of files. Honestly I don't think we have any need to reconcile? I've only checked out the files I need and just need to submit what's checked out. Maybe i'm missing something but I feel like this should be an option on whether to do that step. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Aaron Wilson commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java I'd love to get an update on this, too. We're seeing it more and more often - I don't know if it's because the size of our stream is getting larger, or if there's something else that is degrading it. It's a big problem if I have to manually log into the jenkins machine and get the latest revision myself every time, which is the only workaround I've managed to find so far. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Alexander Raine commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java Any further progress on this issue? I'm encountering it on some of my builds when I attempt to switch to the official Perforce plugin, as opposed to the third-party perforce plugin. I've upgraded to the latest plugin (1.4.7), and I'm on latest Jenkins (2.7.4); the target box in the failure cases is a Windows box hosted on AWS. I'm happy to share any other relevant details that could help diagnose it. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Paul Allen commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java Thank you for checking again, there was nothing specific in 1.4.6 release for the memory issue. We have a reproduction case here and it seems to be something in the p4java API, we are investigating and will let you know what we find. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Aaron Wilson commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java I just started seeing the same thing. I upgraded to 1.4.6, just to check the latest and greatest, and I'm still seeing the same thing. This is on a sync only execution. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Johannes Löthberg commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java No longer get a stack trace in the log, just "ERROR: P4 Task: failed: com.perforce.p4java.exception.ConnectionException: Java heap space". There are some 24 thousand files in the data directory that it tries to check out, and I'm not sure how to check the heap memory? It has 4G RAM at least. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Paul Allen commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java Please can you include (or update) the stack trace for 1.4.4 How many files are you potentially cleaning up (versioned/non-versioned files) and how much java heap memory does the slave have? Thanks, Paul Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Johannes Löthberg commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java Same problem on Jenkins 2.19 with P4 plugin version 1.4.4. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Paul Allen commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java The 1.4.4 release or P4 uses a more efficient method to sync and reconcile: https://swarm.workshop.perforce.com/changes/19918 Please can you verify and update or close the issue as needed. Thanks, Paul Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
