If you are running a Federation Sync in Landmark, and you get the below message “Socket timeout exception occurred”, you may need to increase the max heap on the lase node. This error message will also present itself in the security_authen.log on the Landmark server.

Sun Apr 25 17:07:26.438 EDT 2021 – 1584534648 – L(2) : Sync Analysis failed with exception. Details: Socket timeout exception occurred. (read timed out).

Stack Trace :

com.lawson.security.server.LawsonNetException: Socket timeout exception occurred. (read timed out).

at com.lawson.security.server.events.BaseEvent.readMsg(BaseEvent.java:235)

at com.lawson.security.server.client.ClientActorEvent.getNextActorIds2(ClientActorEvent.java:239)

at com.lawson.lawsec.authen.SyncAnalysis.getRemoteActorList(SyncAnalysis.java:2962)

at com.lawson.lawsec.authen.SyncAnalysis.loadActorsToSync(SyncAnalysis.java:1299)

at com.lawson.lawsec.authen.SyncAnalysis.performActorSyncAnalysis(SyncAnalysis.java:513)

at com.lawson.lawsec.authen.SyncAnalysis.run(SyncAnalysis.java:269)

at java.lang.Thread.run(Thread.java:748)

To update the lase max heap, open the Grid Admin window. Go to Configuration Manager > Grid Configuration > Grid Properties > Node Memory > Max Heap. Update the max heap to an appropriate level.

Save the setting and restart the lase node, or restart Landmark.

While you are running the federation sync, you can monitor the lase node in the grid’s topology view to see if your setting is appropriate for future syncs.

 

When installing a new IPA product line using the intall-lpa.pl command in Landmark, you may encounter the error “Security Class does not exist.” This will prevent the IPA environment from completing the install. To resolve this error, first run the command “scupdate <product line>”. This command will generate all the security classes needed for the new IPA product line. Then, rerun the install-lpa.pl command, and it should complete successfully.

Error messages (on the command line, and also found at LALOGDIR/managelpa_<pdl>.log)

Run the scupdate command and verify no errors

Complete the IPA product line install

 

If you perform a Java update on your Landmark server, and your JAVA_HOME location is moving, you will need to update the java location in several places in Landmark.

InforIONGrid

For the Grid, first open an administrator command window and navigate to GRID_HOME/grids/<grid name> and run the “ChangeJDK.cmd” command with the NEW location of Java:

Next, open the Grid Management Pages. Go to Configuration > Grid Configuration > Grid Properties. Select Property “Java Executable (Path)”. Set the Java path to the new location under your grid host.

Landmark

For Landmark, set the JAVA_HOME and LAW_JAVA_HOME environment variables to the new location. It is also a good idea to update LAW_JAVA_HOME in the LASYSDIR/install.cfg file for future patches.

Finally, open an administrator command window and set the Landmark environment variables. Navigate to the NEW java location. Run the command java -jar %LAENVDIR%/java/jar/bcinstall.jar. Verify that this command adds the bouncycastle provider to the java.security file located at JAVA_HOME/jre/lib/security. Also, verify that the command copies the “bcprov” jar to JAVA_HOME/jdk/jre/lib/ext. If either of these tasks is not completed, you can handle them manually.

Run a stoplaw/startlaw and restart the grid. Or, better yet, reboot the server.

To verify that the new java location is being used by all the application systems, open task manager, and add the “Command line” header under the details screen. Verify that all “java.exe” processes are running from the correct location. You are now safe to uninstall your old java instance.