It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,883
×7,479
×2,352

question asked: Sep 04 '13, 8:29 p.m.
question was seen: 55,907 times
last updated: Sep 05 '13, 5:28 p.m.

Related questions

Unable to Start JTS after CLM 4.0.3 Install

0
Andrew Torres (1●1●1●1) | asked Sep 04 '13, 8:29 p.m.

Hi All, I have been fighting this install for the past week and wanted to see if anyone could help.

1. Installed IBM CLM 4.0.3 using installation manager. The following components are installed:

Jazz Team Server 4.0.3

Trial Keys

Change and Configuration Management

2. I should mention this is on a Windows 2008 server R2 64 bit

3. I try to run the jts service as an administrator which brings up the command screen.

4. I get the following error:

Sep 4, 2013 4:07:07 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performanc
e in production environments was not found on the java.library.path: D:\Program
Files\IBM\JazzTeamServer\server\jre\bin\compressedrefs;D:\Program Files\IBM\Jazz
TeamServer\server\jre\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\
Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\
Windows\Tools;C:\ProgramData\Opsware\custom\local_security_cli;C:\PROGRA~1\DISKE
E~1\DISKEE~1\;;.
Sep 4, 2013 4:07:08 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9080"]
Sep 4, 2013 4:07:08 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9443"]
Sep 4, 2013 4:07:08 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-9009"]
Sep 4, 2013 4:07:08 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1862 ms
Sep 4, 2013 4:07:08 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Sep 4, 2013 4:07:08 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.32
Sep 4, 2013 4:07:08 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive D:\Program Files\IBM\JazzTeamServer\serv
er\tomcat\webapps\admin.war
Sep 4, 2013 4:07:11 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive D:\Program Files\IBM\JazzTeamServer\serv
er\tomcat\webapps\ccm.war
Sep 4, 2013 4:07:20 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive D:\Program Files\IBM\JazzTeamServer\serv
er\tomcat\webapps\clmhelp.war
Sep 4, 2013 4:07:24 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive D:\Program Files\IBM\JazzTeamServer\serv
er\tomcat\webapps\jts.war
Sep 4, 2013 4:07:30 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory D:\Program Files\IBM\JazzTeamServer\se
rver\tomcat\webapps\ROOT
Sep 4, 2013 4:07:30 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-9080"]
Sep 4, 2013 4:07:30 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-9443"]
Sep 4, 2013 4:07:30 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-9009"]
Sep 4, 2013 4:07:30 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 21475 ms
java.net.ConnectException: Connection timed out: connect
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:381)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:243)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:230)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:377)
        at java.net.Socket.connect(Socket.java:539)
        at java.net.Socket.connect(Socket.java:488)
        at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:424)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:538)
        at sun.net.www.http.HttpClient.<init>(HttpClient.java:221)
        at sun.net.www.http.HttpClient.New(HttpClient.java:304)
        at sun.net.www.http.HttpClient.New(HttpClient.java:323)
        at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLC
onnection.java:999)
        at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConne
ction.java:935)
        at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection
.java:853)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
nection.java:1207)
        at java.net.URL.openStream(URL.java:1022)
        at com.ibm.ccl.ut.help.info.entry.NavTree.categorizeTocXML(NavTree.java:
245)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at com.ibm.ccl.ut.help.info.IndexThread.run(IndexThread.java:105)

5. I run a netstat -a -b and find that port 9009 is in use by a windows process svchost.exe. I have tried changing the port in the server.xml file however there seems to be a conflict regardless of which port I use.

Did I miss a step somewhere? Any help would be appreciated.

Thanks,

Andrew

2 answers

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Abraham Sweiss (2.4k●13●31) | answered Sep 05 '13, 8:05 a.m.
I would do the following:

1.  verify that  llocalhost is defined in the  windows hosts file.  It should be mapped to 127.0.0.1
2. verify  which DNS server is configured for that host, and that the host name being used is defined in the DNS server

then

1. check the task manager to make sure there are no java / tomcat processes running
2. Take a netstat before running the server start script and validate that the ports in the server.xml are not in use
3. start RTC.  

IF the connect error persists then

1. redue steps 1 and 2
2. start up a cmmand prompt with admin user
3. cd to the <>RTC_Install_root\servers directory
4. execute the start script from the command prompt

Comments
Andrew Torres commented Sep 05 '13, 2:53 p.m. | edited Sep 05 '13, 5:28 p.m.

Thank you for the reply but unfortuneately I am still having the issue. Any other suggestions. I am not sure if it is actually a port issue. Here is the output of netstat:


Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            WDVWA00A0049:0         LISTENING
  RpcSs
 [svchost.exe]
  TCP    0.0.0.0:445            WDVWA00A0049:0         LISTENING
 Can not obtain ownership information
  TCP    0.0.0.0:1002           WDVWA00A0049:0         LISTENING
 [python.exe]
  TCP    0.0.0.0:1556           WDVWA00A0049:0         LISTENING
 [pbx_exchange.exe]
  TCP    0.0.0.0:3389           WDVWA00A0049:0         LISTENING
  TermService
 [svchost.exe]
  TCP    0.0.0.0:9009           WDVWA00A0049:0         LISTENING
 [java.exe]
  TCP    0.0.0.0:9080           WDVWA00A0049:0         LISTENING
 [java.exe]
  TCP    0.0.0.0:9443           WDVWA00A0049:0         LISTENING
 [java.exe]
  TCP    0.0.0.0:13724          WDVWA00A0049:0         LISTENING
 [vnetd.exe]
  TCP    0.0.0.0:13782          WDVWA00A0049:0         LISTENING
 [bpcd.exe]
  TCP    0.0.0.0:31038          WDVWA00A0049:0         LISTENING
 [DkService.exe]
  TCP    0.0.0.0:47001          WDVWA00A0049:0         LISTENING
 Can not obtain ownership information
  TCP    0.0.0.0:49152          WDVWA00A0049:0         LISTENING
 [wininit.exe]
  TCP    0.0.0.0:49153          WDVWA00A0049:0         LISTENING
  eventlog
 [svchost.exe]
  TCP    0.0.0.0:49154          WDVWA00A0049:0         LISTENING
 [lsass.exe]
  TCP    0.0.0.0:49155          WDVWA00A0049:0         LISTENING
  Schedule
 [svchost.exe]
  TCP    0.0.0.0:55016          WDVWA00A0049:0         LISTENING
 [services.exe]
  TCP    0.0.0.0:55028          WDVWA00A0049:0         LISTENING
  PolicyAgent
 [svchost.exe]
  TCP    127.0.0.1:1557         WDVWA00A0049:0         LISTENING
 [pbx_exchange.exe]
  TCP    127.0.0.1:9005         WDVWA00A0049:0         LISTENING
 [java.exe]
  TCP    127.0.0.1:54990        WDVWA00A0049:54991     ESTABLISHED
 [pbx_exchange.exe]
  TCP    127.0.0.1:54991        WDVWA00A0049:54990     ESTABLISHED
 [pbx_exchange.exe]
  TCP    127.0.0.1:54993        WDVWA00A0049:0         LISTENING
 [pbx_exchange.exe]
  TCP    127.0.0.1:54993        WDVWA00A0049:55004     ESTABLISHED
 [pbx_exchange.exe]
  TCP    127.0.0.1:54993        WDVWA00A0049:55020     ESTABLISHED
 [pbx_exchange.exe]
  TCP    127.0.0.1:55004        WDVWA00A0049:54993     ESTABLISHED
 [vnetd.exe]
  TCP    127.0.0.1:55017        WDVWA00A0049:0         LISTENING
 [bpcd.exe]
  TCP    127.0.0.1:55020        WDVWA00A0049:54993     ESTABLISHED
 [bpcd.exe]
  TCP    170.43.198.247:139     WDVWA00A0049:0         LISTENING
 Can not obtain ownership information
  TCP    170.43.198.247:3389    DTC97C3E06CC35A:62614  ESTABLISHED
  TermService
 [svchost.exe]
  TCP    170.43.198.247:55024   altdsaztm02:402        ESTABLISHED
 [dagent.exe]
  TCP    [::]:135               WDVWA00A0049:0         LISTENING
  RpcSs
 [svchost.exe]
  TCP    [::]:445               WDVWA00A0049:0         LISTENING
 Can not obtain ownership information
  TCP    [::]:1556              WDVWA00A0049:0         LISTENING
 [pbx_exchange.exe]
  TCP    [::]:3389              WDVWA00A0049:0         LISTENING
  TermService
 [svchost.exe]
  TCP    [::]:9009              WDVWA00A0049:0         LISTENING
 [java.exe]
  TCP    [::]:9080              WDVWA00A0049:0         LISTENING
 [java.exe]
  TCP    [::]:9443              WDVWA00A0049:0         LISTENING
 [java.exe]
  TCP    [::]:31038             WDVWA00A0049:0         LISTENING
 [DkService.exe]
  TCP    [::]:47001             WDVWA00A0049:0         LISTENING
 Can not obtain ownership information
  TCP    [::]:49152             WDVWA00A0049:0         LISTENING
 [wininit.exe]
  TCP    [::]:49153             WDVWA00A0049:0         LISTENING
  eventlog
 [svchost.exe]
  TCP    [::]:49154             WDVWA00A0049:0         LISTENING
 [lsass.exe]
  TCP    [::]:49155             WDVWA00A0049:0         LISTENING
  Schedule
 [svchost.exe]
  TCP    [::]:55016             WDVWA00A0049:0         LISTENING
 [services.exe]
  TCP    [::]:55028             WDVWA00A0049:0         LISTENING
  PolicyAgent
 [svchost.exe]
  UDP    0.0.0.0:123            *:*                   
  W32Time
 [svchost.exe]
  UDP    0.0.0.0:161            *:*                   
 [snmp.exe]
  UDP    0.0.0.0:5355           *:*                   
  Dnscache
 [svchost.exe]
  UDP    127.0.0.1:54100        *:*                   
  LanmanWorkstation
 [svchost.exe]
  UDP    127.0.0.1:60970        *:*                   
 [Smc.exe]
  UDP    127.0.0.1:62242        *:*                   
 [taskhost.exe]
  UDP    127.0.0.1:63642        *:*                   
 [lsass.exe]
  UDP    127.0.0.1:63645        *:*                   
  ProfSvc
 [svchost.exe]
  UDP    170.43.198.247:137     *:*                   
 Can not obtain ownership information
  UDP    170.43.198.247:138     *:*                   
 Can not obtain ownership information
  UDP    [::]:123               *:*                   
  W32Time
 [svchost.exe]
  UDP    [::]:161               *:*                   
 [snmp.exe]

Abraham Sweiss commented Sep 05 '13, 3:03 p.m.

was this netstat taken before the tomcat server was started?

Andrew Torres commented Sep 05 '13, 3:11 p.m. | edited Sep 05 '13, 5:28 p.m.

It was take after I started Tomcat. Actually it was taken once the command startup window errored out. I ran a netstat prior to starting the service and there were no java processes and nothing taking these ports. Here is the full contents of the error:

Sep 5, 2013 11:47:30 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performanc
e in production environments was not found on the java.library.path: D:\Program
Files\IBM\JazzTeamServer\server\jre\bin\compressedrefs;D:\Program Files\IBM\Jazz
TeamServer\server\jre\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\
Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\
Windows\Tools;C:\ProgramData\Opsware\custom\local_security_cli;C:\PROGRA~1\DISKE
E~1\DISKEE~1\;;.
Sep 5, 2013 11:47:31 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9080"]
Sep 5, 2013 11:47:31 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9443"]
Sep 5, 2013 11:47:32 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-9009"]
Sep 5, 2013 11:47:32 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1859 ms
Sep 5, 2013 11:47:32 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Sep 5, 2013 11:47:32 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.32
Sep 5, 2013 11:47:32 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive D:\Program Files\IBM\JazzTeamServer\serv
er\tomcat\webapps\admin.war
Sep 5, 2013 11:47:34 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive D:\Program Files\IBM\JazzTeamServer\serv
er\tomcat\webapps\ccm.war
Sep 5, 2013 11:47:43 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive D:\Program Files\IBM\JazzTeamServer\serv
er\tomcat\webapps\clmhelp.war
Sep 5, 2013 11:47:47 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive D:\Program Files\IBM\JazzTeamServer\serv
er\tomcat\webapps\jts.war
Sep 5, 2013 11:47:53 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory D:\Program Files\IBM\JazzTeamServer\se
rver\tomcat\webapps\ROOT
Sep 5, 2013 11:47:53 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-9080"]
Sep 5, 2013 11:47:53 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-9443"]
Sep 5, 2013 11:47:53 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-9009"]
Sep 5, 2013 11:47:53 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 21715 ms
java.net.ConnectException: Connection timed out: connect
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:381)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:243)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:230)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:377)
        at java.net.Socket.connect(Socket.java:539)
        at java.net.Socket.connect(Socket.java:488)
        at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:424)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:538)
        at sun.net.www.http.HttpClient.<init>(HttpClient.java:221)
        at sun.net.www.http.HttpClient.New(HttpClient.java:304)
        at sun.net.www.http.HttpClient.New(HttpClient.java:323)
        at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLC
onnection.java:999)
        at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConne
ction.java:935)
        at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection
.java:853)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
nection.java:1207)
        at java.net.URL.openStream(URL.java:1022)
        at com.ibm.ccl.ut.help.info.entry.NavTree.categorizeTocXML(NavTree.java:
245)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at com.ibm.ccl.ut.help.info.IndexThread.run(IndexThread.java:105)

0
permanent link
Abraham Sweiss (2.4k●13●31) | answered Sep 05 '13, 4:15 p.m.
specify a unique host in the tomcat server.xml.
then define the host in the windows hosts file and map it to localhost
then try starting up the server.

Your answer

Register or to post 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.