It's all about the answers!

Ask a question

Client unable to get token licenses from the Server, Any way to fix this?


Luis Calderon (2919) | asked Jan 17 '18, 10:25 a.m.

Hi:

I set my environment to get the token licenses from a server. My client is not getting them with JTS 6.0.5. I checked the logs and got the "warning" below.

2018-01-17 11:10:32,043 [   jts: Remote license updater]  WARN ory.service.internal.license.FloatingLicenseClient  - CRJAZ1275I The floating license available from "https://XXXXX.XXXXXX.com/jts/service/com.ibm.team.repository.service.internal.license.IFloatingLicenseService/licenses/com.ibm.xtools.dm.rsa.designer.token-v3_b92a5960-cb65-11df-bd3b-0800200c9a66?includeFullJar=true" could not be processed. The floating license will be ignored.

Any way to fix this?

I'm also getting this other error, don't know if it is related, but just in case:

com.ibm.team.repository.common.TeamRepositoryException: CRJAZ1028I The "rules.xml" file was not signed.
    at com.ibm.team.repository.service.internal.license.SignedJarReader.verifySignedEntry(SignedJarReader.java:90)
    at com.ibm.team.repository.service.internal.license.SigningRulesJarReader.readPolicyImpl(SigningRulesJarReader.java:41)
    at com.ibm.team.repository.service.internal.license.SigningRulesJarReader.readPolicyImpl(SigningRulesJarReader.java:1)
    at com.ibm.team.repository.service.internal.license.SignedJarReader.readPolicy(SignedJarReader.java:72)
    at com.ibm.team.repository.service.internal.license.SignedJarReader.readPolicy(SignedJarReader.java:52)
    at com.ibm.team.repository.service.internal.license.SigningRulesJarReader.readRules(SigningRulesJarReader.java:48)
    at com.ibm.team.repository.service.internal.license.PolicyJarReader.getKeySigningRules(PolicyJarReader.java:96)
    at com.ibm.team.repository.service.internal.license.PolicyJarReader.readPolicyImpl(PolicyJarReader.java:115)
    at com.ibm.team.repository.service.internal.license.PolicyJarReader.readPolicyImpl(PolicyJarReader.java:1)
    at com.ibm.team.repository.service.internal.license.SignedJarReader.readPolicy(SignedJarReader.java:72)
    at com.ibm.team.repository.service.internal.license.SignedJarReader.readPolicy(SignedJarReader.java:52)
    at com.ibm.team.repository.service.internal.license.PolicyJarReader.readPolicy(PolicyJarReader.java:75)
    at com.ibm.team.repository.service.internal.license.FloatingLicenseClient.fetchPolicyWithTranslation(FloatingLicenseClient.java:268)
    at com.ibm.team.repository.service.internal.license.FloatingLicenseClient.getFloatingPolicies(FloatingLicenseClient.java:190)
    at com.ibm.team.repository.service.internal.license.ManagedFloatingLicenseClient.getFloatingPolicies(ManagedFloatingLicenseClient.java:845)
    at com.ibm.team.repository.service.internal.license.LicenseService.updateRemoteFloatingLicenses(LicenseService.java:988)
    at com.ibm.team.repository.service.internal.license.LicenseService.access$9(LicenseService.java:986)
    at com.ibm.team.repository.service.internal.license.LicenseService$4$1.run(LicenseService.java:704)
    at com.ibm.team.repository.service.internal.TeamServiceContext.runAsAdmin(TeamServiceContext.java:257)
    at com.ibm.team.repository.service.internal.license.LicenseService$4.run(LicenseService.java:701)
    at java.lang.Thread.run(Thread.java:785)


Thanks in advance....

Accepted answer


permanent link
Zeeshan Choudhry (6541612) | answered Feb 19 '19, 2:43 a.m.
Please refer this workaround mentioned in the defect if it helps

Ralph Schoon selected this answer as the correct answer

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.