IBM Support

IJ36197: BMXAA4189E HAPPENS FREQUENTLY ON PUT REQUEST FOR AN ASSET DURING A REST CALL MADE TO MAXIMO FROM CVI(CONNECTED VEHICLE INSIGHTS)

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

  • DESCRIPTION:

Maximo session gets untimely terminated while a REST session is
performed during a PUT request to /maxrest/rest.


STEPS TO REPRODUCE:

While accessing Maximo REST API from backend on CVI(Connected
Vehicle Insights) for a PUT request to /maxrest/rest
The following exceptions can be seen at the SystemOut logs of
Maximo:

Error snippet from the logs:
BMXAA4189E - Not currently connected to a server. Make sure the
server is up and running.
at psdi.util.RMISession.getMboSet(RMISession.java:433)
...
[6/7/21 22:14:49:684 UTC] 00000735 SystemOut O 07 Jun 2021
22:14:49:684 [ERROR] [MXMIF2] [CID-MXREST-358236] BMXAA4189E -
Not currently connected to a server. Make sure the server is up
and running.
...
psdi.util.MXSystemException: BMXAA4189E - Not currently
connected to a server. Make sure the server is up and running.
at psdi.util.RMISession.getMboSet(RMISession.java:433)
at com.ibm.tivoli.maximo.rest.OSResourceRequestHandler.handleFo
rmDataPost(OSResourceRequestHandler.java:413)
at com.ibm.tivoli.maximo.rest.BaseResourceRequestHandler.handle
Request(BaseResourceRequestHandler.java:336)
at com.ibm.tivoli.maximo.rest.MaximoRestServlet.invokeRequestHa
ndler(MaximoRestServlet.java:795)
at com.ibm.tivoli.maximo.rest.MaximoRestServlet.doGet(MaximoRes
tServlet.java:340)
at com.ibm.tivoli.maximo.rest.MaximoRestServlet.doPost(MaximoRe
stServlet.java:623)
at com.ibm.tivoli.maximo.rest.MaximoRestServlet.doPut(MaximoRes
tServlet.java:629)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(Servl
etWrapper.java:1235)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest
(ServletWrapper.java:779)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest
(ServletWrapper.java:478)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleReq
uest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFil
ters(WebAppFilterManager.java:1124)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.j
ava:4217)
at com.ibm.ws.webcontainer.webapp.WebAppImpl.handleRequest(WebA
ppImpl.java:2208)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGro
up.java:304)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContai
ner.java:1030)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebCo
ntainer.java:1817)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChanne
lLink.java:382)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleD
iscrimination(HttpInboundLink.java:465)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleN
ewRequest(HttpInboundLink.java:532)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.process
Request(HttpInboundLink.java:318)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.com
plete(HttpICLReadCallback.java:88)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCom
pletedCallback.complete(SSLReadServiceContext.java:1833)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.future
Completed(AioReadCompletionListener.java:175)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(Abstract
AsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(As
yncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at
com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(Result
Handler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909)
...
For this PUT request, the following message is seen at the http
access log and it returns code 400
161.156.160.152 10.144.157.131 - - [07/Jun/2021:22:14:49 +0000]
?PUT /maxrest/rest/os/iotcvasset/111176?_format=json&status=ACT
IVE&DESCRIPTION=210400399046000191&SERIALNUM=210400399046000191
&IOTCVREFRESHDATA=1HTTP/1.1" 400 102 556053 maximo-was.iot:9445



RESULT: MAXSESSION is not available for the session.


EXPECTED RESULT: MAXSESSION record should will available.


REPORTED IN VERSION:
Tivoli's process automation engine 7.6.1.2
IBM Connected Vehicle Insights - Maximo Extension 3.1.1.0

Local fix

  • N/A

Problem summary

  • ****************************************************************
* USERS AFFECTED:                                              *
* Users of Maximo REST API                                     *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* Maximo session gets untimely terminated while a REST session *
* is                                                           *
* performed during a PUT request to /maxrest/rest              *
****************************************************************
STEPS TO REPRODUCE:
While accessing Maximo REST API from backend on CVI(Connected
Vehicle Insights) for a PUT request to /maxrest/rest
The following exceptions can be seen at the SystemOut logs of
Maximo:
Error snippet from the logs:
BMXAA4189E - Not currently connected to a server. Make sure the
server is up and running.
at psdi.util.RMISession.getMboSet(RMISession.java:433)
...
[6/7/21 22:14:49:684 UTC] 00000735 SystemOut O 07 Jun 2021
22:14:49:684 [ERROR] [MXMIF2] [CID-MXREST-358236] BMXAA4189E -
Not currently connected to a server. Make sure the server is up
and running.
...
psdi.util.MXSystemException: BMXAA4189E - Not currently
connected to a server. Make sure the server is up and running.
at psdi.util.RMISession.getMboSet(RMISession.java:433)
at com.ibm.tivoli.maximo.rest.OSResourceRequestHandler.handleFo
rmDataPost(OSResourceRequestHandler.java:413)
at com.ibm.tivoli.maximo.rest.BaseResourceRequestHandler.handle
Request(BaseResourceRequestHandler.java:336)
at com.ibm.tivoli.maximo.rest.MaximoRestServlet.invokeRequestHa
ndler(MaximoRestServlet.java:795)
at com.ibm.tivoli.maximo.rest.MaximoRestServlet.doGet(MaximoRes
tServlet.java:340)
at com.ibm.tivoli.maximo.rest.MaximoRestServlet.doPost(MaximoRe
stServlet.java:623)
at com.ibm.tivoli.maximo.rest.MaximoRestServlet.doPut(MaximoRes
tServlet.java:629)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(Servl
etWrapper.java:1235)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest
(ServletWrapper.java:779)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest
(ServletWrapper.java:478)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleReq
uest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFil
ters(WebAppFilterManager.java:1124)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.j
ava:4217)
at com.ibm.ws.webcontainer.webapp.WebAppImpl.handleRequest(WebA
ppImpl.java:2208)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGro
up.java:304)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContai
ner.java:1030)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebCo
ntainer.java:1817)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChanne
lLink.java:382)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleD
iscrimination(HttpInboundLink.java:465)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleN
ewRequest(HttpInboundLink.java:532)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.process
Request(HttpInboundLink.java:318)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.com
plete(HttpICLReadCallback.java:88)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCom
pletedCallback.complete(SSLReadServiceContext.java:1833)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.future
Completed(AioReadCompletionListener.java:175)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(Abstract
AsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(As
yncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at
com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(Result
Handler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909)
...
For this PUT request, the following message is seen at the http
access log and it returns code 400
161.156.160.152 10.144.157.131 - - [07/Jun/2021:22:14:49 +0000]
?PUT /maxrest/rest/os/iotcvasset/111176?_format=json&status=ACT
IVE&DESCRIPTION=210400399046000191&SERIALNUM=210400399046000191
&IOTCVREFRESHDATA=1HTTP/1.1" 400 102 556053 maximo-was.iot:9445
RESULT: MAXSESSION is not available for the session.
EXPECTED RESULT: MAXSESSION record should will available.
REPORTED IN VERSION:
Tivoli's process automation engine 7.6.1.2
IBM Connected Vehicle Insights - Maximo Extension 3.1.1.0

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
    IJ36197
    • 

  • Reported component name
    MAXIMO ASST MGM
    • 

  • Reported component ID
    5724R46AM
    • 

  • Reported release
    761
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2021-11-18
    • 

  • Closed date
    2021-12-02
    • 

  • Last modified date
    2021-12-02
    • 





    

  • 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
    MAXIMO ASST MGM
    • 

  • Fixed component ID
    5724R46AM
    • 



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:
            

            03 December 2021
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback