It's all about the answers!

Ask a question

Unable to launch default CLM 6.0


Rajat Singh (59833442) | asked Jun 30 '15, 11:36 p.m.
Hi Team

I have downloaded CLM 6.0 from jazz.net and installed it on Windows 7 (64 bit).
The setup is on defaults to evaluate the new release.
Derby database, tomcat7.

After installing the server, when I run the start jazz team server, the command line windows pops for a second and then dissappears.
Have tried running it using 'Run as Administrator' which gave same results.

I also tried running the startup batch file found in IBM\JazzTeamServer\server\tomcat\bin; this kept the command prompt alive but did not give me the start server seconds:

Please let me know if I am missing anything here.

Regards
Rajat

Comments
Howard Hsiao commented Jul 03 '15, 4:05 a.m. | edited Jul 03 '15, 4:07 a.m.
JAZZ DEVELOPER

Hi Rajat,
Have you checked if port 9443, 9080, 9009 have been in LISTENING state prior to you start the server?
If port 9443, 9080, 9009 are in LISTENING state prior to you start the server, you might want to kill that process that listens to port 9443, 9080, 9009 and then start the server again.

Accepted answer


permanent link
Howard Hsiao (5.4k7) | answered Jul 03 '15, 4:34 a.m.
JAZZ DEVELOPER
edited Jul 03 '15, 10:29 a.m.
Most Probable Cause:
JazzTeamServer is installed under C:\Program Files\IBM\JazzTeamServer and for some reason, it cannot load class under a path with space in it. Hence "Files/IBM/JazzTeamServer/server/conf" appears in the error.
Since that class cannot be loaded, JTS quits.

Test the probable cause:
Reinstall to a directory with no space, such as c:\ibm\JazzTeamServer 

Think beyond the fix:
It is recommended to install CLM in a non-virtual directory: any directory that is outside C:\program files or C:\program files (x86)
Rajat Singh selected this answer as the correct answer

6 other answers



permanent link
Donald Nong (14.3k213) | answered Jul 01 '15, 1:19 a.m.
It's possible that your machine does not have enough memory to support the default 4GB JVM heap size. To verify this, follow the steps below.
1. Open a command prompt (elevated if necessary).
2. Run the command IBM\JazzTeamServer\server\server.startup.bat
3. Observe any errors reported there.

If it's indeed due to the shortage of memory, you can decrease the heap size by modifying the server.startup.bat file, changing the "-Xmx4G" and "-Xms4G" to "-Xmx3G" and "-Xms3G" or even "-Xmx2G" and "-Xms2G" if you are desperate. Do expect slow performance and/or OutOfMemory issues though. Ultimately you should increase the physical memory of the machine.

The server.startup.bat script is the correct way to start up the Jazz server,  not the startup.bat found in Tomcat, as it sets up quite many environment variables and Java options for the Jazz server to run properly.

If you see other errors in the command prompt, please report here.

Comments
Rajat Singh commented Jul 01 '15, 1:35 a.m.

 I see the below response:


D:\Program Files\IBM\JazzTeamServer\server>server.startup.bat
Using CATALINA_BASE:   "D:\Program Files\IBM\JazzTeamServer\server\tomcat"
Using CATALINA_HOME:   "D:\Program Files\IBM\JazzTeamServer\server\tomcat"
Using CATALINA_TMPDIR: "D:\Program Files\IBM\JazzTeamServer\server\tomcat\temp"
Using JRE_HOME:        "D:\Program Files\IBM\JazzTeamServer\server\jre"
Using CLASSPATH:       "D:\Program Files\IBM\JazzTeamServer\server\tomcat\bin\bo
otstrap.jar;D:\Program Files\IBM\JazzTeamServer\server\tomcat\bin\tomcat-juli.ja
r"


Taki Nakajo commented Jul 01 '15, 2:15 a.m.

That is normal. Then you need to have a look at the \server\tomcat\logs\catalina.log and \server\logs\jts.log.


permanent link
Taki Nakajo (1.1k1945) | answered Jun 30 '15, 11:58 p.m.
The error message in the tomcat console must be about failure to connect to the IBM online help. You can ignore this error. 
When you scroll up the console messages, you will see ' server startup xxxx ms', it mean the Jazz Team Server (tomcat) starts up.
Can you test to access https://localhost:9443/jts/setup in a browser?

permanent link
Howard Hsiao (5.4k7) | answered Jul 01 '15, 12:37 a.m.
JAZZ DEVELOPER
To see "INFO: Server startup in xxx ms" message without scrolling up the console, please check the latest Catalina log under <JTS-Home>\server\tomcat\logs.
The Catalina log file names look like catalina.yyyy-mm-dd.log. (yyyy-mm-dd is the date when you start JTS server).

Please also run the following command to see the status of port 9443:
netstat -ano | findstr 9443


Make sure it exists and in LISTENING state.

permanent link
Rajat Singh (59833442) | answered Jul 01 '15, 1:43 a.m.
  Hi All

Thank you for the response.
As starting the server using server.startup batch file is the correct way, I using this method.
When I run this batch file, the reported issue occurs. The command window pops up and vanishes in a second.
Is there any logs that I can share?

I searched under the logs folder in \IBM\JazzTeamServer\server\tomcat\logs and found localhost and catalina txt.
The contents are:

Localhost:
-------------

Jul 01, 2015 9:17:33 AM org.apache.catalina.core.StandardContext listenerStop
SEVERE: Exception sending context destroyed event to listener instance of class com.ibm.team.integration.reporting.common.configs.SG_ServletContextListener
java.lang.NullPointerException
at com.ibm.team.integration.reporting.metamodel.internal.model.ModelContextBuilderExtender.cleanupContext(ModelContextBuilderExtender.java:100)
at com.ibm.team.integration.reporting.common.configs.BaseContextBuilder.cleanupContext(BaseContextBuilder.java:169)
at com.ibm.team.integration.reporting.common.configs.SG_ServletContextListener.contextDestroyed(SG_ServletContextListener.java:31)
at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:5063)
at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5719)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
at org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1591)
at org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1580)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)



Catalina:
-----------

Jul 01, 2015 9:17:23 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-9080"]
Jul 01, 2015 9:17:23 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-9443"]
Jul 01, 2015 9:17:23 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["ajp-bio-9009"]
Jul 01, 2015 9:17:23 AM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
Jul 01, 2015 9:17:33 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-9080"]
Jul 01, 2015 9:17:33 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["ajp-bio-9009"]
Jul 01, 2015 9:17:33 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-9080"]
Jul 01, 2015 9:17:33 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-9443"]
Jul 01, 2015 9:17:33 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-9443"]
Jul 01, 2015 9:17:33 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["ajp-bio-9009"]
------------------------------------------------------------------------------------------

Regards
Rajat

Comments
Taki Nakajo commented Jul 01 '15, 2:28 a.m.

 The output in the catalina log shows the only about stopping the tomcat server.


Taki Nakajo commented Jul 01 '15, 2:30 a.m.

Can you collect fresh logs for us?


1. Reboot the windows machine.
2. Delete all logs under server/tomcat/logs.
3. Start the Jazz Team Server.
4. Collect the new catalina and the new localhost log.


1
Don Yang commented Jul 01 '15, 8:11 a.m.

Donald is right that the root cause could be that you dont have enough JVM memory. By default CLM requires min JVM 4GB memory. If you have less memory, you will see the flash windows only. You can try to start the server process at below way so that more information can be captured in the logs(\server\tomcat\logs) as well as command prompt.
In <rtc install="">\server\tomcat\bin\starup.bat , change "start" to "run" in the following line near the end of the file:
"%EXECUTABLE%" start %CMD_LINE_ARGS% to "%EXECUTABLE%" run %CMD_LINE_ARGS%

Then run server.startup.bat.
From the further details, you may determine whether it is JVM related, or user not having enough rights for some installed directories and so on.


anoop mc commented Jul 02 '15, 2:46 a.m.

 Hi Rajat,


One more tip - you may try running the tomcat using option - Run as an administrator.



permanent link
Rajat Singh (59833442) | answered Jul 03 '15, 2:39 a.m.
  @dnong

 Hi 

The machine has 8 GB of RAM.
I did open the command prompt and tried the suggested steps.
No errors recieved. Response was:
D:\Program Files\IBM\JazzTeamServer\server>server.startup.bat
Using CATALINA_BASE:   "D:\Program Files\IBM\JazzTeamServer\server\tomcat"
Using CATALINA_HOME:   "D:\Program Files\IBM\JazzTeamServer\server\tomcat"
Using CATALINA_TMPDIR: "D:\Program Files\IBM\JazzTeamServer\server\tomcat\temp"
Using JRE_HOME:        "D:\Program Files\IBM\JazzTeamServer\server\jre"
Using CLASSPATH:       "D:\Program Files\IBM\JazzTeamServer\server\tomcat\bin\bo
otstrap.jar;D:\Program Files\IBM\JazzTeamServer\server\tomcat\bin\tomcat-juli.ja
r"

@dyang 

I also changed the startup.bat file from start to run and then ran the server.startup file.
This gave the same result. The command prompt came for a sec and vanished away.

I deleted the localhost and catalina files.
When I run the server.startup batch, no new catalina or localhost file is getting created.

Regards
Rajat


Comments
Taki Nakajo commented Jul 03 '15, 3:52 a.m.

It seems even the tomcat catalina startup won't be started because no catalina.log.

Can you try to open the command prompt as admistrator then run server.startup.bat?

or Can you test/install the CLM 6.0 under D:\IBM instead of D:\Program Files\IBM? (to see if you have too restrict permission under D:\Program Files.)


Rajat Singh commented Jul 03 '15, 4:17 a.m.

 Here is what I got:



Taki Nakajo commented Jul 03 '15, 4:41 a.m. | edited Jul 03 '15, 4:41 a.m.

 Finally, you got the exception what I wanted to see for investigation.


1
Taki Nakajo commented Jul 03 '15, 4:47 a.m.

 Hi Rajat, please see the comment from Howard. Can you test/install under D:\IBM...?


Taki Nakajo commented Jul 03 '15, 4:48 a.m.

Hi Rajat, please see the comment from Howard. Can you test/install under D:\IBM...?


permanent link
Rajat Singh (59833442) | answered Jul 15 '15, 6:45 a.m.
 @hhsiao Yes that solved the issue!!
I reinstalled it in directory d:\ibm\jazzteamserver (no spaces in the path) and it launched perfectly fine!!

Thank you all for the support.

Regards
Rajat

Your answer


Register or to post your answer.