Maximo Open Forum

Hi,

For Integration Scripts, I have observed that sometimes, Maximo's scripting engine doesn't reflect changes instantly.

For example, I added one raise TypeError() and it starts showing up as an exception during inbound but as soon as I comment or remove that line, I still keep getting that error for next couple of transactions. 

It is only after 2-3 attempts, it goes away and in some cases, it comes back after couple of triggers. What can be the reason behind it?
#Customizations
#Integrations
#MaximoApplicationSuite

------------------------------
Hitesh Sharma
Infosys
------------------------------

I assume your environment is clustered (IE more than one JVM)? Assuming that's the case, that is to be expected. Automation scripts (like many things in Maximo) are cached on the JVMs. When you make a change, that change is reflected immediately on the JVM that you're on but it's put into the serversession (or maxsession if you're on earlier versions that didn't have a serversession table) in the reloadcache attribute and each JVM every ~1 minute looks to see if there are caches that need to be reloaded.

Unfortunately, there's no good way to get around this. The cache is important for performance purposes and there is no way to disable it.

------------------------------
Steven Shull
IBM
------------------------------

Hi Hitesh,

As steven mentioned, there is no way out of this.

If you are trying things in non-prod clustered environment then you can try to run the following query after updating the scripts.
Delete from SERVERSESSION;

There is no issue with running this query on a non-prod environment and it might work for you.

------------------------------
Biplab Choudhury
Tata Consultancy Services
------------------------------