We have our JIRA URL hosted over Internet. When i access it dirtecly from the server where it is installed it opens fine however when my other users access it from there local computer it is very slow.
Atlassian Support asks to coordinate with Network admin of my office and as per Network team some changes needs to done in JIRA.
Any one has faced such problem.
My Analysis is:
When type ipaddress of server:port number it still redirects it to ".com" url I'm not sure if this statement is clear.
We are also using Load balancer F5 and have proxy setting set to reverse.
Let me know if any help can be provided.
If it's fast on the server, and slow remotely, then there is something wrong with your network, or the client machine.
I'm afraid there's not a lot more we can really tell you on this - you need to do the network analysis to see where it's slow, or look at the users machine to work out what is slow on that.
I'd start with a look at the client machines first - are they of a decent specification, are they using supported versions of browsers, and do they work ok with other sites (internal and external)? If they are running other external sites ok, then you know it's your network. One good test would be to browse around https://jira.atlassian.com and see if that's equally slow. Another one would be to use a tool that can analyse how fast parts of pages load and respond. I usually use Firebug's "net" tab - that can tell you what elements are slow, and if you can identify one thing that loads slowly where everything else is fast, that could tell you something.
If you want to investigate the network, then that's a whole set of tests and you have lots to narrow down. On the two points you mention:
I don't know what you're redirecting here. Do you mean that when you use http:ip-address then JIRA takes you to http://your-jira-server/browse/jira-stuff as you navigate? If so, then that is expected behaviour - JIRA uses the base url you have set for everything, so it's going to end up taking you off the ip address and on to the url link almost immediately.
However, that does give you one test of the network - try setting the base url to server:port and testing the speed. If it solves the speed problem, you know that your DNS is broken
On the load balancer - this should be fine, but poorly configured load balancers can cause your networks to crawl. I don't know how to test them beyond checking that trace-routes and pings respond ok.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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