You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Some timeout parameters are set between the integration of Atlassian applications. If the timeout is not working properly as expected due to bugs, there is a need to reproduce a timeout. However, the process is usually very quick, like below 5 seconds, after you clicked a button from browser. How to reproduce a 60 seconds timeout?
Basically, it use the options of kill command, as below steps.
For example, a customer reported the timeout between Jira and Fisheye is not working properly, as the case in JSWSERVER-13296-DevStatus timeouts not taking affect
You need to verify if the customer report is true, and want to do a timeout reproduce in your environment.
ssh to Fisheye server, and find the the process ID of Fisheye.
ps aux |grep fisheye
You must suspend Fisheye process as quickly as possible since the process may finish in 5 seconds. The command is like below .
kill -TSTP [pid]
After the time span of timeout , check if timeout happened in Jira log.
When you finished your timeout reproducing, the below command can be used to resume the suspended process of Fisheye.
kill -CONT [pid]
11 accepted answers