Hi Sahil,
This is unlikely to be a memory issue.
It is much more likely to be something related to the records or what you are doing in the if/else blocks.
Are you changing the changing the MBOSet in a significant way e.g. deleting MBOs or changing MBOs that you were expecting to work through?
Are you triggering any other code (e.g. automation script/Java) that could be changing the records you would expect to see in the set?
Could any of the records be child records and so be being affected by operations on an earlier MBO?
Have you looked at the data in record 4 to see why it may not be listed?
Have you looked at the SystemOut/SystemErr.logs to see if there are any error messages in there?
There are unlikely to be any but it is always worth a check.
best regards,
Mark
------------------------------
Mark Robbins
Support Lead/Technical Design Authority / IBM Champion 2017 & 2018 & 2019 & 2020
Vetasi Limited
https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins/------------------------------
Original Message:
Sent: Fri May 07, 2021 02:05 AM
From: Sahil Dutta
Subject: Maximo Java Customization
Hi all I am facing one strange issue in java
I am getting the set from mxserver after doing set where and reset I got count of set let's say 7 then I am traverssing using for loop
MboSetRemote assetSet = mx.getMboSet("ASSET", userInfo);
assetSet.setWhere(my where clause)
assetSet.reset()
for (Int i= 0; (assetMbo= assetSet.getMbo(i))!= Null; i++)
{
if()
{
}
else{
}
if()
{
}
}
But when loop traverse it works fine for first 3 records it is working fine as soon as 4 the record loop mbo is coming null.
Is it because of memory issue ? Or in debugging where or how can we know that why mbo is coming null which shouldn't be null as we have 7 records in set
#Maximo
#AssetandFacilitiesManagement