Floating License Server in 1.0.1.1
We are getting an error setting up a Floating License Server in RQM 1.0.1.1. When we enter the HTTP address for the server in the URI field of the admin site we get the following:
A connection to the license server was attempted with warnings. Resolve warnings to continue.
WARNING: CRJAZ1300I The license server "http://10.12.88.157:9085/jazz" could not be contacted. Check to make sure the address is correct, and that the server has been started.
If we attempt to hit the address in a browser, it allows us to connect.
I have included the relevant pieces of the Server.xml below.
<!-- Define a non-SSL HTTP/1.1 Connector on port 9080 -->
<Connector port="9085" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="1905" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true"
URIEncoding="UTF-8" />
<Connector port="1905"
connectionTimeout="20000"
maxHttpHeaderSize="8192"
maxThreads="150"
minSpareThreads="25"
maxSpareThreads="75"
enableLookups="false"
disableUploadTimeout="true"
acceptCount="100"
scheme="https"
secure="true"
clientAuth="false"
keystoreFile="ibm-team-ssl.keystore"
keystorePass="ibm-team"
sslProtocol="SSL"
algorithm="IbmX509"
URIEncoding="UTF-8" />
<!-- Define an AJP 1.3 Connector on port 9009 -->
<Connector port="9009"
enableLookups="false" redirectPort="1905" protocol="AJP/1.3" />
A connection to the license server was attempted with warnings. Resolve warnings to continue.
WARNING: CRJAZ1300I The license server "http://10.12.88.157:9085/jazz" could not be contacted. Check to make sure the address is correct, and that the server has been started.
If we attempt to hit the address in a browser, it allows us to connect.
I have included the relevant pieces of the Server.xml below.
<!-- Define a non-SSL HTTP/1.1 Connector on port 9080 -->
<Connector port="9085" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="1905" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true"
URIEncoding="UTF-8" />
<Connector port="1905"
connectionTimeout="20000"
maxHttpHeaderSize="8192"
maxThreads="150"
minSpareThreads="25"
maxSpareThreads="75"
enableLookups="false"
disableUploadTimeout="true"
acceptCount="100"
scheme="https"
secure="true"
clientAuth="false"
keystoreFile="ibm-team-ssl.keystore"
keystorePass="ibm-team"
sslProtocol="SSL"
algorithm="IbmX509"
URIEncoding="UTF-8" />
<!-- Define an AJP 1.3 Connector on port 9009 -->
<Connector port="9009"
enableLookups="false" redirectPort="1905" protocol="AJP/1.3" />
One answer
This issue has been resolved. The following section of the web.xml was removed by our team accidentally :
<!-- Opens up the floating license service to unauthenticated / unencrypted
access to avoid dealing with credentials and security certificates in
server to server communication -->
<security-constraint>
<web-resource-collection>
<web-resource-name>open-unencrypted</web-resource-name>
<url-pattern>/service/com.ibm.team.repository.service.internal.license.IFloatingLicenseService/*</url-pattern>
</web-resource-collection>
<!-- Leaving out the <auth-constraint> section means these resources don't require authentication -->
<!-- Leaving out the <user-data-constraint> section means these resources don't require SSL -->
</security-constraint>
<!-- Opens up the floating license service to unauthenticated / unencrypted
access to avoid dealing with credentials and security certificates in
server to server communication -->
<security-constraint>
<web-resource-collection>
<web-resource-name>open-unencrypted</web-resource-name>
<url-pattern>/service/com.ibm.team.repository.service.internal.license.IFloatingLicenseService/*</url-pattern>
</web-resource-collection>
<!-- Leaving out the <auth-constraint> section means these resources don't require authentication -->
<!-- Leaving out the <user-data-constraint> section means these resources don't require SSL -->
</security-constraint>