Please Wait Screen

I'd like to impose a 'please wait' screen between 2 JSP pages. I have a jsp page that prompts the end-user for reporting parameters, such as begin-date & end-date(and others). The user clicks a submit button which links to another jsp page that actually runs the report. The report page calls a bean that calls some Oracle packages, which in turn formats the results in an HTML table. Depending on the report parameters, it can take several minutes to generate the report (millions of rows possible). I want to have some kind of intermediate page with a please wait message, so the user doesn't get impatient and start clicking around, thinking that nothings happening. I have teenage daughters, I know the impatience routine all too well.
I thought about using a forward declarative, and an include, but based on the doc I've read, it doesn't look like they would work. Any ideas where I could go with this.
Should I have the destination page try to display the please wait screen, or should the caller display the screen and wait for the destination to catch up?
I'm still fairly new to JSP, but not new to programming (20+ years). Any help would be appreciated.

Try using a wait page by putting this code at the top level of your page
if ( session.getValue( "waitPage" ) == null ) {
     session.putValue( "waitPage", Boolean.TRUE );
     // I have the WAIT_PAGE constant defined in an external file...it's just
     // the html string that builds the "loading...please wait" message
     out.println(WAIT_PAGE);
     out.close();
}else {
     session.removeValue( "waitPage" );
     //     End of logic for displaying the wait message
     //     build your page in here

Similar Messages

  • Boot up of Windows Server 2012 Essentials seems slow (extended Please Wait screen) and there are errors in Health Report

    Dear Sir or Madam,
    I have been experimenting with the evaluation version of WS2012e trying to get the installation and subsequent build into an optimal set up, and once I have everything I want it to do mapped out, I'll set it up with the full version with using the key that
    I bought.
    However, I've noticed that the server seems to experience a delay during cold boot - it sits with a Please Wait screen for about 60-90 seconds before it presents the screen with an option to Log on.  I have also discovered from running Health
    Report, that there are some entries in the event logs which appear to coincide with start up times, and which seem to be interconnected to each other in the issues they are describing, and I have copied an example of one of those health reports below. 
    I assume that everything sorts itself out in due course, because the events say the process will be re-attempted and these errors don't repeat again after the system has booted up.  I also have the server set to suspend when not in use with the Lights
    Out add in, so it shouldn't need to cold boot often - but I wondered if there's a way to correct these errors so that they don't hold up the boot up process?  I'm also concerned that these errors will cause me later problems with storage pools and
    the like at a later date - the disk replication one seems particularly worrying.  Alternatively, are these errors just a normal part of the start up process - the timing of when different processes start relative to each other - and can be safely ignored?
    In trying to understand what the events describe, I thought that WE2012e acted as its own Domain Controller, and yet it seems from the event log entries that it is waiting for another server to respond to AD / DC requests (but there isn't another server
    on my home network).  The other thing I remember from when I first tried out WS2012e, is that it took control of DHCP or DNS from the router, and I found that frustrating when waking up my laptop and it wouldn't connect to the internet until the server
    had fully booted up and re-asserted its network settings.  Is this another symptom of the same problem?  I remember seeing a posting at the SBS Diva's site about how to update the server so that it gave connected PCs a backup option for connecting
    to the internet when the server wasn't available, and was going to try to find that again to see if that helped.
    By way of background - there isn't another server in my home network.  This is an attempt to do a clean install onto the same hardware that I ran the initial trial of WS2012e, now that the trial has expired, so I'm not trying to migrate from an existing
    server.  I moved all the data on the trial server off onto an external disk, with the intention of importing it back once I had the Storage Pools set up the way I wanted on the new build, and since I didn't want to keep anything else about the server
    trial.  Am I correct in thinking that I don't need to go down the Migration route during installation, and can go through a Clean install in this circumstance? 
    I'm running on an Asus P8-H77-i motherboard, with an i5-3470s CPU and 16MB RAM, and I have WS2012e installed on 256Mb SSD formatted under GPT with uEFI boot - the latter being the main reason for the reinstall, instead of just giving the Evaluation
    version the new key on the original MBR set up.  I've also enabled Intel Rapid Storage and Rapid Start - and successfully set aside the hibernate partition on the SSD - but discovered that this is about forcing a hibernate after suspend, allowing
    the system to power down until its needed again, and then resuming from hibernate on the SSD rather than cold boot each time.  That seems to work, but doesn't improve the cold boot times at all, which was what I was hoping for - ideally the way my
    laptop will boot from cold in a few seconds into Windows 8. 
    Yours faithfully,
    Avon
    ======
    Health Report extract.
    Critical Errors in Event Logs in Last 24 Hours
     DFSR
    Event ID: 3221226674
    The DFS Replication service failed to contact domain controller  to access
    configuration information. Replication is stopped. The service will try again
    during the next configuration polling cycle, which will occur in 60 minutes.
    This event can be caused by TCP/IP connectivity, firewall, Active Directory
    Domain Services, or DNS issues.
    Additional Information:
    Error: 160 (One or more arguments are not correct.)
    Last occurrence: 26 May 2014 18:51:28
    Total occurrence(s): 2
     DNS
    Event ID: 2147487661
    The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS
    data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet
    Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.
    Last occurrence: 26 May 2014 18:51:15
    Total occurrence(s): 2
     ADWS
    Event ID: 3221226674
    This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
    Last occurrence: 26 May 2014 18:51:08
    Total occurrence(s): 2
     NTDS General
    Event ID: 2147486534
    The security of this directory server can be significantly enhanced by configuring the server to reject SASL (Negotiate,
    Kerberos, NTLM, or Digest) LDAP binds that do not request signing (integrity verification) and LDAP simple binds that
    are performed on a cleartext (non-SSL/TLS-encrypted) connection.  Even if no clients are using such binds,
    configuring the server to reject them will improve the security of this server.
    Some clients may currently be relying on unsigned SASL binds or LDAP simple binds over a non-SSL/TLS connection,
    and will stop working if this configuration change is made.  To assist in identifying these clients, if such binds occur this
    directory server will log a summary event once every 24 hours indicating how many such binds
    occurred.  You are encouraged to configure those clients to not use such binds.  Once no such events are observed
    for an extended period, it is recommended that you configure the server to reject such binds.
    For more details and information on how to make this configuration change to the server, please see http://go.microsoft.com/fwlink/?LinkID=87923.
    You can enable additional logging to log an event each time a client makes such a bind, including
    information on which client made the bind.  To do so, please raise the setting for the "LDAP Interface Events" event logging category
    to level 2 or higher.
    Last occurrence: 26 May 2014 18:51:00
    Total occurrence(s): 2
    =======

    Hi KerguelanAvon,
    Based on your description, it seems to be hard to narrow down the cause of this issue. Please refer to following operations and monitor the result. It may help us to go further, and then solve this issue.
    1. Please refer to the following article and troubleshoot slow boot.
    New Slow Logon, Slow Boot Troubleshooting Content
    2. On your server 2012 essentials, please start a BPA scan and fix all that it can find, then monitor the result.
    Regarding to those critical Errors in Health Report, please perform
    Dcdiag on the server. Meanwhile, please refer to the following article and troubleshoot network connectivity, firewall setting and AD DS issue.
    DFSR Event 1202 (DFS Replication)
    Hope this helps.
    Best regards,
    Justin Gu
    Hi Justin,
    I'm reading through the links you referred me to but it's taking a while.  In the meantime I tried running BPA as you suggested.  I'm sure when I ran it before, it didn't say much beyond 81 checks completed, and I couldn't find a way to get any
    more detail.
    Now it says
    Problem:
    The DNS client is not configured to point only to the internal IP address of the server.
    Impact:
    If the DNS client is not configured to point only to the internal IP address of the server, DNS name resolution can fail.
    Resolution:
    To resolve this problem:
    1. From the client computer, open the Properties page for the network connection.
    2. Make sure that DNS is configured to point only to the internal IP address of the server.
    Except that it is.
    Connection-specific DNS Suffix:
    Description: Broadcom 802.11n Network Adapter
    Physical Address: ‎00-1B-B1-28-AE-63
    DHCP Enabled: Yes
    IPv4 Address: 192.168.1.133
    IPv4 Subnet Mask: 255.255.255.0
    Lease Obtained: 03 June 2014 21:56:49
    Lease Expires: 05 June 2014 20:24:20
    IPv4 Default Gateway: 192.168.1.1
    IPv4 DHCP Server: 192.168.1.1
    IPv4 DNS Server: 192.168.1.49
    IPv4 WINS Server:
    NetBIOS over Tcpip Enabled: Yes
    Link-local IPv6 Address: fe80::80ef:48d5:9fde:f10e%14
    IPv6 Default Gateway:
    IPv6 DNS Server:
    I'll try rebooting from the current windows 7 build over to windows 8 on my dual boot laptop, to see if that makes any difference, since it is the only other client PC connected to the server at the moment.
    Thanks, Avon.

  • Envy 360 freezes on please wait screen

    Computer freezes on please wait screen and won't load. Yesterday I installed a mouse but it was a USB 2.0 not 3.0 and then after I shut it down it won't won't after the wait screen.Please help!

    Won't work*

  • Connecting to device...please wait screen freezes

    I am tring to download pictures to Photoshop Element 8 from my camera, I have tried 2 different cameras, but the connecting to device...please wait screen seems to freeze so I can no longer import pictures. I have the Windows 7 operating system. What are some solutions I can try.

    Have you tried using a card reader?

  • T440s stuck in "Please wait" screen

    It happens a few times since last week.
    When I started my laptop, it seems to stuck in "Please wait" screen before Windows 8 logon screen appears.
    Any suggestion how to fix it?

    If you are stuck in "Please Wait" screen, to resolve the issue follow below method
    Boot the system into Safe Mode, to do so follow below steps:
    1. While at the "Please Wait" screen, press ALT+CTRL+DEL
    2. Click the power icon displayed at the bottom right
    3. Hold down the SHIFT key and select Restart. This will take you to the Windows Startup Settings screen
    4. Select Troubleshoot
    5. Click Advanced options and choose Startup Settings
    6. Click Restart
    7. From the Startup Settings screen, select the number corresponding to Enable Safe Mode
    8. Choose the user account that has administrative rights
    If you are able to enter to safe mode, perform clean boot and check error still persists
    http://support2.microsoft.com/kb/929135
    And if you are not able to login to safe mode, perform "Repair system files using SFC scan."
    This is a command-line tool that scans for corrupted files crucial to the system, and automatically initiates a repairing process.
    1. Run this command using the steps mentioned below:
    2. Reach Advanced options from the Windows Startup Settings described formerly
    3. Choose Command Prompt
    4. In the command prompt screen, type the following command: Sfc /scannow
    5. Press Enter
    6. Execute the on-screen instructions to complete the scan
    Note: This method may require you to insert the Windows installation DVD to extract missing/damaged system files from the media

  • Re: Please wait screen

    A previous message (Please wait screen) on this forum asked about delays on boot times with Vista on a u300 and mentioned tempro. That thread is closed so I start a new one; see http://eu.computers.toshiba-europe.com/innovation/generic/TEMPRO_RELEASE/ for latest version where it says "if you are using TEMPRO version 1.0 or 1.1 then you may see a quicker boot up time if you upgrade to this version".

        Hummm, well stacyadell, let's figure out what's going on. Is you application on the memory card or is it on the phone memory? Try moving it inbetween each of them and see if you still get the error. Let's also try running on wi-fi and see if that works at all.
    I have seen that you also might need to install My Verizon and sign in to make sure that NFL mobile is linked to your phone number and thus your Verizon Wireless account. Please make sure that you can sign on to your account on My Verizon and then retest.
    Thanks!
    MichelleG_VZW
    Please follow us on Twitter @vzwsupport

  • Please Wait Screen Delay

    Hello, I have a Toshiba Satellite running on windows 8.1
    Whenever I get logged out or anything that requires me to log in to my account I either get a "Please Wait" screen that lasts about 5 minutes until it lets me log in or a blank screen that only goes away if I restart the computer using the power
    button. I've tried many different solutions to fix this but none work. It might be a manufacturing defect but it has been affecting me computer sense the beginning so I don't think I did it. If you can help me please do.
    NOTE: when I get to the "Please Wait" or blank screen it will periodically go back to the lock screen but if I click on it, it will just go back to the "Please Wait" or blank screen.

    1. Is thsi from the very first moment or after you did something?
    2. Inspect Event logs for errors and warnings. Share your findings here.
    3. Try to create new user. If the new user account behaves normály, then the original profile has been corrupted and needs repain. Search repair user profile.
    4. This may be specific for Toshiba Satellite and that is why you should ask in Toshiba support/forum.
    Regards
    Milos

  • Please Wait Screen when I touch any key

    I believe that I am upgraded to windows 8.1, but I'm not entirely sure about that. I do have automatic updates on, so that is why I believe that I do. I have been having trouble getting an internet connection over the last week on boot up. A few days ago I used a reset command at the command prompt, restarted my computer and the connection was fine.
    Yesterday I decided that I would do something different because I still had no internet connection. I uninstalled my Qualcomm Atheros AR9845 wifi adapter software from the control panel and now that I'm writing this, I probably shouldn't have done that. The computer froze at the "finding a software to update with" window and I had to power off the computer. It booted up with no problems, though I had no chance of getting an internet connection now. Then I went on to uninstall the drivers for the wifi adapter. There were no drivers to be found, obviously, since I had no internet connection. I used another computer and found one for win 8, not realizing at the time that I had 8.1 as I believe, downloaded it, saved it to a flash drive, and then uploaded it to my internet connectionless computer. It said it was fine and I rebooted.
    Ever since I rebooted I have been stuck in a loop. Once it starts booting up it comes to a green screen with a Please Wait sign and it just spins then it goes to the welcome screen. If I click my mouse it goes to the Please Wait screen. If I touch a key on the keyboard it goes to the Please Wait screen. After 30 seconds or so it goes back to the welcome screen. On the welcome screen there is an icon with the monitor and cord with a red x where the internet connection usually shows. I know this means there is no network connection. I don't know if that has any relevance to the problem.
    I used my son's computer and made a flash drive reboot drive to get to the repair/recovery process, only that didn't work because it's not looking for it. This is when I realized I most likely had windows 8.1 because I couldn't make a repair/recovery disk. I had to use a flash drive when using his computer. Apparently that's a windows 8.1 thing. I have looked up everything I know to use as keywords to find a solution to this problem. I have seen a couple of similar issues, but they were old or didn't have quite the same problem. One was about static discharge and to unplug everything from your computer and even unplugging the power cord. Tried that. Didn't work. I am completely unable to get to anything where I can actually get into a screen because it goes to the Please Wait screen. I tried the safe mode from outside of windows trick for HP computers using the ESC key when it boots up. Guess what? The Please Wait screen. Every time I hit any key it just goes to the Please Wait screen. Right now I have a very expensive paper weight. It is completely unusable and I have no idea how to get to the troubleshooting screen since everything I do just takes me right back to the Please Wait screen.
    If anyone has any idea how to fix this, I would be absolutely grateful! I have included all that I know to include at this point.
    Thanks so much!
    Jill

    Hello @jillysue72,
    Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
    I have read your post on how a "Please Wait" error message displays on your desktop computer, and I would be happy to assist you in this matter!
    Since you are attempting to recover your computer, I recommend following the steps in this document on Troubleshooting HP System Recovery Problems (Windows 8), as well as Obtaining HP Recovery Discs or an HP USB Recovery Drive. This should help successfully recover the operating system, as well as acquiring the necessary recovery media for your system.
    If the issue persists, please call our technical support at 800-474-6836. If you live outside the US/Canada Region, please click the link below to get the support number for your region.
    http://www8.hp.com/us/en/contact-hp/ww-phone-assist.html
    I hope this helps!
    Regards
    MechPilot
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

  • L305d-s593​4 Won't get past "please wait screen"

    My l305d-s5934 started ranodmly shutting off recently.  It is only a year and a half old so I figured it was getting too hot.  About a week and a half ago it started getting stuck at the Windows "please wait" screen.  I have  been forced to power off with the power button.  I tried startup repair and system restore.  Now the only way I can boot completely is in safe mode.  It won't get past that screen.  When I try to restore now, it shuts off halfway through.  Is this just the lifespan of this particular machine, or is there something I can do?  Thanks for any help.

    sounds like an OS issue to me..but have youu tried disabling all startup items, disconnect all usb devices and check it again. If there will be no changes then consider running an OS reinstall.
    =========================================================
    the only easy day was yesterday.....
    =========================================================

  • Windows server 2012 stuck at 'Please Wait' screen

    I did read through some of the post on a similar scenario with 2008 R2 or earlier versions stuck on "Please Wait" screen while logging in.
    There were some suggestions about disabling NLA service or applying the hotfix- KB Article 983551. I'm not sure if this is applicable for Windows 2012 server.
    These are virtual machines joined to the domain. After a reboot I'm able to login to the server.
    I'm now starting to see this issue occuring on multiple servers on the domain. Can someone advice on this please?

    Do you have all the latest patches applied to the system?
    Is there any consistency in your environment as to which servers are exhibiting this behavior?  For example, servers with a specific MB, BIOS level, firmware, etc.
    All systems listed on www.windowsservercatalog.com?
    Latest BIOS, Firmware, Drivers on all systems?
    This is not typical.  It is something in your environment, so you need to look for what is different about your environment.
    . : | : . : | : . tim

  • Windows 8.1 stuck at "Please wait" screen

    Source4ward wrote:
    I realize that I could have done a backup and wiped the drive. I did not want to do that since the client had spent a lot of time training his voice recognition software.
    Well, "reality" and the "wants of a residential customer" are often mutually exclusive.  You can "want" there to be a magical, miracle fix, but there simply is not.  Your time is worth money, and the more days you sit around and wait for this problem to suddenly resolve itself, the less $ you make per hour.  

    I have a client who powered off his computer during Windows updates. After that, Windows updates would take upward of 24 hours to run, and would not even install successfully. The updates would roll back and he would have to start over. I tried doing a refresh, but it did no good. I also booted to the command prompt and ran the following commands:ren system system.001ren software software.001Now I cannot seem to get it to boot to Windows. It is stuck at the screen saying "Please wait" and will not go any further. Any ideas how to salvage this Windows install without doing a complete restore? I want to avoid the complete restore because this client is an elderly gentleman who had a lot of custom settings in Windows and also was using Dragon Naturally Speaking which he had spent time to get working right for his voice.
    This topic first appeared in the Spiceworks Community

  • Windows 7 Professional Hangs at Please Wait

    Hey, so I'm working on an HP Compaq 6000 Pro.  The other week it stopped allowing logins.  I can get into safe mode, but beyond that it's
    hit and miss.  I have gone over a few articles, and I've tried a few things with temporary results.  When it first happened, I ran Start Up Repair and it proceeded to the login screen.  The next day it stuck at Please Wait again, so I ran sfc.exe,
    got no errors, and then did a clean boot.  That time it allowed me to login twice I believe.  The next day it hung at Please Wait again, so I disabled NLA, Windows Error Reporting, and Network List Services, and, again, it allowed me to login.  It
    stopped again the next day, and everything has been a hit and miss trial.  Occasionally it will allow me to login, but not even close to consistently.  I found multiple hotfixes, but everyone I try either says the update is not applicable, or it
    will start to install, and then simply say the update was not installed.  This machine is the only one experiencing the issue on the domain.  In addition, I had
    read a few times that a possible cause was WMI and one its repositories building up too much, or something along those lines.  I just checked C:\Windows\System32\WBEM\Repository , which I read was the actual folder, and the size is only 20 Mb.  I
    believe this rules out another cause, and my only idea.  The last thing I tried was disabling IPv6, which I heard could fix the issue, and got nothing.  I
    want to avoid just wiping and reloading Windows, since all of the user's data is on the local machine.  Any advice?

    Hi,
    Please understand that there are lots of factors can lead to logon hang. To make the issue clear, please paste exact error messages from Event Viewer directly. Then I will look into it and try to find the culprit.
    What information appears in event logs (Event Viewer)?
    http://windows.microsoft.com/en-US/windows7/What-information-appears-in-event-logs-Event-Viewer
    Please use Windows Live SkyDrive (http://www.skydrive.live.com/) to upload the Error logs to a public folder and share the URLs with us.
    Based on the current situation, I would also suggest you try the following:
    1. Check for the updated drivers especially the network adapter drivers on your computer. if the drivers are not updated then, try updating the drivers.
    2. Perform a system restore using the Windows installation disc.
    Refer the link provided below to run the system restore using the system recovery options.
    http://windows.microsoft.com/en-US/windows7/What-are-the-system-recovery-options-in-Windows-7
    In addition, when the issue occurs, you can press Ctrl+Shift+Esc combine key to launch Task Manager, on the Processes tab, find the process which is taking the most usage of the CPU.
    Please also refer to the links below to check the issue:
    Windows 7 or Windows Server 2008 R2 stops responding at the "Please wait" screen before you are requested to press Ctrl+ALT+DEL
    http://support.microsoft.com/kb/983551
    Windows 7 stuck on "Please Wait.." screen (You can refer to gbps's reply.)
    http://answers.microsoft.com/en-us/windows/forum/windows_7-system/windows-7-stuck-on-please-wait-screen/927cac79-debc-43ec-9d36-9f5b0a19a1f9
    Hope it helps.
    Regards,
    Blair Deng
    Blair Deng
    TechNet Community Support

  • Please wait please wait please wait

    Hi
    I have new Toshiba lap top Model Satellite U400 with 4 GB  (ram) (win. Vista home premium 32 bit O.S)
    When i  turn it on the " please wait "screen  comes up for about 2-3 minutes before showing the login screen.
    Do you have any way to solve this problem or idea what could be causing it to say " please wait " for so long ?
    Regardes
    saad

    Are you putting ur computer to sleep? If u do, it can do that. How about when restarting the computer normally from windows?
    Fixing Computers no Jutsu! (Ninja Help and Support Technique )

  • Stuck in 'Please Wait' after few automatic Updates

    As usual there were some pending updates in the LOG IN Screen of my lappy. So, I selected the "Update and Restart " button. That's it after that BOOM. I have been stuck in "Please  Wait" screen ever since. Any suggestions for a quick recovery will be helpful .    

    You might need to go to a Verizon Wireless corporate store and have them assist you with getting the SIM cards activated and then the phones activated.

  • UWL Startup "Please wait"

    Hi, is there a way to provide a "please wait" image or some kind of status bar at the startup of the UWL rather than seeing a blank screen in the Portal?
    Cheers,
    Ray

    The hard drive mode solution above probably won't work. If the iPod had enough juice to enter drive mode it would probably have enough juice to charge.
    Here's the solution that just worked for me:
    The problem is that the iPod doesn't have enough power to move past the initial boot process, and it can't charge while it's stuck in the process of booting (when you see the black screen with the Apple logo). Hopefully Apple will get their act together and make the next generation iPod charge via USB while it's booting, but I digress.
    When you see the "Please Wait. Very Low Battery." screen, the iPod is in the process of taking as much of a charge as it can before entering the boot process. The trick is to keep resetting the iPod (hold Select and Menu) once it leaves the "Please Wait" screen. Eventually you'll be able to work up just enough juice to move beyond the boot screen.
    Try resetting it 5 times once you see the black/Apple page, then let it run through the whole boot process once and see if it works. If not, just repeat that process. It worked for me after just a few tries.
    Message was edited by: Saul123

Maybe you are looking for