<-- Back

Mislead license information in the Mendix Service Console runtime log

Issue

During the application startup, the log node LicenseService shows different information regarding the license, which may cause confusion for the reader.

The log message is like the one below where the log node line LicenseService appears twice.

First part:

2024-10-05 08:06:36.037 INFO - Core: Initializing license...
2024-10-05 08:06:36.062 INFO - LicenseService: Using PredefinedLicenseService: This license:
- is a developer license: true
- has concurrent user restrictions: true
- license type: Unspecified
- runtime mode: Unspecified
- company:
- separate anonymous users: false
- expiration date: Unspecified
- components:
- products: Map()
- user limitations: 6 Specified Concurrent

Second part:

2024-10-05 08:06:36.475 INFO - LicenseService: Project company name is 'ABC'
2024-10-05 08:06:36.475 INFO - LicenseService: License expiration date is 'Some(Fri Aug 29 20:00:00 EDT 2025)'
2024-10-05 08:06:36.475 INFO - LicenseService: License type is: 'Subscription'
2024-10-05 08:06:36.475 INFO - LicenseService: PredefinedLicenseService, received new license: This license:
- is a developer license: false
- has concurrent user restrictions: true
- license type: Subscription
- runtime mode: Production
- company: ABC
- separate anonymous users: true
- expiration date: Fri Aug 29 20:00:00 EDT 2025
- components: Mobile
- products: Map()
- user limitations:

Environment

  • Mendix for Private Cloud
  • On-Premises

Cause

This is an issue with how the Runtime log shows the previously mentioned first part as default information regarding the actual license type the customer has.

Solution/Workaround

The fix for the issue will be included starting from Mendix Studio Pro 10.6.0 and all MTS/LTS versions; then only the second part will be displayed in the log.

Internal information related

  • 230319
  • RUN-4134

Additional information

Have more questions? Submit a request

0 Comments

Article is closed for comments.

To provide feedback, please open a ticket here. Don't forget to include the article's URL along with the feedback you would like to provide.