Long time to start Java Web Client (Analyzer 6.2.1)??

Does anyone know why Analyzer(6.2.1) takes a long time to start Java Web Client. Sometime it's even take more than 5 minutes. I think it is the Java Plug-in starting on the client computer. Any solution?

The key to Analyzer 6.2.1 running correctly is the version of Sun Java Plugin. The ideal version (most optimal) is 1.3.0_02.Secondary to this if Analyzer performs OK once you are logged in then it could be down to the speed of your connection. The applet compiles at runtime (unlike Analyzer 5 which was a one time download). The delay in getting to the login screen could be this download.Hope this helps.Paul ArmitageAnalitica Ltd.www.analitica.co.uk

Similar Messages

How can i make my website the default so i can start Java web client?

I have tried he fix on the top of the page for terminal to fix problem but it creates a second website and doesn't work anyway. Does anybody know how to fix this so i can use the java web client. At the moment i keep getting page not found

Try disabling any other websites you've created on the same IP that are on port 80.
~D

NW2004s takes a long time to start up

I am trying to find out why out NW2004s takes a long time to start up.
We have installed NW2004s SP8 JAVA only to use it as Enterprise Portal with Oracle 10g on SUN SPARC 64. While the shutdown of J2EE is pretty fast, the startup take over an hour and half.
/usr/sap/<SID>/JC##/work/dev_server0 file shows:
Thu Aug 10 15:31:48 2006
4017.515: [GC 4017.515: [ParNew: 104368K->17613K(131328K), 0.0423530
secs] 797893K->711138K(1004800K), 0.0428819 secs]
Thu Aug 10 15:31:50 2006
4019.309: [GC 4019.310: [ParNew: 105165K->17610K(131328K), 0.0762693
secs] 798690K->711134K(1004800K), 0.0767036 secs]
Thu Aug 10 15:34:35 2006
4184.118: [GC 4184.119: [ParNew: 105162K->22685K(131328K), 0.0762199
secs] 798686K->716210K(1004800K), 0.0766811 secs]
and /usr/sap/<SID>/JC##/work/std_server0.out file show entries like:
2051.407: [GC 2051.408: [ParNew: 112475K->25810K(131328K), 0.1614717
secs] 678386K->591721K(1004800K), 0.1619460 secs]
2060.554: [GC 2060.555: [ParNew: 113362K->26687K(131328K), 0.1458862
secs] 679273K->592599K(1004800K), 0.1463431 secs]
2068.742: [GC 2068.742: [ParNew: 114239K->27592K(131328K), 0.1464110
secs] 680151K->593504K(1004800K), 0.1470097 secs]
2077.575: [GC 2077.576: [ParNew: 115144K->28470K(131328K), 0.1545706
secs] 681056K->594382K(1004800K), 0.1550365 secs]
2086.411: [GC 2086.411: [ParNew: 116022K->29505K(131328K), 0.1559618
secs] 681934K->595417K(1004800K), 0.1564804 secs]
2094.803: [GC 2094.803: [ParNew: 117057K->30419K(131328K), 0.1531343
secs] 682969K->596331K(1004800K), 0.1536090 secs]
2103.255: [GC 2103.255: [ParNew: 117971K->31345K(131328K), 0.1602581
secs] 683883K->597257K(1004800K), 0.1620506 secs]
2112.423: [GC 2112.424: [ParNew: 118897K->32236K(131328K), 0.1715456
secs] 684809K->598147K(1004800K), 0.1721748 secs]
2123.276: [GC 2123.276: [ParNew: 119788K->33014K(131328K), 0.1640996
secs] 685699K->598926K(1004800K), 0.1645846 secs]
2132.172: [GC 2132.172: [ParNew: 120566K->33980K(131328K), 0.1673372
secs] 686478K->599891K(1004800K), 0.1678214 secs]
2141.072: [GC 2141.072: [ParNew: 121532K->34784K(131328K), 0.1810283
secs] 687443K->600695K(1004800K), 0.1814991 secs]
2149.693: [GC 2149.694: [ParNew: 122336K->35368K(131328K), 0.1670516
secs] 688247K->601280K(1004800K), 0.1675269 secs]
2158.486: [GC 2158.486: [ParNew: 122920K->36435K(131328K), 0.1756513
secs] 688832K->602347K(1004800K), 0.1761320 secs]
2167.314: [GC 2167.315: [ParNew: 123987K->37497K(131328K), 0.1852015
secs] 689899K->603409K(1004800K), 0.1857250 secs]
2176.397: [GC 2176.398: [ParNew: 125049K->38251K(131328K), 0.1741406
secs] 690961K->604163K(1004800K), 0.1746117 secs]
2185.352: [GC 2185.352: [ParNew: 125803K->39375K(131328K), 0.1920462
secs] 691715K->605287K(1004800K), 0.1925810 secs]
2194.150: [GC 2194.151: [ParNew: 126927K->40253K(131328K), 0.1923566
secs] 692839K->606165K(1004800K), 0.1928781 secs]
2202.884: [GC 2202.884: [ParNew: 127805K->38024K(131328K), 0.2031970
secs] 693717K->607088K(1004800K), 0.2036677 secs]
2211.384: [GC 2211.385: [ParNew: 125576K->38851K(131328K), 0.1844842
secs] 694640K->607915K(1004800K), 0.1849062 secs]
2219.963: [GC 2219.964: [ParNew: 126403K->39869K(131328K), 0.1842210
secs] 695467K->608932K(1004800K), 0.1846878 secs]
2228.866: [GC 2228.867: [ParNew: 127421K->39719K(131328K), 0.1920358
secs] 696484K->609702K(1004800K), 0.1925630 secs]
2238.453: [GC 2238.453: [ParNew: 127271K->40643K(131328K), 0.1889567
secs] 697254K->610627K(1004800K), 0.1894261 secs]
2247.056: [GC 2247.056: [ParNew: 128195K->40718K(131328K), 0.1947238
secs] 698179K->611585K(1004800K), 0.1951833 secs]
2255.409: [GC 2255.410: [ParNew: 128270K->40804K(131328K), 0.1939193
secs] 699137K->612886K(1004800K), 0.1943765 secs]
2264.305: [GC 2264.306: [ParNew: 128356K->39943K(131328K), 0.1884611
secs] 700438K->613753K(1004800K), 0.1889279 secs]
2273.187: [GC 2273.188: [ParNew: 127495K->39907K(131328K), 0.1996605
secs] 701305K->614598K(1004800K), 0.2001354 secs]
2281.869: [GC 2281.870: [ParNew: 127459K->39951K(131328K), 0.1870669
secs] 702150K->615514K(1004800K), 0.1875029 secs]
2290.306: [GC 2290.307: [ParNew: 127503K->39975K(131328K), 0.1803927
secs] 703066K->616409K(1004800K), 0.1809368 secs]
2300.101: [GC 2300.101: [ParNew: 127527K->39897K(131328K), 0.1830319
secs] 703961K->617187K(1004800K), 0.1835056 secs]
2310.130: [GC 2310.130: [ParNew: 127449K->39869K(131328K), 0.1858475
secs] 704739K->618039K(1004800K), 0.1862819 secs]
Does anyone know what these entries are and some possible options to speed up the startup process? Thanks. I have already gone through the notes for Virtual memory and heap settings for SUN systems. Has anyone had any similar experience?
Thanks!

What SP are you on? We had a similar issue w/SP6 but it was resoloved with SP7.
Michael

App-V 5 Full Infrastructure Apps take long time to stream to the client

Hi was wondering if anyone has the same issue as i am or knows a fix for this, below is my problem and the troubleshooting i have done.
Overview of problem
App-V 5 apps delivered via App-V 5 full infrastructure take a long time to stream to the client and this means the user has to wait if they try and run an application before it has streamed to the client. Users sometimes have to
wait 2 or 3 minutes for an application to stream and this is about 40 times slower than basic SMB and HTTP transfer tests show the system is capable of (see performance results below).
App-V 4.6 apps delivered via App-V 4.6 full infrastructure and HTTP streaming are fine.
Overview of environment
App-V 5.0 SP1 Full Infrastructure.
App-V servers are running Server 2012 on Hyper-V 3 or ESX 5.1 with 2 x vCPU and 4GB RAM.
SQL servers are a SQL 2012 cluster.
Separate servers for SQL, management, publishing, content and reporting.
Management, Publishing and Content servers have two servers per role and NLB to provide load balancing. So 7 servers (2 x Man, 2 x Pub, 2 x Content, 1 x Reporting)
Two further sites with 2 x Pub and 2 x Content each. All publishing servers pointed at the load balance address for management.
Content delivered via HTTP
Clients are physical desktops and laptops running Windows 7 SP1 x86 and Windows 8 x86
App-V client is 5.0SP1
Clients are pointed at their nearest publishing server NLB via a script which looks up the client IP address and uses PowerShell to configure the publishing server
Content is streamed from the nearest content server NLB by setting the PackageSourceRoot to the nearest content NLB (via the same PowerShell script above).
App-V apps delivered per-user via AD group. One AD group per application. Approximately 200 App-V apps published so far - will eventually reach 400 as we sequence more. About 9000 users.
Analysis performed so far
Servers not heavily loaded. CPU averages 5%. Lots of RAM free. Very low disk IO. Problem also occurs out-of-hours so we are 99.9% certain that server resources are not a cause.
Streaming performance is the same from all 6 content servers and all 3 NLB addresses (tested by changing the value of PackageSourceRoot). Wireshark used to confirm packages are really streaming from the correct location, enforcing
our belief that the problem isn't at the server end (unless all 6 servers are affected).
Streaming via both HTTP and SMB2.1 is approximately the same (tested by changing the value of PackageSourceRoot between http://xxxx and \\server\AppVContent).
Wireshark used to confirm we really are using the protocol we think we are using.
All clients exhibit the same behaviour. Issue reported by many users. 5 test PCs chosen at random at all 3 sites confirmed to have the slow streaming problem.
Slow streaming from both Hyper-V and VMware ESX servers.
Client not heavily loaded.
Affects all App-V apps although it obviously affects the larger ones more.
All App-V apps have a Feature Block 1 setup.
If we copy the ".appv" file from the server to the client via either HTTP or SMB then it's reasonably quick (up to 480Mb/s). So we don't believe the network or servers are at fault. For example:
We can copy a 149MB .appv file via SMB from the content server to the client in 5 seconds.
We copy HTTP download the .appv file from the content server using IE on the client in 5 seconds.
But if you ask the App-V 5 client to fully download the sequence then it takes 2 - 3 minutes.
The App-V 4.6 client takes about 8 - 10 seconds to fully download a similar sized application.
App-V 5 publishing works fine - when a new user logs on they get their list of application straight away, it's just the streaming which is slow.
Once the App-V app has streamed locally it runs fine and with a decent performance.
Looking at a Wireshark trace of the streaming you can see that the slow performance is due to the transfer stopping and starting a lot. You only notice this when you zoom into the performance graph a fair bit.
Each time the HTTP server stops sending traffic, it doesn't start again until the client sends a "TCP Window update". Each "stop" is of a different length, but just taking a few from the middle I get 0.06s, 0.11s,
0.13s wasted etc.
I can see that it's the client stopping the transfer by reducing its advertised TCP Window Size. I'll provide an example:
Server sends 9 x 1514 bytes. Client responds with an ACK and a Window size of 54016 bytes (256x211)
Server sends 11 x 1514 bytes. Client responds with an ACK and a Window size of 37888 bytes (256x148)
Server sends 10 x 1514 bytes. Client responds with an ACK and a Window size of 23296 bytes (256x91)
Server sends 15 x 1514 bytes. Client responds with an ACK and a Window size of 1280 bytes (5 x 256)
Server stops sending (I'm guessing because the client advertised Window size was less than a single packet's worth of bytes)
<0.1 seconds passes>
Client sends a "TCP Window Update" re-advertising a TCP window size of 65536 (256x256).
Server starts transmitting again
So the way I see this is that the App-V 5 client is controlling the transfer speed by utilising TCP Window flow control. The trace was taken at the client end so there's no room for anything on the network to be fiddling with flow
control (and we've confirmed there are no traffic shapers in the loop).
We've also tried streaming directly from the local client by copying some App-V 5 apps down to the client, creating a SMB share on the client and changing PackageSourceRoot to \\localhost\AppVContent (i.e. so we are streaming directly
from the client to the client - to remove the network from the equation) and there is only an improvement of 5 to 10 seconds. So we know it's nothing to do with the network or the servers.
We've tried turning off TCP auto-tuning on the client with:
netsh interface tcp set global autotuninglevel=disabled
and turning off TCP chimney offloading (which is off anyway because the NIC doesn't support it and Netstat -t output shows "InHost" for offload state for all connections) with:
netsh int tcp set global chimney=disabled
and nothing has improved.
So we've now focussed on the extraction of the .appv (ZIP) file on the client.
Using Windows Explorer it takes 75 seconds to extract the ZIP file
Using 7ZIP it takes 9 seconds to extract the ZIP file
Yeah we've always known that the Explorer ZIP engine is terrible. That's why we use 7ZIP or WinRAR on our clients.
So we've started to wonder if the problem with the slow App-V 5 streaming is because the client is downloading the .appv file and extracting it as it goes along in a single thread. If the App-V 5 client is using the same terrible
ZIP engine that Explorer does then that would explain the slow performance. The "download" appears to take a long time because the client is using TCP flow control to slow the transfer since it's extracting the .appv file using a very slow ZIP engine
and it's all in a single thread.

Guys,
Just wanted to give you a brief update basically close this thread as Answered.
We had submitted 4 App-V 5 Bugs to Microsoft and these were reproducible and an explanation was given on work around to them. Microsoft
sent down a App-v developer to have a look at our problems. They said they will try and include the Bug fixes in SP2 which should be out in a few weeks or they will definitely be included in SP3.
In regards to the slow streaming it all came down to the Disk IO.
We found that you could simply enable "Turn off
Windows write-cache buffer flushing on the device", then start streaming the app and then disable "Turn
off Windows write-cache buffer flushing on the device" immediately after
(we don't want to leave it on) and that basically fixed the issue.
But a normal user would not have permissions to do
this, so a code was written to enable and disable this option.
Apology for not going in detail, like my opening thread, its very late.
but if you would like a detailed analysis please message me.
I would like to Thank the Talented Consultant who designed and implemented are App-V infrastructure who found the bugs and created all
the work around and who also emailed the detailed analysis of the problems to Microsoft that got them interested.
Simon Bond from Ultima Business Solutions.
Thank you

Macbook Pro, bought 2012, takes a very long time to start up/restart (5 mins). How do I fix this?

My Macbook Pro, bought 2012, takes a very long time to start up/restart (5 mins) every single time I have shut it down. I try not to shut it down at all now because once or twice, I have got a grey screen, and then nothing. I've held down the power button to shut down again and restart How do I fix all this?

Start up with your built-in Recovery disk by holding down the Command and R keys when starting. Open Disk Utility from there and use it to REPAIR your disk (you've already verified it and it came up with errors).
With any luck, your problems will be solved. While I was there, I would also repair permissions.
Good luck,
Clinton

Installation of Yosemite 10.10.1 has severely slowed the performance of my Mac. Takes a long time to start-up and to load any apps. Any suggestions?

Installation of Yosemite 10.10.1 has severely slowed performance of my Mac Mini. Tales a long time to start, and a very long time to start any apps.

Open Activity Monitor and kill this process - rapportd.
Reinstalling OS X Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Reinstalling OS X Without Erasing the Drive
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility and press the Continue button. After Disk Utility loads select the Macintosh HD entry from the the left side list. Click on the First Aid tab, then click on the Repair Disk button. If Disk Utility reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit Disk Utility and return to the main menu.
Reinstall OS X: Select Reinstall OS X and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
Alternatively, see:
Reinstall OS X Without Erasing the Drive
Choose the version you have installed now:
OS X Yosemite- Reinstall OS X
OS X Mavericks- Reinstall OS X
OS X Mountain Lion- Reinstall OS X
OS X Lion- Reinstall Mac OS X
Note: You will need an active Internet connection. I suggest using Ethernet
if possible because it is three times faster than wireless.

When i turn it on it takes a long time to start up and it freezes in some of the apps so I had to turn it off

Recently when I turn on my mac it takes a long time to start up and at first and in the beginning it appears with a grey screen and at the end it turns blue.
Also it freezes in some of the Apps, so it make me to turn of.
Please be kind enough to guide me to solve these problems.
I thank you in advance for your cooperation and quick response.
Best Regards
Ahmad Emami

What SP are you on? We had a similar issue w/SP6 but it was resoloved with SP7.
Michael

Lenovo Services/Program takes a long time to start after bootup

It seems like Lenovo services take a long time to start after boot up is completely done.
My Bootup time is less than a minute (0:51s), but my lenovo services (Power Manager Gauage, Lenovo Services in the Sidebar, have th ThinkVanatage Button work, and most annoying of all is having access to my network card to change networks) takes about 2 minutes.
Is there a reason why this is taking so long?
I've uninstalled and installed the lastest Lenovo Interface Driver, and a lot of ThinkVantage/Lenovo software and drivers.
Any ideas?

No response?
Anyone else on T400 notice this?

My macbook pro takes a long time to start up, my macbook pro takes a long time to start up

my macbook pro takes a long time to start up, my macbook pro takes a long time to start up

up to 10 mins

MacBook Pro takes a long time to start up or hangs at gray apple logo after minor fall

I upgraded to Mavericks a few days ago. Everything was working fine until yesterday, when my MacBook Pro started taking a really long time to start up or restart.
Before upgrading I had some directory problems which I fixed with DiskWarrior. I then upgraded to Mavericks. There was also a fall that I took, which resulted in the MacBook Pro hitting on one corner and getting a minor dent (It was inside a padded messenger bag when I fell). It worked fine for a whole day, but the next day it started slowing down and getting stuck.
I run DiskWarrior again and there was more directory problems, which were fixed again. When I start the MacBook Pro from an external HD with Mac OS X 10.8, there is no delay in starting up. When I switch to the internal HD, then I get very long delays (5-10min) or hangs at the gray apple logo screen.
DiskUtility did not report any problems, neither did SMART report.
Could it be that the HD got somewhat damaged and gets stuck intermittently? Is it possible to start up OK some times and others to get stuck?
How can I check the HD? Shouldn't the SMART report indicate a problem?
Any help would be greatly appreciated as this is my main work computer!
Chris

I think that my Mac was shutdown when it fell, but I am not 100% sure.
I did perform both SMC and PRAM resets. I will also try to run maintenance scripts. Thanks for the suggestion.
It keeps on taking around 10min to restart now, but it has not frozen yet.
The other very strange thing that happens (and this was the first sign I had when it started acting up) is that Mail.app cannot connect to my IMAP servers (a host provider and Google), even though my Mac connects to the internet. I have the MacBook Pro on the same ethernet network as my home iMac, and I get mail without a problem on the iMac! So something is blocking the mail on the MacBook Pro.
This happened for the first time on Friday and after that I kept having the long delays in startup or freezes I mentioned before.
Could those two be connected?
When I use an external HD as as start up I can get mail fine.

Long Time to Start

Hi.
My Airport Extreme N has a strange behaviour nowadays. If for any reason I need to unplug it from the power outlet, it takes a LONG time to turn on again after repluging.
Since it is on, there is no issue. The only strange thing is the long time to start, when it has no sign of life, no lights, etc.
It has about 1 1/2 years of use, so is it a prenounce it is about to "die"? Is it common?
Thanks
Carlos Inglez

System Preferences=>Spotlight=>Privacy=>click on the plus button and add the BOOTCAMP partition.
Turn OFF MAC, Turn ON MAC and good luck!

Long time to start up ( 10 min )

I have a problem with my Iphoto 11, it takes a really long time to start up. I have tried to format my mac to times, it dident help. Is there anyone who can help me?

System Preferences=>Spotlight=>Privacy=>click on the plus button and add the BOOTCAMP partition.
Turn OFF MAC, Turn ON MAC and good luck!

Takes long time to start mobile 5200

Hello Friends,
I have Nokia 5200 from last one year. These days, I am facing a strange problem, whenever I change a simcard, it takes too long time to start mobile, even more than half an hour. I am frustated by this. Can Anybody please help Me?
Thanks in advance.
Priyanka

hi im michael from phil. just update your phone/using pc usb cable

Takes a long time to start

My Zen Micro 6 GB takes a long time to start up (aprox. -2 minutes). This is not the end of the world but it is annoying. He started doing this 2 days ago, have it for half a year.
I did the cleanup, but before I format the thing I want to be sure that's the only way.
Thanks in advance.

What SP are you on? We had a similar issue w/SP6 but it was resoloved with SP7.
Michael

Movies taking long time to start playing!

I like watching movies in Front Row but I have a problem, Whenever I try watching a full length movie it takes really long time to start playing.
The screen is black for like 2-3min and nothing responds (Pressing ESC, or pressing menu etc...) after that it starts playing normal.
Smaller movies (30 min episodes) load up normally.

you need more ram it will go faster. You should have at least 2 GB to go faster.

Long time to start Java Web Client (Analyzer 6.2.1)??

Similar Messages

Maybe you are looking for