Topic
  • 2 replies
  • Latest Post - ‏2013-10-14T17:32:54Z by MarcNehme
MarcNehme
MarcNehme
3 Posts

Pinned topic UrbanCode Release server startup issue failure

‏2013-10-09T17:16:15Z |

I've installed UrbanCode Release v6 from Xtreme Leverage. The install process, using IBM Install manager, was pretty straight forward. After successful installation, the next step is to run 'server.startup.bat' which starts up the tomcat server for URelease. Upon running this script, after about 1-2 seconds, the process automatically terminates.

The JRE_HOME variable is set in the 'server.startup.bat' and is valid. I left the memory requirements (Xms / Xmx), set in the same script, the default. I made no changes after the installation and according to Infocenter (and the uRelease site) there should be no other post-install steps needed.

Running a 'netstat' shows that the ports in question (8080 & 8443) are not being used and are available, so this should rule out a port conflict.

There are no logs generated in <uReleaseInstallDir>\server\tomcat\logs

Has anyone experienced this? Any ideas?

Updated on 2013-10-09T17:16:26Z at 2013-10-09T17:16:26Z by MarcNehme
  • Zaev
    Zaev
    1 Post

    Re: UrbanCode Release server startup issue failure

    ‏2013-10-11T00:36:19Z  

    Marc

    It looks like you *may* have run into the dodgy path issue:-) Take a look at http://sudhakarf.wordpress.com/2013/10/04/urbancode-release-microsoft-windows-silent-installation-notes-and-woes/ . I had to add a semi-colon to the end of the Windows PATH variable and the startup script worked.

    Sudhakar Frederick
    DevOps Specialist, Rational Emerging Technologies Team
    My Jazz and DevOps Blog
     

     

  • MarcNehme
    MarcNehme
    3 Posts

    Re: UrbanCode Release server startup issue failure

    ‏2013-10-14T17:32:54Z  
    • Zaev
    • ‏2013-10-11T00:36:19Z

    Marc

    It looks like you *may* have run into the dodgy path issue:-) Take a look at http://sudhakarf.wordpress.com/2013/10/04/urbancode-release-microsoft-windows-silent-installation-notes-and-woes/ . I had to add a semi-colon to the end of the Windows PATH variable and the startup script worked.

    Sudhakar Frederick
    DevOps Specialist, Rational Emerging Technologies Team
    My Jazz and DevOps Blog
     

     

    Thanks Freddy, you helped me resolve the issue. All I had to do was update the PATH variable in Windows by removing the final '\' and adding a semi-colon. I did that and Release fired right up. Thanks again!