"Start Jazz Team server" on Win 7 only executes briefly after about 1 month of use
Near the beginning of April, I downloaded and installed RTC 4.0.1 including the Jazz Team Server components on a Windows 7 Enterprise edition laptop (SP 1). I ran and used the software fairly successfully for about a month through the day on Thursday, May 2. As far as I recall, I ran the “Stop the Jazz Team Server” on May 2 when I was done with my work. Based on my schedule, I didn’t try to start the Jazz Team Server again until Thursday, May 9. At that time, the black command window flashed up on the screen very briefly and then went away (normally it stays up, takes 2 - 5 min. to start the JTS, then stays up as long as the JTS is running). I assumed my laptop needed a reboot and went on with other activities.
However, after rebooting my laptop and multiple attempts, the Jazz Team server will not start. Most of the time, the command window just flashes up briefly and goes away. It looks like there is about a paragraph of text in the command window but it comes and goes so quickly I can’t capture it. Occasionally, a second command window is launched after the first one but that too goes away very quickly. (I think the second command window is supposed to come up when you start the JTS and that is normally the window that starts and runs the JTS.)
I can’t explain what caused the break and I don’t know where to start looking. I did try to review various log directories in the IBM program files location. But the latest dates on the folders and log files are from May 2. I can’t seem to find anything (log files or otherwise) near the current date that can be used to diagnose. Any help to get the JTS running again is appreciated.
Accepted answer
You will need to set up tomcat to open both windows in the same window.
To do that see this post: "why is my tomcat console dying just after starting up?"
Once that is done you should be able see the error causing the problem.
I suspect the problem it will be quite obvious once you do that. If not you can post the error message here for further analysis.
Best guess without seeing the error is that your XMX and XMS values are too high for your available memory
If you want to just set those lower and test you can open your server.startup and look for the following lines.
set JAVA_OPTS=%JAVA_OPTS% -Xmx4G
set JAVA_OPTS=%JAVA_OPTS% -Xms4G
Depending on how much memory you have on the laptop you could cut the values to 2G or even less.
If it is just a test server on your laptop there should be no real problems with using a value less than 4 gigs.
I generally use 1.5 - 2 gigs on all my test RTC installs.
Note to set to 1.5 gig you would want to use the Megs rather than Gigs.
i.e.
set JAVA_OPTS=%JAVA_OPTS% -Xmx1536M
set JAVA_OPTS=%JAVA_OPTS% -Xms1536M
To do that see this post: "why is my tomcat console dying just after starting up?"
Once that is done you should be able see the error causing the problem.
I suspect the problem it will be quite obvious once you do that. If not you can post the error message here for further analysis.
Best guess without seeing the error is that your XMX and XMS values are too high for your available memory
If you want to just set those lower and test you can open your server.startup and look for the following lines.
set JAVA_OPTS=%JAVA_OPTS% -Xmx4G
set JAVA_OPTS=%JAVA_OPTS% -Xms4G
Depending on how much memory you have on the laptop you could cut the values to 2G or even less.
If it is just a test server on your laptop there should be no real problems with using a value less than 4 gigs.
I generally use 1.5 - 2 gigs on all my test RTC installs.
Note to set to 1.5 gig you would want to use the Megs rather than Gigs.
i.e.
set JAVA_OPTS=%JAVA_OPTS% -Xmx1536M
set JAVA_OPTS=%JAVA_OPTS% -Xms1536M
Comments
showing 5 of 8
show 3 more comments
3 other answers
Based on the error you need to lower your XMX and XMS settings Note: XMS has to be <= the XMX setting.
Java will use all the memory given by the XMX & XMS setting plus a little bit more native memory (outside the java heap) So that immediately puts you at 4+ gigs of memory just for the JVM.
It is hard to say why it stopped working or really why it was working in the first place.
Six gigs is cutting it a bit close. It could be some other application you installed that put it over the top.
I would also recommend removing the -Xgc:preferredHeapBase=0x100000000 setting all together.
The SDK Information center under Compressed references says this about that setting:
-Xgc:preferredHeapBase= address , where address is the base memory address for the heap. In the following example, the heap is located at the 4GB mark, leaving the lowest 4GB of address space for use by other processes.
Java will use all the memory given by the XMX & XMS setting plus a little bit more native memory (outside the java heap) So that immediately puts you at 4+ gigs of memory just for the JVM.
It is hard to say why it stopped working or really why it was working in the first place.
Six gigs is cutting it a bit close. It could be some other application you installed that put it over the top.
I would also recommend removing the -Xgc:preferredHeapBase=0x100000000 setting all together.
The SDK Information center under Compressed references says this about that setting:
-Xgc:preferredHeapBase= address , where address is the base memory address for the heap. In the following example, the heap is located at the 4GB mark, leaving the lowest 4GB of address space for use by other processes.
-Xgc:preferredHeapBase=0x100000000
If I'm understanding correctly this means you need at least 8 gigs of memory to use that setting.
Comments
You've probably already thought of this, but also make sure the command window where you're executing server.startup is being run as an Administrator. Right-click the Command window program and "Run as administrator".
Comments
1 vote
Michael,
I assume you run on Tomcat? If the window starts and closes again that quick, this typically has something to do with Java not starting. This can be related to too few memory which is unlikely because it started in the past.
You can try to copy the server.startup.bat and remove the "call" statements at the end of that script, I believe than the window should not close immediately. There was a tip in this forum, but I can't find it anymore, so I am not 100% sure about removing the call 8-( but I think this does the trick.
I assume you run on Tomcat? If the window starts and closes again that quick, this typically has something to do with Java not starting. This can be related to too few memory which is unlikely because it started in the past.
You can try to copy the server.startup.bat and remove the "call" statements at the end of that script, I believe than the window should not close immediately. There was a tip in this forum, but I can't find it anymore, so I am not 100% sure about removing the call 8-( but I think this does the trick.
Comments
