This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Solved! I was deceived into thinking that when I deployed my new ear that every file in my old one was replaced during an update. By uninstalling and reinstalling the maximi-MIF and maxino-UI ears it overwrote the critical properties.jar that was causing my issue.
Lonnie Stone
@LonStone3
-----Original Message-----
From: "Lonnie Stone" <lonnie_s_stone@yahoo.com>
Sent: 3/29/2014 11:15 PM
To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
Subject: [MAXIMO List] RMI Cluster Issues
I have Maximo in a vertical cluster with 1 MIF and 3 UI. TRM is involved so I have the RMI Registry in the mix. I want to designate the rmi.port for each JVM. So I removed the mxe.rni.port from all the maximo.properties files and instead created instance properties for each JVM in the system properties app. I have also added the -Dmxe.name with the server name to the WebSphere arguments.
I start the RMI Regustry JVM first.
Then the MIF JVM.
Then each of the UI JVM's.
Maximo never starts up correctly because the ports I defined for the instance are in use already. Even though as soon as I stop the JVM's they are no longer in use. I validated this with the net stat -abn
Any help or advice would be great.
RMI us great for hair loss.
Lonnie Stone
@LonStone3