I installed Stash on a Windows Server 2008 R2 according to the installation instructions and the server has been blue screening anywhere from one to five times a day since. When my system administrators looked at the memory dump they said Tomcat was the problem (CRITICAL_OBJECT_TERMINATION). I had multiple Tomcats running but as of the last crash, only the ones for JIRA and Stash were enabled. I have since disabled Stash and have not had a crash in almost 24 hours. I would like to continue using stash but can not unless I find a solution to this. I have tried both Stash 1.1.1 and 1.1.2. I am using 32bit Java 1.6.0_33 and the git linked from the installation instructions, currently Git-1.7.11-preview20120710. I have Stash running as a service as per the atlassian instructions. Thanks to anyone who might be able to help.
(stash_bsod_minidump.txt) I've experienced a similar BSOD twice on a virtual (VMware) Windows Server 2008 R2 instance running Stash as a service. The first time it happened a few hours after the initial install of Stash 1.1.1 & Git-1.7.11-preview20120620. The second time it happened a few minutes after upgrading to Stash 1.1.2 & Git 1.7.11-preview20120710. In both cases the minidump analysis (attached) indicates that the crash happened in the Tomcat process but it doesn't say where exactly. I'm using a 32-bit JDK 7u5.
The latest upgrade to Stash 1.2.0 appears to have gone ok.
I'm suspecting it could be a VMware problem but right now I don't know what to do about it. I'm just hoping the server won't start crashing in between Stash updates.
I have raised the issue with Atlassian support.
One thing that we noticed is that the BSODs seem sensitive to the VMware coresPerCpu setting. Our VM is allocated 8 virtual CPUs and we've tried running with the following configurations:
A. 1 socket with 8 cores per socket
B. 4 sockets with 2 cores per socket
C. 8 sockets with 1 core per socket
We can easily get the machine to crash in configurations A and B by running a script that replays some random clicking activity in Stash. Configuration C appears stable thus far but we're obviously very concerned whether it'll hold up in the long run.
We've managed to reproduce the BSOD locally on a Windows Server 2008 RC2 VM. Implementing the suggestions from the following Microsoft KB Article appears to prevent the BSOD from occurring in our environment:
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot