Maximo

Then rebuild and redeploy ear
The problem was resolved

May be you can give it a go as well?

Thanks
May

------------------------------
May On
Tech Support
IBM

Original Message:
Sent: Mon August 02, 2021 12:18 PM
From: sandy s
Subject: Automation Scripting Error - SystemError: __getattribute__ not found on type

Hi Mark,

Thanks for your valuable inputs! Much Appreciated!

Case has already been logged with IBM.

Meanwhile, will try to add workaround of delay and seems should work.

I will let you know on the outcome.

Thanks again :).

------------------------------
sandy s

Original Message:
Sent: Mon August 02, 2021 04:11 AM
From: Mark Robbins
Subject: Automation Scripting Error - SystemError: __getattribute__ not found on type

Hi Sandy,

The best thiing would be to raise a case with IBM Support.
Reading the notes it appears there could be a "race condition" where data is still being prepared and another component tries to use that data. In that situation the second component (in your case a script) cannot access the data because it is still being prepared.

IBM will be able to advise whether the fix mentioned in your link can be deployed against your Maximo system or if it is something else.
Consider setting the autoscript logger to INFO to record details of the automation scripts that are running - this could help identify if two scripts could be processing the same records at the same time. IBM will probably want these details in the logs if you raise a case with them

You mention that it occurs with automated processes (e.g. crontasks).

You could try modifying the script to have a sleep before accessing the attributes - this may give the component preparing the data time to finish its work - even one second may make a differenceCode to add sleep
import time
sleepTimeSecs = 1
time.sleep(sleepTimeSecs)

Feel free to reach out to me privately. My contact details are in my profile

------------------------------
Mark Robbins
Support Lead/Technical Design Authority / IBM Champion 2017 & 2018 & 2019 & 2020 & 2021
Vetasi Limited
https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins/

Original Message:
Sent: Thu July 29, 2021 11:09 AM
From: sandy s
Subject: Automation Scripting Error - SystemError: __getattribute__ not found on type

Hello Experts,

Getting below error in against scripts when triggered by background job like PMWOGEN. But works fine in next run for same PM.

This has been observed in upgraded environment from 7609 to 7612. No such observation in 7609.

Error is very random against any random script on lines like get/set/count operations on MBOs. Example below. 

BMXAA3212E - Error while generating work order for PM 123456.
BMXAA7837E - An error occured that prevented the test script for the test launch point from running.
SystemError: __getattribute__ not found on type PlusGWO. See http://bugs.jython.org/issue2487 for details. in <script> at line number 7

This error is pointing to some jython bug.

Please advise.

Thanks in advance.

------------------------------
sandy s
------------------------------

Then rebuild and redeploy ear
The problem was resolved

May be you can give it a go as well?

Thanks
May

------------------------------
May On
Tech Support
IBM

Original Message:
Sent: Mon August 02, 2021 12:18 PM
From: sandy s
Subject: Automation Scripting Error - SystemError: __getattribute__ not found on type

Hi Mark,

Thanks for your valuable inputs! Much Appreciated!

Case has already been logged with IBM.

Meanwhile, will try to add workaround of delay and seems should work.

I will let you know on the outcome.

Thanks again :).

------------------------------
sandy s

Original Message:
Sent: Mon August 02, 2021 04:11 AM
From: Mark Robbins
Subject: Automation Scripting Error - SystemError: __getattribute__ not found on type

Hi Sandy,

The best thiing would be to raise a case with IBM Support.
Reading the notes it appears there could be a "race condition" where data is still being prepared and another component tries to use that data. In that situation the second component (in your case a script) cannot access the data because it is still being prepared.

IBM will be able to advise whether the fix mentioned in your link can be deployed against your Maximo system or if it is something else.
Consider setting the autoscript logger to INFO to record details of the automation scripts that are running - this could help identify if two scripts could be processing the same records at the same time. IBM will probably want these details in the logs if you raise a case with them

You mention that it occurs with automated processes (e.g. crontasks).

You could try modifying the script to have a sleep before accessing the attributes - this may give the component preparing the data time to finish its work - even one second may make a differenceCode to add sleep
import time
sleepTimeSecs = 1
time.sleep(sleepTimeSecs)

Feel free to reach out to me privately. My contact details are in my profile

------------------------------
Mark Robbins
Support Lead/Technical Design Authority / IBM Champion 2017 & 2018 & 2019 & 2020 & 2021
Vetasi Limited
https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins/

Original Message:
Sent: Thu July 29, 2021 11:09 AM
From: sandy s
Subject: Automation Scripting Error - SystemError: __getattribute__ not found on type

Hello Experts,

Getting below error in against scripts when triggered by background job like PMWOGEN. But works fine in next run for same PM.

This has been observed in upgraded environment from 7609 to 7612. No such observation in 7609.

Error is very random against any random script on lines like get/set/count operations on MBOs. Example below. 

BMXAA3212E - Error while generating work order for PM 123456.
BMXAA7837E - An error occured that prevented the test script for the test launch point from running.
SystemError: __getattribute__ not found on type PlusGWO. See http://bugs.jython.org/issue2487 for details. in <script> at line number 7

This error is pointing to some jython bug.

Please advise.

Thanks in advance.

------------------------------
sandy s
------------------------------

Then rebuild and redeploy ear
The problem was resolved

May be you can give it a go as well?

Thanks
May

------------------------------
May On
Tech Support
IBM

Original Message:
Sent: Mon August 02, 2021 12:18 PM
From: sandy s
Subject: Automation Scripting Error - SystemError: __getattribute__ not found on type

Hi Mark,

Thanks for your valuable inputs! Much Appreciated!

Case has already been logged with IBM.

Meanwhile, will try to add workaround of delay and seems should work.

I will let you know on the outcome.

Thanks again :).

------------------------------
sandy s

Original Message:
Sent: Mon August 02, 2021 04:11 AM
From: Mark Robbins
Subject: Automation Scripting Error - SystemError: __getattribute__ not found on type

Hi Sandy,

The best thiing would be to raise a case with IBM Support.
Reading the notes it appears there could be a "race condition" where data is still being prepared and another component tries to use that data. In that situation the second component (in your case a script) cannot access the data because it is still being prepared.

IBM will be able to advise whether the fix mentioned in your link can be deployed against your Maximo system or if it is something else.
Consider setting the autoscript logger to INFO to record details of the automation scripts that are running - this could help identify if two scripts could be processing the same records at the same time. IBM will probably want these details in the logs if you raise a case with them

You mention that it occurs with automated processes (e.g. crontasks).

You could try modifying the script to have a sleep before accessing the attributes - this may give the component preparing the data time to finish its work - even one second may make a differenceCode to add sleep
import time
sleepTimeSecs = 1
time.sleep(sleepTimeSecs)

Feel free to reach out to me privately. My contact details are in my profile

------------------------------
Mark Robbins
Support Lead/Technical Design Authority / IBM Champion 2017 & 2018 & 2019 & 2020 & 2021
Vetasi Limited
https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins/

Original Message:
Sent: Thu July 29, 2021 11:09 AM
From: sandy s
Subject: Automation Scripting Error - SystemError: __getattribute__ not found on type

Hello Experts,

Getting below error in against scripts when triggered by background job like PMWOGEN. But works fine in next run for same PM.

This has been observed in upgraded environment from 7609 to 7612. No such observation in 7609.

Error is very random against any random script on lines like get/set/count operations on MBOs. Example below. 

BMXAA3212E - Error while generating work order for PM 123456.
BMXAA7837E - An error occured that prevented the test script for the test launch point from running.
SystemError: __getattribute__ not found on type PlusGWO. See http://bugs.jython.org/issue2487 for details. in <script> at line number 7

This error is pointing to some jython bug.

Please advise.

Thanks in advance.

------------------------------
sandy s
------------------------------

Then rebuild and redeploy ear
The problem was resolved

May be you can give it a go as well?

Thanks
May

------------------------------
May On
Tech Support
IBM

Original Message:
Sent: Mon August 02, 2021 12:18 PM
From: sandy s
Subject: Automation Scripting Error - SystemError: __getattribute__ not found on type

Hi Mark,

Thanks for your valuable inputs! Much Appreciated!

Case has already been logged with IBM.

Meanwhile, will try to add workaround of delay and seems should work.

I will let you know on the outcome.

Thanks again :).

------------------------------
sandy s

Original Message:
Sent: Mon August 02, 2021 04:11 AM
From: Mark Robbins
Subject: Automation Scripting Error - SystemError: __getattribute__ not found on type

Hi Sandy,

The best thiing would be to raise a case with IBM Support.
Reading the notes it appears there could be a "race condition" where data is still being prepared and another component tries to use that data. In that situation the second component (in your case a script) cannot access the data because it is still being prepared.

IBM will be able to advise whether the fix mentioned in your link can be deployed against your Maximo system or if it is something else.
Consider setting the autoscript logger to INFO to record details of the automation scripts that are running - this could help identify if two scripts could be processing the same records at the same time. IBM will probably want these details in the logs if you raise a case with them

You mention that it occurs with automated processes (e.g. crontasks).

You could try modifying the script to have a sleep before accessing the attributes - this may give the component preparing the data time to finish its work - even one second may make a differenceCode to add sleep
import time
sleepTimeSecs = 1
time.sleep(sleepTimeSecs)

Feel free to reach out to me privately. My contact details are in my profile

------------------------------
Mark Robbins
Support Lead/Technical Design Authority / IBM Champion 2017 & 2018 & 2019 & 2020 & 2021
Vetasi Limited
https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins/

Original Message:
Sent: Thu July 29, 2021 11:09 AM
From: sandy s
Subject: Automation Scripting Error - SystemError: __getattribute__ not found on type

Hello Experts,

Getting below error in against scripts when triggered by background job like PMWOGEN. But works fine in next run for same PM.

This has been observed in upgraded environment from 7609 to 7612. No such observation in 7609.

Error is very random against any random script on lines like get/set/count operations on MBOs. Example below. 

BMXAA3212E - Error while generating work order for PM 123456.
BMXAA7837E - An error occured that prevented the test script for the test launch point from running.
SystemError: __getattribute__ not found on type PlusGWO. See http://bugs.jython.org/issue2487 for details. in <script> at line number 7

This error is pointing to some jython bug.

Please advise.

Thanks in advance.

------------------------------
sandy s
------------------------------