IBM Support

IJ37569: MAXIMO INTEGRATION FRAMEWORK RETURNS NULL POINTER WHEN IMPORTING NEW ATTACHMENT USING UNC PATH.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Abstract
Maximo Integration Framework returns Null Pointer when importing
new attachment using UNC path.

STEPS TO REPRODUCE:

The steps below uses MAXDEMO as example.

Prerequirement: Configure the doclink attachment folder in UNC
path.

1)Create an Object Structure(MXWOATT) using WORKORDER and
DOCLINKS, using DOCLINKS relationship.

Enable the Flat Structure.

Fix Alias conflict.

2)Create a new Enterprise Service(MXWOATT) using the Object
Structure of the step 1.

3)Add the Enterprise Service in the EXTSYS1 External System.

4)Manually create a test.jpg file in DOCLINKS\ATTACHMENTS folder
in the remote host responsible to administrate attachments.

5)Import the flat file below:

EXTSYS1,MXWOATT,AddChange,
WONUM,SITEID,ADDINFO,COPYLINKTOWO,DOCTYPE,DOCUMENT,UPLOAD,NEWUR
LNAME,URLNAME,URLTYPE,OWNERTABLE
1116,BEDFORD,1,0,Attachments,test.jpg,1,\\REMOTE_HOST\DOCLINKS\
ATTACHMENTS\test.jpg,\\REMOTE_HOST\ATTACHMENTS\test.jpg,FILE,WO
RKORDER

RESULTS:

Null Pointer.

java.lang.NullPointerException
at psdi.iface.mos.MosProcessImpl.checkDocumnetMaxSize(MosProces
sImpl.java:2875)
at psdi.iface.mos.MosProcessImpl.setAttachments(MosProcessImpl.
java:2809)
at psdi.iface.mos.MosProcessImpl.setAdditionalTableData(MosProc
essImpl.java:1713)
at psdi.iface.mos.MosProcessImpl.createChildrens(MosProcessImpl
.java:986)
at psdi.iface.mos.MosProcessImpl.fillMaximoTables(MosProcessImp
l.java:823)
at psdi.iface.mos.MosProcessImpl.processExternalData(MosProcess
Impl.java:356)
at
psdi.iface.mic.MicSetIn.processExternalData(MicSetIn.java:149)
at psdi.iface.mic.EntMicService.processDataIn(EntMicService.jav
a:1439)
at psdi.iface.mic.EntMicService.processExternalData(EntMicServi
ce.java:1335)
at psdi.iface.jms.QueueToMaximoProcessor.processMessage(QueueTo
MaximoProcessor.java:129)
at psdi.iface.jms.JMSContQueueProcessor.processMessage(JMSContQ
ueueProcessor.java:227)
at psdi.iface.jms.JMSListenerBean.onMessage(JMSListenerBean.jav
a:203)
at psdi.iface.jms.MDBProxyJMSContQueueProcessor_1_5bf7eeaa.onMe
ssage(MDBProxyJMSContQueueProcessor_1_5bf7eeaa.java)
at com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl.invo
keEndpoint(JmsJcaEndpointInvokerImpl.java:258)
at com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch(SibR
aDispatcher.java:919)
at com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener$Si
bRaWork.run(SibRaSingleProcessListener.java:597)
at
com.ibm.ejs.j2c.work.WorkProxy$RunWork.run(WorkProxy.java:282)
at java.security.AccessController.doPrivileged(AccessController
.java:704)
at javax.security.auth.Subject.doAs(Subject.java:490)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.jav
a:133)
at
com.ibm.ejs.j2c.work.WorkProxy$RunWork.run(WorkProxy.java:285)
at com.ibm.ws.security.util.AccessController.doPrivileged(Acces
sController.java:63)
at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:667)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909)

EXPECTED RESULTS:

Import should work without errors.

REPORTED IN VERSION:

Tivoli's process automation engine 7.6.1.2

Local fix

  • NA

Problem summary

  • ****************************************************************
* USERS AFFECTED:                                              *
* Maximo MIF users                                             *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* Maximo Integration Framework returns Null Pointer when       *
* importing                                                    *
* new attachment using UNC path.                               *
****************************************************************
STEPS TO REPRODUCE:
The steps below uses MAXDEMO as example.
Prerequirement: Configure the doclink attachment folder in UNC
path.
1)Create an Object Structure(MXWOATT) using WORKORDER and
DOCLINKS, using DOCLINKS relationship.
Enable the Flat Structure.
Fix Alias conflict.
2)Create a new Enterprise Service(MXWOATT) using the Object
Structure of the step 1.
3)Add the Enterprise Service in the EXTSYS1 External System.
4)Manually create a test.jpg file in DOCLINKS\ATTACHMENTS
folder
in the remote host responsible to administrate attachments.
5)Import the flat file below:
EXTSYS1,MXWOATT,AddChange,
WONUM,SITEID,ADDINFO,COPYLINKTOWO,DOCTYPE,DOCUMENT,UPLOAD,NEWUR
LNAME,URLNAME,URLTYPE,OWNERTABLE
1116,BEDFORD,1,0,Attachments,test.jpg,1,\\REMOTE_HOST\DOCLINKS\
ATTACHMENTS\test.jpg,\\REMOTE_HOST\ATTACHMENTS\test.jpg,FILE,WO
RKORDER
RESULTS:
Null Pointer.
java.lang.NullPointerException
at
psdi.iface.mos.MosProcessImpl.checkDocumnetMaxSize(MosProcessImp
l.java:2875)
at
psdi.iface.mos.MosProcessImpl.setAttachments(MosProcessImpl.java
:2809)
at
psdi.iface.mos.MosProcessImpl.setAdditionalTableData(MosProcessI
mpl.java:1713)
at
psdi.iface.mos.MosProcessImpl.createChildrens(MosProcessImpl.jav
a:986)
at
psdi.iface.mos.MosProcessImpl.fillMaximoTables(MosProcessImpl.ja
va:823)
at
psdi.iface.mos.MosProcessImpl.processExternalData(MosProcessImpl
.java:356)
at
psdi.iface.mic.MicSetIn.processExternalData(MicSetIn.java:149)
at
psdi.iface.mic.EntMicService.processDataIn(EntMicService.java:14
39)
at
psdi.iface.mic.EntMicService.processExternalData(EntMicService.j
ava:1335)
at
psdi.iface.jms.QueueToMaximoProcessor.processMessage(QueueToMaxi
moProcessor.java:129)
at
psdi.iface.jms.JMSContQueueProcessor.processMessage(JMSContQueue
Processor.java:227)
at
psdi.iface.jms.JMSListenerBean.onMessage(JMSListenerBean.java:20
3)
at
psdi.iface.jms.MDBProxyJMSContQueueProcessor_1_5bf7eeaa.onMessag
e(MDBProxyJMSContQueueProcessor_1_5bf7eeaa.java)
at
com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl.invokeEn
dpoint(JmsJcaEndpointInvokerImpl.java:258)
at
com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch(SibRaDis
patcher.java:919)
at
com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener$SibRaW
ork.run(SibRaSingleProcessListener.java:597)
at
com.ibm.ejs.j2c.work.WorkProxy$RunWork.run(WorkProxy.java:282)
at
java.security.AccessController.doPrivileged(AccessController.jav
a:704)
at javax.security.auth.Subject.doAs(Subject.java:490)
at
com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:13
3)
at
com.ibm.ejs.j2c.work.WorkProxy$RunWork.run(WorkProxy.java:285)
at
com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon
troller.java:63)
at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:667)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909)

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
package:
Release 7.6.1.3 of Base Services

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IJ37569
    • 

  • Reported component name
    INTEGRATION
    • 

  • Reported component ID
    5724R46I1
    • 

  • Reported release
    761
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2022-02-01
    • 

  • Closed date
    2022-02-09
    • 

  • Last modified date
    2022-02-09
    • 





    

  • APAR is sysrouted FROM one or more of the following:
    

    • 

  • APAR is sysrouted TO one or more of the following:
    

    • 



Fix information


    

  • Fixed component name
    INTEGRATION
    • 

  • Fixed component ID
    5724R46I1
    • 



Applicable component levels


    








      
              
                            

              

              [{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761"}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            10 February 2022
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback