In the "Run Application" flow, there is a "Timeout" setting. Is this setting in seconds? Milliseconds? Something else? The information tooltip does not say in what format it is, nor does the online documentation.
It's stored in seconds.
I tested that by launching Visual Studio and it waits for the amount of seconds specified before it moves on.
Related
We are trying to change the socket timeout in Jira as some of the REST API calls are taking too long to respond due to which we are getting Request Time Out Error.
For changing it, we tried the following but NONE of them worked:
We made changes in the General Configuration settings by following this article.
We followed the following article and changed the JVM_SUPPORT_RECOMMENDED_ARGS parameter to increase the socket time and these are our observations:
When setting the JVM_SUPPORT_RECOMMENDED_ARGS to 20000milliseconds (20sec), we found that it fails for the delay above 20sec; rest it is working fine for any value below it.
When the JVM_SUPPORT_RECOMMENDED_ARGS parameter set to any value between 2min to 14min, the delay above 50sec gives error. For the delay uptill 50sec in project creation, it is working fine.
The snapshot of setenv.sh file, where we made our changes:
Please suggest how to increase the socket time out so that we do not get a Request Time Out for a delay of around 2 min.
Any suggestions would be helpful.
If you use unproxied access to your Jira (i.e. via Tomcat distributed together with Jira), then you will have to change the timeout also in the Tomcat configuration: <jira-install>/conf/server.xml.
There's Tomcat's connector configuration:
<Connector port="8080" connectionTimeout="20000" ...
^^^^^
Notes:
Also feel free to contact official Atlassian Support if you have paid subscription.
Also take a look into logs to find out why project creation takes so much time and times-out (it's not normal, project creation is a matter of a second).
I am using TFS Release gates to call severall api's before i deploy.
Usually this works great. But sometimes the gates don't fire at all and the api is never called.
I set the timeout on 5 minutes.. so after 5 minutes it should try again.... But that sheduled is then messed up. sometimes it retries after 5 minutes (as it is supposed to) but sometimes it takes 11 or 12 minutes.....
It looks like the requests are queued somewhere... but i really gave no idea.
Anybody knows this behaviour ?
Updated
The Delay before evaluation is a time delay at the beginning of the gate evaluation process that allows the gates to initialize, stabilize, and begin providing accurate results for the current deployment
Gate actually is a sever task which is currently run on server. Some examples could prove
On-premise - Any on-premise/behind the firewall resources are
inaccessible
Env Variables - some of the environment variables are not accessible
(they are not yet initialized at the time of gate check)
It's run by release service account just as other tasks in release pipeline.
Besides, Delay before evaluation is meant to be the time samples from the gates might be unreliable. It's an acceptable phenomena. Sometimes it may need more time than your configuration to do the check.
Source Link: Release approvals and gates overview
From our Advanced Installer setup, we install/upgrade a service that needs up to a minute to shut down. We cannot decrease the time it needs, and it will be shut down after a minute.
If AI tries to stop that service, it comes up with an error message after less than a minute ("The setup was unable to automatically close all requested applications. Please ensure that the applications holding files in use are closed before continuing with the installation").
I have not found an option in Advanced Installer Professional to change the timeout of the wait.
Is this possible?
I don't think this is possible. You can try to use a custom action to stop the service. That means you could write your own code to trigger a service stop operation and wait for a minute. This code can be executed as a custom action.
To make sure the described error message is not thrown you should execute your custom action before "Paths Resolution" action.
I have the following scenario:
LR Portal 6.1.20 EE GA2 Portal behind IBM WebSeal
Staged Sites
Custom portlet which needs to publish it’s contents from staging to live
The custom portlet is publishing it’s contents with a class that extends BasePortletDataHandler and overrides the following methods:
doExportData
doImportData
doDeleteData
isAlwaysExportable
isPublishToLiveByDefault
isAlwaysStaged
This works quite well in developing mode, where there is no WebSeal. In control panel, you go to "site pages" and invoke “publish to live”.
In production however, we get WebSeal timeouts whenever this process takes more than 2 minutes. The process is still running in the background, but the user has no way telling if it's done, if it worked or if it did not. He gets no feedback about it what so ever.
Is there a way to implement a custom portlet for the control panel which takes care of these problems? How do I get/track the status of the process and how do I keep the session alive?
I don't have any experience with liferay, but I administrator WebSEAL daily so I can approach your question from that angle. You can increase the timeouts on individual junctions. I have encountered similar scenarios with applications in the past. We have had to go up to a 300 second timeout.
[junction:junction_name]
http-timeout = 300
https-timeout = 300
http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=%2Fcom.ibm.itame.doc_6.1.1%2Fam611_webseal_admin95.htm
You may also need to increase the server timeouts:
[server]
client-connect-timeout = 300
http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.itame.doc_6.1.1/am611_webseal_admin94.htm?path=3_10_3_3_1_4_0_6_5#http-https-timeouts
The problem is the application doesn't send any data over the TCP connection, so WebSEAL times out the connection. Unless you can change the way your application works, you'll have to increase the timeouts. Preferably you would use AJAX or similar technology to have the client routinely query the server for a status once the procedure is kicked off. However, I had a customer that was integrating with us and they couldn't change their application code, so I was forced to increase the timeouts for them as well.
After finishing some task, how is it possible in jira log this current(finish) time?
So I don't want calculate time spending on task as start time of task + time spended on task, I want only enter finish time and time spent will be calculated(in jira) as finish time-start time.
JIRA doesn't currently offer real-time time tracking.
However your IDE should have some means of logging you time - for example Eclipse has this built in in the tasks plugin and it could also be connected to JIRa so that you could see your tasks in the IDE and log your time in "real-time" right there.
I have found this to be rather inconvenient since if inactive inside the IDE for a certain period of time the tracking will stop - this is an option in the IDE though.
I personally use Toggl which is free for a "one-man show" team. Also their pricing for teams is very nice. There are other services like Toggl and they are not all web-based. For example Project Hamster if you're on Linux. Just google time tracking. ;) Otherwise as I said the only way is to connect your IDE to JIRA via some task module.