{"id":4973,"date":"2018-07-21T04:24:34","date_gmt":"2018-07-21T11:24:34","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=4973"},"modified":"2025-12-15T06:29:09","modified_gmt":"2025-12-15T14:29:09","slug":"see-java-console","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/see-java-console\/","title":{"rendered":"Q&A: How can I see my Java Console Window when Running as a Service with AlwaysUp?"},"content":{"rendered":"
\"Q<\/div>\n
\n  I am running a Java application as a windows service with AlwaysUp. My JAR starts up fine and seems to be working as expected but I can’t see the Java console window to make sure that there are no errors. How can I see the console window?<\/p>\n

— Alain Thir\u00e9, Thikro<\/p>\n<\/div>\n

Hi Alain. You cannot see your Java console window because it is running in a different Windows “Session”<\/a>.<\/p>\n

Let me explain a bit about Sessions and how they work:<\/p>\n

    \n
  1. \n

    When you log into your PC, Windows creates a Session<\/b> for you. That Session holds your desktop and all the programs you start. All your applications (processes) run inside that Session. Think of the Session as your own private room, holding all your things.<\/b><\/p>\n<\/li>\n

  2. \n

    If your wife logs in, she receives her own Session to hold all the applications she uses. Her Session is completely separate from yours and any program she starts will only be visible to her on her desktop. She gets her own private room.<\/b><\/p>\n<\/li>\n

  3. \n

    When your computer starts, windows creates a special Session for all services. That is, Windows Services have their own room<\/b>. And because this is the first Session created, it is named Session 0<\/b>.<\/p>\n<\/li>\n<\/ol>\n

    \nNow when AlwaysUp starts your application as a Windows Service, it launches it in Session 0 (the home for all Windows Services). And because you are logged into a completely different Session (perhaps Session 1 or Session 2), you will not be able to see your application’s windows on your desktop. Your Java application isn’t in your room.<\/b>\n<\/p>\n

    But fortunately that is not the end of the story. Here are three ways to see what Java is printing to the console.<\/p>\n

    \n
    \n
    \"\"<\/a><\/div>\n<\/div>\n

    Solution #1: Temporarily Switch to Session 0<\/b><\/h2>\n

    Windows gives you the opportunity to view the Session 0 desktop whenever a window is displayed there. Click View the message<\/b> when the Interactive Services Detection alert<\/a> pops up:<\/p>\n

    \"Interactive<\/a><\/div>\n

    AlwaysUp allows you to access Session 0 at any time. Simply select Tools > Switch to Session 0<\/b><\/nobr> from the menu:<\/p>\n

    \"Switch<\/a><\/div>\n

    Or click the “monitor” button on the toolbar to do the same:<\/p>\n

    \"Switch<\/a><\/div>\n

    Now be warned — Session 0 is a strange looking place! You won’t see a task bar, desktop icons or the familiar start button. Here is what the austere Session 0 looks like with Notepad running:<\/p>\n

    \"Session<\/a><\/div>\n

    Click Return now<\/b> to revert to the safety of your normal desktop.<\/p>\n

    \nNote: Switching to Session 0 may not be a viable option on Windows 10 and Windows Server 2016 because you will be unable to use the keyboard and mouse in Session 0<\/a>. Unfortunately there is no workaround and we cannot confirm if\/when Microsoft will address this annoying problem.\n<\/div>\n
    \n
    \n
    \"\"<\/a><\/div>\n<\/div>\n

    Solution #2: Restart your Java application in your Session<\/b><\/h2>\n

    A second way to view the Java window is to have AlwaysUp restart your Java application in your login session. Select Application > Restart in this session<\/b> to have the console appear on your desktop, alongside your other windows:<\/p>\n

    \"Restart<\/a><\/div>\n

    AlwaysUp will automatically return your application to Session 0 after you log off (or you can return it manually).<\/p>\n

    The obvious downside of this approach is that your application has to be stopped. Might a brief interruption cause problems?<\/b> If so, restarting in your session may not be the solution for you.<\/p>\n

    \n
    \n
    \"\"<\/a><\/div>\n<\/div>\n

    Solution #3: Capture the Java console output to a file<\/b><\/h2>\n

    The final solution reframes the problem. Instead of seeing the Java console window, is viewing the text printed in the window good enough?<\/p>\n

    If so, setup AlwaysUp to capture the console output to a text file. Activate the option and specify the full path to the log file on the Extras tab:<\/p>\n

    \"Capture<\/a><\/div>\n

    Simply open the text file to see what Java has printed to the console. Or even better, use a free “tail” utility to follow the file’s additions in real time. Both Powershell’s Get-Content cmdlet<\/a> and Tail for Win32<\/a> have worked well for our team.<\/p>\n

    Best of luck with your Java application\/service!<\/p>\n

    \n
    \n\n\n\n
    More articles about AlwaysUp…<\/nobr><\/span><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n