It's all about the answers!

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

×42,874
×7,461
×4,713
×4,316
×267
×110

question asked: Nov 28 '14, 3:01 a.m.
question was seen: 6,908 times
last updated: Feb 19 '15, 12:29 p.m.

Related questions

After upgrade JTS log is constantly rotated with license errors

2
Kim Soederhamn (1.5k●3●43●48) | asked Nov 28 '14, 3:01 a.m.
After upgrading from 4.x to 5.x we see the following error in jts.log the log is constantly filled with this error and rotated. We are using floating token licenses

2014-11-28 08:48:48,693 [WebContainer : 10 @@ 08:48 <unauthenticated> /jts/service/com.ibm.team.repository.service.internal.license.ILicenseRestService/licenseTypes] ERROR vice.internal.license.MergedContributorLicenseType  - CRJAZ2581E CAL policy files cannot be merged if the two policies have different values for the "countedInServerLimit" attribute.
com.ibm.team.repository.service.internal.license.LicenseKeyMergeException: CRJAZ2581E CAL policy files cannot be merged if the two policies have different values for the "countedInServerLimit" attribute.
    at com.ibm.team.repository.service.internal.license.MergedContributorLicenseType.createConflictingValueException(MergedContributorLicenseType.java:337)
    at com.ibm.team.repository.service.internal.license.MergedContributorLicenseType.assertEqual(MergedContributorLicenseType.java:166)
    at com.ibm.team.repository.service.internal.license.MergedContributorLicenseType.assertValidMerge(MergedContributorLicenseType.java:116)
    at com.ibm.team.repository.service.internal.license.MergedContributorLicenseType.<init>(MergedContributorLicenseType.java:60)
    at com.ibm.team.repository.service.internal.license.MergedContributorLicenseType.addKeyToType(MergedContributorLicenseType.java:51)
    at com.ibm.team.repository.service.internal.license.LicenseState.processPolicy(LicenseState.java:500)

The reson for this behaviour is that we have both the version 4 and version 5 of the floating token licenses in the system. Thinking version 5 would automatically replace the version 4.

To fix the error you on the license key management page you must scroll down to the floating licenses and remove the old version 4 licenses (delete them on the red x). when all old licenses are removed the log will go back to normal.
Comments
Kim Soederhamn commented Nov 28 '14, 3:06 a.m.

The error seen from JTS side is this:


Inactive (The license key "Rational Requirements Composer-Token Server Managed" is not compatible with the license type "Contributor-Token". It is possible that the key was migrated from an earlier version and is now incompatible with the current version. To fix the problem you may want to either replace the key with an updated version or remove the key if it is possible.)

One answer

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Don Yang (7.7k●21●114●139) | answered Nov 30 '14, 7:35 p.m.
thanks for sharing the info, you will need to manually remove the 4.x license.
Comments
Frank Ning commented Feb 19 '15, 12:29 p.m.

I don't have any 4.x licenses but purely V5 licenses. However, I got the same error:


 2015-02-19 11:52:11,832 [WebContainer : 13 @@ 11:52 frank.ning /jts/service/com.ibm.team.repository.service.internal.ILicenseAdminRestService/licenseInfo] ERROR vice.internal.license.MergedContributorLicens
eType  - CRJAZ2581E CAL policy files cannot be merged if the two policies have different values for the "tokenCost" attribute.
com.ibm.team.repository.service.internal.license.LicenseKeyMergeException: CRJAZ2581E CAL policy files cannot be merged if the two policies have different values for the "tokenCost" attribute.
        at com.ibm.team.repository.service.internal.license.MergedContributorLicenseType.createConflictingValueException(MergedContributorLicenseType.java:337)
        at com.ibm.team.repository.service.internal.license.MergedContributorLicenseType.assertEqual(MergedContributorLicenseType.java:166)
 ... more

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.