Page History

...

• Magic Collaboration Studio (release 2021x , 2021x Refresh1, 2021x Refresh2, 19.0 SP2, 19.0 SP3, 19.0 SP4)
• Magic Software Architect (release 2021x Refresh1, 2021x Refresh2)
• Magic Cyber Systems Engineer (release 2021x Refresh1, 2021x Refresh2)
• Magic Systems of Systems Architect (release 2021x Refresh1, 2021x Refresh2)

No Magic portfolio

• Teamwork Cloud (release 2021x Refresh1, 2021x Refresh2)
• Cameo Collaborator for Teamwork Cloud (release  2021x Refresh1, 2021x Refresh2)
• MagicDraw (release 2021x Refresh1, 2021x Refresh2)
• Cameo Systems Modeler (release 2021x Refresh1, 2021x Refresh2)
• Cameo Enterprise Architecture (release 2021x Refresh1, 2021x Refresh2)

Apache Log4j2 version <2.15.0 is a part of the following products in these versions, however it is not used for logging:

• Magic Collaboration Studio (release 2021x, 19, 19.0 SP1, 19.0 SP2, 19.0 SP3, 19.0 SP4)
  
  
• Cameo Collaborator for Teamwork Cloud (release  2021x, 2021x Refresh1, 2021x Refresh2, 19.0 SP1, 19.0 SP2, 19.0 SP3, 19.0 SP4)MagicDraw
• Teamwork Cloud (release 2021x Refresh1, 2021x Refresh2)
• Cameo Systems Modeler (release 2021x Refresh1, 2021x Refresh2)
• Cameo Enterprise Architecture (release 2021x Refresh1, 2021x Refresh2)

...

• , 19.0 SP1, 19.0 SP2, 19.0 SP3, 19.0 SP4)

Remediation

For modeling tools (Magic Software Architect, Magic Cyber Systems Engineer, Magic Systems of Systems Architect , MagicDraw, Cameo Systems Modeler, Cameo Enterprise Architecture)

...

to a <modeling tool installation directory>\bin\<modeling tool>.properties file (e.g. magicdraw.properties, csm.properties, cameoea.properties) on the classpath to prevent lookups in the log event message.

For collaboration tools (Magic Collaboration Studio

...

, Cameo Collaborator for Teamwork Cloud

...

, Teamwork Cloud

...

)

Option 1

You may prevent  lookups in the log event message by adding parameter via command line or in Web Application Platform setenv.sh / setenv.bat properties file.

...

1. In the Java application server home directory (on which Web Application Platform runs), go to the bin folder. For example, if you use Apache Tomcat, go to <tomcat_home>\bin.
2. Using a plain text editor, create the setenv.bat file in that directory if it does not already exist.

3. Copy and paste the following line to the setenv.bat file:

   Code Block
   log4j-Dlog4j.formatMsgNoLookups=true

   
   

4. Save and close the file.
5. Restart the Java application server.

...

1. Stop the Web Application Platform if it is running.
2. Open the command-line interface and go to the Web Application Platform installation directory.

3. In the command-line interface, run the following command:

   Code Block
   .\bin\tomcat<version>.

   exe 

   exe //US//WebApp --JvmMs=8000 --JvmMx=8000 ++JvmOptions

   ='-Dcom.sun.management.jmxremote

   =

   true

   '

   Code Block
   -Dlog4j.formatMsgNoLookups=true'

   
   

4. Restart the Web Application Platform.

...

1. In the Java application server (on which Web Application Platform runs) home directory, go to the bin folder. For example, if you use Apache Tomcat, go to <tomcat_home>/bin.
2. Using a plain text editor, create the setenv.sh file in that directory if it does not already exist.

3. Copy and paste the following lines to the setenv.sh file:

   
   

   Code Block
   log4j-Dlog4j.formatMsgNoLookups=true

   
   

4. Save and close the file.
5. Restart the Java application server.

...