IBM Support

IJ20469: CAN'T START A RECORD IN WORKFLOW VIA RMI IN 7.6.1.1.

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

  • PROBLEM DESCRIPTION:
Can't start a record in Workflow via RMI in
7.6.1.1.

STEPS TO REPRODUCE:

The WFInstance and WFAssignment
classes are calling setReferencedMbo("String", Mbo) instead of
calling setReferencedMbo("String", MboRemote), so our RMI call
from outside to start Workflow results in a java
IllegalArgumentException.


RESULTS:

java.lang.IllegalArgumentException: argument type mismatch
 at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
Impl.java:90)
 at sun.reflect.DelegatingMethodAccessorImpl.invok
e(DelegatingMethodAccessorImpl.java:55)
 at
java.lang.reflect.Method.invoke(Method.java:508)
 at sun.rmi.ser
ver.UnicastServerRef.dispatch(UnicastServerRef.java:374)
 at
sun.rmi.transport.Transport$1.run(Transport.java:212)
 at
sun.rmi.transport.Transport$1.run(Transport.java:209)
 at java.s
ecurity.AccessController.doPrivileged(AccessController.java:732)

 at
sun.rmi.transport.Transport.serviceCall(Transport.java:208)
 at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.j
ava:585)
 at sun.rmi.transport.tcp.TCPTransport$ConnectionHandle
r.run0(TCPTransport.java:847)
 at sun.rmi.transport.tcp.TCPTrans
port$ConnectionHandler.lambda$run$0(TCPTransport.java:700)
 at s
un.rmi.transport.tcp.TCPTransport$ConnectionHandler$$Lambda$50.0
000000008CE33F0.run(Unknown Source)
 at java.security.AccessCont
roller.doPrivileged(AccessController.java:666)
 at sun.rmi.trans
port.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:69
9)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadP
oolExecutor.java:1160)
 at java.util.concurrent.ThreadPoolExecut
or$Worker.run(ThreadPoolExecutor.java:635)
 at
java.lang.Thread.run(Thread.java:811)
 at sun.rmi.transport.Stre
amRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:2
95)
 at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRem
oteCall.java:272)
 at
sun.rmi.server.UnicastRef.invoke(UnicastRef.java:173)
 at java.r
mi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(Remot
eObjectInvocationHandler.java:238)
 at java.rmi.server.RemoteObj
ectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:1
90)
 at com.sun.proxy.$Proxy72.setReferencedMbo(Unknown Source)

at
psdi.workflow.WFInstance.setControlledMbo(WFInstance.java:120)

at psdi.workflow.WFProcess.initiateWorkflow(WFProcess.java:738)

at psdi.workflow.virtual.InitiateWorkflowMboSet.execute(Initiate
WorkflowMboSet.java:93)

EXPECTED RESULTS:
The RMI call
should trigger the Workflow without exception.

REPORTED IN
VERSION:
Tivoli's process automation engine 7.6.1.1 Build
20190514-1348 DB Build V7611-365

Local fix

  • NA

Problem summary

  • ****************************************************************
* USERS AFFECTED:                                              *
* Maximo users who access workflow from a device using RMI.    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* Can't start a record in Workflow via RMI in 7.6.1.1.         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
RMI call from outside to start Workflow results in a java
IllegalArgumentException.

java.lang.IllegalArgumentException: argument type mismatch
 at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
Impl.java:90)
 at sun.reflect.DelegatingMethodAccessorImpl.invok
e(DelegatingMethodAccessorImpl.java:55)
 at
java.lang.reflect.Method.invoke(Method.java:508)
 at sun.rmi.ser
ver.UnicastServerRef.dispatch(UnicastServerRef.java:374)
 at
sun.rmi.transport.Transport$1.run(Transport.java:212)
 at
sun.rmi.transport.Transport$1.run(Transport.java:209)
 at java.s
ecurity.AccessController.doPrivileged(AccessController.java:732)

 at
sun.rmi.transport.Transport.serviceCall(Transport.java:208)
 at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.j
ava:585)
 at sun.rmi.transport.tcp.TCPTransport$ConnectionHandle
r.run0(TCPTransport.java:847)
 at sun.rmi.transport.tcp.TCPTrans
port$ConnectionHandler.lambda$run$0(TCPTransport.java:700)
 at s
un.rmi.transport.tcp.TCPTransport$ConnectionHandler$$Lambda$50.0
000000008CE33F0.run(Unknown Source)
 at java.security.AccessCont
roller.doPrivileged(AccessController.java:666)
 at sun.rmi.trans
port.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:69
9)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadP
oolExecutor.java:1160)
 at java.util.concurrent.ThreadPoolExecut
or$Worker.run(ThreadPoolExecutor.java:635)
 at
java.lang.Thread.run(Thread.java:811)
 at sun.rmi.transport.Stre
amRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:2
95)
 at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRem
oteCall.java:272)
 at
sun.rmi.server.UnicastRef.invoke(UnicastRef.java:173)
 at java.r
mi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(Remot
eObjectInvocationHandler.java:238)
 at java.rmi.server.RemoteObj
ectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:1
90)
 at com.sun.proxy.$Proxy72.setReferencedMbo(Unknown Source)

at
psdi.workflow.WFInstance.setControlledMbo(WFInstance.java:120)

at psdi.workflow.WFProcess.initiateWorkflow(WFProcess.java:738)

at psdi.workflow.virtual.InitiateWorkflowMboSet.execute(Initiate
WorkflowMboSet.java:93)

EXPECTED RESULTS:
The RMI call
should trigger the Workflow without exception.

REPORTED IN
VERSION:
Tivoli's process automation engine 7.6.1.1 Build
20190514-1348 DB Build V7611-365

Problem conclusion

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

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IJ20469
    • 

  • Reported component name
    INTEGRATION
    • 

  • Reported component ID
    5724R46I1
    • 

  • Reported release
    761
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2019-10-23
    • 

  • Closed date
    2020-03-03
    • 

  • Last modified date
    2020-03-03
    • 





    

  • 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


    








      
              
                            

              

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

                                                                    

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            03 March 2020
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback