It's all about the answers!

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

×7,451
×6,108

question asked: Jun 12 '14, 11:47 p.m.
question was seen: 4,496 times
last updated: Jun 21 '14, 8:48 p.m.

Related questions

After CLM 5.0 Installation Server doesnt appear to start

1
Fred Bickford (28●18●32) | asked Jun 12 '14, 11:47 p.m.
JAZZ DEVELOPER
CLM 5.0 on AIX 7.1

From JTS.log

2014-06-12 17:50:45,361 [Component Resolve Thread (Bundle 87)]  INFO nternal.OverridablePropertyFileServerConfiguration  -
 To submit questions about issues, go to the Jazz.net forum at https://jazz.net/forum.
 To find more information about a message, see the CLM Messages Information Center at
 https://jazz.net/help-dev/CLMErrorMessages/index.jsp.
2014-06-12 17:50:45,361 [Component Resolve Thread (Bundle 87)]  INFO nternal.OverridablePropertyFileServerConfiguration  - CRJAZ1363I Loading the configuration from "file:/IBM/JazzTeamServer/server/conf/jts/teamserver.properties".

From Catalina.out
Jun 12, 2014 5:49:26 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /IBM/JazzTeamServer/server/jre/lib/ppc64/default:/IBM/JazzTeamServer/server/jre/lib/ppc64:/IBM/JazzTeamServer/server/jre/lib/ppc64:/IBM/JazzTeamServer/server/jre/lib/ppc64/default:/IBM/JazzTeamServer/server/jre/lib/ppc64/j9vm:/IBM/JazzTeamServer/server/jre/lib/ppc64:/IBM/JazzTeamServer/server/jre/../lib/ppc64:/usr/lib:/usr/lib
Jun 12, 2014 5:49:28 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9080"]
Jun 12, 2014 5:49:28 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9443"]
Jun 12, 2014 5:49:30 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-9009"]
Jun 12, 2014 5:49:30 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 4282 ms
Jun 12, 2014 5:49:30 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Jun 12, 2014 5:49:30 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.52
Jun 12, 2014 5:49:30 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /IBM/JazzTeamServer/server/tomcat/webapps/admin.war
Jun 12, 2014 5:49:31 PM org.apache.tomcat.websocket.server.WsSci onStartup
INFO: JSR 356 WebSocket (Java WebSocket 1.0) support is not available when running on Java 6. To suppress this message, run Tomcat on Java 7, remove the WebSocket JARs from $CATALINA_HOME/lib or add the WebSocketJARs to the tomcat.util.scan.DefaultJarScanner.jarsToSkip property in $CATALINA_BASE/conf/catalina.properties. Note that the deprecated Tomcat 7 WebSocket API will be available.
Jun 12, 2014 5:49:32 PM com.ibm.team.osgi.patch.PatchConfigurator addHooks
INFO: Patch service started
Jun 12, 2014 5:49:32 PM com.ibm.team.osgi.patch.PatchConfigurator addHooks
INFO: No patches found
Jun 12, 2014 5:49:37 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /IBM/JazzTeamServer/server/tomcat/webapps/ccm.war
Jun 12, 2014 5:49:38 PM com.ibm.team.osgi.patch.PatchConfigurator addHooks
INFO: Patch service started
Jun 12, 2014 5:49:38 PM com.ibm.team.osgi.patch.PatchConfigurator addHooks
INFO: No patches found
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://352.fwk899691936/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://352.fwk899691936:1/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
Jun 12, 2014 5:50:15 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /IBM/JazzTeamServer/server/tomcat/webapps/clmhelp.war
Jun 12, 2014 5:50:21 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /IBM/JazzTeamServer/server/tomcat/webapps/jts.war
Jun 12, 2014 5:50:22 PM com.ibm.team.osgi.patch.PatchConfigurator addHooks
INFO: Patch service started
Jun 12, 2014 5:50:22 PM com.ibm.team.osgi.patch.PatchConfigurator addHooks
INFO: No patches found
[Fatal Error] :48:29: The entity name must immediately follow the '&' in the entity reference.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://326.fwk1198540656/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://326.fwk1198540656:1/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
Jun 12, 2014 5:50:50 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /IBM/JazzTeamServer/server/tomcat/webapps/qm.war
Jun 12, 2014 5:50:51 PM com.ibm.team.osgi.patch.PatchConfigurator addHooks
INFO: Patch service started
Jun 12, 2014 5:50:51 PM com.ibm.team.osgi.patch.PatchConfigurator addHooks
INFO: No patches found
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://471.fwk775695932/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://471.fwk775695932:1/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
Jun 12, 2014 5:51:28 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /IBM/JazzTeamServer/server/tomcat/webapps/rm.war
Jun 12, 2014 5:51:28 PM com.ibm.team.osgi.patch.PatchConfigurator addHooks
INFO: Patch service started
Jun 12, 2014 5:51:28 PM com.ibm.team.osgi.patch.PatchConfigurator addHooks
INFO: No patches found
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://80.fwk1372738002/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://80.fwk1372738002:1/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://358.fwk1372738002/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://358.fwk1372738002:1/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
Jun 12, 2014 5:51:58 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /IBM/JazzTeamServer/server/tomcat/webapps/ROOT
Jun 12, 2014 5:51:58 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-9080"]
Jun 12, 2014 5:51:58 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-9443"]
Jun 12, 2014 5:51:58 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-9009"]
Jun 12, 2014 5:51:58 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 148596 ms


4 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Donald Nong (14.5k●6●14) | answered Jun 13 '14, 2:30 a.m.
There was a fatal error when deploying JTS.
INFO: Deploying web application archive /IBM/JazzTeamServer/server/tomcat/webapps/jts.war 
Jun 12, 2014 5:50:22 PM com.ibm.team.osgi.patch.PatchConfigurator addHooks 
INFO: Patch service started 
Jun 12, 2014 5:50:22 PM com.ibm.team.osgi.patch.PatchConfigurator addHooks 
INFO: No patches found 
[Fatal Error] :48:29: The entity name must immediately follow the '&' in the entity reference. 
SLF4J: Class path contains multiple SLF4J bindings. 
SLF4J: Found binding in [bundleresource://326.fwk1198540656/org/slf4j/impl/StaticLoggerBinder.class] 
SLF4J: Found binding in [bundleresource://326.fwk1198540656:1/org/slf4j/impl/StaticLoggerBinder.class] 

SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. 
Jun 12, 2014 5:50:50 PM org.apache.catalina.startup.HostConfig deployWAR 

Probably the .war file is corrupted. You can try to replace the file itself. You can extract the file from the com.ibm.team.install.jfs.app.jazz.war_0.7.0.20140509_1342.zip file found in the "native" folder of your installation media.
0
permanent link
Marcio Braga (6) | answered Jun 18 '14, 10:49 p.m.
Same here.

No installation media.
Not sure but, it seems IBM Installation Mgr use this public repository
( http://public.dhe.ibm.com/software/rationalsdp/v7/im/173/repository )
Comments
Donald Nong commented Jun 18 '14, 11:36 p.m.

The link that you posted is the Installation Manager update site. The public repository for Jazz products are on jazz.net.

Marcio Braga commented Jun 18 '14, 11:58 p.m.

Oh, right. Thank you.

I got the CLM-Web-Installer-Win-5.0.1M1 from jazz.net and after installation I got this same "Fatal Error" as the fellow here.
But despite this error, the installation seems to be working well.
Should I not worry with this "Fatal Error" message ?

Donald Nong commented Jun 19 '14, 6:17 a.m.

When you said the installation seems to be working, does it mean that you can access to all the CLM applications? In Fred's case, the fatal error occurred when deploying jts.war and I guess the deployment was not successful and maybe that's the reason he said "server doesn't appear to start".

Marcio Braga commented Jun 20 '14, 10:36 p.m.

I reinstalled JTS + CCM, from remote repository (Jazz.net 5.0.1) and from downloaded repository ( IBM 5.0) and in both cases I got this Fatal Error, but the application is working fine. I wonder what could be the implications of such Fatal Error.

As a parallel comment regard the "Server not start": Double-check if it is not a short memory problem. My VMwares are 4GB by default and the server.startup.bat is 4GB by default -- it will not start. I need to reduce the server.startup.bat config to 2GB.

0
permanent link
Davyd Norris (202●2●10●14) | answered Jun 21 '14, 8:42 p.m.
I got this same Fatal Error - in fact your log pretty much looks exactly like mine, but it all started just fine.

The one problem I had was when I went through the upgrade process. The last step in the RRC upgrade re-establishes links between existing applications and it failed. After much mucking round I found that this step requires your admin user to have a valid CLM license, and since the licenses have changed between 4.x and 5.x, your existing 4.x license will not work :-(

I ended up logging into the 5.0 server, upgrading all licenses, and then manually running the last step, which then passed.

I imagine you could get around this by upgrading your licenses BEFORE starting the upgrade, as a 4.x server will still work with a 5.0 license, but obviously not the other way round.
0
permanent link
Davyd Norris (202●2●10●14) | answered Jun 21 '14, 8:48 p.m.
The other error you may encounter is when you are checking your installation as per the instructions in the Installation Guide. It tells you to run all data collections jobs for all applications and you will find the 'Requirements' job fails for the RM application.

I once again chased this down for ages, and the error logs talk about Authentication problems, and about an error 500 in the server REST API call. In the end I found that there's a bug in the RM application when you have no RM projects defined - it looks like it's asking for a list of RM project areas for the job, which returns null. THis isn't being checks for and that's where the errors are coming from. So you will find the 'Requirements' data collection job will fail with weird errors if you have a new installation or if you have no requirements projects defined.

I created an empty basic RM project and the problem went away, but you can probably ignore the error if you want - it will fill your logs up though so you may want to turn off the job.

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.