RTC 5.0.2 tomcat Service error

 Thanks. I will check to make sure I spelled it correctly but that tag is in the java tab.

This is set correctly as I cut and paste these and several other options directly from the server.startup file. IBM is not sure what is going on with this keymanager error. Tomcat does startup as I can get to the page at port 9080 but since it cannot open 9443 I can't get into RTC.

So this does work other than JTS says it can no longer talk to the database (SQL Server). When I check the log file I see that everything starts but a trigger on a stopInternal happens and there a Servlet Destroy msg appears. I haven't seen these before but in the tomcat log I see no errors. I'm using the same sql string that we have in the teamserver.properties file which works manually.

Still unable to talk to SQL Server. IBM thinks I have the path wrong. But what they suggest isn't working for the path.

It may be another case of failing to pass the Java option/parameter to Tomcat. It would be helpful if you can show the configuration GUI of the Tomcat service, so that any potential mistakes can be spotted.

I cannot get a screen shot but manually I have typed below. I am trying not to misspell but because the server is disconnected from the world I have to do it this way. So this starts but still gives the error that the keymanager will no lock 9443

Current Java tags

-DJRE_HOME=file:///c:/rtc/server/jre

-Djava.awt.headless=true

-DSQLSERER_JDBC_DRIVER_FILE=c:\rtc\serer\sqljdbc4.jar

-Djazz.connector.sslProtocol=SSL_TLS

-Djazz.connector.alogorithm=IbmX509

-Xmx4G

-Xms4G

-Xmn512M

-Dlog4j.configuration.file:file:///c:/rtc/server/cof/startup_log4j.properties

-Dcom.ibm.tea.repository.debugMode=true

-Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true

-Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true

-Dorg.apache.cataline.connector.coyoteAdapter.ALLOW_BACKSLASH=true

-Dcom.ibm.teamrepostory.tempDir=
"%TEMP%"

The reason for a screen shot is that we may see any potential mistakes in the configuration. If this is indeed your current setting, then "JAZZ_HOME" is missing. Also, "JRE_HOME" should be set as "-DJRE_HOME=c:/rtc/server/jre", without the "file:///". The SQL Server driver parameter is misspelled "SQLSERER_JDBC_DRIVER_FILE" (probably only when you copied it to this forum, but worth mentioning).