It's all about the answers!

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

×7,478
×4,321
×2,352
×40
×40
×8

question asked: Jan 24 '14, 1:27 p.m.
question was seen: 5,969 times
last updated: Jan 27 '14, 5:08 a.m.

Related questions

running configtest on AIX with CLM 4.0.5 causes java.security.NoSuchAlgorithmException

0
Fred Bickford (28●18●32) | asked Jan 24 '14, 1:27 p.m.
JAZZ DEVELOPER
edited Jan 27 '14, 5:03 a.m. by Krzysztof Kaźmierczyk (7.5k●4●80●103)
After CLM 4.0.5 installation, choosing Tomcat(Planning to deploy WAS, yet trying to get started quickly)

Server version: Apache Tomcat/7.0.32
Server built:   Oct 3 2012 08:51:20
Server number:  7.0.32.0
OS Name:        AIX
OS Version:     6.1
Architecture:   ppc64
JVM Version:    pap6460sr15-20131017_01 (SR15)
JVM Vendor:     IBM Corporation

running the tomcat configtest.sh I get

Using CATALINA_BASE:   /opt/IBM/JazzTeamServer/server/tomcat
Using CATALINA_HOME:   /opt/IBM/JazzTeamServer/server/tomcat
Using CATALINA_TMPDIR: /opt/IBM/JazzTeamServer/server/tomcat/temp
Using JRE_HOME:        /usr/java6_64
Using CLASSPATH:       /opt/IBM/JazzTeamServer/server/tomcat/bin/bootstrap.jar:/opt/IBM/JazzTeamServer/server/tomcat/bin/tomcat-juli.jar
Jan 24, 2014 2:06:46 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: /usr/java6_64/jre/lib/ppc64/default:/usr/java6_64/jre/lib/ppc64:/usr/java6_64/jre/lib/ppc64:/usr/java6_64/jre/lib/ppc64/default:/usr/java6_64/jre/lib/ppc64/j9vm:/usr/java6_64/jre/lib/ppc64:/usr/java6_64/jre/../lib/ppc64:/usr/lib:/usr/lib
Jan 24, 2014 2:06:47 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9079"]
Jan 24, 2014 2:06:47 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9444"]
Jan 24, 2014 2:06:49 PM org.apache.coyote.AbstractProtocol init
SEVERE: Failed to initialize end point associated with ProtocolHandler ["http-bio-9444"]
Throwable occurred: java.io.IOException: ${jazz.connector.sslProtocol} SSLContext not available
        at org.apache.tomcat.util.net.jsse.JSSESocketFactory.init(JSSESocketFactory.java:475)
        at org.apache.tomcat.util.net.jsse.JSSESocketFactory.createSocket(JSSESocketFactory.java:158)
        at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:393)
        at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:610)
        at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:429)
        at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)
        at org.apache.catalina.connector.Connector.initInternal(Connector.java:981)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
        at org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
        at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:633)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:658)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:281)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:455)
Caused by: java.security.NoSuchAlgorithmException: ${jazz.connector.sslProtocol} SSLContext not available
        at sun.security.jca.GetInstance.getInstance(GetInstance.java:210)
        at javax.net.ssl.SSLContext.getInstance(SSLContext.java:27)
        at org.apache.tomcat.util.net.jsse.JSSESocketFactory.createSSLContext(JSSESocketFactory.java:488)
        at org.apache.tomcat.util.net.jsse.JSSESocketFactory.init(JSSESocketFactory.java:448)
        ... 19 more
Jan 24, 2014 2:06:49 PM org.apache.catalina.core.StandardService initInternal
SEVERE: Failed to initialize connector [Connector[HTTP/1.1-9444]]
Throwable occurred: org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-9444]]
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
        at org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
        at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:633)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:658)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:281)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:455)
Caused by: org.apache.catalina.LifecycleException: Protocol handler initialization failed
        at org.apache.catalina.connector.Connector.initInternal(Connector.java:983)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
        ... 12 more
Caused by: java.io.IOException: ${jazz.connector.sslProtocol} SSLContext not available
        at org.apache.tomcat.util.net.jsse.JSSESocketFactory.init(JSSESocketFactory.java:475)
        at org.apache.tomcat.util.net.jsse.JSSESocketFactory.createSocket(JSSESocketFactory.java:158)
        at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:393)
        at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:610)
        at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:429)
        at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)
        at org.apache.catalina.connector.Connector.initInternal(Connector.java:981)
        ... 13 more
Caused by: java.security.NoSuchAlgorithmException: ${jazz.connector.sslProtocol} SSLContext not available
        at sun.security.jca.GetInstance.getInstance(GetInstance.java:210)
        at javax.net.ssl.SSLContext.getInstance(SSLContext.java:27)
        at org.apache.tomcat.util.net.jsse.JSSESocketFactory.createSSLContext(JSSESocketFactory.java:488)
        at org.apache.tomcat.util.net.jsse.JSSESocketFactory.init(JSSESocketFactory.java:448)
        ... 19 more
Jan 24, 2014 2:06:49 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Jan 24, 2014 2:06:49 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 3633 ms

SInce I am using an IBM Java, I have even tried changing the algorithm for the the SSL port.

    <Connector port="9444"
               connectionTimeout="20000"
               maxHttpHeaderSize="8192"
               maxThreads="150"
               minSpareThreads="25"
               enableLookups="false"
               disableUploadTimeout="true"
               acceptCount="100"
               scheme="https"
               secure="true"
               clientAuth="false"
               keystoreFile="ibm-team-ssl.keystore"
               keystorePass="ibm-team"
               protocol="HTTP/1.1"
               SSLEnabled="true"
               sslProtocol="${jazz.connector.sslProtocol}"
               algorithm="IbmX509"



same error shows up in the catalina logs trying to start Tomcat

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
David Mehaffy (901●2●33●38) | answered Jan 24 '14, 1:49 p.m.
JAZZ DEVELOPER
 why are you trying to run the tomcat config - that is not part of running a clm server.  4.05 runs fine on AIX - i have been running on AIX for several weeks.  Have you tried just running server.startup from the CLM_HOME/server directory?  You need to read the documentation.  If you run the server.startup and then do the setup wizard in clm it should configure the server.xml correctly for you as well as the webapp xml files.  You don't run clm on tomcat the way you are trying.
Comments
Fred Bickford commented Jan 24 '14, 2:27 p.m. | edited Jan 27 '14, 5:04 a.m.
JAZZ DEVELOPER

David, the attempt to run tomcat was to debug the fact that starting the CLM server didnt really yield much of anything, the server is non repsonsive and the following was the only thing in the ccm or JTS log

2014-01-24 15:14:01,339 [Component Resolve Thread (Bundle 91)]  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-01-24 15:14:01,340 [Component Resolve Thread (Bundle 91)]  INFO nternal.OverridablePropertyFileServerConfiguration  - CRJAZ1363I Loading the configuration from "file:/opt/IBM/JazzTeamServer/server/conf/jts/teamserver.properties".

althought I was targetting port 9444 for SSL, it seems that 9443 is what is being used( so will use that for now)

David Mehaffy commented Jan 24 '14, 2:31 p.m.
JAZZ DEVELOPER

that sounds like there is a problem your conf/jts/teamserver.properties file.  Either something is not there that needs to be there or is corrupt. 
0
permanent link
Krzysztof Kaźmierczyk (7.5k●4●80●103) | answered Jan 27 '14, 5:08 a.m.
Hi Fred,
I don't see any error message in jts.log file you have provided. There are only INFO traces. From your tomcat log it seems that it is used port 9444 as it is configured in server.xml.
If you want to further investigate this issue, please provide us the information what you see on the screen when you are attempting to login to RTC server (empty screen, error message from tomcat, server not found, other?)
Please also use
netstat -a -o
to see what are the ports for your servers.
It might happen that you have 2 servers installed on this machine and you are using wrong one.

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.