Tomcat server not starting
![]()
Hi,
I've recently installed jazz team server with the aim of using RTC. When I select to start the server, a dos window opens for a few seconds and then disappears. Nothing else happens. I think that Windows is somehow stopping the tomcat server from running or connecting to any of the ports. Has anyone seen this before or have any ideas about resolving this? Thanks in advance |
6 answers
![]()
Memory. Running Windows 2008 R2 VM on ESXi, setup with 2GB of memory and same symptoms. Upted the memory to 8GB and all is right in the world again. Thank you for this post. Good work whomever debugged catalina.bat to figure this out.
|
![]()
Ralph Schoon (63.3k●3●36●46)
| answered Jun 20 '12, 4:30 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Richard,
can you open a console as Administrator and CD to the JazzTeamServer/server folder and run the server.startup.bat from there? Does it work then? Is it Windows 7? from my experience: - don't install anything into Program Files First thing I make sure is to install Installation manager into C:/IBM/InstallationManager. I use the C:/IBM also for shared resources. I install CLM/RTC into something like C:/MyRTCFolder The issue with Program files is, it is virtualized and it prevents from creating files and folders if you don't run as administrator. Even if you are logged in with administrative permissions that does not give you all the permissions on win7. You have to explicitely run from a shell you run as Admin or start the app as admin. Comments Hi Ralph, Thanks for responding. ![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Richard, Hi Ralph, ![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Richard, Ralph, ![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Richard,
showing 5 of 6
show 1 more comments
|
![]()
What really helped me when I had this problem was to add echo statements to the .bat files to see how far it's getting. In my situation, it got all the way to the end of the catalina.bat file, and I printed out the final run commands on the screen. When I called that same command manually in a dos window, I was able to see what error was being returned since it didn't close after a split second. Perhaps that approach would help you as well.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.